Roofing
$450,000
Roofing company
Exclusive · perpetual · full operating record
Your orders, returns and tickets show how a store makes its calls.
Running a store means applying policy to messy cases all day: the order that needs a new address, the return that's two days late, the reorder placed before a promotion, the ticket that turns into a refund. AI teams building commerce agents need years of those decisions with the result attached, and the customer taken out. We take an anonymized summary of your record to several buyers at once, and you choose the license.
Small commission on close. Nothing up front.
Usually held in
- Shopify
- BigCommerce
- Adobe Commerce (Magento)
- Square
- Lightspeed
- Gorgias
- Zendesk
- Klaviyo
- NetSuite
- Extensiv (3PL Central)
What buyers pay for in retail and e-commerce.
Buyers value records that show a decision and what came of it more than they value finished paperwork. These are the parts of your record they look for.
Orders and order changes
Edits, cancellations, split shipments, address fixes and fraud holds, with the rule that was applied and what happened next.
Returns and exchanges under policy
Each request, the policy decision, the exceptions granted and whether it ended in a refund, an exchange or store credit.
Support tickets and macros
Full conversations with agent replies and resolutions, plus the macros and policy notes agents worked from. Customer details come out before delivery.
Inventory, purchasing and replenishment
Stock levels, reorder decisions, supplier purchase orders and stockouts. Long-horizon decisions with a measurable result are what synthetic stores can't supply.
Pricing, promotions and merchandising
Price changes, promotion calendars and catalog edits, set against how sales moved in aggregate.
Store and fulfillment operations
Point-of-sale activity without card data, store transfers and the tickets raised with warehouses and 3PLs.
Systems that hold it and what to watch for.
This is where the record usually lives. Where we've written a data guide for a system, its card links to it, with steps to find out how much you have.
- ShopifyE-commerce and point of saleRead the data guide
- BigCommerceE-commerce and point of sale
- Adobe Commerce (Magento)E-commerce and point of sale
- SquareE-commerce and point of sale
- LightspeedE-commerce and point of sale
- GorgiasCustomer support
- ZendeskCustomer supportRead the data guide
- KlaviyoEmail and SMS marketing
- NetSuiteERP and financeRead the data guide
- Extensiv (3PL Central)Transportation, warehouse and fleet
Who buys it and what they do with it.
We describe buyers by category and don't publish their names. Each one is qualified and under NDA before seeing your summary, and when they bid you see every offer side by side, with exclusivity, term and payment next to the price.
Customer-service agents for commerce
Companies building AI that handles order changes, returns and where-is-my-order questions under a store's policy. Real tickets with outcomes show them where the policy bends.
Inventory, pricing and forecasting AI
Teams modeling demand, reorder points and markdowns. Years of purchasing and inventory decisions, with what followed, are the check on their models.
Shopping and store-operations agents
Agent builders training on the admin work behind a store: editing listings, updating stock, setting up promotions and answering suppliers.
AI labs testing long-horizon business tasks
Labs and evaluation builders that want to see whether an agent can run a store over months. A real store's record gives them ground truth.
What a package looks like to a buyer.
Before anyone signs, a buyer sees a summary shaped like this one. It is built from rounded ranges: no name, no website, no people, no addresses.
The numbers in this example are made up. Yours come from your intake and the review call, and you read the summary before any buyer does.
See the full processExample package · Retail
Illustrative- Sector
- DTC home goods brand with a flagship store
- Region
- US-wide shipping
- History
- 7+ years, continuous
- Record
- ~200K orders, ~20K support tickets, ~10K returns
- Mix
- ~90% online, ~10% in store
- In scope
- Order and return workflows, support tickets, inventory and purchasing history
- Left out
- Customer identities, individual purchase histories, card data, loyalty profiles
What stays out by default.
Some records aren't yours to license, and some shouldn't leave the building. Intake and the review call bring these up early. The main ones for this industry are below.
Customer identities and purchase histories
Names, emails, addresses and phone numbers are removed before delivery under the license, and individual purchase histories and loyalty profiles stay out. Several state privacy laws treat data as de-identified only with reasonable safeguards, a public commitment not to re-identify it and contracts binding recipients, such as California Civil Code §1798.140(m).
Payment card data
Card numbers and other cardholder data fall under the card industry's security standard (PCI DSS). They never come into scope.
Children's data
Brands that collect personal information online from children under 13 are covered by COPPA (16 CFR Part 312). That information is excluded.
Marketplace and supplier data
Orders fulfilled through a marketplace come under that marketplace's own data rules, which can limit what you may do with buyer details. Supplier cost agreements are often confidential. We check those terms during review and leave out what you can't relicense.
This is not legal advice. Whether a record can be licensed depends on your contracts, your software terms and how it was collected, and your counsel should review any license before you sign. The rules named on this page are linked under Sources.
Licenses in our network closed by buyers, not by us.
Recent licenses of operating records, closed by buyers in our network. They come from trades and services businesses rather than this industry, so read them as a sense of the market and nothing more.
Construction
$300,000
General contractor
Exclusive · 24-month term · full operating record
Solar
$275,000
Solar company
Exclusive · 18-month term · full operating record
Marketing
$110,000
Agency with global clients
Exclusive · 24-month term · full operating record
Licenses closed by buyers in our network, shown to describe the market. They are not deals thedata.broker brokered and not a forecast of what your record will bring. Every record is priced on its own.
Retail and e-commerce questions worth settling early.
More in Answers, or ask us on a call after your intake.
No. Buyers want to see how the business runs: how orders were changed, how returns were decided, how stock was reordered and how tickets were resolved. Customer identities and individual purchase histories stay out, and the license can bar the buyer from trying to re-identify anyone.
Yes. FTC staff have warned that quietly changing a privacy policy after the fact to allow new uses, such as AI training, can be unfair or deceptive under Section 5 of the FTC Act (15 U.S.C. 45). What your policy said when the data was collected matters, so we read it on the review call. This is not legal advice; have counsel review it.
Support tickets and chats usually can, with customer details removed. Recorded calls depend on how callers were told, since some states require everyone on a call to agree (for example California Penal Code §632). A license can use redacted transcripts instead of audio. This is not legal advice.
Sometimes. Marketplace terms often limit how sellers may use buyer information, so those orders may need to stay out or be reduced to aggregate counts. Records from your own storefront are usually simpler. We check the terms during review.
Yes. Point-of-sale activity without card data, purchasing and inventory decisions, transfers between locations and the tickets raised with suppliers all show how the business runs. Customer identities, card data and staff HR records stay out.
We are paid a small commission out of a deal that closes. If nothing closes, you owe nothing. You keep ownership of your records and keep using them.
Sources
Primary sources for the rules this page names. Summaries above are not legal advice.
- Cal. Civ. Code 1798.140: CCPA definitions, including deidentified (opens in a new tab)
- PCI DSS: card industry data security standard (opens in a new tab)
- 16 CFR Part 312: children's online privacy (COPPA rule) (opens in a new tab)
- 15 U.S.C. 45: unfair or deceptive acts or practices (opens in a new tab)
- FTC Office of Technology, "AI (and other) Companies: Quietly Changing Your Terms of Service Could Be Unfair or Deceptive" (Feb. 13, 2024) (opens in a new tab)
- Cal. Penal Code 632: recording confidential communications (opens in a new tab)
Not quite your business?
See every industry we take on, the business functions buyers ask for, and which records need special handling.