Promotion exception handling referral brief: a fill-in template with a completed example

Short answer

A company introduction about promotion exception handling should fit on one page and hold metadata only: the company's size, the systems that hold promotion rules, POS receipts and corrections, how many years each covers, rough record volumes, the open question a stacked promotion raises, who owns the records, and who can authorize a licensing discussion. Below is the blank template, guidance for each field, and one completed Illustrative example you can copy.

Visual briefFull-size diagram
A blank referral brief form with eight fields, company size, systems, years of history, record volumes, open question, record owner, authorized contact and rights notes, filling in one by one with Illustrative values for a fictional 520-person home and garden retailer.
Illustrative values. The brief describes records; it never contains them.

The brief belongs to exception handling records for AI agents, which explains why a promotion that stacks contrary to its rule is a useful case. This page is the handoff document a retail systems consultant writes after a first conversation.

The blank brief

Copy the table, keep the field names, and fill the right-hand column in plain words. Every answer comes from a conversation, not from looking at data.

FieldWhat to write
CompanySector, number of stores, full-time headcount at peak, countries of operation
Business taskOne sentence on the exception: catching and correcting offers that combined when they should not have
Promotion rulesSystem name, whether past configurations can be shown with dates, years covered
POS receiptsSystem name, whether each discount line carries a promotion ID, years covered
CorrectionsWhere overrides, credits and refunds are recorded, years covered
VolumesOrders of magnitude: stores, annual transactions, promotions per year, corrections per year
Coverage eventsAny planned system change that could affect history, with the company's own date
Open questionThe one thing the records may or may not show
Record ownerThe role that owns each system
Authorized contactThe executive who can authorize a licensing discussion, and the systems contact
Rights notesFranchised stores, supplier-funded promotions, loyalty program terms

Keep it to one page. A reader at the company should be able to check every line against what they know without opening a system.

How to fill each field without touching a record

Company. Headcount matters because introduced companies need 50+ full-time employees at peak; contractors do not count. Ask for the peak figure, not today's.

Promotion rules. The question is whether past configurations can be shown with their dates, or only today's. In Shopify, for example, each discount carries a Combinations setting that decides which discount classes it can combine with, and product discounts apply before order discounts. Whether two offers were allowed to stack on a given day depends on that setting as it stood then.

POS receipts. Ask whether a discount line names the promotion that produced it. Promotion IDs on receipt lines are what let an analyst join a receipt to a rule. Reporting can mislead here: Shopify notes that its sales by discount report may count the same order more than once when combinable discounts are on, so a report total is not a receipt count. Write what the operations director says and mark estimates as estimates.

Corrections. Overrides may sit in the POS, credits in the ERP and the reason in an email to finance. Name each place.

Volumes. Orders of magnitude are enough: "about 85 stores, tens of millions of transactions a year, a few hundred promotions a season".

Coverage events. If a system change is planned, write the company's date and whether history moves with it. The retention timeline for promotion records shows why that date matters.

Rights notes. Loyalty numbers and card tokens on receipts can identify a person. Under the GDPR, personal data includes information about someone identifiable by an identification number or online identifier. Note that such identifiers exist; do not try to assess them.

Completed example: a 520-person home and garden retailer

Illustrative and fictional. The values are invented to show the level of detail.

FieldCompleted entry
CompanyHome and garden retailer, 62 stores, 520 full-time employees at peak, U.S. and Canada
Business taskCatching and correcting seasonal offers that stacked with loyalty coupons contrary to the intended rule
Promotion rulesLegacy pricing system; dated configurations since 2019, about seven years
POS receiptsPOS data warehouse; promotion ID on each discount line since 2018
CorrectionsStore overrides in POS with reason codes; credits in the ERP; some reasons in finance email
VolumesRoughly 9 million transactions a year; 300 to 400 promotions a season; corrections not counted
Coverage eventsNew pricing system planned for next spring, per the company; only active offers will move
Open questionFor a weekend when two offers stacked, can the rule version in force that day still be shown beside the corrected receipts?
Record ownerMerchandising director (rules), CIO (pricing system and POS), controller (corrections)
Authorized contactCEO; retail operations director as systems contact
Rights notesEight stores franchised; some promotions supplier-funded under trade agreements; loyalty identifiers on receipts

Notice what the example leaves out: no receipt numbers, no customer names, no promotion prices, no screenshots. It still tells SourceX enough to decide whether a review is worth the company's time.

What to leave out, and what to say about the reward

Leave out anything that would require the company to send you data: sample receipts, rule exports, override logs, loyalty files. Partners never ask for or handle raw client records. Leave out guesses about value or price; nobody can estimate a payout before SourceX reviews rights and fit.

Say three things plainly when you send it:

  1. You are a registered SourceX partner and have signed the Channel Partner Agreement.
  2. You may receive a referral reward paid separately by SourceX. It never comes out of the company's payout and is never calculated on SourceX's revenue.
  3. Whether any records can be licensed depends on rights, qualification and the proposed use, which SourceX reviews with the company.

Who in a retailer can actually say yes is covered in who can license promotion exception handling records. The general shape of a first message is in the warm introduction brief, and the client opportunity brief generator can draft a first version for other workflows.

Before sending, check the baseline: 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. Sector context is on the retail operations 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 you can fill at least the rules, receipts, owner and authorized contact fields from a first conversation, register, confirm the retailer against who qualifies, read the terms and then send the brief to the systems contact.

  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

Can the brief include a sample receipt to show what the records look like?

No. The brief stays at metadata level: systems, years, counts and owners. Receipts can carry loyalty and payment identifiers, and any sample exchange happens later under an agreement and SourceX's review.

Who should receive the brief first?

Usually the retail operations director, who can check the facts and forward it to the executive who can authorize a licensing discussion. Send it only after you have registered and signed the partner agreement.

What if the retailer does not know its record volumes?

Write an order of magnitude or 'not known'. A brief with honest blanks is more useful than one with guesses, and SourceX confirms volumes during its own review.

Sources

  1. help.shopify.com/en/manual/discounts/discount-combinations
  2. help.shopify.com/en/manual/reports-and-analytics/shopify-repo…
  3. eur-lex.europa.eu/eli/reg/2016/679/oj/eng
  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