Logistics and distribution
Order guides and customer order history: who owns them in foodservice?
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
Foodservice order guide data is split rather than owned outright by one side. A restaurant controls its own purchasing information and can take a copy of what it bought, while the distributor controls the records it creates: item setups, cost and margin, substitutions, delivery and credit history, and rep notes. Customer agreements and ordering portal terms decide the edges.
Key takeaways
- An order guide is a shared working document; the restaurant's choices and the distributor's item records sit side by side in it.
- A switching restaurant can usually take its order guide and invoice history, but not the distributor's cost, margin or internal notes.
- Ordering portal terms and chain or group purchasing contracts often say more about data use than a street account's paperwork does.
- Order history becomes far more useful when it stays linked to substitutions, shorts and credits.
- Any reuse of order history beyond serving the customer should remove customer identity and pricing and be checked against written agreements.
Who created each part of an order guide?#
An order guide is built by both sides: the restaurant decides what it buys and how much, and the distributor supplies the item records, pricing and fulfillment history around those choices. Ownership questions get easier once each element is traced to whoever created it.
The table separates what a restaurant customer typically sees from what stays inside the distributor's systems.
Par levels show the split well. The chef sets them, so they reflect the menu and the walk-in cooler, but a suggested-order feature may adjust them using the distributor's own demand data. Keep track of which figure came from which side if a guide is ever exported or analyzed.
| Record | What the restaurant sees | What the distributor holds |
|---|---|---|
| Order guide item list | Items it buys, pack sizes, its own sort order and par levels | Item master, brand alternatives and the reasons items were added |
| Pricing | Its invoice prices and any agreed deviations | Landed cost, margin, rebates and price change history |
| Order history | Its past orders and invoices | The same orders linked to other accounts, routes and seasons |
| Substitutions and shorts | Notices on the invoice or in the portal | Why the substitution was made and what alternatives existed |
| Credits | Credit memos it received | Reason codes, route, picker and root cause |
| Rep and service notes | Usually nothing | Visit notes, menu changes, competitive intelligence |
| Forecasts | Suggested orders, if the portal offers them | Demand models and purchasing plans built on many accounts |
What can a restaurant take when it switches distributors?#
A restaurant switching distributors can usually take its order guide and its own purchase history, because those describe what it bought and what it paid. Many ordering portals let a customer export the guide, and invoices are the customer's records as much as the distributor's.
What does not travel is the distributor's internal layer: cost and margin, rebate income, rep notes, credit root causes and any forecasting built across many customers. The new distributor rebuilds the guide by mapping items to its own catalog, often using the export and recent invoices as the starting point.
Street accounts rarely sign anything that addresses the question. Where nothing is written, distributors generally treat portability as a customer service question and their internal records as confidential business information.
What customer agreements and portal terms decide#
Customer agreements and ordering portal terms decide whether either side can use order data beyond the relationship. A chain or contract account agreement may define pricing and purchase data as the customer's confidential information, while portal terms of use often grant the distributor rights to use usage data to operate and improve its services.
When reviewing these documents, look for:
- Confidentiality clauses that cover pricing, volumes or purchase history, and whether they run in both directions.
- Portal terms on who owns content the customer enters, such as custom item names, pars and notes.
- Rights to use aggregated or de-identified usage data across customers.
- Termination terms on exporting or deleting customer data.
- Group purchasing or chain program terms that restrict sharing contract pricing or volumes.
- Audit rights that let a chain customer verify pricing, which can require keeping history for set periods.
Why order history matters to AI ordering tools#
Order history matters to AI ordering tools because suggested orders, substitution prompts and demand forecasts all learn from what kitchens actually bought, when and in what quantity. The same records interest AI developers building assistants for distribution and purchasing work more broadly.
Order lines alone are the weakest form. The useful version keeps each order linked to what happened next: the substitution offered when an item was out, whether the customer accepted it, the short that triggered a credit, and the menu change a rep noted the week before purchases shifted. Those links show decisions, not just transactions.
That is also why distributors should be careful. The linked version contains the most customer detail, so any use beyond serving that customer needs identity, pricing and free-text notes handled before anything leaves the company.
Illustrative: a restaurant group asks for all of its data#
Illustrative: a fictional produce and specialty foods distributor sells to chef-owned restaurants and one small regional restaurant group, taking orders through reps and an online ordering portal. The restaurant group decides to consolidate purchasing with another supplier and asks for all of its data.
The distributor's general counsel checks the group's supply agreement, which treats pricing and purchase volumes as the group's confidential information but says nothing about the distributor's internal records. The team provides an order guide export and invoice history, and declines to share margin data, rep notes and credit root causes, citing them as the distributor's confidential business records.
Later, when the distributor considers whether its order histories could be licensed, it excludes the group's records entirely because of the confidentiality clause. For street accounts with no written terms, it plans to remove customer names, addresses, prices and rep notes, and to keep only item categories, quantities, dates, substitutions and credit reasons.
Rules of thumb for distributors#
Distributors can handle most order data questions with a few defaults, then let written agreements override them where they exist.
Write the defaults down. A one-page internal policy naming who may approve a customer export, what it includes and what is withheld keeps reps from promising a departing account more than the business intends to share, and it gives counsel a consistent baseline when a request arrives in a hurry.
| Question | Default answer | When it changes |
|---|---|---|
| Can the customer export its order guide? | Yes, as a service courtesy | Rarely restricted; check portal terms |
| Must we share our cost or margin? | No | Cost-plus agreements with audit rights |
| Can we use one customer's history to advise others? | Only as aggregated, unattributed insight | Confidentiality clauses that bar any use |
| Can we reuse order history outside the business? | Only after rights review and de-identification | Chain or group contracts that forbid it |
| Do rep notes go to the customer? | No | A customer dispute or legal request |
How SourceX treats customer order history#
SourceX treats customer order history as the distributor's operating record only after the Rights step of the SourceX five-step transaction confirms that no customer agreement forbids its use. Supply, Rights, Preparation, Approval and Delivery each need the distributor's sign-off.
In Preparation, customer names, addresses, prices and free-text notes are removed or coded, and the SourceX Evidence Packet records provenance, licensing rights, permitted use, the privacy record and release authorization, including which customer contracts led to exclusions.
Frequently asked questions
Is a restaurant's order history its trade secret?
It can be confidential to the restaurant, especially when it reveals menu mix, volumes or pricing. Whether it is legally a trade secret depends on the facts and on how the restaurant protects it. Distributors should treat customer-identifiable purchase data as confidential regardless and keep it inside the relationship unless written terms say otherwise.
Should our customer terms address order guide portability?
It helps. A short clause saying the customer may export its order guide and invoices, while the distributor's cost, margin and internal notes remain confidential, prevents arguments at the end of a relationship. Pair it with a data use clause covering aggregated, de-identified analysis, reviewed by counsel.
Who owns custom item names and pars a chef typed into our portal?
Content a customer enters, such as its own item names, par levels and notes, is usually treated as the customer's information, and portal terms often say so. The distributor may still use it to fulfill orders. Exporting it back to the customer on request is normal; using it for anything else needs a look at the portal terms.
Does a group purchasing organization contract change anything?
It can. GPO agreements may include their own confidentiality and data reporting terms, and member restaurants may be covered by them even when they buy through a distributor directly. Read the GPO agreement and the distributor's participation terms before using member purchase data for anything beyond fulfillment and required reporting.
Can we keep a former customer's order history?
Generally, yes, as part of the distributor's business records, subject to any agreement requiring return or deletion and to tax and accounting retention needs. Keeping it is different from reusing it; any new use of a former customer's identifiable history should go through the same rights review as a current customer's.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.