This system map is part of exception handling records for AI agents. It answers one question for retail systems consultants: which system holds each record, and what ties them into one case?
Four systems around one receipt line
A promotion exception touches more than the till. Each system holds a different part of the case.
| System | Record it holds | Linking key | Usual owner |
|---|---|---|---|
| Promotion engine | Offers, combination settings, start and end dates, edit history | Promotion ID, rule version, effective-from date | Pricing or category management |
| POS | Receipts, line items, discounts applied, price file each store loaded | Receipt number, store, terminal, line, promotion ID | Retail operations and IT |
| Back office or ERP | Refunds, price overrides, reason codes, margin reports | Original receipt number, manager ID, reason code | Store operations and finance |
| Supplier claims | Vendor-funded promotion deals and the claims made against them | Supplier deal number, promotion ID, claim period | Commercial finance |
The receipt line sits in the middle. The engine explains why it was priced that way, the back office records what was done about it, and supplier claims record who paid for the discount.
The keys, one by one
Promotion ID on the line. Without it, an analyst can only infer a discount from the price. Shopify's order model shows what a well-kept line looks like: each line item has discount allocations, the actual amount taken off that line, each pointing to the discount application behind it, and allocations stay on refunded quantities. Shopify notes that a discount application captures intent, while the allocation holds the amount actually discounted. An exception is precisely a gap between the two.
Rule version with dates. Every offer needs dated versions. In Shopify, each discount's Combinations setting decides what it can stack with, and product discounts apply before order discounts. Change that setting, or a start date, in place and the configuration that caused the problem is gone. Some engines keep an edit log; others keep only the live offer.
Original receipt number on corrections. In Shopify POS, a return or refund starts from the original order, so the link is built in. Elsewhere, a refund of the difference may be keyed only by store and day, and then it floats free of the basket it fixed.
Supplier deal number. When a vendor funds a price cut, finance claims the discount back per unit sold on promotion. The claim cites a deal and a period, not a receipt. Joining it back needs the promotion ID on each line.
One fully joined case (Illustrative)
Invented for this page. A fictional 650-person home and garden retailer with 24 stores runs a vendor-funded spring price cut on a garden hose, due to start on a Thursday. Six stores on an older POS build load the price file a day late, so Thursday shoppers there pay full price. Customer service refunds the difference on request, and finance must decide which units to claim from the vendor.
| Step | System | Record | Key to the next step |
|---|---|---|---|
| Vendor deal agreed | Supplier claims | Deal for a per-unit allowance over four weeks | Supplier deal number, promotion ID |
| Offer set to start Thursday | Promotion engine | Rule version 1 with start date | Promotion ID, effective date |
| Six stores load prices Friday | POS | Price file log per store with load time | Store, timestamp |
| Thursday baskets at full price | POS | Receipt lines with no promotion ID | Receipt number |
| Shopper refunded the difference | Back office | Refund with manager ID and reason code | Original receipt number |
| Claim prepared | Supplier claims | Units on promotion, plus refunded Thursday units, by approval | Promotion ID, claim period |
| Deployment fixed | Promotion engine and POS | Note moving start dates a day earlier for late stores | Store list, rule version 2 |
Every row joins the next with a key a reviewer can check. Lose the price file log and the full-price receipts look like a cashier error. Lose the original receipt number on refunds and finance cannot show which Thursday units were sold at the promoted price after all. The worked promotion case follows a different failure, two offers stacking, as a sequence of decisions.
Where the joins break
- Offers edited in place. The most common gap. Engine replacements migrate active offers and leave history in the old system's change log, if anywhere.
- Receipts with net prices only. Older POS exports may drop discount lines.
- Refunds without the receipt. Manual price adjustments keyed by store and day.
- Claims at deal level. Supplier claims summarize units, so the link to individual baskets depends on the promotion ID; see deductions management.
A single system rarely makes a licensable record set; is one system's data enough for licensing explains why. Planner judgment around promotional volume also appears in forecast overrides.
Questions for the retail operations director
Stay at metadata level. Ask about keys and years, not records.
- Does the promotion engine keep dated versions of each offer, and since when?
- How many years of receipts carry a promotion ID per line?
- Do refunds and overrides cite the original receipt number?
- Are vendor-funded promotions claimed against a deal number that also appears in the engine?
- Who owns transaction data and supplier terms, and who can authorize a licensing discussion? The data often sits with the CFO or CIO, while authorization comes from the CEO, or the owner-CEO in an owner-run chain; the who-can-license decision tree maps it.
The company needs 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. Supplier trade terms, loyalty data and franchise arrangements all need rights review, so what is licensable stays unknown until SourceX reviews it. Partners never ask for or handle raw client records. More sector context is on the retail operations industry page.
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's offers, receipts, refunds and claims still join into whole cases, register as a partner, check the company on who qualifies and read the program terms before you introduce its decision-maker.