# Promotion-to-service-recovery record chain | SourceX

Canonical: https://refer.sourcex.si/guides/promotion-to-service-recovery-record-linkage
Last updated: 2026-11-04

A retailer connects promotion-to-service-recovery records mostly by store and hour, because its POS, workforce system and incident log rarely share an ID. The discount name ties a promotion to its sales, store and timestamp tie sales to the shifts added that day, store and visit time tie complaints to the spike, and a coded comp or reason field ties the remedy back to the complaint. Where the remedy is typed as free text, that last hop is only a guess.

This record chain is part of the [promotion-to-service-recovery guide](/guides/chain-promotion-to-service-recovery), which covers the metadata packet a partner fills in. Here the job is narrower: follow one store's Sunday through six records and name the key that holds each pair together.

## Six records from discount to accepted remedy

Illustrative. A fictional 70-store outdoor and sporting goods chain. At store 31, the manager opens a local trail-shoe clearance at 09:00 on a Sunday. The roster assumed about 45 transactions an hour and one shoe fitter. Runners hear about it on a club chat, and by mid-morning customers are waiting 40 minutes to be fitted.

| Step | Record | Key that points to the next record | System |
|---|---|---|---|
| 1. Promotion set up | Local discount TRAIL30, store 31, Sunday only | Discount name, location and date range | POS |
| 2. Sales against it | Transactions per hour: 52 at 09:00, 71 at 10:00, 83 at 11:00 | Location and timestamp | POS |
| 3. Planned roster | Sunday schedule built on Wednesday: one fitter, three cashiers | Store, role, shift start and end | Workforce system |
| 4. Same-day change | A second fitter called in from a day off at 10:40, original roster kept in the edit history | Timesheet history: editor, time, before and after values | Workforce system |
| 5. Service failure | Fitting-wait complaints from 10:15, some at the desk and some by phone the next day | Store and time typed by staff | Incident log |
| 6. Remedy accepted | Bonus loyalty points offered at 12:30 to anyone who waited over 30 minutes | Comp reason code, if the store used one | POS or loyalty system |

Read down the key column and the pattern is plain. Only steps 1 and 2 share a native identifier, because both live in the POS. Every other hop crosses a system boundary and depends on two systems agreeing about which store and which hour they mean. That is normal for retail and not a defect. It just has to be described accurately, so SourceX knows which joins were recorded and which would be inferred.

## How strong each join is

Not every key carries the same weight. Grade each hop before describing the chain to anyone, because the grade, not the number of systems, decides how much of the story survives.

| Join | Key | Strength | What makes it fail |
|---|---|---|---|
| Promotion to sales | Discount name, location, date | Strong | The discount is renamed mid-campaign, so one promotion reports as two |
| Sales to roster | Store and hour | Strong | The POS uses store names while the workforce system uses store codes |
| Roster to same-day edit | Timesheet history | Strong where history is kept | Edits overwrite the original roster instead of sitting beside it |
| Spike to complaint | Store and visit time typed by staff | Medium | A call center logs the complaint the next day with no visit time |
| Complaint to remedy | Comp reason code or complaint reference | Weak unless coded | Bonus points are keyed as a manual loyalty adjustment |

Two of the strong grades, promotion to sales and roster to same-day edit, depend on vendor features covered below; the medium and weak grades at the bottom depend on habits.

## Where store-and-hour joins slip

Because most of this chain rests on store and time, the breaks tend to be mismatches between systems rather than missing records. Four are worth naming, each with a signature a partner can ask about.

**Store identity drifts.** A store relocates, merges with another or is renumbered, and one system updates its location list while another keeps the old one. The signature: a store that appears under two names or codes in one system across the same years.

**Clocks disagree.** One system stores time in UTC and another in local time, or a scheduling tool records the moment a shift was approved rather than when it starts. The signature: added shifts that appear to begin before the spike they were added to cover.

**Edits land late.** A manager calls in a second fitter at 10:40 but enters the change on Monday. The edit history then shows a Monday timestamp for a Sunday decision. The signature: clusters of schedule edits on the first working day after a weekend.

**Retention clocks differ.** Under the FLSA, the U.S. Department of Labor sets a three-year minimum for payroll and for sales and purchase records, against two years for time cards and work schedules. A chain that keeps only the minimum can still hold a clearance and its sales a year after the roster that explains the wait has gone. The signature: schedule history that starts later than POS history.

Vendor documentation explains two of the grades in the table above. Square's help center says its discounts report shows the top used discounts and total discount amounts for a date range, filterable by location, and that renaming a discount makes it a separate entry in reporting. So if store 31 had extended TRAIL30 into Monday under a new name, one clearance would report as two unrelated discounts unless someone noted the rename. Deputy's help center says each timesheet keeps a history of every action, who took it, when, and the before and after values, which is why step 4 can show the original one-fitter roster and the 10:40 call-in side by side. Neither detail implies SourceX connects to either product; they show what a company using those tools can say about its own records.

None of these makes the records useless. Each sets a boundary on which years and which stores the chain can be joined end to end, and the [missing-context comparison](/guides/promotion-to-service-recovery-missing-context) shows what a reader loses on the far side of that boundary.

## Repairing the weakest hop: the uncoded remedy

The complaint-to-remedy join is the easiest to lose, and it matters most, because the remedy is the outcome: what the chain decided a long wait was worth. In the illustrative case, the 12:30 bonus points were keyed as manual loyalty adjustments at the till. In the loyalty system they look like any goodwill top-up. In the incident log, the remedy sits in a free-text note, if anyone wrote one.

| Weak join | Repair the retailer may already have | Key it creates |
|---|---|---|
| Remedy keyed as a manual loyalty adjustment | A dedicated service recovery reason code on points and comps | Coded remedy that can be counted by store and day |
| Remedy written only in a free-text note | A remedy field on the incident form | Structured outcome on the complaint record |
| Complaint and comp never reference each other | Complaint number typed into the comp note | Typed reference both ways |
| Rename splits a promotion | A naming rule for local discounts | One name per campaign across its dates |

For a referral, the point is not to fix anything. It is to find out which of these repairs already exist and from which year. A retailer that introduced a service recovery comp code in 2021 has five clean years of the final hop; one that never did has the hop only as free text, which the review should know before anyone describes the records as linked. The [completeness checklist](/resources/promotion-to-service-recovery-completeness-checklist) turns this into a pass, partial or fail score.

## Who owns each hop, and what a partner records

The retail systems manager usually administers the POS and can answer for steps 1, 2 and 6. The workforce management lead owns steps 3 and 4. The customer service lead owns step 5 and often the remedy policy. Each can describe their hop from admin settings and report layouts without opening a sale, a timesheet or a complaint. Incident logs often hold customer names and phone numbers, so the [incident and on-call records checklist](/resources/a-company-introduction-checklist-for-incident-and-on-call-records) is a useful model for asking about fields rather than entries. Authorizing a licensing discussion across all three systems takes the CEO, often with the COO or the VP of store operations as sponsor.

Before introducing, confirm the basics: 50+ full-time employees at peak (contractors and agency staff excluded), documented operating history, rights to license the records, 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.

A partner records only the shape of the chain: which hops exist, the key each one uses, the stores and years covered, and who owns it. Unknown until SourceX reviews it: rights at franchised stores, how employee and customer data would be de-identified, whether a buyer wants this chain, and what the retailer would be offered. For neighboring record types, see [deductions management](/data-types/deductions-management) and the [retail operations industry page](/industries/retail-operations); other system guides sit in the [systems hub](/systems).

## 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 retail client can name the key at each hop, including how remedies are coded, [register as a partner](/register), check the chain against [who qualifies](/who-qualifies) and read the [program terms](/terms) before introducing its operations sponsor.

## Sources

- https://squareup.com/help/us/en/article/8359-view-discounts-comp-and-void-reports
- https://help.deputy.com/hc/en-au/articles/17638531661967-Understanding-Timesheets
- https://www.dol.gov/agencies/whd/fact-sheets/21-flsa-recordkeeping
- https://refer.sourcex.si/terms
