FMCG · Running an audit trail for promotional and pricing data
At 11:58pm, a category manager at a household goods company pushes a price change for a laundry detergent SKU across 900 stores. Two minutes later, the shelf-edge label system, the e-commerce site, and the retailer's EDI (Electronic Data Interchange) feed all need to agree on the same number. If they don't, a shopper gets overcharged, a regulator gets a complaint, and someone has to explain why. This lesson traces the checks that should have happened long before that midnight push.
Why pricing data needs its own audit trail
An audit trail is a time-stamped record of who changed what, when, and why. For pricing and promotions, every price change, discount, and promotional flag needs a traceable chain: request, approval, system update, and verification.
This matters for three reasons specific to FMCG (fast-moving consumer goods):
- Volume and speed. A large household goods company can run thousands of SKU-store-week price points simultaneously. Manual checking doesn't scale.
- Multi-system sprawl. Price lives in ERPERPA single integrated software backbone that runs core operations: finance, procurement, supply chain, HR and manufacturing on shared data.View full definition → (Enterprise Resource Planning) systems, trade promotion management (TPM) tools, retailer portals, and point-of-sale (POS) systems. Each is a place things can drift out of sync.
- Regulatory exposure. A single pricing error can breach consumer protection law and competition law at the same time.
The core regulatory backdrop
Resale price maintenance (RPM)
RPM is when a manufacturer tries to dictate or enforce the price a retailer charges consumers. In most jurisdictions this is treated as a serious antitrust violation.
- In the US, RPM is assessed under the Sherman Act, enforced by the Federal Trade Commission (FTC) and Department of Justice (DOJ). Since the 2007 *Leegin* Supreme Court decision, minimum RPM is judged under a "rule of reason" rather than being automatically illegal, but it remains high-risk and many states still treat it more strictly.
- In the EU, RPM is treated as a "hardcore restriction" under Article 101 of the Treaty on the Functioning of the European Union (TFEU) and the Vertical Block Exemption Regulation (Regulation 2022/720). It is presumed illegal, enforced by the European Commission and national competition authorities.
Why this belongs in a data lesson: compliance depends on being able to prove, from system logs, that "suggested retail price" communications to retailers were advisory and that sales reps did not pressure or monitor retailers into compliance. That proof comes from audit trails of pricing communications and CRMCRMCustomer Relationship Management: software and strategy to manage and analyse customer interactions throughout their lifecycle.View full definition → (Customer Relationship Management) notes, not from memory.
Consumer pricing and labeling rules
- US: The FTC Act prohibits unfair or deceptive pricing practices. Many states also have unit pricing and item pricing laws (for example, requiring price-per-ounce on shelf labels).
- EU: The Price Indication Directive (98/6/EC) requires unit pricing. Since 28 May 2022, the Omnibus Directive ((EU) 2019/2161) has added Article 6a: any announced price reduction must show the prior price, defined as the lowest price charged in the previous 30 days. This applies in every member state, enforced by national consumer protection authorities. The Commission's guidance on Article 6a) covers edge cases such as progressive discounts and newly launched products.
- UK: Under the Digital Markets, Competition and Consumers Act 2024, the CMA can directly fine businesses up to 10% of global turnover for unfair commercial practices, including misleading reference prices. These powers have been in force since April 2025. Misleading "was/now" pricing is a long-standing enforcement target.
A shelf-edge label showing "was £5.00, now £3.50" when the lowest price in the past 30 days was £4.00 is a data governancedata governanceData governance is the set of policies, roles, and processes that ensure data is accurate, secure, well-defined, and used responsibly across an organization.View full definition → failure with legal consequences. It is more than a display bug.
Mapping the data flowdata flowAn automated sequence of steps that moves data from source to destination: ingestion, transformation, validation, and loading, so it arrives clean and ready to use.View full definition → before it goes live
Before any price or promo change reaches the shelf, it typically moves through:
- Request: category or trade marketing team proposes a price or promo (e.g., "20% off, 2 weeks, 400 stores").
- Approval: pricing governance committee or finance sign-off, checked against margin floors and legal constraints.
- System entry: input into the TPM or ERP master pricing table.
- Propagation: sync to POS, e-commerce catalog, retailer EDI feed, and shelf-label systems.
- Verification: a check that what's live matches what was approved.
Each handoff is a place where the audit trail should capture: timestamp, user ID, old value, new value, and approval reference.
A simple structure for a pricing change log
change_id | sku_id | store_group | old_price | new_price |
lowest_price_30d | requested_by | approved_by | approval_ts |
system_ts | promo_flag | rpm_review_flag | live_verified_tsThree fields deserve attention. lowest_price_30d is the reference price an EU discount claim must use. rpm_review_flag records whether legal or compliance confirmed the change isn't crossing into RPM territory, especially in retailer-facing communications. live_verified_ts is the timestamp when someone or something confirmed the price appeared correctly in-store or online, closing the loop.
Checks that catch errors before shelf edge
Practical, concrete checks a governance team runs:
- Reconciliation check: does the price in the ERP match the price in the retailer's EDI feed and the e-commerce listing? Mismatches often surface first as customer complaints, not internal alerts, unless this is automated.
- Threshold check: any price change beyond a set percentage (e.g., more than 15% in a week) auto-flags for a second approver. Catches fat-finger errors, like a decimal point shift turning $4.99 into $0.49.
- Promo overlap check: does this SKU already have an active promo in that store group? Stacking unintended discounts is a common and costly error.
- Reference price check: for "was/now" claims, does the system hold the full price history, so it can compute the lowest price in the prior 30 days (EU) and justify the reference price (UK, US)?
- RPM language audit: sampling retailer-facing emails, rep call notes, and portal messages for language that could read as "you must sell at X" rather than "we suggest X."
- Segregation of duties: the person requesting a price change should not be the same person approving it. This is a standard control borrowed from financial audit practice.
A minimal automated check (illustrative)
# Flag price changes missing an approval reference, exceeding threshold,
# or making a discount claim against the wrong reference price
def flag_pricing_risks(change):
flags = []
if change["approved_by"] is None:
flags.append("missing_approval")
pct_change = abs(change["new_price"] - change["old_price"]) / change["old_price"]
if pct_change > 0.15:
flags.append("large_change_needs_second_approval")
if change["promo_flag"] and change["rpm_review_flag"] is None:
flags.append("rpm_review_required")
if change["promo_flag"] and change["old_price"] > change["lowest_price_30d"]:
flags.append("reference_price_above_30d_low")
return flagsThis isn't production code. It is the logic a governance dashboard should run on every batch of price changes before go-live.
Knowledge check
1. Why is a traceable audit trail (request, approval, system update, verification) especially critical for pricing and promotional data in FMCG, rather than just good practice in general?
2. A manufacturer's sales rep tells a retailer, 'If you sell our detergent below $X, we'll stop supplying you.' What concept does this scenario most directly illustrate?
3. Since the Leegin decision, how is minimum resale price maintenance treated under US federal antitrust law?
4. Select ALL correct answers about why pricing data is prone to drifting out of sync across systems in a large FMCG company.
Select all the correct answers.
5. Select ALL correct answers about the potential consequences when pricing data across systems (e.g., shelf-edge labels, e-commerce site, retailer EDI feed) fails to match.
Select all the correct answers.
Who owns this in practice
At most household goods companies, no single team owns the full chain. That's the problem the audit trail is meant to solve.
- Trade marketing / category management: originates price and promo requests.
- Finance / pricing governance: approves against margin and policy.
- Legal / competition compliance: reviews RPM exposure, especially for supplier-retailer pricing communication, and reference price rules for consumer-facing claims.
- IT / data governance: owns the systems of record and ensures logs are complete, immutable, and retained per policy.
- Internal audit: periodically samples the trail to confirm controls actually worked, not just that they exist on paper.
A useful external reference for how competition authorities think about pricing algorithms and data more broadly is the OECD's work on algorithms and collusion. It is relevant as more FMCG pricing becomes automated.
🎬 [VIDEO: "How Retail Pricing Algorithms Work (and Where They Get Risky)" - https://www.youtube.com/results?search_query=retail+pricing+algorithms+antitrust+risk - Search results for explainer videos on dynamic pricingdynamic pricingAutomatically adjusting prices in real time based on demand, competition or user behaviour to optimise revenue, margin or conversion.View full definition → systems and the competition law risks they raise, useful for seeing how automated repricing tools intersect with RPM concerns]
Key Takeaways
- An audit trail for pricing is a structured, timestamped record of request, approval, system entry, and verification. A general sense that "someone checked it" does not count.
- RPM (resale price maintenance) is treated as high risk in the US (Sherman Act, FTC/DOJ, rule of reason since *Leegin*, 2007) and presumed illegal in the EU (TFEU Article 101). Audit trails of retailer-facing pricing communications are the evidence base for compliance.
- Across the EU since May 2022, any announced discount must reference the lowest price of the prior 30 days (Article 6a of the Price Indication Directive). Systems need full price history, not just current and previous price. In the UK, the CMA can fine directly for misleading pricing since April 2025.
- Concrete checks (reconciliation across systems, threshold flags, promo overlap detection, reference price validation, segregation of duties) catch errors before they reachreachThe number of unique people exposed to your message in a given period. Unlike impressions, reach counts each person once, no matter how often they see it.View full definition → the shelf edge, where they become customer-facing and regulator-visible.
- Ownership is cross-functional: trade marketing, finance, legal, IT, and internal audit each hold a piece. The audit trail stitches their actions into one traceable chain.