How to manage co-packer production runs on Starch
Managing a co-packer production run means coordinating ingredients, packaging, specs, and timing across an organization you don't control — and then reconciling what actually came out against what you expected. You're sending purchase orders, confirming production dates, tracking yield, and hoping the invoice you get at the end matches what you shipped in and what got palletized out. When something slips — a spec change that didn't make it to the line, a yield that ran 8% short, an invoice for a run quantity that doesn't match your records — you find out late, usually when a customer order is already at risk. What this looks like in practice varies: a solo founder running two SKUs with one co-man has different pressure points than a brand with five facilities and seasonal runs across multiple formats. But the core problem is the same — too much visibility depends on someone at the co-packer responding to your email. On Starch, you get a production calendar that's always current, purchase orders that generate from your demand forecast, and yield variance flagged before it becomes a billing dispute. The apps built for this workflow — Co-Packer Manager, Inventory Planner, and Lot Tracker — are currently in development; you can request beta access today. Describe what you need and Starch builds it around your co-packer relationships, your SKUs, and how you actually track a run.
Why it matters
A missed production window or unresolved yield variance can cascade fast: stockouts on a retail shelf, late POs to your co-packer, and ingredient inventory that doesn't line up with your next scheduled run. On the other side, operators who know exactly what's in production, what came out, and what it cost can negotiate better run quantities, catch shrinkage before it becomes a pattern, and close their books without a week of back-and-forth with the co-man's accounting team.
Common pitfalls
Relying on email threads to confirm spec versions — so when a formula changes, the co-packer runs last month's sheet. Reconciling invoices against purchase orders monthly instead of per-run, which lets billing errors compound. Tracking yield at the batch level but not comparing it against historical variance, so a slow creep in shrinkage goes unnoticed until it's a margin problem. Keeping ingredient inventory and finished goods in separate spreadsheets that nobody reconciles until a stockout forces it.
Starch apps used
See this running on Starch
Connect your tools, describe what you want, and the agent builds it. Closed beta is free.
Choose your operator
A version of this guide tailored to your role — same recipe, different starting context.
Related workflows in Ops & Supply
Inventory shrinkage is the gap between what your records say you have and what's actually on the shelf, in the warehouse, or at your co-packer.
Read guide →Closing out the POS at end of night means verifying that what the register says happened actually matches what the cash drawer holds, what the card processor settled, and what the day's receipts show.
Read guide →Contractor job costing is the practice of tracking what a job actually costs — labor, materials, subcontractors, equipment — against what you estimated, and updating that number as work progresses and change orders land.
Read guide →Retailer deductions and distributor chargebacks are line items that show up on your remittance as money already taken — a short-pay for a late delivery, a promotional allowance you never agreed to, a compliance fee for a label that met spec.
Read guide →