Customer-supplied raw materials are ingredients and packaging a client sends you to make their product with. They sit on your shelves and go through your kettle, and they're never yours. That one fact drives how they're tracked. They're received at no cost, so they don't inflate your stock value. They're kept apart, by client, on the shelf and in the records. They're used only in that client's runs. Every movement is written down: in, used, lost, returned, counted. And the client gets a statement, because it's their money on your floor. A co-packer who tracks its own flour carefully and a client's flour "roughly" finds out the difference the first time a client asks for their materials back. Below are the rules, a ledger for a made-up co-packer, and a file.
The short version
- Theirs, not yours: no cost, no value on your books.
- One place for each client. Label every drum and pallet with the client and their lot.
- A run for a client uses that client's materials. Never borrow from another's.
- Write down every movement, with the run it belongs to.
- Count monthly. Tell the client about any difference in writing.
- TaroStack keeps a client's goods apart and gives each client a monthly statement by lot. More below.
The five movements
| Movement | What happened | In or out |
|---|---|---|
| Received | The client's delivery arrived | In |
| Used in a run | It went into their product | Out |
| Lost or scrapped | Left in the kettle, spoiled at set-up, spilled, expired | Out |
| Returned | Sent back, or to wherever they said | Out |
| Count difference | The shelf and the ledger disagreed | In or out |
Nothing else can happen to a client's material. If a kilogram left the shelf, it's on one of those rows.
A month's ledger
A made-up co-packer, one client, November.
| Date | Material | Client's lot | Movement | In | Out | Reference |
|---|---|---|---|---|---|---|
| Nov 5 | Pepper mash | PM-2291 | Received | 600 kg | Their delivery note 3318 | |
| Nov 5 | Front labels | LB-1107 | Received | 5,000 | Their delivery note 3318 | |
| Nov 6 | White vinegar | V-0933 | Received | 200 L | Their delivery note 3321 | |
| Nov 12 | Pepper mash | PM-2291 | Used in a run | 552 kg | Run CP-1112 | |
| Nov 12 | Pepper mash | PM-2291 | Lost or scrapped | 8 kg | Run CP-1112 | |
| Nov 12 | White vinegar | V-0933 | Used in a run | 184 L | Run CP-1112 | |
| Nov 12 | Front labels | LB-1107 | Used in a run | 4,800 | Run CP-1112 | |
| Nov 12 | Front labels | LB-1107 | Lost or scrapped | 112 | Run CP-1112 | |
| Nov 28 | Pepper mash | PM-2291 | Count: short | 2 kg | Month-end count |
Balances at the end of the month:
| Material | In | Out | On hand |
|---|---|---|---|
| Pepper mash, kg | 600 | 562 | 38 |
| White vinegar, L | 200 | 184 | 16 |
| Front labels | 5,000 | 4,912 | 88 |
The mash was two kilograms short at the count: the ledger said 40, the drum weighed 38. That's on the ledger as its own row, dated, and the client was told the same day. Two kilograms in 600 is nothing. Not mentioning it is how a small difference becomes a question about everything else.
Receiving
Receive a client's delivery with the same care as your own, and one more step.
| Check | Why |
|---|---|
| Count or weigh against their delivery note | The opening figure is what every later number rests on |
| Record their lot number, as written | It's how their recall, or yours, finds the material |
| Condition, seals, temperature | A drum that arrives bad is their problem only if you said so on the day |
| Label it: client, material, lot, date received | Two clients' vinegar looks the same |
| Put it in that client's place | Separation starts at the dock |
If the count is short or a seal is broken, tell the client before you use any of it.
Keeping it apart
On the shelf. A bay, a rack or a colored tag for each client. Where space is tight, a label on every unit is the minimum.
In the run. A run's sheet lists the client's lots to use, and the operator checks the label against the sheet before opening anything. Using client B's sugar to finish client A's run because A's ran out is the mistake to design against: it's taking B's property, it breaks A's traceability, and if B's sugar is organic or allergen-free by specification, it may break A's label claim too.
Allergens. A client's peanut flour on your premises is your allergen risk as well as theirs. Store it as you would your own.
On the books. Not in your stock value. Not in your cost of goods. Your accountant will want to know the materials exist, and they'll want them off your balance sheet.
Loss, yield and the agreement
Some loss is part of making anything. The question is how much, and who bears it. That belongs in the contract as a yield or a scrap allowance: say, 98% of mash received becomes sauce. The ledger then shows whether each run stayed inside it. On run CP-1112, 8 kg was lost on 560: 1.4%, inside a 2% allowance. If a run loses 9%, both sides will want to know why, and the ledger is where the conversation starts. The clauses are in co-packing agreement template.
What the client sees
Send a statement each month: for each material and lot, opening, received, used, lost, returned and closing, and the finished goods made and released. It takes the place of the phone call asking what's left. The same figures go out with every invoice: see tolling invoice template. What a toll arrangement is, and how it differs from buying the materials yourself, is in toll manufacturing, and the wider business in how to start a co-packing business.
Get the ledger
Download the client materials ledger. A Ledger sheet with one row for each movement, a Balances sheet that adds them up for each material and lot, and a read-me. Add a line to Balances for each new material. It's an ordinary Excel file with no macros, and it works in Google Sheets, LibreOffice and Numbers.
Where this stops working
A ledger depends on every movement being typed. On a production day the operator uses 552 kg of mash, writes it on the run sheet, and the run sheet goes in a tray. The ledger is updated on Friday, if Friday is quiet. Meanwhile the client phones on Wednesday to ask what's left, and the answer is a walk to the back with a dipstick. With six clients, the ledger is six ledgers, always a few days behind.
How TaroStack does it
TaroStack's copacking makes the run itself the ledger entry.
Every item says whose it is: yours; yours made for a client; or the client's own, which comes from them, goes back to them and is in no stock value of yours. A client's own code is kept beside yours.
A client's own goods are received at no cost, from that client, and kept apart.
A toll run uses that client's goods and yours, never another client's. It records every material it used and whose each was.
Releases. A client's goods go out only on a release to that client, to them or wherever they say.
A monthly statement for each client, by lot: opening, received, used, made, released, counted, closing, with the month's charges. Printed, or as a spreadsheet.
A client's page shows their goods here, their runs, releases, orders and charges.
| The job | Spreadsheet ledger | In TaroStack |
|---|---|---|
| Record what a run used | Typed afterwards from the run sheet | The run records it |
| Keep clients' goods apart | Labels and care | The run takes only that client's goods |
| What's left of the client's vinegar | Friday's figure | The client's page |
| The monthly statement | Built by hand | Printed, by lot |
A shared kitchen or small warehouse that only keeps members' goods can receive, count and release them the same way, with nothing made. Copacking is on Business, $89 a month, with 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.
