Promotion exception records across systems: a map of promotion engine, POS, back-office and supplier claim keys

Short answer

Reconstructing a promotion exception takes four keys around one receipt line: the promotion or discount ID printed on the line, a rule version with its start and end dates, the original receipt number on any refund or override, and the supplier deal number when a vendor funded the offer. With all four, a reviewer can show what the rule said, what the till charged, how the shopper was made whole and what was claimed back. The key most often missing is the dated rule version, because promotion engines are reconfigured in place.

Visual briefFull-size diagram
A receipt line at the center with four systems around it, promotion engine, POS, back office and supplier claims, and keys traveling inward: promotion ID, rule version and start date, original receipt number and supplier deal number.
One receipt line joins four systems. Illustrative layout; real systems and keys vary by retailer.

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.

SystemRecord it holdsLinking keyUsual owner
Promotion engineOffers, combination settings, start and end dates, edit historyPromotion ID, rule version, effective-from datePricing or category management
POSReceipts, line items, discounts applied, price file each store loadedReceipt number, store, terminal, line, promotion IDRetail operations and IT
Back office or ERPRefunds, price overrides, reason codes, margin reportsOriginal receipt number, manager ID, reason codeStore operations and finance
Supplier claimsVendor-funded promotion deals and the claims made against themSupplier deal number, promotion ID, claim periodCommercial 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.

StepSystemRecordKey to the next step
Vendor deal agreedSupplier claimsDeal for a per-unit allowance over four weeksSupplier deal number, promotion ID
Offer set to start ThursdayPromotion engineRule version 1 with start datePromotion ID, effective date
Six stores load prices FridayPOSPrice file log per store with load timeStore, timestamp
Thursday baskets at full pricePOSReceipt lines with no promotion IDReceipt number
Shopper refunded the differenceBack officeRefund with manager ID and reason codeOriginal receipt number
Claim preparedSupplier claimsUnits on promotion, plus refunded Thursday units, by approvalPromotion ID, claim period
Deployment fixedPromotion engine and POSNote moving start dates a day earlier for late storesStore 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.

  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

Is a POS export enough to show how a promotion exception was handled?

Rarely. Receipts show what was charged, but not what the rule said that day or who approved the correction. Those sit in the promotion engine and back office, and the keys between them decide whether the case can be rebuilt.

What if receipts only show the final price, with no promotion ID?

Then a reviewer can only infer the discount from the price, which is weak evidence. It is worth noting in the introduction; SourceX decides whether the remaining records are enough.

Sources

  1. shopify.dev/docs/api/admin-graphql/latest/objects/LineItem
  2. shopify.dev/docs/api/admin-graphql/latest/interfaces/Dis…
  3. help.shopify.com/en/manual/discounts/discount-combinations
  4. help.shopify.com/en/manual/sell-in-person/shopify-pos/order-m…
  5. 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