FactoryLink Friday: The Traceability File Your Wholesale Buyers Ask For, And How to Build It Without Drowning in Paperwork

Author: Cocoa Craft

The holiday buying season has a way of turning a tidy little chocolate operation into a detective story.

A buyer asks which cocoa lot went into last month’s bars. A distributor wants your allergen statement and the lot code printed on every case. Someone on your team remembers changing the roast profile, but nobody remembers whether that happened before or after the formula update.

The answer is not “ask the person who was there.” That system works until the person is on vacation, the batch is six weeks old, or a wholesale buyer needs a defensible answer by 3 p.m.

For craft chocolate makers moving into wholesale, traceability is not a mountain of paperwork. It is a clear chain of evidence:

supplier lot → ingredient record → formula version → process run → finished lot → customer shipment

Start building that chain with a free Cocoa Craft account, then use the Recipe Builder to turn your next formulation into a record your team can actually use.

Get free, unlimited access to the full Cocoa Craft software suite in exchange for monthly feedback. Join the beta at cocoa-craft.com!

What wholesale buyers are really asking for

Most buyers are not looking for a 70-page binder filled with beautiful handwriting. They want confidence that you can answer six practical questions:

1. What product is this?
   Product name, SKU, pack size, production date, and best-before date.

2. Which lot is it?
   A unique lot code printed on the individual package, case, or both.

3. What went into it?
   Ingredient names, supplier lots, receiving dates, and allergen status.

4. How was it made?
   Formula version, key process settings, equipment used, and any deviations.

5. Did it pass release checks?
   Sensory observations, particle size or viscosity checks where relevant, packaging inspection, and release approval.

6. Where did it go?
   Customer, shipment date, quantity, purchase order, and affected lot codes.

That is the traceability file. It may live in a digital workspace, a structured spreadsheet, or a combination of both. The format matters less than the links between records.

The minimum viable batch record

For a two- or three-person team, one batch record should contain:

Record area	What to capture
Product identity	Product name, SKU, pack size, finished lot code
Production	Date, operators, batch size, equipment used
Formula	Recipe name, formula version, approved change notes
Ingredients	Ingredient, quantity, supplier, supplier lot code
Process	Roast, grind, refine, conche, temper, mold, and cooling notes
Allergens	Declared allergens, cross-contact risks, cleaning or changeover check
QC	Sensory notes, appearance, packaging check, test results if applicable
Release	Hold or release decision, reviewer, date
Distribution	Case quantities, customers, ship dates, invoices or purchase orders

You do not need to record every movement of every spatula. You do need to record the decisions that affect product identity, safety, consistency, and release.

Build a batch plan before your next production run, and give each record a single owner. A shared record with no owner is just a communal suggestion.

Build a lot code that tells a story

A lot code should be short enough to print and specific enough to investigate.

One practical structure is:

PRODUCT-ORIGIN-DATE-RUN

For example:

70-BEL-261002-R02

That could mean:

• 70 = 70% dark chocolate product family
• BEL = internal origin or recipe identifier
• 261002 = production date, October 2, 2026
• R02 = second process run that day

Your own code can use different elements. The important rules are consistency, uniqueness, and documentation.

Do not use only the production date. Two batches made on the same day need different identifiers. Do not use an employee’s initials as the main key. People change roles, and initials are surprisingly easy to duplicate. Do not silently reuse a lot code after a failed or partial run.

The finished lot code should connect to:

• the formula version used;
• the ingredient and supplier lots consumed;
• the process record;
• the finished quantity;
• the cases or units packed;
• the customers who received it.

A case label should make the lot code easy to find without opening the carton. If your buyer has to call you to locate it, the code is not doing enough work.

The gap: spreadsheets, paper logs, and tribal memory

Spreadsheets are useful. Paper logs are useful. Memory is useful for tasting notes and terrible as a production control system.

The trouble starts when each tool holds a different piece of the truth:

• the formula is in a recipe document;
• the roast settings are on a whiteboard;
• ingredient receiving is in a spreadsheet;
• the batch size is in a text message;
• the final lot code is on a label roll;
• the wholesale shipment is in accounting software.

You can still make excellent bean to bar chocolate this way. You just cannot investigate it quickly.

The same problem appears in product development. A maker remembers that the last 60 dark chocolate bar had a cleaner finish, but the recipe file does not show whether the improvement came from the cocoa percentage, conching time, particle size, or a different cocoa nib lot. A 60 cocoa chocolate product may look simple on the shelf, but the production history behind it should not be a guessing game.

This is where a structured system earns its place.

In Chocolate Lab, the Formulation Tool and Recipe Builder keep the formula, percentages, process context, and version history together. A dark milk chocolate recipe can move from an experiment to an approved version without losing the notes that explain why it changed.

Then the production record should carry that approved formula version into the actual run:

Formula v1.3 → Batch Plan → Run 261002-R02 → Finished lot 70-BEL-261002-R02

That one chain is more useful than a folder full of files named final_recipe_NEW2.xlsx.

Allergen controls belong in the record, not in someone’s head

Allergen control is one of the first areas a retail buyer will examine, particularly if you make milk chocolate, nut-containing bars, or products on shared chocolate making equipment.

For every batch, record:

• declared allergens;
• supplier allergen information;
• whether the ingredient was received in a sealed, identified container;
• shared-equipment risks;
• cleaning or changeover completed before the run;
• label version applied;
• reviewer and release decision.

For example, a batch of 60% Dark Milk Chocolate with Cocoa Nibs should point to the cocoa nib supplier lot, the milk-related declaration, the formula version, and the label version used. A batch of Peanut Butter Dark Chocolate should make its allergen controls especially easy to retrieve.

This record does not replace a properly developed food safety program or local regulatory requirements. It gives your team a reliable operational trail and gives buyers something better than reassurance.

What a two-person team can do every Friday

Traceability becomes manageable when you treat it as a production rhythm rather than an annual audit panic.

Before production

Create the Batch Plan with:

• product and formula version;
• planned quantity;
• ingredient lots selected;
• equipment and process checkpoints;
• expected packaging and lot code.

If you are using a professional stone grinder, melanger, commercial roaster, or other cocoa craft equipment, list the equipment or asset identifier. This is useful when a process change affects texture, flavor, or throughput.

During production

Record only what matters:

• actual ingredient quantities;
• actual start and finish times where useful;
• key roast, grind, refine, conche, temper, and cooling observations;
• deviations from the plan;
• operator initials.

A short note such as “temper restarted after room temperature rose” is far more valuable than a blank field or a paragraph of vague commentary.

At release

The second person reviews:

• formula version;
• ingredient lots;
• allergen and label checks;
• finished quantity;
• QC notes;
• printed lot code;
• release status.

If you are working alone, perform the review after a break and sign it as a separate check. Fresh eyes are a modest but effective control.

At the end of the week

Use analytics to look for missing records, repeated deviations, rejected batches, and products that require more labor than expected. A traceability system should help you improve the process, not merely prove that a process existed.

This is the practical difference between documentation and operational knowledge. Cocoa Craft is built by chocolate makers, for chocolate makers, so the record should help you make a better next batch, not just satisfy a buyer’s questionnaire.

Keep the finished product connected to the real work

A production record should eventually answer this question:

If a buyer sends us a lot code today, can we identify the formula, ingredients, process run, QC decision, and customer shipments without calling three people?

If the answer is no, start with your next batch. Do not attempt to reconstruct the last five years of production before creating a usable system.

Pick one product. Pick one lot code format. Pick one batch record. Test it on a product you already make, whether that is a 60% Dark Milk Chocolate bar, a 65% Madagascar bar, drinking chocolate mix, or another regular line.

Then expand.

The Cocoa Craft software suite connects formulation work, recipe versioning, Batch Plan records, production details, and analytics in one place. That is the direction craft chocolate makers need as they move from successful batches to dependable wholesale supply. The operating system for chocolate production, built around the work already happening on the floor.

Get free, unlimited access to the full Cocoa Craft software suite in exchange for monthly feedback. Join the beta at cocoa-craft.com!

Create your free account, log in, and save your next batch. Use Chocolate Lab to preserve the formula, the process decisions, and the evidence that makes the result repeatable. You can also browse Cocoa Craft’s chocolate making equipment and products when your production plan calls for a professional stone grinder for chocolate, a melanger, a commercial roaster, cocoa nibs, or finished artisan chocolate.

The same discipline applies to serious home chocolate making. You may not have a wholesale buyer asking for a recall report, but recording your bean lot, recipe version, roast profile, and tasting result is how an experiment becomes a repeatable chocolate craft process.

When the file is saved and the tempering room needs a short reset, visit the Cocoa Craft Arcade, play a quick round, then come back ready to diagnose your process.