Otto Market
Purpose
Otto Market becomes a sales channel. Otto is not a shop but a marketplace with catalogue sovereignty: an item is proposed and reviewed by Otto.
Scope
- Item proposal — creation is asynchronous.
- Price and quantity through their own endpoints, not through item creation. That is the norm for
marketplaces and the reason the channel framework knows three separate operations instead of one „catalogue push".
- Orders and fulfilment.
- Two settings per channel: brand name and product category.
Interplay
The channel is a sales channel in the sense of Channels — not a special path beside the document. Items, prices and stock come from the product catalogue and stock; incoming orders become regular sales orders and travel through warehouse, shipping and invoicing like any other order. Credentials live as an integration under Integrations in the encrypted store. Flows and mappings at the system boundary — which field goes where, when a sync runs — belong to OctiConnect; conditions and waiting times remain the business of automations.
Limits
- „Accepted" means „accepted for review", not „online". The framework is told exactly that — a
reported success that is in truth a queue would be the worse answer.
- The real run is still outstanding. What is verified is that we ask correctly and read the
answer correctly — not that Otto accepts the request. A real seller account is missing.