Order history summary
How past orders are summarized for reordering and personalization.
Purchase history is what turns a reorder from a search into a sentence. It is also the largest, least structured payload in the integration, so it is summarized rather than used raw.
What the summary contains
The most recent order, with its date, how long ago it was, and how many items it held.
A per-product view keyed by your identifier, carrying the product name and the dates it was bought.
Enough of a cadence signal to tell a weekly staple from a one-off purchase.
Why a summary
Raw order history is too large and too noisy to be useful at the moment a shopper is assembling a cart. Compacting it first is what makes reorder suggestions fast rather than merely possible.
Optional by design
Everything else works without this module. It improves the experience rather than enabling it, which makes it a reasonable second-phase addition.
Note on this page
Described from the current implementation rather than from a published contract. Field names and shapes are what Neomi normalizes to today; our engineering team confirms the public naming when the reference is finalized.