# Promotion to service recovery: metadata packet | SourceX

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

Without reading a sale, a timesheet or a complaint, a partner can record which systems hold each step from promotion event to staffing exception to accepted remedy (typically the POS, a workforce scheduling system and an incident or customer service log), the stores and years each covers, who administers them, and whether store number, date and promotion name are captured consistently enough to join them. The case to flag is a local promotion that created a workload spike nobody planned for.

## The business task the packet describes

Retail chains run promotions to move stock and bring people in. Most are planned centrally, with staffing adjusted in advance. Some are local: a store manager discounts a slow line for the weekend. When a local promotion works better than expected, the store runs short of staff, queues form, customers complain, and someone has to decide what to offer them to keep the sale.

Each of those decisions is recorded somewhere different. The POS knows the promotion and the transactions. The workforce system knows the schedule and the shifts added on the day. The incident or customer service log knows the complaints and the remedy. Across dozens of stores and years, the joined history is a record of how a retailer responds to its own exceptions. The packet's job is not to capture that history but to tell SourceX where it lives and how well the pieces fit together.

## What each system can tell you without opening it

Fill in the packet from one conversation with the operations, workforce management and customer service leads. Ask about the shape of the records, never their content.

- **POS.** Which platform, which stores, since when? How are local promotions set up: as named discounts, price overrides or manual markdowns? If the chain uses Square, its discounts report lists the top discounts and totals for a date range by location, and renaming a discount makes it a separate entry in reporting. So whether stores reuse or rename promotions is a packet fact.
- **Workforce system.** Are schedules built centrally or by store? Are same-day shift additions recorded as edits or as new shifts? If the chain uses Deputy, each timesheet keeps a history log of every action, who took it, when, and the before and after values. In the U.S., the Department of Labor's FLSA guidance requires time cards and work schedules to be kept for two years and payroll records for three, which gives a floor for how far back staffing records may go.
- **Incident log.** Which channels feed it: store, phone, email, social? Are remedies recorded as a field or in free text? Are entries edited or appended?

## Sample packet, filled in

Illustrative: a fictional 48-store home and garden retailer with about 1,600 staff; every figure is invented to show the level of detail.

| Packet field | POS | Workforce system | Incident log |
|---|---|---|---|
| Object types | Discounts, transactions, comps and voids | Schedules, shifts, timesheets and their history | Complaints, service failures, remedies |
| Coverage | All 48 stores since 2019 | All stores since 2020 | Store and phone since 2018; email since 2021 |
| Rough volume | About 30 local promotions a month chain-wide | About 9,000 shifts a week | About 1,200 incidents a month |
| Administrator | Retail systems manager | Workforce management lead | Customer service lead |
| Change history | Renamed discounts split in reports | Edits keep before and after values | Entries appended, not edited |
| Join fields | Location, timestamp, discount name | Store, shift start and end | Store and time, required since 2021 |
| Known gap | Local promotions not flagged as local | Same-day additions sometimes entered next day | Remedy in free text before 2021 |
| Unknown until review | Rights at franchised stores | Employee personal data handling | Customer personal data handling |

Leave out amounts, names and any sample rows. "About 30 local promotions a month" is the right level of detail. For a broader structure, see the [metadata-only inventory guide](/guides/how-to-prepare-a-metadata-only-inventory-of-business-systems); for the incident side, the [incident and on-call records checklist](/resources/a-company-introduction-checklist-for-incident-and-on-call-records) adapts well to store incident logs.

## How the packet flags an unplanned workload spike

The case to surface is a local promotion that outruns the schedule. In the illustrative retailer, one store manager starts a patio furniture discount at 10:00 on a Saturday. The day was scheduled for about 60 transactions an hour. Transactions run 32 at 09:00 and 58 at 10:00, then jump to 94 at 11:00, 97 at 12:00 and 81 at 13:00, before falling back to 55, 44 and 38. Complaints about the queue are logged from 11:00, two associates are added at 11:20, and at 13:00 the manager offers free delivery to customers who waited.

The partner never sees those numbers. The packet makes the case findable through three rows: "Known gap" shows local promotions are not flagged as local and same-day shifts are sometimes entered late, "Join fields" shows store and time are required in the incident log only since 2021, and "Change history" shows schedule edits keep before and after values. Together they tell SourceX that spikes like this exist in the records, from which year they can be joined, and where the timing may be off. Ask the workforce lead one question: "When a store adds staff on the day, where does that show up, and when?"

## Sponsor, eligibility and the unknowns

Introduce the CEO, who can authorize a licensing discussion, or a sponsor who will take it to the CEO: usually the COO, the VP of store operations or the CFO. Name the workforce management lead and the customer service lead as the people who can answer the packet. If the chain is replacing its POS or ERP, note the date; the [ERP replacement handoff checklist](/resources/a-data-opportunity-handoff-checklist-for-an-erp-replacement) shows what to capture before a cutover.

Before introducing, check: 50+ full-time employees at peak (contractors and seasonal agency staff 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.

What stays unknown until SourceX reviews the opportunity: SourceX's current data needs for this record type, the rights review result, how employee and customer data would be de-identified, the offer and any reward. Partners never ask for or handle raw records. For more on retail, see [assessing a retail chain](/guides/how-to-assess-business-data-opportunities-in-a-retail-chain), the [retail operations industry page](/industries/retail-operations) and the [systems hub](/systems).

## Go deeper on promotion-to-service-recovery records

- [Promotion-to-service-recovery record linkage](/guides/promotion-to-service-recovery-record-linkage): the record chain, step by step, with the identifier that joins each hop and where it breaks.
- [Promotion-to-service-recovery completeness checklist](/resources/promotion-to-service-recovery-completeness-checklist): a pass, partial or fail scorecard for judging whether the trail is complete enough to discuss.
- [What a single-system promotion export loses](/guides/promotion-to-service-recovery-missing-context): a before-and-after reading of one store's day, with and without its surrounding records.

## 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 where local promotions, schedule edits and service remedies are recorded, [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
