Go live
SKUU switches each capability on per shop and per environment after the store and SKUU have tested it together. The environment sheet says what is on.
The order
- Products come first: SKUU reads the whole catalogue and accepts it only when every page validates, and SKUU starts linking the store's products to the network after that.
- Inventory comes next: the store sends
inventory.updated; SKUU writesSKUU_Network. Proven with a replay and a restore to zero. - Then Orders and Fulfilment: a paid order becomes a shipping order; a shipped package sends tracking back. First in dry run, where SKUU builds and logs the request without sending it, then live.
- Then Cancellation: one
order.cancelledfor a seller order before anything shipped, with a confirmedPOST /cancelat the custom shipping shop. Also prove a duplicate receipt and an already-shipped409. - Finally Returns: one
return.createdfor a shipping order received back, and onePOST /returnson the store's own order, replayed once without creating a duplicate.
Each step ends with both sides saying "done" in writing, and an email is enough for that.
What each test proves
Checks per capability
| Capability | Checks |
|---|---|
| Products | A complete run, stable cursors, stable ids, images resolve, a variant left out of a full run is retired |
| Inventory | Signature accepted, exact replay is a no-op, an older event is ignored, the SKUU_Network write and its echo match, restore to zero |
| Orders | Unpaid orders rejected, correct shipping order, required receipt fields, replay returns the same order, unknown order handled |
| Fulfilment | Tracking reaches the order once, replay is a no-op |
| Cancellation | Whole order stopped before shipment, stock released, event acknowledged |
| Returns | Return stored from the store's event, POST /returns creates one return on the store's own order, replay does not duplicate |
A paid order that reaches SKUU is routed and shipped. To stop it before shipment, send order.cancelled for the whole order; see Cancellation. For an address change, contact SKUU straight away.
After sign-off
SKUU opens the capability for the store's test shop. Recurring traffic and production open after a separate written sign-off, and production starts with the same dry-run step. Before each joint session SKUU checks its own side: schema, access, the store's baseline data, and that every switch that should be off still is.
Use Checklist when reviewing the implementation.
Updated 22 days ago