Promotion-to-service-recovery completeness scorecard: eight metadata checks with a pass, partial or fail guide

Short answer

A promotion-to-service-recovery trail breaks in five places: the promotion was renamed or never registered, store codes differ between systems, schedule edits overwrite the plan, complaints carry no store or visit time, or the remedy is not coded. The scorecard below turns those breaks into eight checks across coverage, linkage, timestamps, outcomes and gaps. Each is answered at metadata level and scored pass, partial or fail, so a partner can say how complete the trail is before promising anything.

Visual briefFull-size diagram
An eight-item checklist ticks through POS coverage, incident channels, discount naming, store codes, roster history, complaint time, remedy coding and local promotion flags, while a vertical meter rises to 10 of 16 points.
Illustrative score for a fictional 52-store retailer: 10 of 16, enough to discuss with its gaps labeled.

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

CheckAreaHow to check at metadata levelPass (2)Partial (1)Fail (0)
1. POS historyCoverageAsk which stores and years the POS holds discount and transaction history forAll stores, three or more yearsSome stores, or under three yearsNot known
2. Incident channelsCoverageAsk which channels feed the incident log: store desk, phone, email, socialAll channels in one logSome channels, or several separate logsNot known
3. Discount namingLinkageAsk whether local discounts follow a naming rule and whether renames are trackedNaming rule in use and renames recordedRule exists but is not enforcedNo rule; renames common
4. Store identityLinkageAsk whether the POS, workforce system and incident log use the same store codesOne code list shared by all threeA mapping table existsCodes differ and no mapping
5. Roster historyTimestampsAsk whether same-day changes sit beside the original roster with who and whenOriginal roster and edits both keptEdits kept, original overwrittenOnly the final roster
6. Complaint timingTimestampsAsk which fields the incident form requiresStore and visit time requiredStore required, time optionalNeither required
7. Remedy codingOutcomesAsk whether service-recovery gestures have their own comp or reason codeDedicated code, used chain-wideCode exists for some years or storesFree text or manual price change
8. Local promotion flagGapsAsk where local promotions are recorded besides the POSRegistered centrally with store and datesKnown informally, e.g. by emailNot 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.

CheckAnswer givenScore
1. POS historyAll 52 stores since 20192
2. Incident channelsStore and phone since 2018, email added 2021, social handled separately1
3. Discount namingNaming rule issued in 2023, not always followed by stores1
4. Store identitySame store codes in all three systems2
5. Roster historyEdits keep before and after values since 20202
6. Complaint timingStore required; visit time required only since 20211
7. Remedy codingService recovery comp code added 2021; free text before1
8. Local promotion flagNot recorded outside the POS discount name0
Total10 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

ScoreWhat it meansWhat the partner does
13 to 16The trail can be followed end to end for most stores and yearsIntroduce, attaching the scorecard
8 to 12Joinable for a known period, with labeled gapsIntroduce, naming the years and checks that are partial
4 to 7Pieces exist but rarely joinIntroduce only if the sponsor accepts that the gaps will be discussed openly
0 to 3Too little is known to describe the trailAsk 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.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Does a low score mean the retailer should not be introduced?

No. The scorecard describes the trail; it does not decide eligibility. A retailer scoring 6 of 16 with honest answers is a better introduction than one scoring 14 on guesses, because SourceX can plan around known gaps.

How long does the scorecard take?

Usually one conversation of under an hour with the retail systems manager, the workforce management lead and the customer service lead. Every check is answered from settings, report layouts and policy, not from records.

Should the scorecard go to SourceX with the introduction?

Yes. It holds no sales, names or complaint text, and it tells the review where the trail is complete, where it is partial and which years each answer covers.

Sources

  1. squareup.com/help/us/en/article/8359-view-discounts-comp-…
  2. help.deputy.com/hc/en-au/articles/17638531661967-Understandi…
  3. dol.gov/agencies/whd/fact-sheets/21-flsa-recordkeeping
  4. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment