How to Vet a Hot Sauce Co-Packer Before You Sign
Make your own: hot sauce recipe builder → Choose a pepper, scale a sourced recipe, and print your batch.
A co-packer is not a supplier you can judge by the sample bottle. Four things decide whether the relationship works: whether the facility runs a written food safety plan, whether its batch records hold the values an inspector will ask for, what the minimum run actually is, and who carries the liability when a bottle makes someone sick. Each is checkable before you sign, and each has a document behind it.
Start with the food safety plan
The first document to request is the facility's written food safety plan. The rule requires a plan prepared, or with its preparation overseen, by one or more preventive controls qualified individuals. That is a named role, not a job title of convenience, and asking who holds it for the sauce line is a fair opening question.
The plan has required contents, which makes it easy to audit for completeness. It must include the written hazard analysis and a written recall plan. A co-packer that can produce a hazard analysis but not a recall plan has a gap in a document the buyer can read, and the recall plan is the one you will care about most if a lot is implicated.
Read the hazard analysis against your own formula. Allergen cross-contact, pH control, and thermal process are the hazards that matter for a shelf-stable sauce, and each should appear with a control and a monitoring frequency. A generic plan that names none of them is a template, not a plan for your product.
Ask also how the plan changes when a new SKU arrives. A co-packer running dozens of formulas should be able to describe the reanalysis step, because your sauce is a new product in their facility even if it is old to you.
The batch records that prove control
Records are where a co-packer's claims become checkable. Under the preventive controls rule, monitoring and corrective action records must be reviewed within 7 working days after they are created, and calibration of process monitoring and verification instruments is part of the verification record set.
The content standard is stricter than most operators expect. Records must contain the actual values and observations obtained during monitoring, and they must be created concurrently with the activity documented. A batch sheet filled in from memory at the end of the shift fails both tests, even if every number is right.
Availability matters too. All records required by the part must be made promptly available to an authorized representative for official review and copying on request. That obligation runs from the facility to the agency, but it tells you what a well-run co-packer already has on hand: pH readings, calibration logs, and lot codes, retrievable without a scramble.
Before signing, ask to see one redacted batch record for a sauce similar to yours. You are looking for real values rather than checkmarks, a calibration entry for the meter used, and a code that ties the run to the cases it produced. If the sample record is a blank template, you have learned something useful.
Minimums arrive in gallons, not cases
Co-packers quote minimums in production units, and for sauce that usually means volume. One program describes brewing in 100 gallon kettles and bottling into 5 oz woozy bottles, a scenario that nets approximately 2,500 bottles of finished product. Another lists a typical hot-fill start of 40 gallons.
Those two numbers set very different first orders. The smaller minimum is friendlier to a brand testing a flavor; the larger kettle is more efficient per bottle. Neither is a price, and neither is a promise about your yield.
Yield deserves its own line in the conversation. Saleable output will be lower than the batch volume after process losses, retained samples, and fill allowances. A 100 gallon brew does not deliver 100 gallons of sellable sauce, and a plan built on the kettle number alone will overstate inventory.
Two more quoting mechanics are worth confirming in writing. Each recipe and SKU is quoted separately, and supplier or packaging minimums may increase the run. That means a five-flavor lineup is five runs, and a custom bottle can move the minimum without moving the recipe. Turnaround is a separate clock: one program quotes 3 to 5 weeks for custom recipe orders.
What a certification actually certifies
Certification questions need precision, because the logo on a website can mean several different things. The benchmark body describes itself as bringing together food retailers and manufacturers to oversee third-party food safety standards for food business operators globally, and as harmonising and driving improvements in food safety certification programmes. In practice, a buyer asking for a recognized certificate is asking for an audit against one of those benchmarked schemes.
That is different from a facility describing itself as certified. One co-packer states that its manufacturing occurs in a certified and regulated co-packing facility, which is a claim worth asking to see evidence for: the certificate, the scheme name, the scope, and the expiry date.
Certification also does not replace the product-specific work. The same program lists nutrition analysis, shelf stability testing, and scheduled process certifications among its inclusions, which are separate deliverables from a facility audit. A facility certificate says the plant's systems were audited; a scheduled process says this sauce, in this container, was reviewed.
Ask which certificate covers the line your sauce will run on, and whether the scope includes hot fill. A certificate for dry blending does not tell you anything about a 100 gallon kettle.
Liability and the insurance question
Liability is the part of the agreement that nobody reads until something goes wrong. Two coverages come up in every co-packing negotiation, and the federal small business guide describes both plainly.
Product liability insurance is written for businesses that manufacture, wholesale, distribute, and retail a product, and it protects against financial loss as a result of a defective product that causes injury or bodily harm. General liability is broader and covers bodily injury, property damage, medical expenses, libel, slander, defending lawsuits, and settlement bonds or judgments.
The useful question is not whether the co-packer has insurance but whose policy responds to a claim about your bottle. Ask for the certificate of insurance, the coverage limits, and whether your brand is named as an additional insured. Ask, too, what the contract says about who handles a recall and who pays for it; the facility's recall plan is the operational document, and the indemnity clause is the financial one.
Product liability follows the product, which is why the manufacturer line on your label matters. If the co-packer is named as manufacturer, the claim path runs through them; if your brand is named, it runs through you first. Decide that deliberately rather than discovering it after a letter arrives.
Costing one run before signing
A co-packing quote is built from more line items than a self-filled batch. Pricing reflects the formula, ingredient sourcing, packaging, labels, batch size, process, testing or process-authority work, equipment time, labor, setup, finishing, cases, pallets, freight, storage, and fulfillment services that apply.
That list is a checklist for reading the quote. If a line is missing, ask whether it is included or simply not yet priced; freight and storage are the two that most often appear later. The first run usually carries additional one-time items: a test batch with pH testing before the facility will commit to production, and a required production sample the buyer approves before a full run.
The calculator below turns a batch into a per-bottle number. It takes ingredient cost, bottles per batch, bottle cost, label cost, labor hours, and labor rate, then returns packaging cost, labor cost, batch cost, and cost per bottle. Use the saleable bottle count rather than the nominal batch size, and add freight, storage, and any test-batch fee outside the tool, because it does not model them.
Run it twice: once at the co-packer's minimum and once at the larger kettle volume. The difference between the two per-bottle numbers is the real price of starting small, and it is the number to negotiate against.
Two published hot-fill volumes
A typical hot-fill start at one co-packer and the kettle size at another, both in gallons. Different facilities and different products; not a range and not a recommendation.
| Item | Value | Unit |
|---|---|---|
| Typical hot-fill start | 40 | gallons |
| Kettle size | 100 | gallons |
Batch cost per bottle
Enter your own batch numbers. The calculator adds ingredients, packaging and labor, then divides by the bottles the batch actually fills. It does not assume a price for you.
Peppers, vinegar, salt, spices, any purchased mash.
Use the count that passed QA, not the theoretical yield.
Delivered cost per bottle, including caps and shrink bands.
Printed label cost per bottle at your order quantity.
Cooking, filling, capping, labeling and cleanup.
Your own wage, including the owner's time.
- Packaging
- $123.60
- Labor
- $132.00
- Batch cost
- $315.60
- Cost per bottle
- $2.63
Excludes fixed costs such as kitchen rent, permits and insurance; add those separately when you price the bottle.
FAQ
What should I ask a co-packer for before signing?
Ask for the written food safety plan and who oversees it, a redacted batch record showing actual monitoring values, evidence behind any certified facility claim, the certificate of insurance, and a quote that lists every pricing line.
What is a typical minimum run for hot sauce co-packing?
Published figures are in gallons. One co-packer lists a typical hot-fill start of 40 gallons; another brews in 100 gallon kettles and describes that run as approximately 2,500 bottles. Saleable output is lower than the batch volume.
Does a co-packer's certificate cover my sauce?
Not by itself. A facility certificate covers a third-party audit of the plant's systems, while a scheduled process covers a specific product in a specific container. Ask for both, and check that the certificate scope includes the line your sauce runs on.
Who needs product liability insurance in a co-packing deal?
Product liability coverage is written for businesses that manufacture, wholesale, distribute, and retail a product, and it responds to loss from a defective product that causes injury. Confirm whose policy responds to a claim about your bottle and whether your brand is named on the certificate.