Food & Beverage ERP Consultant, USA

From formula to retail shelf: how US food plants run

Most US food and beverage businesses I talk to sit somewhere between a commercial kitchen and a full process plant. The flow I map with them usually looks like this:

• Sourcing: approved suppliers -> purchase orders for ingredients and packaging -> receipt with supplier lot, best-by date and a certificate of analysis where the ingredient calls for one.
• Production: batch tickets from the approved formula -> runs sequenced so allergen changeovers and sanitation happen in the right order -> actual weights, yield and giveaway recorded.
• Co-manufacturing: ingredients shipped to, or bought by, a co-packer -> finished cases received back under the co-packer's lot codes.
• Distribution: stock held in your own warehouse or with a third-party logistics provider -> orders from grocery chains, club stores, foodservice distributors and online channels -> shipment with lot numbers and compliant labels.

Where it tends to break is at the joins. The formula in the spreadsheet is not the one used on the floor, the warehouse provider's stock report never quite matches the books, and nobody can say what a case of a given SKU really cost last month. My food and beverage ERP guide covers the general module set; this page is about what the US market adds on top of it.

FDA traceability expectations and recall readiness

The FDA's food traceability requirements center on foods listed on its Food Traceability List and ask for defined key data elements at critical tracking events such as receiving, transformation and shipping, tied together by traceability lot codes. Meat, poultry and certain egg products sit under USDA oversight instead, with their own expectations. Which rules apply to your products, and how, is a decision for your QA or regulatory lead and their advisors, not for me or a software vendor.

My job is to make sure the ERP can hold and produce the records once that scope is agreed:

• Each receipt carries the supplier lot, any assigned traceability lot code, quantity, location and date.
• Each production batch links every consumed ingredient lot to the finished lot, including rework.
• Each shipment records lot, customer, ship-to location and carrier.
• A trace report can be exported as a sortable file for an investigator or a retail customer.

I then write a mock recall into UAT: choose a single supplier lot, list each finished lot and customer it reached, reverse the trace from a complaint, and time each exercise. Auditors and retail customers may ask you to demonstrate exactly this, so the test doubles as rehearsal for your team.

Co-packers, private label and who owns the stock

Many US food brands make part of their range in-house and outsource the rest to co-packers, while some plants do the opposite and produce private label for retailers. Both models raise ownership questions the ERP has to answer clearly:

• Who buys the ingredients? If you supply them, the stock sits at the co-packer but stays on your books, and consumption has to be reported back by lot.
• How is yield reconciled? Ingredients shipped out should reconcile against finished cases received, within an agreed tolerance and with a process for the difference.
• Whose lot code wins? The co-packer's lot code must link to yours, or a recall stops at their dock door.
• Which specification applies? Private label items carry the retailer's specification, artwork and sometimes a separate formula version.

Platforms model this through subcontracting or tolling features, consigned locations and receipt routings, but they vary a great deal in how much is standard and how much has to be built. I set these scenarios out in the solution design before configuration starts, and I test them during demos rather than accepting a slide that says the feature exists.

Retail programs, catch weight and shelf-life promises

Selling to US grocery, club and foodservice customers brings rules written outside your own business. Each large account tends to publish a supplier guide covering EDI documents, advance ship notices, GS1 barcodes on cases and pallets, delivery appointments and the deductions it takes when something goes wrong. Without good data, those chargebacks get written off instead of disputed.

The requirements I write for this area usually include:

• EDI orders, acknowledgements, ship notices and invoices through a connected EDI provider, with errors visible to customer service.
• Minimum remaining shelf life per customer or distribution center, enforced at allocation and picking, with FEFO as the default rule.
• Catch weight for meat, cheese, seafood or produce sold by actual weight, so the invoice, inventory and margin all use the same figure.
• Trade promotions, slotting fees and deductions recorded against customer and SKU, so true net margin is visible.
• Sales tax handling for food, which differs by state and by product type; check current treatment with your tax advisor.

If most of your volume moves through distributors, my US distribution ERP page goes deeper into the warehouse side.

Leaving QuickBooks and spreadsheets, delivered remotely

The starting point for many US producers is QuickBooks or a similar accounting package, an inventory add-on, formulas in Excel and lot numbers on paper batch sheets. Some run an older food-specific system that no longer keeps up with new retail accounts or a second plant. The migration priorities rarely change: one approved version of each formula, clean units of measure from pound to case to pallet, and opening stock counted by lot, best-by date and location, including stock sitting at co-packers and third-party warehouses.

I work remotely across US time zones, scheduling workshops around production shifts and recording walkthroughs for second-shift supervisors. Plant visits can be arranged when a walk-through adds real value, though the bulk of the engagement happens by video, shared documents and screen-shared demos. For the wider factory questions, such as tariffs, sales and use tax on equipment and lender reporting, see my US manufacturing ERP page. For general ERP advice, begin with my ERP consulting for US companies and the wider United States hub.