Customer and authentication
Account linkage and session, so a signed-in shopper is the same person on both storefronts. The account itself stays in your systems.
Reference in progress
Covers:
Account linkage, session, identity
A shopper who is signed in on your store should be recognised on the Neomi storefront, without a second account to manage.
What Neomi reads
Account linkage, so an existing customer is matched to their record.
Session handling between the two storefronts.
Whatever identifier your systems already use to recognise a customer.
What stays in your systems
The customer account lives in your systems. Neomi does not create a competing customer database, and the customer relationship stays yours.
How to connect
How the hand-off works depends on what your identity layer supports today. This is usually the shortest conversation of the integration.
Agree the scope of this domain and the locations it applies to.
Expose the interface, or point us at the one you already run.
We validate against a non-production environment before anything goes live.
Data expectations
Documentation in progress. Our engineering team publishes this section with the reference.
Errors and edge cases
Documentation in progress. Our engineering team publishes this section with the reference.
Reference
The endpoint reference for this module is published here when it is finished. Until then, nothing on this page describes a specific interface, because we would rather leave it blank than have you build against something that changes.