One order. One set of records.
A customer buys something. That single fact should not have three different versions depending on where it happened.
Order 4821
Two repair kits · collect tomorrow, 10:00
- StockReserved from Bay 2
- FulfilmentPicked for collection
- AccountsInvoice raised
Illustrative example · one order, one set of records
The situation
Selling happens in more than one place: a storefront, a counter, a phone call, a marketplace, sometimes an assistant acting for the customer. Each channel arrives with its own vendor, its own idea of a product, and its own export format, and the organization spends its energy making them agree.
How this usually goes
The online catalog and the counter disagree about price and availability.
Stock is accurate twice a day, briefly, after a sync.
A refund is easy in one channel and a manual process in another.
Customer history is split by where the customer happened to buy, which the customer experiences as being unrecognized.
What happens here
An order placed online, in person, or by an agent lands in the same records, with stock, pricing, fulfilment, and accounting seeing the same event.
1. The product is defined once
Catalog, variants, pricing rules, taxonomy, and media are one definition that every channel renders, rather than a definition per channel that someone keeps in step.
2. Channels are surfaces, not systems
A storefront, a counter interface, and a conversational surface are different ways into the same records, composed from the same shared parts.
3. The order is an event before it is a screen
Placing it publishes one fact, which stock, fulfilment, accounting, and support each act on independently. None of them needs an integration with the channel it came from.
4. Promises are checked against reality
Availability, delivery windows, and incentives are evaluated against the same stock and pricing records the back office uses, so a promise made to a customer is one the organization can keep.
5. The customer is one person
History, preferences, and entitlements follow the person across channels, held as the organization's record of a relationship rather than as a vendor's audience segment.
What the organization keeps
The customer relationship stays with the organization, not with whichever platform hosted the transaction. Changing a storefront becomes a front-end decision instead of a migration, and the sales history is portable because it was never trapped inside a channel.