This before-and-after reading is part of the promotion-to-service-recovery guide. It takes one Illustrative day at one branch and reads it twice: first as the sales file alone, then with its neighboring records restored.
Before: Sunday as the sales file tells it
Illustrative. A fictional 35-branch pet supplies chain, branch 9. The branch manager marks down aquarium starter kits from 11:00 on a Sunday, a local decision that head office does not see. Here is what a reviewer handed only the point-of-sale export would read.
| Hour | Sales | Starter kit markdown used | Manual price changes |
|---|---|---|---|
| 10:00 | 28 | 0 | 0 |
| 11:00 | 44 | 15 | 0 |
| 12:00 | 72 | 41 | 0 |
| 13:00 | 76 | 47 | 1 |
| 14:00 | 63 | 35 | 11 |
| 15:00 | 39 | 18 | 2 |
On its own, this reads as a win. A branch-level markdown went live at 11:00, sales almost tripled within two hours, and the kits kept moving into mid-afternoon. A merchandiser would recommend rolling the markdown out to every branch. The one loose thread is the jump in manual price changes at 14:00, which the file cannot explain. They might be damaged packaging, price matches or staff purchases.
Nothing in the table is false. It is partial, and the missing part steers the reader toward the wrong call.
After: the same Sunday with scheduling and service desk records beside it
Now line up the other two sources hour by hour, matched on branch and time.
| Hour | Point of sale | Scheduling tool | Service desk log |
|---|---|---|---|
| 10:00 | 28 sales | Planned for about 40 sales an hour | Nothing logged |
| 11:00 | 44 sales, markdown begins | No change | Nothing logged |
| 12:00 | 72 sales | Three team members moved from replenishment at 12:10 | First complaints about the wait |
| 13:00 | 76 sales, 1 price change | Moved staff still on tills | Further wait complaints |
| 14:00 | 63 sales, 11 price changes | Plan and change both kept in the edit log | Store credit, keyed at the till, offered to those who waited |
| 15:00 | 39 sales | Staff return to replenishment | Last complaint closed |
The meaning flips. Branch 9 had planned for about 40 sales an hour and ran far beyond it from 12:00 to 14:00. The manager reacted at 12:10, but only by stripping the stockroom, so shelves emptied while the line shrank. Shoppers complained, and from 14:00 the branch offered store credit. The unexplained price changes in the sales file are that remedy, keyed by hand at the till.
The right lesson is not "roll the markdown out everywhere". It is "branch-level promotions need a staffing trigger", and only the combined record supports it. That gap between what one source shows and what the connected history explains is why missing context matters for AI training and evaluation, and why agents trained on partial records fail in predictable ways.
What goes missing, and where it actually lives
Each lost piece has a home. The table below is the evidence asset a partner can use in a first conversation: it names the context, the system that holds it and the person who can say whether it still exists.
| Context lost in a sales-only export | Why a reader needs it | Where it lives | Who can confirm it exists |
|---|---|---|---|
| The day's planned capacity | Shows the spike exceeded what the store expected | Workforce system: original roster | Workforce management lead |
| The same-day staffing change | Shows the branch noticed and reacted, and when | Workforce system: timesheet edit history | Workforce management lead |
| The service failure | Turns a sales spike into a customer problem | Incident log: complaints by store and time | Customer service lead |
| The remedy and its reason | Explains the manual price changes and what the bad hours cost | Incident log note or POS comp reason code | Customer service lead and retail systems manager |
| That the promotion was local | Explains why nobody planned staff for it | Often nowhere outside the POS discount name | Store operations |
| Renames of the discount | Keeps one promotion from reporting as two | POS reporting, where Square notes a renamed discount becomes a separate entry | Retail systems manager |
Two rows deserve care. The same-day change survives only if the workforce system keeps edits beside the original roster; Deputy's help center says its timesheets keep a history of each action, who took it, when, and the before and after values. And the "local" flag often lives nowhere at all, which is worth saying plainly rather than guessing.
Retention can quietly remove the explanation
The gap between the before and after tables can grow over time. U.S. Department of Labor guidance under the FLSA requires payroll records and sales and purchase records to be kept for at least three years, but time cards and work schedules for only two. A retailer that keeps exactly what the law requires may still hold year-three sales and promotions with no roster beside them. For those months, the after table collapses back into the before table.
Ask each system owner one question: how far back does your history go, and is anything purged on a schedule? Note the answers as years per system. If a POS replacement or a workforce tool switch is planned, note the date too; history left behind in a migration is a documented, time-bound reason to start the conversation now. For a related case where a planner's change only makes sense beside the original plan, see forecast value added and planner overrides.
Describing the gap without opening a record
A partner never needs the tables above. What SourceX needs is a description of which columns of the after table the retailer can fill, for which stores and years, and which it cannot. The record chain page names the key behind each join, and the completeness checklist scores whether the trail is complete enough to discuss.
Before introducing, confirm: 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license, and an authorized contact: the CEO, with the COO or VP of store operations often as sponsor. 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.
Unknown until SourceX reviews the opportunity: whether franchised stores' records belong to the franchisor, how employee and customer data would be de-identified, demand for this record type and any offer. Partners never ask for or handle raw records. Other system guides are in the systems hub.
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 a retailer can say which columns of the after table it still holds, and for how many years, register as a partner, check it against who qualifies and read the program terms before you introduce its sponsor.