Playbooks/ Dernière mise à jour: 2026-10-29

Playbook: a status says shipped, but nothing left the building

The situation

An order is marked shipped. Nobody picked it, nobody packed it, no carrier has it. The status was forced to clear a queue, and from that moment the order counts as revenue, the customer expects a parcel, and every report says the work is done.

This is not rare. In the demo workspace Otiox checked 31 recent claims: 7 were supported by the records behind them, 24 were contradicted or had no evidence at all.

Before you start

  • The check covers *shipped*, *delivered*, *received*, *completed* and *paid* on customer orders, purchase orders, manufacturing orders and invoices, over the last 30, 90 or 180 days.
  • Command only reads. You correct the record on its own page.

Step 1 — See which statuses do not hold up

Open Command → Claims & Consistency.

Claims & Consistency: statuses checked against the records behind them
Claims & Consistency: statuses checked against the records behind them

What you see: one card per claim, grouped by record, with the verdict and the reason it fails:

  • order 7b3eae92: *Contradicted, shipped*. No shipped box and no shipment.
  • SO-PRED-Q1/Q2/Q3: *Contradicted, delivered*. No box, no shipment, no delivery confirmation from the carrier.
  • purchase orders marked received with no goods receipt, manufacturing orders completed with nothing received into stock, invoices paid with no payment linked.

Each verdict is marked *Fact*: it follows from the records, not from a model.

Step 2 — Verify the record itself

Open the order and choose the Verify tab.

The order's Verify tab: Contradicted, shipped, no shipped box and no shipment
The order's Verify tab: Contradicted, shipped, no shipped box and no shipment

What you see: the claim (*shipped*), the verdict (*Contradicted*) and the evidence against it. Otiox models how records depend on each other (an order, its boxes, its shipment, the carrier event), so it knows what *must* exist for the status to be true.

Step 3 — See who changed it, and when

Choose the Timeline tab.

Timeline: created at 09:29, switched from pending to shipped two minutes later, nothing packed in between
Timeline: created at 09:29, switched from pending to shipped two minutes later, nothing packed in between

What you see: the order was created on 12 October at 09:29. At 09:31 the status changed from *pending* to *shipped*, by a named user, recorded in the order log and by change capture. Between the two there is no pick, no box and no shipment.

This is the conversation to have: not *the system says shipped*, but *who clicked it and why*.

Step 4 — Correct it and make it a rule

Fix the order on its own page: pick, pack and ship it, or put it back to processing. Then choose Make this a rule. In the demo the rule *Shipment behind every “shipped”* already runs in Monitor and lists six orders today; move it to Warn to show the problem on the order itself, or to Block to refuse the status change without a shipment.

After: the next check shows the claim as supported, or the order back in processing, and the rule keeps watching every future status.

What you have at the end

  • Every *done* status backed by evidence, or flagged.
  • The reason for each contradiction and the person who made the change.
  • A rule that stops the same shortcut next time.
Screenshots come from the Otiox demo workspace. Choose Switch to demo in the sidebar to follow along; changes there never touch live data. Command reads your records and never changes them.