In a tolling arrangement you own the materials, someone else owns the equipment, and you pay them a fee to turn one into the other. A farm sends taro to a mill and gets flour back. A roaster sends green coffee to a packer. What sets it apart from buying finished goods is that title never moves: the materials are yours going in, yours on the processor's floor, and yours coming out. Most of what a tolling agreement has to say follows from that one fact. Whose loss is it when the yield is short? Who insures your goods while they're in another company's building? Who can say which of your lots went into which run? Below are thirteen clauses to settle, an example for each, the three that cause the arguments, and a checklist.
The short version
- The owner keeps title to the materials and the finished goods throughout.
- The processor is paid a fee for the service: per unit, per batch or per hour.
- Agree a yield, a loss you'll both accept, and who bears loss beyond it.
- Agree what records come back with every run.
- Agree storage: how long, at what charge, and how goods are released.
- Agree who insures the owner's goods on the processor's floor.
- TaroStack keeps a client's own goods apart and bills the fee for making them. More below.
The clauses
| Clause | What to decide | This example |
|---|---|---|
| The parties and the service | Who owns the materials, who processes them, what the processing is | Kalo Farm owns the taro. Windward Roots mills and packs it |
| Title | That materials and finished goods stay the owner's at every stage | Title stays with Kalo Farm |
| What the owner supplies | Which materials, to what specification, delivered how and when | Peeled taro, to the agreed spec, two days before each run |
| What the processor supplies | Labor, equipment, and any materials of its own, at what price | Bags and labels at cost, as their own line |
| The fee | Per unit made, per batch or per hour; minimums; when it changes | $0.45 for each bag made; 400 bag minimum a run |
| Yield and loss | Expected yield, loss allowed, who bears loss beyond it | 92 percent expected. Loss beyond 10 percent is examined together |
| Specifications and testing | The finished spec, who tests, who releases | Moisture and bag weight each run; owner releases |
| Records | Batch records, lot codes, which of the owner's lots went into which run | A batch record for each run, sent with the invoice |
| Storage and release | How long goods may stay, at what charge, how they're released | 14 days free, then a pallet fee; released on written order |
| Insurance and risk | Who insures the owner's goods on the processor's floor | Owner insures its goods; processor carries liability cover |
| Recalls and complaints | Who decides, who pays, who talks to customers | Owner decides and leads; costs follow the cause |
| Confidentiality | Who owns the formula and the process know-how | Formula is the owner's; a separate NDA |
| Term and ending | Length, notice, what happens to materials on hand | One year; 60 days' notice; materials returned or run out |
The example is made up, and it's a list for a conversation. Have a lawyer draft the agreement itself.
The three that cause arguments
Yield. Say a farm sends taro that should make about 900 bags and gets 780 back. Was that the taro, which was wetter than usual, or the mill? With no agreed yield there's no way to say, and no way to settle the invoice. An agreement names the yield expected, the loss both sides treat as normal, how each run's yield is measured, and what happens beyond the allowance: in this example, the two look at the run's records together before anyone pays for anything. The sum is in batch yield formula.
The fee, and what it's charged on. "Per bag made" pays the processor for good output. "Per kilo received" pays for throughput whatever comes out. The first puts the yield risk on the processor's income, the second on the owner's. Neither is wrong. It has to be chosen, along with a minimum for a small run. What a run then costs you is in co-packing fees, and the bill in tolling invoice template.
Records. Because the goods are yours, a recall is yours. To run one you need to know which of your lots went into which run and which bags came out of it. That only exists if the agreement asks the processor to record it and send it. Ask for a batch record with every invoice.
Tolling, co-packing and buying
| Who owns the materials | What you pay for | |
|---|---|---|
| Tolling | You | The processing |
| Co-packing | You, the co-packer, or a mix | Processing, and often some materials |
| Buying finished goods | The seller, until you buy | The product |
An arrangement can sit between these, which is another reason to write down who owns what. The terms are compared in toll manufacturing, and the agreement for the middle case is in co-packing agreement template.
Get the checklist
Download the tolling agreement checklist. One sheet and a read-me: the thirteen clauses, what to decide in each, a filled-in example and a column for yours. It's an ordinary Excel file with no macros, and it works in Google Sheets, LibreOffice and Numbers.
Where this stops working
An agreement says what should be recorded. It doesn't do the recording. Six runs later the owner has six invoices and four batch records, and the processor has pallets of the owner's flour beside pallets of its own. How much of the owner's taro is still unprocessed? How many bags are finished and not yet collected? What's the fee owed on runs that haven't been billed? Both sides are answering from different spreadsheets.
How TaroStack does it
TaroStack is built for the processor's side of this, and keeps the owner's goods as the owner's.
A client's own goods are received at no cost to you, from that client, kept apart and left out of your stock value.
A run for a client is a batch that uses that client's goods and yours, never another client's. It records every material it used and whose each was.
A fee per unit made is set on the item.
Bill the client puts what's still to bill onto an ordinary sales order: the production fee and your materials at cost, each line naming its run, billed once.
A release sends the client's goods back, or wherever they say, and a monthly statement shows what you hold for them and how each lot moved.
| The question | Two spreadsheets | In TaroStack |
|---|---|---|
| How much of the client's taro is left | Count it | The client's goods, by lot |
| Which lots went into run 6 | The batch sheet, if sent | The materials on the batch, and whose each was |
| What's finished and not collected | Walk the floor | The client's page |
| What's owed and not yet billed | Add up the runs | What's still to bill |
TaroStack doesn't write the agreement or take payment. Work for clients is on Business at $89 a month, with up to 5 active clients. 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.
