Orders
Understand how paid consumer orders become safe, idempotent seller orders.
Orders
Orders connect a paid consumer purchase at the origin merchant to one or more
seller orders in the SKUU network.
Two directions
| Flow | Direction | Purpose |
|---|---|---|
| Consumer order | Your platform to SKUU | Report a paid order and its fulfilment allocation |
| Seller order | SKUU to your platform | Create a paid, ship-only order for the selected seller |
Consumer order flow
The origin platform sends one signed event after payment succeeds. The event
contains the original order, delivery address and all lines. SKUU acts only on
lines allocated to the agreed virtual SKUU_Network location.
The origin platform keeps ownership of its native order and customer
relationship.
Seller order flow
SKUU groups routed lines by seller and asks the selected platform to create one
paid, ship-only order. The seller resolves each line through the stable
variant_id supplied by Products and returns its own stable order ID.
The request identity is also its idempotency key. An exact retry returns the
same result and never creates a second order. A reused identity with different
data is rejected.
Orders created by SKUU are marked as network shipper orders and are not sent
back into the consumer-order flow.
Testing the flow
In TESTING, both teams prove one consumer event, one seller order, one exact
retry and one conflicting retry. The result must be one seller order with a
stable response and no loop back to SKUU.
Technical reference
- Deliver a signed Connect event
defines the exactorder.createdevent. - Create a paid shipper order
defines the exact customer endpoint.
Updated 12 days ago
