Margin drift in food and beverage manufacturing

Executive Summary

Food and beverage manufacturers carry a pricing structure most other verticals do not: catch-weight product, where the invoiced amount depends on an actual measured weight rather than a fixed unit price. That single fact creates a category of margin drift that a rate-card audit built for fixed-unit industrial spend will not catch, because the error is not in the rate, it is in the weight the rate was applied to.

Cold chain freight adds a second mechanism unique to this vertical: temperature-control surcharges and continuous reefer monitoring fees that are billed whether or not the shipment ever left the temperature band the surcharge exists to fund. Co-packer and contract manufacturing agreements add a third: per-unit tolling rates that are supposed to shift with the client's own formulation changes and often do not.

None of these three mechanisms appear on a generic indirect-spend page, and none of them are solved by the same control that catches a stale freight rate card in industrial distribution. The rest of this guide names the mechanism in each case and what to check against the contract.

1. How does margin drift differ in food and beverage manufacturing?

Food and beverage margin drift concentrates in variable-weight pricing, temperature-controlled freight, and co-packer tolling rates. These are billing structures built around a measured, changing input rather than a fixed unit price, so the invoice can be internally consistent and still diverge from the contract because the input it was applied to was wrong. A generic fixed-rate audit does not test for this.

A metal fabricator's freight invoice and a beverage bottler's freight invoice look similar until you check what the rate is applied to. The fabricator's rate applies to a fixed weight class. The bottler's rate often applies to a catch weight recorded at time of shipment, a number nobody outside the plant floor and the carrier's scale ever compares against the invoice.

Co-packer and contract manufacturing agreements add another layer specific to this vertical. The tolling rate is contractually tied to a formulation and a run size. When the client changes an ingredient or a case pack, the rate is supposed to change with it. It frequently does not, because the invoice comes from the co-packer's own ERP running off a price list that update lags the amendment.

Sanitation and changeover labor billing is the third mechanism. Allergen changeovers and washdown cycles are billed as contract labor hours, but the trigger for a changeover is a production schedule the labor vendor does not see. The hours on the invoice reflect what the vendor scheduled, not what the changeover actually required.

2. What is catch-weight pricing and why does it create drift?

Catch-weight pricing invoices against an actual measured weight, such as a case of protein or cheese, rather than a fixed per-unit price. Drift appears when the weight recorded on the invoice does not match the weight recorded at the scale, when a minimum weight clause is ignored, or when a price break tied to a weight tier is applied to the wrong tier. The contract's weight tolerance clause is the first thing to check.

Fixed-unit pricing fails in one place: the rate. Catch-weight pricing can fail in two places, the rate and the weight the rate is multiplied against, which doubles the number of places an invoice can diverge from a contract without looking wrong on its face.

Most catch-weight contracts include a tolerance band, a minimum billable weight, or a rounding rule. An invoice that rounds up on every case, always within tolerance individually, compounds across a full order and a full year.

The test is arithmetic the reader can run directly: take the invoiced weight per case, compare it against the actual scale weight recorded in the plant's own receiving log, and multiply the difference by the per-pound rate and the annual case volume. That is the exposure, computed from the reader's own data rather than an industry figure.

3. Where does cold chain freight drift come from?

Cold chain freight drift comes from temperature-control surcharges, continuous monitoring fees, and reefer fuel adjustments that are billed as flat accessorials regardless of whether the shipment's actual temperature log stayed in band. The contract usually ties the surcharge to a service level; the invoice usually does not reference the temperature log at all.

A dry van freight invoice and a reefer freight invoice differ in one structural way: the reefer invoice carries accessorials that exist to fund a service, continuous temperature control, that either happened or did not. The invoice rarely says which.

The carrier's own temperature log, when the shipper requests it, is the record that resolves the question. Contracts for temperature-sensitive freight increasingly specify a rebate or credit when the load excursions outside the contracted range. Few shippers ask for the log routinely enough to invoke that clause.

A second driver is the reefer fuel surcharge schedule, which is typically indexed separately from the dry van fuel surcharge and moves on its own published table. An invoice that applies the dry van fuel index to a reefer load, or leaves last quarter's reefer index in place after the carrier's published table moved, is a stale-index error specific to cold chain lanes.

4. How do co-packer and contract manufacturing agreements create drift?

Co-packer and contract manufacturing agreements price by formulation, run size, and case pack. Drift appears when the client changes any of those three and the co-packer's invoice keeps billing the prior rate, or when minimum run charges and changeover fees stack on invoices that should have been billed at the standard tolling rate.

A co-packer relationship is a hybrid of a supply contract and a labor contract: the client supplies or specifies the formulation, the co-packer supplies the plant, and the invoice is a per-unit tolling rate meant to reflect both.

That rate is contractually tied to variables the client controls, not the co-packer: case pack size, run length, ingredient specification. When a client-side change happens, procurement often does not route the amendment to whoever issues the co-packer's invoices, so the old rate persists.

Minimum run and changeover fees are the second failure point. These fees exist for genuinely short runs. Applied to a run that met the contracted minimum, they are an overcharge invisible unless someone checks the run size on the invoice against the production order it corresponds to.

5. What role does shelf life play in freight and expedite drift?

Short shelf life pushes food and beverage shippers toward expedited freight more than most verticals, and expedite premiums are contractually distinct from standard rates: different fuel surcharge basis, different accessorial schedule, sometimes a different carrier entirely. Invoices billed at expedite rates for shipments that moved on standard transit time are the specific drift to check for.

An expedited shipment exists to protect remaining shelf life on arrival. The contract for expedited service usually specifies a transit time commitment tied to the premium charged.

The drift shows up two ways. First, an invoice bills the expedite rate for a lane and transit time that the standard service already meets, meaning the premium bought nothing. Second, a shipment genuinely expedited for shelf-life reasons is billed on a fuel surcharge table built for the standard service rather than the one the expedite tariff specifies.

Both require comparing the transit time actually achieved, from the carrier's own tracking record, against what the contract's standard service already promises before assuming the premium was earned.

6. What should a food and beverage manufacturer check first?

Start with the three mechanisms unique to this vertical: catch-weight invoices against scale records, cold chain accessorials against temperature logs, and co-packer tolling rates against the current formulation and case pack on file. These three checks require no industry benchmark, only the reader's own contract and their own receiving and production records.

Each of these checks is arithmetic against internal records, not a lookup against a published rate index, which is what makes them tractable for a plant controller to run directly rather than wait on an external audit.

A catch-weight check compares invoiced weight to receiving-log weight, line by line, on a sample of recent invoices. A cold chain check pulls the temperature log for a sample of reefer shipments and checks it against the surcharge billed. A co-packer check pulls the current formulation and case-pack specification and compares it to the tolling rate the co-packer is actually invoicing.

1. Catch-weight reconciliation: Sample recent invoices and compare invoiced weight to the scale weight in the plant's own receiving log.
2. Cold chain accessorial check: Pull carrier temperature logs for a sample of reefer loads and compare against the surcharges billed.
3. Co-packer rate reconciliation: Compare the current formulation and case pack on file to the tolling rate the co-packer is invoicing.

For the wider pattern this sits inside, start with the margin drift guide. See also margin drift vs. legitimate price increases: how to tell them apart and accessorial charge audit: the surcharges nobody validates.

7. Frequently Asked Questions (People Also Ask)

Does a standard freight audit catch catch-weight pricing errors?

A standard freight audit built around fixed unit rates checks whether the rate matches the contract. It does not typically re-derive the weight a catch-weight rate was applied to, which is where the error usually sits. Catching it requires comparing the invoiced weight against the plant's own scale or receiving record, a step outside a rate-card check.

Why do reefer freight invoices need a separate check from dry van invoices?

Reefer invoices carry temperature-control accessorials and a separate fuel surcharge index that dry van invoices do not. Checking a reefer invoice against a dry van fuel table, or skipping the temperature log entirely, misses the specific error mechanism in cold chain freight.

How often should a co-packer contract be reconciled against current invoices?

Reconciliation should follow any change to formulation, case pack, or run volume, since the tolling rate is contractually tied to those variables. Waiting for a scheduled annual review means an outdated rate can persist on every invoice between the formulation change and the review.

What record proves a cold chain shipment stayed in temperature range?

The carrier's own temperature monitoring log for that shipment, which most cold chain carriers can provide on request. Without it, there is no way to confirm whether a temperature-control surcharge funded a service that was actually delivered.

Is margin drift in food and beverage larger than in other industrial verticals?

There is no dataset comparing drift size across verticals, so that comparison cannot be made. What differs is the mechanism: catch-weight pricing, cold chain accessorials, and co-packer tolling rates are structures specific to this vertical, not a difference in overall magnitude.

Can allergen changeover labor be billed incorrectly?

Yes. Changeover and washdown labor is billed against the labor vendor's own schedule, which reflects what was planned rather than what the actual production schedule required. Reconciling changeover hours billed against the production schedule that triggered them is the relevant check.

Does a minimum run charge always apply to co-packer invoices?

No. Minimum run and changeover fees exist for runs below a contracted threshold. Applying them to a run that met the contracted minimum is an overcharge, and confirming it requires comparing the invoiced run size to the actual production order.

What is the first step if we suspect catch-weight drift but have no audit resource?

Pull a sample of recent invoices and compare the invoiced weight, line by line, against the scale weight recorded in your own receiving log. This requires no external benchmark and no industry data, only records the plant already keeps.