This page is part of exception handling records for AI agents, which explains why a stacked promotion is a useful exception case. Here the job is narrower: a timeline of what fades, and when.
The retention timeline, record type by record type
Each row is a record type a promotion exception depends on. The life spans are typical patterns, not rules; ask the company for its own.
| Record type | Where it usually lives | What usually ends it | Typical exposure | Who approves keeping it |
|---|---|---|---|---|
| Rule change log | Old promotion engine admin | Engine switched off at cutover | Lost on the cutover date unless exported | CIO or IT director, with merchandising |
| Dated rule versions with combination settings | Old promotion engine | Only active promotions migrated | Lost at cutover; often only current rules move | Merchandising or pricing director |
| Store override and manager notes | POS back office or store log | POS replacement or local purge settings | Varies by store system; often months, not years | Retail operations director |
| POS receipts with promotion ID per line | POS data warehouse | Warehouse retention policy | Often kept for years for tax and audit | CFO or controller |
| Finance corrections and credits | ERP general ledger and AR | Statutory period ends | Kept at least the tax period, often longer | CFO |
The crux is the second row. Whether two offers were allowed to stack is a configuration fact: in Shopify, for example, each discount carries its own Combinations setting that decides which discount classes it can combine with. If the configuration in force on the day of the exception is gone, the receipt shows that two discounts applied but no longer shows whether they should have.
Illustrative timeline: an 18-month engine replacement
Illustrative and fictional. A 640-person specialty retailer with 85 stores decides to replace its promotion engine. The dates below are the company's, and the partner only asks about them.
- Month 0. Project approved. The old engine holds seven years of rule versions and a change log with editor names.
- Month 4. Data migration scope agreed: active promotions and the next season's calendar. Historical rule versions are not in scope.
- Month 9. Pilot stores move to the new engine. Store override notes in the pilot stores now sit in two systems.
- Month 14. All stores cut over. The old engine is set to read-only for 90 days, and override notes in the old store log are not carried into the new system.
- Month 17. Old engine licenses lapse. Rule versions and the change log are unreadable unless someone kept them.
- Month 24 and beyond. Receipts with promotion IDs and finance corrections remain in the warehouse and ERP under the finance retention policy.
The window that matters runs from month 4, when migration scope is set, to month 17. After that the company may still hold every receipt and every credit, but the rule that explains them is gone. A partner who hears "we are replacing the promotion engine next year" has heard the most useful date in the conversation.
Why the tax retention floor does not protect the rule history
Retention rules exist, but they cover a different set of records. In the U.S., the IRS ties retention to the period of limitations: generally 3 years, 6 years where more than the greater of $50,000 plus 5% and 15% of gross income was left off a return, and 7 years for worthless securities or bad debt claims, with insurers or creditors sometimes requiring longer. A UK limited company must keep records for 6 years from the end of the last financial year they relate to.
Those rules keep the money trail: receipts, credits and ledger entries. They rarely reach a promotion engine's change log or a store manager's note explaining why an override was given. That is why the timeline above has two speeds. Finance records stay because they must; operational context stays only if someone with authority decides to keep it.
| What survives on the tax clock | What depends on a company decision |
|---|---|
| POS receipts and their discount lines | Dated rule versions and combination settings |
| Credits, refunds and ledger corrections | Change log entries with editor and time |
| Supplier-funded promotion settlements in finance | Store override reasons and manager notes |
Supplier-funded promotions often end up in deductions management, which keeps its own trail of claims and settlements.
Who must approve keeping each record
Access is not authority. The IT team running the cutover can technically export the old engine, but the decision to keep promotion history belongs to the executives who own those records, and the decision to discuss licensing it belongs to the CEO.
- Merchandising or pricing director owns the rules and can say which promotion history matters to the business.
- CIO or IT director owns the engine and the migration scope, and knows the real switch-off date.
- Retail operations director owns store practice and knows where override reasons are written down.
- CFO or controller owns receipts and corrections, and usually the retention policy for both.
- CEO, or the owner-CEO in an owner-run company, is the person who can authorize a licensing discussion and sign.
Do not recommend keeping or exporting anything. The company may have good reasons to let records expire, including privacy commitments to loyalty members.
What to note for the introduction, and what stays unknown
Stay at metadata level: what exists, how many years, which system, who owns it, and the dates. A partner never asks for receipts, rule exports or override notes.
- The read-only and switch-off dates for the old system, as the company states them.
- Whether historical configuration is inside or outside the migration scope.
- Which of the five record types the finance retention policy already covers.
- The executive who can authorize a licensing discussion.
What stays unknown until SourceX reviews it: whether the record types can be joined in practice, how customer identifiers would be removed, which agreements limit use, and whether any buyer wants the record type. How the links between receipt, rule version and correction work is covered in promotion exception handling records across systems, and the one-page handoff is the promotion exception handling referral brief template. Retailers in a wider system change can also read the guide to an ERP replacement, and the sector view is on the retail operations page.
The company also 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.
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 you advise has a promotion engine cutover on its calendar and still holds dated rule versions, register as a partner, check the company against who qualifies and read the terms before you introduce the executive who owns those records.