This scorecard is part of the promotion-to-service-recovery guide. It does not replace SourceX's review. It gives that review an honest starting point.
How to run the scorecard
Score each check 2 for pass, 1 for partial and 0 for fail, for a maximum of 16. Ask the person who administers each system, and ask about settings, report layouts and policy, never about individual sales, shifts or complaints. Write down the year each answer starts from, because a pass from 2021 onward and a fail before it is a useful result.
Three rules keep the score honest:
- Unknown scores as fail. If nobody can answer a check, record 0 and the note "not known". That is more useful to SourceX than an optimistic guess.
- Score the weakest store group. If company-owned stores pass and franchised stores fail, score the franchised result and note the split.
- Do not estimate frequencies. The scorecard asks whether records exist and join, not how often promotions overwhelm a store.
The eight checks
| Check | Area | How to check at metadata level | Pass (2) | Partial (1) | Fail (0) |
|---|---|---|---|---|---|
| 1. POS history | Coverage | Ask which stores and years the POS holds discount and transaction history for | All stores, three or more years | Some stores, or under three years | Not known |
| 2. Incident channels | Coverage | Ask which channels feed the incident log: store desk, phone, email, social | All channels in one log | Some channels, or several separate logs | Not known |
| 3. Discount naming | Linkage | Ask whether local discounts follow a naming rule and whether renames are tracked | Naming rule in use and renames recorded | Rule exists but is not enforced | No rule; renames common |
| 4. Store identity | Linkage | Ask whether the POS, workforce system and incident log use the same store codes | One code list shared by all three | A mapping table exists | Codes differ and no mapping |
| 5. Roster history | Timestamps | Ask whether same-day changes sit beside the original roster with who and when | Original roster and edits both kept | Edits kept, original overwritten | Only the final roster |
| 6. Complaint timing | Timestamps | Ask which fields the incident form requires | Store and visit time required | Store required, time optional | Neither required |
| 7. Remedy coding | Outcomes | Ask whether service-recovery gestures have their own comp or reason code | Dedicated code, used chain-wide | Code exists for some years or stores | Free text or manual price change |
| 8. Local promotion flag | Gaps | Ask where local promotions are recorded besides the POS | Registered centrally with store and dates | Known informally, e.g. by email | Not recorded anywhere |
Checks 4 and 7 are the easiest to answer optimistically. Ask for the name of the code list or the form field, not a yes or no.
A scored example (Illustrative)
A fictional 52-store outdoor and hardware retailer, answered by its retail systems manager, workforce management lead and customer service lead.
| Check | Answer given | Score |
|---|---|---|
| 1. POS history | All 52 stores since 2019 | 2 |
| 2. Incident channels | Store and phone since 2018, email added 2021, social handled separately | 1 |
| 3. Discount naming | Naming rule issued in 2023, not always followed by stores | 1 |
| 4. Store identity | Same store codes in all three systems | 2 |
| 5. Roster history | Edits keep before and after values since 2020 | 2 |
| 6. Complaint timing | Store required; visit time required only since 2021 | 1 |
| 7. Remedy coding | Service recovery comp code added 2021; free text before | 1 |
| 8. Local promotion flag | Not recorded outside the POS discount name | 0 |
| Total | 10 of 16 |
Ten of sixteen, with most partial scores turning to passes from 2021. That tells SourceX the trail is joinable end to end for about five years at most stores, that local promotions have to be inferred from discount names, and that older complaints may not carry a visit time.
Reading the score
| Score | What it means | What the partner does |
|---|---|---|
| 13 to 16 | The trail can be followed end to end for most stores and years | Introduce, attaching the scorecard |
| 8 to 12 | Joinable for a known period, with labeled gaps | Introduce, naming the years and checks that are partial |
| 4 to 7 | Pieces exist but rarely join | Introduce only if the sponsor accepts that the gaps will be discussed openly |
| 0 to 3 | Too little is known to describe the trail | Ask the sponsor to find the system owners first |
A retailer that answers "we know local promotions sometimes swamp a store, and here is how we see it" is describing a known, labeled exception. That is the answer worth bringing. A retailer that has never checked is not disqualified, but the partner should say so rather than fill the gaps.
The local-promotion stress test
One test exposes checks 3, 5, 6, 7 and 8 together. Ask the operations lead to pick a recent weekend when a local promotion drew more customers than planned, and to say, without opening anything, where each of these would be found: the discount, the added shifts, the complaints and the remedy. If they can name a system and a field for all four, the trail likely holds. If one answer is "we would have to ask the store manager", that is the break, and the missing-context comparison shows what a reader loses because of it. The record chain page names the key each answer depends on.
Who answers and who signs off
Check 3 has a concrete reason behind it. Square's help center says renaming a discount makes it a separate entry in its discounts report, so one promotion renamed midway reads as two. Check 5 depends on the workforce tool: Deputy's help center says each timesheet keeps a history of every action, who took it, when, and the before and after values. Check 1 has a legal floor in the U.S.: Department of Labor guidance under the FLSA requires sales and purchase records to be kept for at least three years, while time cards and work schedules need only two, which is why check 5 can score lower for older years.
The retail systems manager answers checks 1, 3 and part of 7; the workforce management lead answers 4 and 5; the customer service lead answers 2, 6 and 7; store operations answers 8. None of them usually has authority to license records. That sits with the COO, the VP of store operations or the CFO.
Confirm the basics before introducing: 50+ 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.
If a POS or ERP replacement is planned, use the ERP replacement handoff checklist; for a portfolio owner reviewing several retailers, the portfolio review handoff checklist applies. The wider retail picture is in assessing a retail chain and the systems hub. Unknown until SourceX reviews it: rights at franchised stores, de-identification of employee and customer data, SourceX's current data needs and any offer.
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 scores 8 or more and the sponsor will take a call, register as a partner, check it against who qualifies and read the program terms, then send the scorecard with your introduction.