New: Odoo and Dynamics 365 cost calculators.Estimate your costs

ERP for food and beverage: traceability, shelf life, and cost

Start from one finished lot and name the ingredient lots inside it and the customers who received it. If that list takes days, the system is not ready for a recall.

FlecticUpdated 23 min read

Start from one finished lot and name the ingredient lots inside it and the customers who received it. If that list takes days, the system is not ready for a recall. The Food Traceability Rule requires an electronic sortable spreadsheet within 24 hours of an FDA request, or a reasonable time FDA agrees, when the request is tied to an outbreak, a recall, or another public-health threat. The original compliance date was 20 January 2026. FDA has proposed 20 July 2028, and the 2026 appropriations act directed FDA not to enforce the rule before that date.

On Microsoft's US pricing page, as of October 2026, manufacturing sits on Business Central Premium at USD 110 per user per month, paid yearly. Essentials is USD 80 per user per month and covers finance, sales, and operations. Odoo lists USD 3,060 for 25 consultant hours and USD 21,250 for 200 hours for a new customer, as of October 2026.

Microsoft's item-tracking pages and Odoo's lot pages describe lots, dates, and where-used reports. They do not describe a Food Traceability Rule spreadsheet or a key data element file. Have each bidder produce that spreadsheet from a finished lot in your plant before you treat the product as ready for the rule.

What an ERP for food and beverage must produce in 24 hours

Section 204(d) applies to persons who manufacture, process, pack, or hold foods on the Food Traceability List. Those firms keep Key Data Elements for Critical Tracking Events and give that information to FDA within 24 hours, or a time FDA agrees. The final rule page names the events: harvesting, cooling before initial packing, initial packing of a raw agricultural commodity other than food from a fishing vessel, first land-based receiving of food from a fishing vessel, shipping, receiving, and transformation.

A traceability lot code is assigned when a covered firm initially packs a raw agricultural commodity (other than food from a fishing vessel), does first land-based receiving of food from a fishing vessel, or transforms a food. Shipping alone does not create a new code. The lot code you already use on a production batch can serve this role only if the same identifier follows the lot through those events and into the spreadsheet FDA can sort.

Unless an exemption applies, the firm provides an electronic sortable spreadsheet of the relevant traceability information within 24 hours of an FDA request when the request is tied to an outbreak, a recall, or another public health threat. Ask counsel whether an exemption applies to your products. A headcount between 30 and 100 people is not, by itself, a reason to skip the records.

The same FDA page still carries a conflict you should see before you plan the project. The Compliance Date section describes the original date of 20 January 2026, the proposed 30-month extension to 20 July 2028, and FDA's statement that it intends to follow the appropriations act directing the agency not to enforce the rule before 20 July 2028. The Getting Started box on that page still says the compliance date is 20 January 2026 and tells firms to start working on it today. The rule has not been withdrawn. The enforcement horizon you can plan against, as of October 2026, is 20 July 2028, and the records take longer to assemble than the license order.

A covered firm also keeps a traceability plan: how records are kept, how Food Traceability List foods are identified, how lot codes are assigned, and a point of contact. Farms that grow or raise a listed food other than eggs must keep a farm map. A processor that only buys those foods still needs the plan, the lot code at transformation, and the 24-hour spreadsheet.

Which foods an ERP for the food industry has to trace

The Food Traceability List, as of October 2026, names specified soft and semi-soft cheeses, shell eggs, nut butters, fresh cucumbers, herbs, leafy greens, melons, peppers, sprouts, tomatoes, tropical tree fruits, fresh-cut fruits and vegetables, specified finfish, smoked finfish, crustaceans, bivalve molluscan shellfish, and refrigerated ready-to-eat deli salads. Requirements also apply when a listed food is an ingredient and stays in the same form, such as fresh. A sauce plant that buys fresh herbs and cooks them down is in a different position from a plant that packs those herbs, still fresh, into a finished item. Read the list against your own formulas before you decide the rule is someone else's problem.

On 20 February 2026 FDA published an exemption for IMS-listed Grade A cottage cheese regulated under the National Conference on Interstate Milk Shipments. That exemption is narrow. It does not take soft and semi-soft cheeses, shell eggs, or nut butters off the list.

For a 30- to 100-person plant, the practical filter is short. If you pack, hold, or transform any food on that list, or you sell a product that still contains a listed food in the same form, the lot record has to survive a 24-hour request. Map each finished SKU to the list before you configure item tracking. A cheese SKU, an egg SKU, and a nut-butter SKU can share one ERP and still need different events recorded.

What Business Central does with lots, FEFO, and formulas

Business Central tracks serial, lot, and package numbers on inbound and outbound documents. When item tracking is set up, the item-tracking line stores an expiration date and a warranty date. That is the base record a food plant uses for a lot that also has a date. Setup is per item: if the item tracking code does not require the lot, the document can post without one.

Item Tracing runs in two directions. Usage to Origin and Origin to Usage can show item-tracked components, all components, or no components. Microsoft documents the report for finding which customers received a lot and which lot a defective component came from. For a mock recall, Origin to Usage from the ingredient lot is the customer list. Usage to Origin from the finished lot is the component list. Ask the demo to run both, with components turned on, against a batch that consumed more than one ingredient lot.

Picking by FEFO is a location setting with prerequisites. The item tracking code must have serial, lot, or package warehouse tracking. Inventory must be posted with an expiration date. Pick According to FEFO must be turned on for the location. If Strict Expiration Posting is on, expired items are left out of the pick. If two lots share an expiration date, the lowest serial or lot number is selected. A plant that receives the same spice on Monday and Thursday, with different dates, should watch a pick choose the earlier expiration, then watch a second pick when the dates match and the lot numbers decide.

Microsoft says some industries call a production BOM a recipe or formula. Component scrap percent increases expected consumption. The standard cost of a production BOM rolls up only when the parent and the components use the Standard costing method, through Calc. Production Std. Cost or the Standard Cost Worksheet. Versions are valid from a starting date until the next version's starting date. A phantom production BOM explodes into the parent order and does not create a separate production order or an inventory item. If the sub-mix should never sit in a tank as its own SKU, the phantom pattern is the one to have shown. If the sub-mix is stored, sampled, and sometimes sold, it needs its own item and its own lot.

Premium is the license that includes manufacturing. The US pricing page describes Essentials as finance, sales, and operations, and Premium as everything in Essentials plus service management and manufacturing. A producer posting production orders needs Premium for the people who run those orders. Team Members, at USD 8 per user per month paid yearly as of October 2026, is the list price for a lighter user. Displayed prices are informational and can differ by country and region, so treat the page as a list, not a quote. Our Business Central manufacturing note walks through BOM versions and scrap in the same product. The Business Central implementation page is where we phase that setup for a single plant.

What Odoo 19 does for a beverage ERP on lots and recipes

In Odoo 19, expiration dates can be stored only on products tracked by lots or serial numbers. Product settings cover expiration time, best-before time, removal time, and alert time, counted from receipt or production. A buyer on the Odoo forum put the constraint in one line: "Why can I register expiration dates details only when using lot numbers? What if I just want to store expiration date to the quantity of the product I am receiving without assigning a lot number?" If your quality team wants a date on a quantity with no lot, the standard screen will not do that. Assign the lot.

FEFO removal picks by the lot or serial removal date, which is a number of days before expiration. The strategy can be set on a location or forced on a product category, and the category force wins when both are set. Another forum post states the mechanic directly: "Just found out that FEFO removal strategy uses the Removal Date and not the Expiry Date in determining which gets allocated first." Set the removal time first, then run a transfer. A lot with a later expiration and an earlier removal date will leave the location first. That surprises teams who set FIFO on the location and then expect dates to override it. One user described the clash: "I'm using products with lots AND also expiration dates, Removal strategy is set as FIFO. LOT 1 arrived first but has a later best before date than LOT 2." FIFO will follow arrival. FEFO will follow the removal date. Pick one strategy per ship location and test it with those two lots.

The lot form has a Traceability button. The stock-move report shows where a lot came from, where it was stored, and who received it. A user wrote that the finished-lot report shows genealogy back to every raw-material lot and still omits component dates: "When I open the traceability report for a finished lot, I get the full genealogy back to every raw material lot, which is great, but I do not see when each of those components expires." Have the demo show component expiration on that report, or show the extra click that reaches it. A related comment on regulated product is the standard you should adopt: "In regulated sectors, a lot without an expiration date is not very useful for traceability."

Manufacturing order cost has two layers. Expected cost comes from the bill of materials: components plus operation time at work-center and per-employee hourly rates. Real cost uses actual quantities, actual durations, and each employee's hourly cost. Compute Price from BoM resets the product cost to the expected bill-of-materials cost, and later manufacturing orders pull the average again. If you reprice from the recipe on Monday and then post a short-yield batch on Wednesday, the product cost moves again. Decide which figure sales uses for a quote, and which figure finance uses after the batch posts.

Bills of materials can allow, warn on, or block component quantities that differ from the recipe. By-products are optional. Odoo documents them with a winery example: grape mush from a grind operation. Detailed work instructions need the Quality app. A beverage plant that records lees, mash, or trim as a second output should post that by-product on the same manufacturing order as the primary item, with its own lot. The Odoo manufacturing module guide covers bills of materials and by-products in more detail. For a phased rollout of inventory, manufacturing, and quality, see Odoo implementation.

  • Lot on the document (Business Central: Serial, lot, and package numbers on inbound and outbound documents · Odoo 19: Expiration dates stored only when the product is tracked by lot or serial)
  • Dates on the lot (Business Central: Expiration date and warranty date on the item-tracking line · Odoo 19: Expiration, best-before, removal, and alert times, counted from receipt or production)
  • FEFO trigger (Business Central: Pick According to FEFO uses the expiration date; a tie goes to the lowest serial or lot number · Odoo 19: Removal strategy uses the removal date; a category force overrides the location)
  • Trace direction (Business Central: Item Tracing: Usage to Origin or Origin to Usage, with or without components · Odoo 19: Traceability report: source, storage, and recipient)
  • Recipe cost (Business Central: Standard cost rolls up only when parent and components use the Standard costing method; scrap percent raises expected consumption · Odoo 19: Expected cost from the bill of materials and operations; real cost from actual quantities, time, and employee rates)
  • Sub-assembly that is not stocked (Business Central: A phantom BOM explodes into the parent and creates no separate item. The Business Central pages reviewed do not describe a by-product line on the production order · Odoo 19: By-products are optional on the manufacturing order)

Sources for this table: Business Central item tracking, Item Tracing, FEFO picking, production BOMs, Odoo expiration dates, Odoo FEFO, Odoo lots, manufacturing order costs, and bill of materials configuration.

What a food ERP costs a 25-user producer

Assume 25 users at a single US plant: 4 post production orders, 4 handle finance or full warehouse work and do not post production, and 17 only clock in or approve. Team Members is priced here only as the USD 8 list rate. Scanning is not assigned to that license in this example. All figures below are list prices as of October 2026. Microsoft's page says displayed prices are informational and can differ by country and region.

Business Central, paid yearly:

  • Premium (List price: USD 110 per user per month · Users in this example: 4 · Yearly list: USD 5,280)
  • Essentials (List price: USD 80 per user per month · Users in this example: 4 · Yearly list: USD 3,840)
  • Team Members (List price: USD 8 per user per month · Users in this example: 17 · Yearly list: USD 1,632)
  • Combined (Users in this example: 25 · Yearly list: USD 10,752)

Premium is the license that adds manufacturing, so it is used for the four people who post production orders. Essentials covers finance, sales, and operations, so it is used for the four finance and warehouse users who do not need manufacturing. The USD 10,752 figure is licenses only. It leaves out implementation, data migration, and any add-on.

Odoo prints more than one dollar figure per plan on the US pricing page, with the yearly toggle selected, as of October 2026. The page says the discount is valid for 12 months for the initial users ordered. The page does not label which figure is the yearly rate and which is the monthly rate, so a budget should carry both pairs. The eight-user columns below are the four production users plus the four finance and warehouse users from the example above.

  • Standard (Figures printed together: USD 24.90 and USD 31.10 per user per month · Second pair printed on the page: USD 31.10 and USD 38.90 · 8 users at the low figure: USD 199.20 per month · 8 users at the high figure: USD 311.20 per month)
  • Custom (Figures printed together: USD 49.00 and USD 61.10 per user per month · Second pair printed on the page: USD 61.00 and USD 76.20 · 8 users at the low figure: USD 392.00 per month · 8 users at the high figure: USD 609.60 per month)

Custom is the plan that includes Odoo Online, Odoo.sh, or on-premise, plus Studio, multi-company, and the external API. Odoo.sh hosting is extra. Light User is listed at USD 8.90 per light user, with a quote arranged through an advisor. The description includes manufacturing shop floor and inventory barcode operator among limited duties. One App Free is USD 0 for one app, unlimited users, on Odoo Online. Detailed work instructions need the Quality app, and manufacturing orders are documented in the Manufacturing app, so inventory plus manufacturing plus quality is outside that free plan.

Odoo says companies with fewer than 50 employees usually implement with Odoo using Success Packs, and companies above 50 employees usually use a partner. Packs are hours with a dedicated consultant. They do not include travel or maintenance of custom modules. New-customer prices as of October 2026:

  • Starter (Hours: 4 · New customer: USD 493 · Returning customer: USD 580 · What the page adds at this tier: 15 percent off the first pack for new customers)
  • Basic (Hours: 25 · New customer: USD 3,060 · Returning customer: USD 3,600 · What the page adds at this tier: Consultant hours)
  • Standard (Hours: 50 · New customer: USD 5,950 · Returning customer: USD 7,000 · What the page adds at this tier: Data import listed)
  • Custom (Hours: 100 · New customer: USD 10,625 · Returning customer: USD 12,500 · What the page adds at this tier: Customizations listed)
  • Pro (Hours: 200 · New customer: USD 21,250 · Returning customer: USD 25,000 · What the page adds at this tier: Odoo says 80 percent of projects in the estimator's selected scope go live in 200 hours or less)

A 40-person plant sits in the group Odoo points toward Success Packs. A 70-person plant sits in the group Odoo points toward a partner. For either size, price data import on its own line: on the published menu, data import is listed at the Standard pack (50 hours, USD 5,950 for a new customer). The Basic pack (25 hours, USD 3,060 for a new customer) does not list data import. Opening balances by lot and expiration date belong on that import line. Partner-led Business Central projects have no public price list in the same form. Ask each bidder to price data migration, recipe setup, and the mock recall as separate lines.

The license math and the pack math answer different questions. USD 10,752 a year is the Business Central list for this 4 Premium, 4 Essentials, and 17 Team Members mix. USD 5,950 is 50 Odoo consultant hours for a new customer, before subscriptions. Adding those two numbers together would mix a Microsoft subscription with an Odoo services pack. Keep them in separate columns when you compare bids.

What the first phase covers at one plant

A first phase for one plant is a short list of records that the recall test can already use. Scope it in this order.

  1. Item setup for every ingredient and finished good that needs a lot, with the expiration field required on those items. In Odoo that means lot or serial tracking before any date will store. In Business Central it means an item tracking code that posts the expiration date.
  2. Opening balances by lot, including on-hand quantity and expiration date, before new production posts. A trace that starts next month still has to see the lots already in the cooler.
  3. Certified recipes. In Business Central, set scrap percent so expected consumption rises, and confirm parent and components use Standard costing if you need a standard rollup. In Odoo, choose allow, warn, or block when the issued quantity differs from the recipe, and add by-products you stock or sell.
  4. FEFO on the locations you ship from. In Business Central, turn on Pick According to FEFO and decide whether Strict Expiration Posting is on. In Odoo, set the removal time and the FEFO strategy, and check whether a product category force overrides the location.
  5. One mock recall on a finished lot that consumed at least two ingredient lots and shipped to at least two customers.
  6. A traceability plan that names how records are kept, how listed foods are identified in the item master, how lot codes are assigned, and who the point of contact is.

That phase is enough to run the plant's own recall test. It is the scope we use when we implement ERP for a manufacturing plant that has outgrown shared spreadsheets for lots and recipes. Hours beyond it (a second site, a retailer label format, a custom quality workflow) belong in a later phase with their own price.

How to run the recall-trace test before you sign

Run the test on your data, during the evaluation, with a consultant in the room only to navigate. Bring one finished lot from the last 90 days.

  1. Name the finished lot, the quantity still on hand, and the quantity already shipped.
  2. List every ingredient lot consumed, including lots that entered through a rework or a by-product.
  3. List every customer and shipment that received the finished lot.
  4. Show the expiration or removal date on the finished lot and on each ingredient lot.
  5. Export the rows to a spreadsheet you can sort by lot code, product, and customer.
  6. Time the whole exercise from the moment you name the lot.

Business Central's path is Item Tracing, once from the finished lot back to components and once from a suspect ingredient lot out to customers. Odoo's path is the Traceability button on the lot. The regulatory bar, when the rule is being enforced, is the sortable spreadsheet within 24 hours. Your internal bar should be tighter: a planner and a quality lead should finish steps 1 to 5 in a single sitting. If the demo needs a developer to write a query, the configuration is not finished.

Time the same test on the system you have today and write down the hours. The gap between that number and a single sitting is the implementation scope. It is also the gap a recall would expose. FDA's clock is 24 hours for the spreadsheet. Your customer's clock is often shorter, because a buyer will ask which of their shipments to hold while you are still pulling warehouse tickets.

How to choose an ERP for food and beverage

Judge the demo by the recall test, the FEFO pick, and the recipe cost, in that order. A bidder who can show a bidirectional lot trace and a FEFO pick on your two lots has cleared the operations test. A bidder who then prices the recipe from current component cost, scrap or actual yield, and a by-product has cleared the margin test. The spreadsheet for FDA is a third demonstration: ask for it even though the standard pages for these two products do not describe it.

For a single-plant producer under 100 people, this comparison is Business Central Premium, where manufacturing is in the license, and Odoo, where inventory, manufacturing, and quality are configured and the published services menu is the Success Pack. Specialty process suites exist for plants that need modules these two products do not document here. Compare them on the same three demonstrations, and keep their services price on its own line.

The filters that decide a partner are the people named on the project, the hours in the first phase, references from a plant of similar size, a phase plan that includes the mock recall, and who owns the configuration and any custom code when the project ends. A tier badge does not answer those questions. If you also operate in Canada, the companion note on ERP for Canadian manufacturers covers the cross-border plant. The lot test in this article stays the same.

Use the months before 20 July 2028 to load the lots, dates, and recipes you already ship. A list of USD 10,752 a year for 4 Premium, 4 Essentials, and 17 Team Members users, or a new-customer Standard pack of USD 5,950 for 50 hours, pays off when the mock recall on one of your finished lots finishes in a single sitting.

How Flectic can help

Flectic connects production, inventory and finance on Dynamics 365 or Odoo for manufacturers of 20 to 100 people whose stock counts drift from the shelf. Our ERP for manufacturers work includes lot traceability from raw lot to finished serial, so a recall is scoped from system records. Flectic sends a written proposal with a fixed price for each phase before work starts. Book a free discovery call to test whether a Flectic first phase fits your plant.

Sources

FSMA Final Rule on Requirements for Additional Traceability Records for Certain Foods, FDA, October 2026

Food Traceability List, FDA, October 2026

Track items with serial, lot, and package numbers, Microsoft Learn, October 2026

Trace item-tracked items, Microsoft Learn, October 2026

Enable picking by FEFO, Microsoft Learn, October 2026

Create production BOMs, Microsoft Learn, October 2026

Dynamics 365 Business Central pricing, Microsoft, October 2026

Odoo pricing, Odoo, October 2026

Odoo Success Packs, Odoo, October 2026

Expiration dates, Odoo 19.0, Odoo, October 2026

FEFO removal, Odoo 19.0, Odoo, October 2026

Lots, Odoo 19.0, Odoo, October 2026

Manufacturing order costs, Odoo 19.0, Odoo, October 2026

Bill of materials configuration, Odoo 19.0, Odoo, October 2026

Lot numbers and expiration dates, Odoo Help forum, October 2026

FEFO removal strategy, Odoo Help forum, October 2026

FIFO strategy with expiration dates, Odoo Help forum, October 2026

Traceability report and component expiration, Odoo Help forum, October 2026

Lot expiration dates on invoices, Odoo Help forum, October 2026

Frequently asked questions

Does the Food Traceability Rule still have a 20 January 2026 compliance date, or is enforcement deferred to 20 July 2028?

The original compliance date was 20 January 2026. FDA proposed a 30-month extension to 20 July 2028, and the 2026 appropriations act directed FDA not to enforce the rule before that date. FDA says it intends to follow that directive. The Getting Started box on the same FDA page still says 20 January 2026, so use the Compliance Date section when you plan the project. The rule has not been withdrawn.

Which foods on the Food Traceability List does a small producer have to trace when a listed food is only an ingredient?

The list includes specified soft and semi-soft cheeses, shell eggs, nut butters, named fresh produce and fresh-cut items, specified seafood, and refrigerated ready-to-eat deli salads. The requirements also apply when a listed food is an ingredient and stays in the same form, such as fresh. A headcount of 30 to 100 people does not by itself create an exemption. On 20 February 2026 FDA published a narrow exemption for IMS-listed Grade A cottage cheese under the interstate milk program.

Does Odoo FEFO use the expiration date or the removal date?

Odoo 19 FEFO picks by the lot or serial removal date, which is a number of days before expiration. You can set the strategy on a location or force it on a product category, and the category force wins when both are set. Set the removal time, then test two lots whose expiration order and removal order differ. A FIFO strategy on the location will keep following arrival order.

Why can expiration dates be registered only when lot numbers are used?

In Odoo 19, expiration dates can be stored only on products tracked by lots or serial numbers. The product settings for expiration, best-before, removal, and alert time all depend on that tracking, and the clock starts at receipt or production. A quantity with a date and no lot is outside that screen. Turn on lot tracking for any item whose date has to drive picking or a recall.

Is manufacturing included in Business Central Essentials or only in Premium?

Microsoft's US pricing page describes Essentials as finance, sales, and operations. Premium includes everything in Essentials plus service management and manufacturing. As of October 2026 the yearly-paid list price is USD 80 per user per month for Essentials and USD 110 for Premium. A plant that posts production orders needs Premium for the people who run those orders. Team Members is listed at USD 8 per user per month. Displayed prices are informational and can differ by country and region.

What does an Odoo implementation cost for a company under 50 people that needs inventory, manufacturing, and quality?

Odoo says companies with fewer than 50 employees usually implement with Success Packs, which are consultant hours and exclude travel and maintenance of custom modules. For a new customer, as of October 2026, the Basic pack is USD 3,060 for 25 hours, Standard is USD 5,950 for 50 hours and lists data import, and Pro is USD 21,250 for 200 hours. Subscriptions are separate, and the pricing page shows two unlabeled dollar pairs per plan plus a 12-month discount for initial users. One App Free covers a single app, so inventory, manufacturing, and the Quality app together sit outside it.

How do I cost a recipe when scrap, labor time, and actual consumption differ from the bill of materials?

In Business Central, component scrap percent increases expected consumption, and a production BOM rolls into standard cost only when the parent and the components use the Standard costing method. In Odoo, expected manufacturing-order cost comes from the bill of materials plus operation time at work-center and employee rates, while real cost uses actual quantities, actual durations, and each employee's hourly cost. The bill can allow, warn on, or block quantities that differ from the recipe. Compute Price from BoM resets the product cost to the expected bill cost, and later orders pull the average again.

How do I run a mock recall and show which customers received a lot?

In Business Central, Item Tracing can run Origin to Usage to see which customers received a lot, and Usage to Origin to see which component lot a defect came from, with components included. In Odoo, the Traceability button on the lot opens a stock-move report of where the lot came from, where it was stored, and who received it. Time the exercise from a finished lot through ingredient lots and customer shipments, and export a sortable spreadsheet. Ask the demo to show component expiration dates on that same path, because the standard trace report is documented around lots, places, and recipients.