Loyalty and purchase history

Optional, and worth doing when you can. Where Neomi can see what a household has bought before, reordering becomes a sentence instead of a search.

What Neomi reads

• Order history, where you expose it.

• Stated preferences, where you hold them.

• Loyalty identifiers, if loyalty pricing affects what the shopper sees.

What stays in your systems

Purchase history is customer data and it stays yours. Access is scoped to personalising the shopping session and nothing else.

How to connect

Everything else works without this module. It improves the experience rather than enabling it, so it is a reasonable thing to add in a second phase.

• 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.