Logistics and distribution
Antitrust and price histories: can distributors share pricing data safely?
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
Distributors can often share pricing data with an AI developer at lower antitrust risk when the data is historical, aggregated or de-identified, and contractually barred from reaching competitors. Risk rises with recency, granularity, identifiability and a recipient that serves rivals. Information-exchange guidance has shifted, so counsel should assess each license before any price history leaves the company.
Key takeaways
- The antitrust concern with price histories is that competitively sensitive information reaches competitors, directly or through an intermediary.
- Older agency safe-harbor rules of thumb on information exchange no longer work as a shield, so each exchange is judged on its facts.
- Recency, granularity, identifiability, the recipient and the permitted use are the main risk factors to assess.
- Sales reps' notes about competitor quotes are often the most sensitive pricing records a distributor holds.
- License terms that bar disclosure to competitors and use for competitor pricing reduce risk but do not replace design choices in the data itself.
Why price histories raise antitrust questions#
Price histories raise antitrust questions because sharing competitively sensitive information can help competitors coordinate, even when no one agrees on a price. The Sherman Act and similar state laws reach agreements that restrain trade, and courts and agencies have long treated some exchanges of current or future pricing among competitors as evidence of, or a vehicle for, such agreements.
Licensing data to an AI developer is not, by itself, an exchange with a competitor. The question is where the data goes next. If a developer pools pricing histories from several distributors and then sells pricing recommendations back to those same distributors, the developer can become a hub through which competitors' information flows. Recent lawsuits over shared pricing algorithms have made that hub-and-spoke concern concrete.
Distribution is a setting where these concerns sharpen. Many distributors sell overlapping lines from the same manufacturers into the same local markets, buying groups already share some information among members, and pricing tools often come from a small number of vendors. Each of those facts makes it more important to know where a licensed dataset could travel.
What has changed in information-exchange guidance#
Information-exchange guidance has shifted in recent years. Federal agencies withdrew older policy statements that had described safety zones for exchanges of aged, aggregated data managed by a third party. Those rules of thumb remain useful as factors, but they no longer carry an agency safe harbor.
The practical effect for a distributor is that no single feature, such as data age or the number of contributors, settles the question. Counsel looks at the whole arrangement: what the data reveals, who can see it, what the recipient does with it and whether competitors could use the result to align prices. Check the current state of agency guidance and case law at the time of any license.
Risk factors: recency, granularity, identifiability and recipient#
Antitrust risk in a pricing data license depends on a handful of factors that work together. A dataset can be old but so granular that it reveals current pricing structure, or aggregated but delivered to a recipient that advises competitors.
| Factor | Higher risk | Lower risk | Question to ask |
|---|---|---|---|
| Recency | Current or recent prices, pending increases, future price plans | Historical prices that no longer reflect current terms | Could a competitor act on this today? |
| Granularity | Net price by customer, SKU and date | Aggregated by product family, region and period | Does the detail reveal our pricing method? |
| Identifiability | Named customers, suppliers and the distributor itself | Identities removed and rare combinations suppressed | Could a reader work out who we are or who we sell to? |
| Recipient | A firm that advises or sells pricing tools to our competitors | A developer using the data only to train or test general models | Who else does this recipient serve? |
| Permitted use | Use to set or recommend prices for other distributors | Use limited to model training or evaluation | What does the license allow? |
| Pooling | Combined with competitors' data and shared back | Kept separate or used only in aggregate across many sources | Will outputs reflect our data to rivals? |
Which pricing records distributors hold#
Distributors hold pricing records in more places than the price file. Each type carries a different level of sensitivity, and some raise contract issues as well as antitrust ones.
- Price lists and matrix pricing by customer class, usually the least sensitive when historical.
- Customer-specific contract pricing and bid pricing, which reveal negotiated terms.
- Quotes with win and loss outcomes, which reveal how the distributor competes.
- Manufacturer special pricing agreements and ship-and-debit claims, which are often confidential under supplier agreements.
- Price overrides and margin exceptions with reason codes from the ERP.
- Cost, rebate and landed cost records, which reveal margin.
- CRM and email notes in which reps record what a competitor quoted, often the most sensitive of all.
Safer practices for licensing price histories#
Safer practices combine design choices in the data with restrictions in the license. Design choices come first, because contract terms only govern what the recipient promises to do, while data design limits what the recipient can learn.
On the data side, counsel commonly considers removing customer, supplier and distributor identities, lagging the data so it no longer reflects current terms, aggregating where detail adds risk without adding value, and excluding competitor price notes and forward-looking pricing plans altogether. On the contract side, the license can bar disclosure to competitors, bar use to set or recommend prices for other distributors, prohibit re-identification and require deletion at the end of the term.
Manufacturer agreements need their own review. Special pricing agreements and rebate programs often carry confidentiality terms that limit disclosure regardless of antitrust analysis.
Document the reasoning. A short memo recording what was excluded, how the data was lagged and aggregated, and why the recipient and use were acceptable helps if questions arise later, and it gives the next license a starting point.
Illustrative: an electrical distributor scopes a pricing dataset#
Illustrative: a fictional electrical distributor runs its business on an Epicor ERP and a CRM where outside sales reps log quotes and call notes. An AI developer building quoting assistants is interested in its quote history, including win and loss outcomes and the reasons recorded for each.
The general counsel works through the risk factors with outside antitrust counsel. Competitor price mentions in CRM notes are removed entirely, and manufacturer special pricing records are excluded pending supplier review. Quotes are lagged, customers are replaced with industry and size bands, and prices are expressed as relative discounts rather than net figures. The license limits use to model training and evaluation and bars use in pricing services offered to other electrical distributors. The CEO approves the narrower scope.
How SourceX handles pricing data#
SourceX treats pricing histories as a rights-sensitive package within the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. The fit check uses metadata only, so no prices are shared during the initial assessment.
Where pricing records are in scope, the Rights step expects the distributor's counsel to assess antitrust and contract questions, and Preparation applies the agreed lagging, aggregation and redaction. The SourceX Evidence Packet records permitted use and restrictions alongside provenance, the privacy record and release authorization. The distributor approves every step and keeps ownership, since the data is licensed, not sold.
Frequently asked questions
Is licensing price data to an AI developer the same as sharing it with a competitor?
Usually not, because the developer is not a competitor. The risk arises if the data, or outputs derived from it, can reach competitors or influence their pricing. That is why the recipient's other customers, the permitted use and any pooling of data across distributors matter so much in the analysis.
Are list prices safe to share because they are already public?
Published list prices generally carry less risk than net prices, but distributors rarely sell at list. The sensitive parts are discounts, customer-specific terms, margin and any signal about future pricing. A dataset of list prices joined to actual transaction prices is far more revealing than list prices alone.
Can we use our own pricing history to train an internal AI pricing tool?
Using your own data for your own pricing generally raises different questions from sharing it. The concern returns when a vendor pools your data with competitors' data or offers recommendations informed by it to rivals. Read vendor terms on data use and pooling carefully, and involve counsel when they are unclear.
What should a pricing data license say?
At a minimum, counsel typically looks for a defined permitted use, a bar on disclosure to competitors, a bar on using the data to set or recommend prices for others, a prohibition on re-identification, security requirements, deletion at the end of the term and audit rights. Terms are tailored to each license.
Do tariff-driven price increases change the analysis?
They can make recent pricing more sensitive. When many distributors are adjusting prices for the same cost changes, sharing current increase plans or timing carries obvious risk. Historical records of past increases, aggregated and lagged, are usually easier to assess.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.