A wholesale agreement is one or two pages that say how a maker and a shop will do business: what's sold at what price, how orders and delivery work, when the shop pays, what can come back, and what happens if it goes wrong or ends. Most small makers start without one, on an email and a handshake, and that works until the first disagreement, which is nearly always about one of three things: returns of unsold stock, how fresh the goods were on arrival, or a late payment. Writing the answers down while everyone is friendly is the reason to have an agreement. Below are 16 clauses with example wording in plain English, the ones food makers forget, and a file to adapt. It's a starting point, not legal advice: have a lawyer read your version.
The short version
- Two pages, plain words, signed by both.
- Attach the price list. Say how much notice a price change gets.
- Say what can be returned. "Nothing unsold" is a fair answer if it's written.
- For food: shelf life on arrival, storage, and what happens in a recall.
- Say how either side ends it.
- TaroStack keeps the price list, the orders and the lots each shop received. More below.
The clauses
| Clause | What it settles | Example |
|---|---|---|
| 1 Parties | Who's agreeing, from when | The maker and the store, from December 1, 2026 |
| 2 Products and prices | The price list; notice of changes | Attached list; 30 days' written notice |
| 3 Ordering | How, by when, the minimum | By Tuesday noon for Monday delivery; 4 cases minimum |
| 4 Delivery | Who delivers; when goods become the store's | Free within 25 miles; the store's once signed for |
| 5 Checking the delivery | Shortages and damage | Reported within 2 business days, with photos |
| 6 Shelf life | Freshness on arrival | At least 90 days before best-by |
| 7 Payment | Terms; what happens when late | Net 30; first two orders on delivery; 15 days late pauses deliveries |
| 8 Returns | What comes back | Faulty goods only; unsold goods aren't taken back |
| 9 Storage and display | How the store looks after it | Cool and dry; oldest first; out-of-date removed |
| 10 Retail price | Who sets it | The maker suggests; the store sets its own |
| 11 Where it's sold | Shop, website, marketplaces | Own shop and site; no third-party marketplaces without agreement |
| 12 Recalls | Who does what | Lot codes the same day; store removes and counts; maker credits |
| 13 Name and photos | Use of the brand | As supplied, while the agreement lasts |
| 14 Insurance | Cover carried | Product liability; certificate on request |
| 15 Ending it | Notice | 30 days in writing; accepted orders completed |
| 16 Law and signatures | Which state's law | Named state; signed and dated by both |
The file has full example wording for each.
The clauses food makers forget
Shelf life on arrival. A shop that receives granola with three weeks left on it will mark it down or bin it, and then ask for credit. A line that says "at least 90 days before best-by on delivery" (or 10 days for bread, or half the product's life) settles that before it happens. Pick a number you can keep, because you'll be held to it.
Returns. There are three honest positions. No returns of unsold stock, which is usual for small food makers. A swap of unsold stock for fresh, which costs you the product. Or sale-or-return, where you own it until it sells, which costs you the product and the risk. Each can work. What doesn't work is not saying which.
Storage. If your chocolate blooms in a shop window or your kombucha is left out of the fridge, the customer blames your brand. One sentence on how the product is kept, and that out-of-date stock comes off the shelf, gives you something to point to.
Recalls. The clause nobody wants to write. It should say that you'll tell the store the lot codes the same day, that the store pulls and counts those lots and follows your instructions, and who pays for what. It only works if every case you ship has a lot code on it and you know which store got which lot. What to do when it happens is in recall plan example.
Where it's sold. A shop reselling your jam on a marketplace at a discount, stored who knows how, is a real problem for a small brand. Say where the store may sell.
Three clauses to be careful with
Retail price. Suggest one. Don't require it. Agreements that fix the price a retailer charges can raise legal problems, and the simple wording ("the maker suggests a retail price; the store sets its own") avoids them.
Exclusivity. A store may ask to be the only stockist in town. If you agree, put a boundary on it (a ZIP code, a radius), a minimum they have to buy to keep it, and an end date.
Payment terms. Net 30 is a loan to the store. Starting new accounts on payment at delivery for the first two orders is ordinary, and nobody good is offended by it. How the terms work is in net 30 terms.
How to use it
Fill in your own terms beside each clause, delete what doesn't apply, and turn it into a two-page document. Send it with your price list and order form when a shop says yes. Small shops will sign it as it is. Larger ones will send their own vendor agreement instead, and then this is your checklist for reading theirs: find each of the 16 answers in their document, and ask about the ones that are missing or that you can't live with.
The form a shop fills in to open an account is in wholesale account application form, the order form in wholesale order form template, and what to send a buyer first in line sheet template.
Get the template
Download the wholesale agreement template. Sixteen clauses, each with what it settles, example wording for a made-up granola maker and a shop, and a column for your own terms, plus a read-me. It's an ordinary Excel file with no macros, and it works in Google Sheets, LibreOffice and Numbers. It's general information, not legal advice.
Where this stops working
The agreement says 90 days of shelf life on arrival, net 30, and lot codes within a day of a recall. Keeping those promises is a different job from writing them. With twelve stores, someone has to know that the cases going to the corner shop on Monday have enough life left, that the co-op's October invoice is 20 days late, and which stores got lot 1104. On a spreadsheet of orders, each of those is a search.
How TaroStack does it
TaroStack keeps the promises in the agreement checkable.
A customer can carry its own shelf-life rule: the days of life that store must receive.
The soonest date ships first by default, so short-dated stock goes to the customers who can take it.
Sales orders, one picking list, delivery notes. The lots picked for each store are on the record.
One report for a recall. Which stores got lot 1104, on which delivery notes, and what's still on your shelf. Starting a recall holds the rest and gives it a number. The notice goes from your own mailbox.
Margins on what things actually cost, by product, so you know what the wholesale price leaves you.
| The promise | Order spreadsheet | In TaroStack |
|---|---|---|
| 90 days of life on arrival | Check each case by hand | A rule kept on the customer |
| Lot codes within a day | Go through delivery notes | One report |
| Oldest stock first | The packer's memory | By default |
| A price that leaves a margin | A guess | Margin on real cost |
TaroStack doesn't write contracts or chase payments. Customers, sales orders, lots and recalls are on every plan, from $9.99 a month. The first 14 days are free, with no credit card. If you'd like a hand setting up, ask, and we'll do it with you.
