Workflow comparison

Order rows or the history of resolving fulfillment exceptions

Map order exceptions, stock changes, customer communications, fulfillment and credits into a record collection with explicit order-line relationships.

What to look for

An order table can show fulfilled even when the team substituted an item, split a shipment or issued a credit. An exception-to-fulfillment collection preserves those intermediate events. Compare the final order state with the records explaining what changed, which line it affected and how the request was resolved.

Follow the affected order line

Fictional order O-52 contains lines L-1 and L-2. A stock exception affects L-2. A customer message approves a substitute, shipment SH-3 sends L-1, and shipment SH-4 sends the substitute. Credit CR-9 adjusts the price difference. The order-level status alone does not describe that sequence.

Use the order-line reference wherever possible. If an exception is recorded only at order level, state that limitation rather than assigning it to a particular item from memory.

GroupReference to inspectQuestion answered
OrderO-52 and line IDWhat was originally ordered?
Stock exceptionAffected line or item referenceWhat could not proceed?
Customer responseOrder/line and message referenceWhich change was agreed?
FulfillmentShipment and order-line referenceWhat was actually sent?
CreditInvoice or line referenceWhat billing adjustment followed?

Separate stock state from the exception event

A current inventory balance does not show what was available when the order was placed. An adjustment history may explain later changes but still require an explicit link to the order. Keep the stock snapshot, movement records and order exception as separate groups.

Likewise, a substitute product can appear as a new line or as an edit to an existing line. Inspect the recorded behavior. If earlier line values were overwritten, the final table may not preserve the original request.

Check partial fulfillment and cancellation

Inspect one split shipment and one canceled line. Record whether each shipment retains the original line reference, whether canceled lines survive and whether refund or credit records link to the relevant invoice. A label such as completed can conceal several different outcomes.

Write the inventory at the right level

The most useful unit may be an order line rather than an entire customer order. Include event dates and the meaning of each status. Keep entered date, scheduled date and actual shipment date distinct if the records provide them.

  • Order and persistent line identities
  • Exception type and affected quantity
  • Recorded approval or response
  • Shipment-to-line references
  • Credits, refunds and cancellation records
  • History of changed line values

Keep returns separate from initial fulfillment

A return happens after an earlier shipment and can have its own authorization, receipt and refund records. Preserve the original order-line reference and the return identity. Otherwise a final net quantity can conceal both the original fulfillment and the later reversal.

Use a source-backed scope question

Mercor’s retail examples name order and inventory records. That supports asking about this collection, while the specific substitution, split-shipment and credit structure remains for review. Describe what you have checked rather than treating the industry example as approval of all associated records.

Sources: Mercor

Questions about this comparison

Does fulfilled mean every original item was shipped?

Not necessarily. Inspect line quantities, substitutions and shipment records before describing the outcome.

Can we use the current stock balance as order history?

A current balance describes current state. Historical movements and order exceptions need separate evidence.

What if credits are recorded in another system?

Add that group to the inventory and identify the invoice or line reference linking it to the order.

Sources

  1. Mercor program pageMercor · Checked 2026-10-06