What Is Scan-Down? Retail Promotion Funding Explained

Scan-Down A promotion funding method based on point-of-sale units scanned during a defined promotional period. In practice, a supplier agrees to fund (fully or partially) a retailer’s promotional activity by reimbursing the supplier-to-retailer payment based on the number of units actually scanned at the point of sale while the promotion runs. This ties promotional spend to verified consumer purchases rather than to shipped or stocked quantities.

Scan-down programs shift the measurement trigger from invoice or shipment events to real-world scanning events captured by the retailer’s point-of-sale (POS) system. The supplier typically supplies product at a negotiated price or funds discounts, and then reconciles payments using POS scan records over an agreed time window and SKU set. For retailers and suppliers, the goal is to better align promotional payments with incremental consumer demand.

What Scan-Down Covers

Scan-down agreements are defined precisely in the contract. Typical elements include the eligible SKUs, promotion start and end dates, qualifying price points or basket conditions, data reporting format, and reconciliation cadence. The method covers:

• Eligible Units: Specific UPCs/SKUs that qualify for the promotion and the unit measures (each, case, weight).
• Promotion Window: The exact start and end timestamps used to select POS scans for reconciliation.
• Payment Terms: The per-unit funding rate or percentage discount the supplier will provide for each scanned unit.
• Data Requirements: The POS extract, file layout, transmission frequency, and any anonymization or privacy constraints.

Why Retailers And Suppliers Use Scan-Down

Scan-down reduces disputes about whether a promotion actually drove consumer purchases by using the retailer’s own sales records as the truth source. Retailers favor it because they only give up margin when customers buy during the promotion; suppliers favor it because funding is tied to measurable lift rather than to inventory placed on shelf. Scan-down can also accelerate reconciliation if data flows are automated.

How Scan-Down Agreements Typically Vary

Programs differ by complexity and risk-sharing. Variations include whether the supplier pays for incremental units only (lift over baseline) or for all scanned units, whether returns/voids are excluded, and how baseline sales are calculated. The supplier may accept a flat per-unit rebate, a percentage of retail price, or a tiered structure that pays at different rates as scanned units cross thresholds.

• Baseline Method: Baseline can be historical average sales for the same weeks in prior years, rolling weeks prior to the promotion, or a statistical baseline agreed in the contract.
• Lift Versus Absolute: Some deals reimburse only the incremental lift; others reimburse all sales during the period but at a lower rate.
• Return/Void Handling: Contracts usually exclude transactions later voided or returned; the process for identifying and subtracting these is specified.

Who Pays And Who Provides Data

Under scan-down the supplier is the funding party; the retailer provides the POS data. Both parties must agree on the data format and the delivery method (secure FTP, EDI, API). Large retailers may supply the raw transaction-level file while smaller chains provide aggregated weekly scans by store and SKU. Data governance and privacy clauses define how sales data is used and protected.

Practical Example

Supplier X and Retailer Y agree a two-week promotion for SKU 12345. The supplier will reimburse $0.50 per unit scanned. Retailer Y supplies a POS extract after the promotion showing 10,000 scanned units at qualifying prices. The supplier pays $5,000 less any agreed deductions (voids, administrative fees) after an audit window. If a baseline/lift model were used — e.g., baseline 6,500 units — the supplier would reimburse for 3,500 incremental units, or $1,750.

Common Operational Challenges

Misaligned filters (price points, coupon stacking), data format mismatches, and timing differences are frequent causes of disputes. Retailers must ensure register overrides, price exceptions, and coupons are flagged correctly in the POS extract. Suppliers must have reconciliation teams capable of validating and tying POS records to invoiced product movement.

• Data Quality: Incomplete or incorrectly formatted POS files delay reconciliation and increase dispute volume.
• Fraud And Abuse: Circular coupons, label-swapping, or incorrect price overrides can inflate scanned units; audit clauses and sampling reduce risk.
• Systems Integration: Automated APIs or EDI reduce manual effort but require upfront IT alignment.

Tips For Successful Scan-Down Programs

• Define Everything In Contract: SKU lists, time windows (with time zone), baseline method, void handling, and dispute resolution steps.
• Agree On Data Format Early: Use a standard CSV/EDI layout with clear field definitions to avoid rework.
• Include An Audit Window: Allow for a short post-promotion audit period to correct returns and voids before final payment.
• Run Pilot Promotions: Pilot on a narrow set of SKUs or stores to validate data flows and reconciliation logic.
• Invest In Traceability: Ensure UPC/GTIN mappings are current and use GS1 standards for identifiers.

In short, the Scan-Down model ties promotion funding to actual consumer purchases recorded at the point of sale, improving alignment between supplier spend and retail performance. When contracts, data feeds, and audit procedures are well-defined, scan-down can reduce disputes and sharpen promotion ROI measurement; when they are not, reconciliation and fraud risk increase.