This analysis is part of starting-state fidelity, which rebuilds an order at 10:42, the minute a customer asked to cut gloves from 200 cartons to 120 after 150 had already shipped. The job here is to compare what a review expects with what distributors usually keep, and to give honest wording for the difference.
What a rebuild of the 10:42 state requires
A reviewer must reconstruct the order as it stood at the request's received time, then judge the response against that state. Every row below supplies one piece of the reconstruction.
| Evidence | Piece of the starting state | Why it matters |
|---|---|---|
| Field change history with old values | The quantities before anyone edited them | Shows the order said 200, not 150, when the request came |
| Timed pick and shipment events | What had left the warehouse, and when | Places the 08:15 shipment before 10:42 |
| Request received time, on the order | When the task began | Fixes the moment to rebuild |
| Approval records with role | Who was allowed to offer what | Shows whether a return offer was within authority |
| Returns linked to the original line | How the case ended | Gives the response a checkable outcome |
AI developers treat this as basic hygiene for their own simulations. Toloka's agent data page (checked 2026-10-18) lists versioned environments, deterministic resets and audit logs for reproducing agent runs exactly, and τ-bench keeps a hidden database state that changes only through tool calls. A business archive that can supply the same five pieces is offering a starting state real enough to test against.
Expected against usually kept
The pattern below reflects common distribution practice, not measured data.
| Gap | How it appears in the order case | Usually kept | Usually missing | Metadata question |
|---|---|---|---|---|
| Overwritten fields | Line edited from 200 to 150 with no log | Current quantity | Old value, editor and edit time | "Does the order system log field changes with user and time?" |
| Untimed events | Shipment 1 dated, not timed | Shipment date | Time of day | "Are pick and shipment events stored with timestamps?" |
| Context outside the system | Request lived in a buyer's inbox | The edited order | The request and its received time | "Are change requests attached to the order with their received time?" |
| Unrecorded authority | Return offered with no reason code | The return authorization | Who approved it, under what limit | "Do returns and credits record who approved them?" |
| Open outcome | 30 cartons returned a month later under a new number | Two separate records | The link between them | "Are returns linked to the original order line?" |
Why the overwritten-field gap is so damaging: order systems restrict edits by state. Shopify's help center, for example, says merchants can edit unfulfilled items but cannot remove fulfilled items or change their quantity. The right response depends on that state at 10:42, and an overwritten quantity erases it. Change logging is often a setting rather than a default; Microsoft Learn describes Business Central's change log as recording old and new values for the tables and fields a company chooses and activates.
Illustrative gap profile: a 290-person electrical wholesaler
Fictional company, invented shares. Each figure is how many of every ten change requests from the last three years have that evidence, as an operations lead might estimate.
| Evidence | Kept, out of 10 | What is missing | What it hides |
|---|---|---|---|
| Field change history | 3 | Order-line logging switched on only last year | Original quantities on older orders |
| Timed shipment events | 8 | Will-call pickups recorded by date | Whether a pickup came before the request |
| Request received time | 2 | Requests handled by phone or personal email | When most tasks began |
| Approval records | 5 | Credits approved verbally by branch managers | Whether offers were within authority |
| Return linkage | 4 | Returns booked under new numbers | How the case ended |
The warehouse system does its part: 8 in 10 shipments are timed. The order desk is weaker, and the request row is the binding constraint. With 2 in 10 requests timed, most cases have a known end but no known start, so the usable set is the recent fifth where request, shipments and edits all carry times.
How each gap distorts the case
- An overwritten field makes the outcome look like the request. A line reading 150 suggests the customer asked for 150.
- An untimed event makes the order of events a guess. A shipment dated the same day as the request could fall on either side of it.
- A request outside the system removes the start of the task entirely.
- Unrecorded authority keeps the action but hides whether it was allowed, so a correct offer and an overreach look alike.
- An open outcome leaves the response ungraded, because nobody can see whether the 30 returned cartons closed it.
Real partial-shipment cases with these details intact are hard to invent, which is part of the argument in synthetic versus real data for AI agents, and of why buyers want licensed data. Adjacent fulfillment checks are in the guide on fulfillment records with documented operational decisions.
Wording the gap in an introduction
One sentence per gap, naming the window that is complete:
- "Shipments are timed for three years; will-call pickups are dated only."
- "Order-line edit history has been logged since last year."
- "Change requests are attached to orders only when they arrive through the portal."
Avoid "the ERP has everything" (overwritten fields usually say otherwise), "we can rebuild any order" (untested) and "we have backups" (a nightly snapshot does not show the state at 10:42). Stay with metadata: systems, years, counts, owners.
Eligibility first: 50 or more full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. The starting-state fidelity scorecard turns these answers into a fit rating, and the starting-state fidelity review packet shows what the company prepares next. More record families are under data types.
Next step
Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If the operations lead can name a window where requests, shipments and order edits all carry times, register as a partner, check the company against who qualifies and read the terms, then introduce the decision-maker with that window and the gaps stated plainly.