Does any of this sound familiar?
The details are right. Just not everywhere at once.
Again, two is enough.
- A price changed, and somewhere the old one is still showing.
- Which place holds the authoritative product detail is a matter of opinion.
- Launching a product means doing the same work again, once per channel.
- Availability is updated afterwards rather than carried along, and sometimes too late.
- After an order there is a chain of forwards and shouted questions.
- Nobody can say what is selling where without asking somebody.
Honestly
This is rarely a shop problem.
It is a question-of-ownership problem. Until it is settled which place leads for a product detail, every integration just moves the contradiction somewhere new and harder to see.
Making that decision costs one conversation. Avoiding it costs continuously.
What we build
One place that leads, and channels that follow it.
Product detail in one place
A place that is authoritative even while several systems stay in use. Leading does not mean only.
Changes that arrive
A price or description change is made once and travels to where it is needed, instead of waiting in somebody's task list.
State you can see
Availability, status and disagreements presented so that a wrong detail is noticed before a customer finds it.
After the order
The path from order to done as one process with a visible state, rather than a chain of individual handoffs.
Product and commerce operations:
- Data
- Content
- Assets
- Product record
- Channels
Where people stay involved
Prices and promises stay your decision.
A system may distribute details and report contradictions. What something costs, what is promised and when an exception is made belongs to people who know the customer and the margin. Automatic price changes without a release are exactly the kind of convenience that ends up expensive.