Your first conversations with a new co-packer should run on a product brief: a document that says what your product is and what you need from the plant, and leaves the recipe out. The full formula by weight waits until a non-disclosure agreement (NDA) is signed and you're close to an agreement with that plant. So does the trial run, because even one trial can teach a plant's crew the process you paid to develop.

Holding the recipe back says nothing bad about the plant. A good plant keeps its other clients' formulas private too, so a brand being careful with its own is nothing new to it. The order matters most when you're talking to several plants at once, because every plant that sees your recipe and doesn't get the job still has it.

If your first plant has made your product for years, the formula went over long ago. A new or second plant starts from nothing. So does any outside developer you bring in, me included. When a brand asks my team for an NDA before sending a recipe, that's the right instinct, and the NDA comes first.

Why the Trial Run Waits Too

A jar tells a plant what your product is. Anyone who tastes it can make a fair guess at the ingredients, and once it's on shelves, the ingredient statement on your label lists them, heaviest first. What the jar can't tell anyone is how much of each goes in, and when, and at what point in the cook the sauce is done. That's the recipe, and it's the expensive part. The test batches got made and remade at the bench, and each one was judged at two weeks, not on the day it was made. Getting the thickener right was a job in itself, because it had to come through a plant's cooking heat and its pumps and still hold its body while a batch waits to be filled.

A trial run puts all of that on the plant's kettle. Say your sauce keeps its body through a hot fill because of the starch you settled on and the moment it goes into the cook. Nobody can see that in a jar. On trial day the crew weighs that starch, adds it at that moment and watches the kettle thicken, while the quality tech writes down every reading. By the end of the day, the plant knows how your product is made.

A plant may never mean to use that knowledge for anyone else. But a crew that has made your sauce once knows how it's done, and if a bigger account walks in next year wanting something close to it, the know-how is already in the building.

The First Brief: What Goes In and What Stays Out

The first brief has a narrow job. It gives a plant enough to say whether it can run your product and roughly what that would cost, and none of that needs a single ingredient amount. For a sauce, dressing, dip or salsa, I'd put in:

  • What the product is. Its name and category, the container and size, and where it sells.
  • How it's made, in general terms. Kettle-cooked or not, hot-filled or cold-filled, smooth or chunky.
  • The targets the finished product has to hit. pH, Brix (a reading of dissolved solids, mostly sugar) and viscosity, each with a range. If the product is acidified, meaning it relies on added acid to be safe, the pH target matters early. In my experience, the upper limit most process authorities (the qualified experts who decide how a product has to be made to be safe) and co-packers set for finished pH falls somewhere between 4.0 and 4.3, to allow for the pH shifting once the product is in the jar.
  • The ingredients, without amounts. Each one by name and grade, with the job it does in the jar (acid, body, heat, color) and any certification it carries.
  • Allergens. Every allergen in the product, so the plant can check it against what already runs in its building.
  • Run size. How much you'd make per run, and roughly how often.
  • Jars to taste, if the product is already on shelves.

What stays out is the recipe itself: the percentages by weight, the order of addition, the cook times and temperatures, and your notes on how the product behaves in production, including the adjustments your current plant has learned to make. That leaves a short first brief. The rest of what's in my co-manufacturing brief template goes to the plant later, in the order below.

The Hand-Over, Step by Step

With a new plant, I'd hand things over in this order. Each step gives the plant only enough to make its next decision.

  1. Build your list of plants. You're only collecting names at this point, so nothing about your product needs to go out yet. Ask the companies that supply your ingredients which plants they'd suggest, then add names from trade shows and co-packer directories. Co-Packer Match, our sister company, is one you could use. It lists U.S. co-packers by state, with a code standing in for each plant's name, and you can browse its co-packer directory by process, hot-fill or kettle-cooked for example. Once you have names, how to find and vet a co-packer walks through checking each plant's business side.
  2. Send every plant the same brief. Add jars if the product is on shelves. From the brief alone, a plant can tell you its minimums and give you a rough price. If it says the price will firm up once it sees the formula, that's normal. Take the rough number for now.
  3. Sign an NDA before the confidential details. Once a plant is a real candidate, the NDA comes before anything sensitive that isn't the formula: your supplier names, your sales figures and forecast, samples of a product that isn't on sale yet, and the details of what your product needs from the equipment, such as the fill temperature it has to hold or how gently it has to be pumped to keep its pieces whole. Whether the NDA is yours or one the plant sends, have your attorney read it before you sign. An NDA keeps things confidential, but who owns the recipe, and any changes a plant makes to it later, is a separate question, which I go into in who owns your recipe when you work with a co-packer.
  4. Narrow to the plant you mean to sign with. Visit, and see the line your product would run on. Work through the quote and the schedule with the plant. Ask who arranges the process authority review, since it can be the plant or you, then put the answer in writing and budget for it. This is what close to signing means: you've chosen this plant, and the main terms are agreed in principle.
  5. Send the formula by weight. Now the plant gets the full formula with a version number, the process notes (how the product is made, step by step), the ingredient specs with approved suppliers, and your gold standard (the reference jar every batch is judged against). It's the same package you'd put together to switch co-packers without changing the taste, or to add a second plant beside the one you have.
  6. Run the trial with that one plant. A trial at three plants, run to compare them, can teach all three your process, and only one of them will end up making it. Be there on the day, and judge the trial product against your gold standard at two weeks, once the flavor has settled. Whether the agreement gets signed just before the trial or just after is for you and the plant to work out.

The Plant That Wants the Recipe on Day One

Some plants ask for the full formula before they'll go further, and they usually have good reasons. A plant needs to know whether your product is safe to run on its line, whether it would bring a new allergen into the building, what the ingredients will cost and whether its process suits your product. Most of that can be answered without the amounts.

So ask what the plant needs the formula for, and answer that question. Say a plant wants your formula before it will quote your hot-filled barbecue sauce. What it needs for the quote may come down to the ingredients and their grades, the container, the run size and the finished pH, and all of that is already in your brief. If the concern is allergens, send the allergen list. If the plant wants to judge the product itself, send jars.

Then tell the plant when the formula will come. Something like: "We'll send the full formula once we've both signed an NDA and we're close to an agreement. Until then, here's our brief. It should tell you whether our sauce will run on your line."

A plant may offer to sign an NDA on the first call. It gets the same read before signing as any other NDA, and once it's signed, the step 3 details, like your supplier names and sales figures, can go over sooner. That doesn't bring the formula forward, though. An NDA puts confidentiality in writing, but it doesn't change what a crew learns from making your sauce, and at this stage you might have NDAs with three plants.

Some plants won't go further without the formula, as a matter of policy. That's a reasonable rule for a plant to have, and there's no point arguing it. Keep their details and put your time into the plants that can work from a brief.

Where the Brief Stops for Your Product

For most sauces, the secret is in the amounts and the step-by-step process, so a brief that says "kettle-cooked and hot-filled" gives nothing away. Some sauces are different, because the process is where the flavor comes from. Say yours gets its depth from taking the onions much darker than most cooks would before anything else goes in. The brief can still say kettle-cooked. It shouldn't say how dark the onions go, because that's the part someone tasting the jar can only guess at.

My part is the formula and the documents that go with it. I write the formula and the spec sheet that go to the plant in step 5, and I can help you work out what your first brief needs to say for a plant to judge the fit, and what can wait. Choosing the plant and agreeing terms with it are yours to do, and I don't write NDAs. Where the brief should stop for your own product is something I can only judge with the formula in front of me, so that part happens once we're working together.