Batch & Expiry Tracking for Food Traders: A Practical Guide Using Odoo

In food trading, inventory rarely stays balanced for long.

At one end, excess stock eventually leads to wastage. On the other hand, stockouts can result in missed sales.

This imbalance doesn’t usually come from one major mistake. It builds up over time - as demand shifts, product lifecycles vary, and decisions are made using partial or delayed information.

Most businesses try to manage this using forecasts, spreadsheets, or basic systems. That works in the beginning. However, as operations scale, these methods become obsolete, and it becomes difficult to keep up with the changes.

This is where systems like Odoo start to make a difference. Connecting sales, inventory, and procurement, it creates a more consistent view of demand and supply, helping teams respond with better timing.

This blog breaks down where inventory planning goes wrong and how food traders can use Odoo to create a more balanced, demand-driven approach.

In food trading, inventory and time play a crucial role in ways that most other industries don’t. Products don’t just sit in storage; they move toward expiry every day, whether they are sold or not.

This makes inventory decisions more sensitive. What looks like available stock today can quickly turn into unsellable inventory if it is not tracked and moved at the right time.

The following are the key reasons why batch and expiry tracking become critical in this environment.

• A. Expired inventory directly impacts margins:
  When products expire before they are sold, they can no longer generate revenue, but the cost of purchasing and storing them has already been incurred.
  
  This is where margins are affected. Instead of earning from that inventory, the business absorbs the loss.
  
  These losses are often recorded as write-offs, which simply means the inventory is removed from financial records because it cannot be sold anymore.
  
  Example:
  A distributor has dairy products for $10,000. If 10% of them expire due to tracking, that is a $1,000 loss that could have been prevented with tracking.
  
  
• Compliance depends on traceability:
  Food businesses need complete tracking of their products. They should know the product's origin, its batch, and the area where it is distributed.
  
  Businesses that lack visibility generally face problems in their audits, and product recalls become more difficult and increase regulatory risk.
  
  Example:
  If a specific batch of food items is defective, the business must find the exact location where the product was distributed. Without batch tracking, they may have to recall all stock instead of just the affected batch.
  
  
• Managing perishable stock across warehouses is complex:
  As inventory moves between locations, batches can get mixed, and expiry visibility becomes harder to maintain.
  
  Without a structured system, teams often lose track of which stock to prioritize.
  
  Without a structured system, teams often lose track of which stock to prioritize.
  
  Example:
  A product received earlier in Warehouse A may expire sooner, but Warehouse B dispatches newer stock first because they don’t remember the near-expiry products in Warehouse A. This leads to confusion around prioritizing different stocks.
  
  
• Basic inventory tracking is not enough:
  Basic inventory tracking alone does not solve the problem. Without batch-level and expiry-level visibility, decisions are made without knowing which stock needs to move first.
  
  Example:
  A system may show 1,000 units available, but if it has no updates on near-expiry products, those products may go unsold while newer stock gets dispatched.
  
  

Without proper batch and expiry tracking, businesses begin to experience gaps in visibility, stock rotation, and decision-making. These issues usually come in the form of expired stock, incorrect dispatches, delayed recalls, and inconsistent inventory records across teams.

Here’s what goes wrong without proper tracking systems:

• No real-time visibility across batches:
  Teams may know how much stock is available, but not which batch it belongs to or when it expires. This makes it difficult to decide what should be sold first.
  
  Example:
  A warehouse with 2,000 units in stock can face challenges when it doesn’t know which product has the nearest expiry date.
  
  
• Errors in stock rotation (FIFO vs FEFO issues):
  Without system-driven logic, stock is usually picked based on convenience rather than expiry. As a result, newer stock sells out first, while older batches remain unused.
  
  Example:
  A newer shipment placed near the dispatch area gets distributed first, whereas the older stock in storage is ignored. This results in expiry.
  
  
• Difficulty in handling product recalls:
  When businesses can’t trace batches, it becomes challenging to find where a specific batch was distributed. This delays response during recalls and increases risk.
  
  Example:
  If a supplier tells the business there is a problem with a batch, the business does not know which customers received it, so it recalls all stock of that batch as a precaution.
  
  
• Dependency on spreadsheets and manual processes:
  Manual batch and expiry tracking results in delays, missed updates, and inconsistent records across teams. Instead of becoming clearer, it gets more confusing with time.
  
  Example:
  Sales teams working on older data commit to stock that is not there. Warehouse updates batch details in a spreadsheet.
  
  

Most businesses already track inventory in some form. The issue is not whether tracking exists; it’s whether it actually supports decisions.

In food trading, a system needs to do more than store data. It should guide how stock moves, what gets sold first, and how risks are identified early.

Here’s a closer look at the core requirements that make batch and expiry tracking work in real operations.

• Batch / lot-level traceability:
  Every product must be linked to a specific batch, and that link should stay intact across its entire lifecycle. Without batch-level tracking, businesses lose visibility into where stock came from and where it went. This becomes a major issue during recalls or audits.
  
  Each incoming shipment is assigned a batch or lot number at the time of receipt, and this information is carried through every transaction: transfers, sales, and returns.
  
  How Uncanny helps:
  Uncanny structures batch tracking during implementation so that it aligns with how goods actually flow across warehouses, ensuring traceability is consistent and not dependent on manual updates.
  
  End Result:
  A food distributor handling packaged goods can trace a specific batch from the supplier's delivery to the customer's dispatch within seconds, rather than manually checking multiple records.
  
  
• Expiry date tracking and alerts:
  Each batch should carry its own expiry timeline, and the system should actively flag products nearing expiry. Knowing expiry dates is not enough; teams need time to act before stock becomes unsellable.
  
  What it does:
  Expiry dates are recorded at the batch level, and alerts are configured based on predefined thresholds (e.g., 7–10 days before expiry).
  
  How Uncanny helps:
  Uncanny configures expiry rules based on product type and lifecycle, ensuring alerts are meaningful and actionable instead of generic notifications.
  
  A business receives product alerts 10 days before expiry, allowing it to prioritize sales or offer discounts before losses occur.
  
  
• FEFO (First Expiry, First Out) stock movement
  Stock should be picked and dispatched based on expiry date, not just arrival order or convenience. Without FEFO, newer stock often gets sold first while older stock sits and expires.
  
  What it does:
  The system applies FEFO logic during picking, automatically suggesting or enforcing the selection of products closest to their expiry dates.
  
  How Uncanny helps:
  Uncanny aligns FEFO rules with warehouse layouts and picking processes, ensuring teams follow expiry-based dispatch without slowing operations.
  
  End Result:
  In a multi-batch inventory setup, warehouse staff are instructed to pick items with the earliest expiry date, even if newer stock is more readily available.
  
  
• Multi-warehouse visibility
  Batch and expiry tracking should work across all locations, not just within individual warehouses. Inventory decisions are often made centrally, but stock is distributed across locations.
  
  What it does:
  The system provides a unified view of stock across warehouses, showing batch details and expiry timelines in real time.
  
  How Uncanny helps:
  Uncanny ensures data consistency across locations by structuring inventory flows and permissions, so all teams work with the same information.
  
  End Result:
  A business can identify stock nearing expiry in one warehouse and move it to a location with higher demand.
  
  
• Audit-ready reporting
  The system needs to make it easy to get reports about the products. These reports should show where the products come from and where they go. They should also show when the products will expire.
  
  What it does:
  All batch-level transactions are recorded automatically, allowing reports to be generated instantly for audits or internal reviews.
  
  How Uncanny helps:
  Uncanny designs reporting structures based on compliance requirements, ensuring businesses are always prepared for audits without last-minute effort.
  
  End Result:
  During an audit, a company can produce batch movement reports within minutes rather than manually compiling data from multiple sources.

Most businesses don’t struggle because they lack systems - they struggle because the system doesn’t match how their operations actually run.

Batch and expiry tracking often exists in some form, but it is stored in separate records or relies on manual updates. The result is that data is available, but not reliable enough to act on.

Odoo changes this by making batch and expiry tracking part of everyday inventory movement, from the moment stock is received to the point it is sold.

#1 Batch and lot number management in Odoo:

Every product can be tracked using batch or lot numbers, and this information stays linked as stock moves across the system.

How it works:
Batches are assigned and recorded upon receipt of goods. Products shipped, sold, or returned transfer the batch information without intervention.

A distributor can punch in a batch number and see the date it was received, where it is stored, and which customers it was sold to without having to go through endless records.

#2 Configuring expiry dates at the product level:

Expiry tracking is defined at the product level, so each batch carries its own lifecycle.

How it works:
Expiry rules are configured once, and the system applies them to every batch. This ensures consistency without manual tracking.

The system can automatically calculate expiry dates for each batch based on the receipt date if the product has a shelf life of 30 days.

#3 Automated stock movement based on expiry rules:

Odoo supports FEFO (First Expiry, First Out), ensuring older stock is used before newer stock.

How it works:
During picking, the system suggests or enforces selecting items closest to their expiry dates, rather than relying on manual judgment.

Even if newer stock is physically closer to the dispatch area, the system directs teams to pick older batches first to reduce the risk of expiry.

#4 End-to-end traceability from purchase to delivery:

Each batch can be tracked across its entire lifecycle, from supplier to customer.

How it works: Every transaction involving the batch is recorded automatically, creating a complete traceability chain.

If an issue arises with a batch, the business can identify exactly where it was received, stored, and sold within minutes.

Batch and expiry tracking only becomes useful when it fits into daily workflows. If teams have to stop and “update the system,” it usually fails. But when tracking happens as part of normal operations, it starts working without extra effort.

Here’s what that looks like in practice:

• Recording batch and expiry details during goods receipt:
  Everything starts at the point of receiving stock. If this step is missed or done incorrectly, tracking breaks down later.
  
  How it works:
  When goods arrive, each batch is recorded with its lot number and expiry date. This becomes the base for all future tracking.
  
  Example:
  A shipment of packaged food comes in three batches. Each batch has an expiry date. They are recorded separately so we can track each batch individually. This way, they are not treated as one stock group.
  
  
• Picking and dispatch based on expiry priority:
  Once stock is in the system, the next challenge is ensuring the right batch is sold first.
  
  How it works:
  During order fulfillment, the system guides picking based on expiry dates using FEFO logic, prioritizing older stock.
  
  Example:
  A warehouse has two batches of the product. One batch of the product is going to expire in 5 days. The other batch of the product is going to expire in 20 days. The system ensures that the batch of the product that is expiring in 5 days is picked first, even if it is not the batch of the product to get.
  
  
• Alerts for near-expiry or expired products:
  Tracking expiry is not useful unless teams know when to act.
  
  How it works:
  The system continuously monitors expiry timelines and flags products that are nearing expiry or have already expired.
  
  Example:
  Products nearing expiry in the next 7–10 days are flagged, allowing teams to run promotions or prioritize dispatch before losses occur.
  
  
• Real-time visibility for warehouse and operations teams:
  For tracking to work, all teams need access to the same updated information.
  
  How it works:
  Inventory updates instantly as stock moves, so warehouse, sales, and operations teams all work with the same data.
  
  Example:
  A sales team checks stock availability and sees not just quantity, but which batches are available and their expiry timelines before confirming an order.

In food trading, compliance and quality control are closely tied to how well products are tracked at the batch level. This process isn’t limited to securing records but also to accessing information in real time.

Once you structure batch tracking properly, it becomes easier to comply with everyday operations and manage everyday operations. It also saves you the time of having separate teams during audits and inspections.

Here’s how batch tracking supports compliance and product quality:

• Traceability reports for audits and inspections
  Regulatory checks need businesses to prove where a product came from. They also need to know how the product moved through the system and where it was sent. With batch tracking, all this information is already recorded at every step.
  
  Teams no longer have to collect data. They can make reports right from the system. This saves time. Reduces mistakes. It also reduces the risk of incorrect or missing information.
  
  
• Faster and more accurate product recalls
  If there’s an issue with the quality of any batch, you know where to find it. If companies don’t track batches accurately, they may need to recall all products because they have no clear idea where the problem lies.
  
  With batch-level visibility, teams get an edge at identifying and resolving batch-level issues at the earliest. They can know which area the product was distributed and resolve it at the earliest.
  
  
• Linking quality checks to specific batches
  Quality control is more effective when it is tied directly to batches rather than products in general. Each batch can carry its own inspection records, test results, or quality notes.
  
  It simplifies pattern identification, issue tracking, and ensures that only approved stock moves forward in the supply chain.
  
  
• Maintaining regulatory compliance with minimal effort
  When tracking becomes part of the day-to-day routine, compliance is a natural by-product, not an added burden.
  
  Records are updated automatically as stock moves, and documentation is always available when required. This reduces dependency on manual processes and helps businesses stay prepared for audits without last-minute effort.

Interestingly, many food and beverage manufacturing companies also face a similar operational issue while running their ERPs. We covered a similar blog post that explores the top ERPs for F&B companies in more detail.

Batch and expiry tracking often fails not because of the system, but because of how it is set up and used.

These issues usually show up after go-live, when day-to-day operations begin to expose gaps.

1. Incorrect system configuration for expiry rules

Many businesses enable expiry tracking but don’t configure the rules properly, including FEFO logic, alert timelines, and product-level settings. As a result, the system records data but doesn’t guide decisions.

The solution: Expiry rules should be defined based on actual product lifecycle and movement patterns, not just system defaults.

How Uncanny approaches this:
We configure expiry and FEFO rules based on how your products move in real operations, ensuring the system actively supports stock decisions rather than just recording them.

2. Misalignment between warehouse processes and ERP

In many cases, warehouse teams continue following old practices while the ERP expects structured workflows. This creates gaps between what the system shows and what actually happens on the floor.

The solution: Processes need to be aligned with the system so that every stock movement is captured accurately.

How Uncanny approaches this:
We map warehouse workflows alongside system configurations, ensuring the ERP reflects real-world operations rather than forcing unrealistic processes.

3. Poor user adoption leading to manual workarounds

When teams do not feel comfortable using a system, they usually revert to spreadsheets or manual tracking. This can create two systems and lead to data that does not match over time.

The solution: Users must understand how a system supports their work, not just how to use its features.

How Uncanny approaches this: We focus on training teams based on practical situations. This way, teams can use the system as a part of what they do every day, not something they have to do on the side.

4. Treating ERP as a tool, not a process system

Many businesses treat ERP as a place to store data rather than as a system that drives operations. This limits its impact and keeps processes fragmented.

The solution: ERP should be implemented as a process system, with decisions and workflows structured around it.

How Uncanny approaches this:
We design the system around your operational flow (from goods receipt to dispatch) so that batch and expiry tracking becomes part of how work gets done, not an isolated function.

When batch and expiry tracking are handled properly, the impact is not limited to inventory control. It starts reflecting across operations, planning, and overall business stability.

What initially feels like a tracking improvement gradually turns into better control over how the business runs.
Here’s a closer look at how batch and expiry tracking impact business (when done right):

• Reduced losses due to expired inventory
  With visibility into when things expire, teams can take action early. They can prioritize sales, adjust how they buy things, or move stock around. This helps reduce waste and improve profits over time.
  
  
• Improved warehouse efficiency and stock rotation
  When stock movement follows rules, such as First In, First Out, warehouse teams spend less time figuring out what to pick from inventory. It reduces the number of errors made by warehouse teams. The inventory becomes consistent, and stock is easier to manage.
  
  
• Better decision-making with accurate inventory data
  Having accurate inventory data helps with planning. It allows teams to make choices about buying, setting prices, and moving products around.
  It enables teams to plan ahead with more confidence. Accurate inventory data makes these decisions more reliable.
  
  
• Increased trust with customers and regulators
  Trust is a result of consistent product quality, on-time deliveries, and a company’s ability to handle audits and recalls. Regulators work with a controlled, compliant system, and customers get better products.

Getting batch and expiry tracking right is not just about enabling features in the system. It depends on how well the setup aligns with your actual operations and how consistently teams follow it.

Here’s a closer look at the best practices for implementing batch and expiry tracking in Odoo:

• Start with high-risk or fast-moving products:
  Simply enabling features is not enough. Expiry rules, batch tracking, and stock movement logic need to be configured based on how products actually move. Without this, the system records data but does not support decisions.
  
  
• Standardize warehouse processes before system rollout:
  If warehouse practices vary across teams or locations, the system will only reflect that inconsistency. Aligning processes first ensures that batch tracking works the same way everywhere, reducing confusion later.
  
  
• Train teams on batch and expiry workflows:
  Teams need to understand not just how to use the system, but how batch tracking fits into their daily tasks, from goods receipt to dispatch. This reduces reliance on manual workarounds.
  
  
• Implement in phases to reduce disruption:
  Managing all your operations at once can be a challenge for almost every organization. Therefore, it’s best to implement batch and expiry tracking in stages. Operating in stages helps teams avoid a lot of stress when rolling things out. It helps teams adapt to the platform as they evolve.

The success of batch and expiry tracking depends less on the software itself and more on how it is implemented. A well-configured system supports daily operations. A poorly configured one creates more confusion than clarity.

Here’s a closer look at how you can choose the right Odoo implementation approach:

• Importance of correct configuration and customization
  Simply enabling features is not enough. Expiry rules, batch tracking, and stock movement logic need to be configured based on how products actually move. Without this, the system records data but does not support decisions.
  
  
• Aligning Odoo with real business workflows
  The system should match how your warehouse and operations teams work every day. If there is a gap between system rules and real-life processes, teams tend to find a way around it. This leads to inconsistent tracking.
  
  
• Working with experienced partners for long-term success
  Implementing systems is an ongoing effort; you can’t expect your development partner to set them up just once. Therefore, collaborate with professionals who help you technically and scale the platform with continued operational support.

Uncanny works with businesses to structure Odoo around real operational workflows, from batch tracking to inventory movement. Along with implementation, we also provide Odoo licenses, ensuring the entire setup (from system access to execution) remains aligned and reliable.

Batch & expiry tracking isn’t just an inventory feature; it’s directly impacting your losses, your compliance, and the integrity of your operations. Handled properly, teams spend less time reacting to issues and more time working with accurate information.

Odoo can manage batch-level traceability and expiry tracking in a structured way with the right setup. The trick is to make sure the system fits the way your products flow and your teams work.

Uncanny supports this through an end-to-end Odoo implementation, including licensing, helping businesses build a setup that works in practice, not just on paper.

The next step is to look closely at your current process. Identify where visibility breaks down, where expiry tracking is inconsistent, and which products carry the highest risk.

From there, you can plan a structured implementation that aligns your processes, teams, and system.

Q. What is batch and expiry tracking in food inventory management?

Batch and expiry tracking is really useful because it links each product to a lot and expiry date. This helps businesses keep an eye on the quality of their stock and how it is moving.

Q. Why is batch tracking important for food distributors?

It is very important because it helps distributors track products as they move through the supply chain. That cuts the losses. Makes audits or recalls easier with accurate and readily available data.

Q. What is FEFO, and how does it help manage expiry dates?

FEFO stands for First Expiry, First Out. It is an idea that ensures products closest to expiry are sold first. This reduces waste. Helps to keep stock moving.

Q. How does Odoo handle batch and expiry tracking?

Odoo uses batch numbers to track products, manage expiry dates, and supports FEFO-based stock movement. This means everything is totally traceable across all operations.

Q. How can food businesses prevent selling expired products?

Food businesses can prevent the sale of expired products by tracking expiry dates, setting alerts for stock nearing expiry, and following FEFO-based picking. This means they prioritize inventory when preparing products to send out.

Q. How do you manage product recalls using batch traceability?

Batch traceability is really helpful for managing product recalls. It helps identify the affected stock track, where it has been sent, and take action without having to recall all the inventory. This makes the process a lot simpler and more efficient.