A customer calls on a Friday afternoon. They want another pallet of the same lot they took last month, and they want to know if it can ship today. Sales messages the warehouse. The warehouse confirms the stock is on the floor. Quality then mentions that two totes from that lot are on hold, waiting on a lab result. Planning, meanwhile, has already earmarked part of the same lot for a different customer whose order goes out Monday. Nobody in that chain is wrong. Everyone is looking at a different slice of the same batch. Twenty minutes of messages later, sales tells the customer "let me get back to you," and by the time the real answer arrives the order has cooled off.
That gap is the problem this guide is about. The batch is physically present. What nobody can say in a single look is whether it is sellable, to whom, and for how long. The number in the system is a quantity. The decision the team actually needs to make depends on status, age, quality hold, allocation, customer restrictions, and where the stock physically sits. When those facts live in different heads and different systems, the cautious move wins every time: under-promise, over-hold, or push it up the chain. All three cost money.
This is written for the person who owns that answer day to day. If you run operations, supply chain, or a plant at a food or agriculture business, you are the one sales calls when they need to know what can really ship. The goal here is a workflow that gives you and everyone downstream one trustworthy view of what each batch can be used for, before a customer promise or a production decision depends on someone chasing it down by phone.
The question is never "how much," it is "in what state"
In most other industries, an inventory count answers the question. In food and agriculture it barely starts it. A batch is not just a quantity sitting in a location. It has an origin, a production or receipt date, a shelf-life window, a quality result that may still be pending, a storage condition it has to stay inside, an allocation that may already be committed, a customer restriction that makes it fine for one buyer and unusable for another, and a traceability history that has to hold together if anyone ever asks where it came from.
So the practical question your team is trying to answer is not "how many kilos do we have." It is "what can we do with this batch right now." Can it be sold? Sold to this particular customer? Used in production? Held for a few more days? Reworked? Substituted for something else? Investigated because a record looks wrong? Every one of those is a different answer, and they change hour to hour as lab results clear, allocations get made, and shelf life ticks down.
When the team cannot trust the batch view, it stops asking the sharp version of the question and starts making defensive decisions instead. Stock gets held longer than it needs to be "just in case." Customers get told no when the answer was actually yes. Product ages out because nobody saw it aging. Escalations pile up because the safe thing to do with an unclear record is to ask someone senior. None of that shows up as a single dramatic failure. It shows up as slower promises, more waste, and a team that quietly distrusts its own numbers.
Follow one batch from the dock to a customer promise
Before changing any system, watch one batch move. Pick a single product family or one facility and trace a real batch from the moment it is produced or received all the way to the point where it either ships against a customer order or gets written off. Do not use the version in the process document. Use the messy version that actually happens.
As you follow it, write down who touches the batch at each step, what they update, where that update lands, and who they call when something is unclear. A batch typically passes through receiving, quality, warehouse storage, planning, allocation, sales promise, picking, shipping, and the traceability log, and the handoffs cross procurement, production, quality, warehouse, planning, sales, logistics, and finance along the way. Each of those functions sees a true but partial picture. Receiving knows it arrived. Quality knows whether it passed. The warehouse knows it moved but not always why. Sales knows it was promised but not whether the promise is still safe.
The distinctions that trip teams up show up clearly once you walk it. A batch can be physically present but commercially unavailable because it is allocated elsewhere. It can be sitting in the warehouse but blocked because quality has not released it. It can be perfectly usable for one customer and unsuitable for another because of a certificate, an allergen line, or a country restriction. If your current view collapses all of that into one "on hand" figure, the figure is technically correct and operationally misleading.
Physical stock and usable stock are two different numbers
Most batch visibility problems come from one habit: treating physical quantity as available quantity. They are not the same, and the difference is exactly where the day-to-day pain sits. A useful workflow keeps these layers separate so anyone can see, for a given batch, how much is genuinely free to promise versus how much is spoken for, blocked, or at risk.
| Stock layer | What it actually means | Decision it affects |
|---|---|---|
| Physical stock | Everything of this lot that is in the building, regardless of status. | Space, storage conditions, stock counts. |
| Quality-released stock | The portion that has passed quality and is cleared to move. | What can leave the site at all. |
| Uncommitted stock | Released stock that is not already allocated to another order. | What a new customer promise can draw on. |
| Customer-eligible stock | Uncommitted stock that also meets this specific customer's restrictions and documentation. | What this order in particular can take. |
| Stock at risk | Anything aging toward its shelf-life limit or missing a record it needs. | What should be used or sold first, or investigated. |
Once those layers are visible, the questions that used to take a round of phone calls answer themselves. What can ship today is the customer-eligible number. What should move first is the stock-at-risk view. What needs a decision before it can be sold is the gap between physical and released. Sales, planning, and production can each read the same view and reach the same conclusion, which is the whole point.
Give every batch a status people trust
The layers above only work if each batch carries a clear, agreed status that everyone reads the same way. Vague statuses are worse than none, because they invite each function to interpret them differently. A dairy team saying a lot is "in the warehouse" tells you nothing about whether it can ship.
Agree on a small set of states that map to real decisions and cover the cases your product actually hits. Useful ones include pending receipt, pending quality, released, allocated, partially allocated, on hold with a reason, rework needed, blocked for a customer restriction, shipped, and under trace review. The exact list matters less than two things: every batch always sits in exactly one of them, and the status changes the moment the underlying fact changes, not at the end of a shift when someone gets around to updating a sheet. A lot that cleared quality at 10am but still reads "pending" at 2pm is the reason a sellable pallet sat still while a customer went elsewhere.
What the batch view has to carry
The minimum useful version of all this is a single batch view, sometimes called a status board, that the team can open instead of making calls. It does not need to be a new platform. It needs to hold enough per batch that a person can make a real decision without reconstructing the story from four systems.
For each lot, that means the batch or lot ID, the product, the quantity and unit, where it physically sits, its production or receipt date, its expiry or shelf-life window, its current quality status, any hold reason, what it is allocated to, any customer restrictions, its movement history, and the name of the person who has to resolve an open exception on it. A concrete version reads like this:
| Batch | Usable status | Constraint | Shelf life | Owner | Next action |
|---|---|---|---|---|---|
| Lot A17 | On hold | Quality release pending on two totes | 18 days | Quality lead | Chase lab result, then release or segregate |
| Lot B22 | Released, uncommitted | Short shelf life relative to the rest of stock | 6 days | Planning | Prioritize for near-term orders before newer lots |
| Lot C09 | Allocated | Customer certificate pack incomplete | 27 days | Sales ops | Complete documentation before pick and ship |
| Lot D31 | Blocked | Allergen line not eligible for this customer | 40 days | Quality lead | Redirect to an eligible customer or channel |
The value is not the table itself. It is that sales, warehouse, quality, and planning are now reading one story instead of assembling four partial ones. When the constraint and the owner sit next to the quantity, an open question turns into an assigned action, and the answer to a customer stops depending on who happens to be at their desk.
Where the batch view breaks
The places this workflow tends to fall apart are specific, and naming them makes them fixable.
Quality holds live outside the inventory view
Holds often sit in a quality system, a lab spreadsheet, or someone's head, while the inventory system still shows the stock as available. Sales sees a number, promises against it, and only discovers the hold when picking fails. If a hold does not immediately change what the inventory view shows, it will keep catching people late.
Allocations only exist in a spreadsheet
When commitments to customers are tracked in a side sheet that only planning maintains, everyone else is promising against stock that is already spoken for. The physical count looks healthy right up until two orders reach for the same pallet.
Shelf life is tracked as a date, not a decision
A shelf-life field on a record is not the same as a view that surfaces what is aging out this week. Product expires not because nobody knew the date, but because the date was buried in a field nobody was watching against today's orders.
Status updates lag the physical reality
A batch that has cleared quality but still reads pending, or shipped but still reads allocated, sends the team the wrong signal. The workflow is only as good as the moment the status flips, so the update has to be tied to the event that changes it, not to an end-of-day catch-up.
Customer restrictions are remembered, not recorded
Which lots a given customer can and cannot take often lives in the experience of one salesperson or one quality manager. When that person is out, the business either stops or guesses, and guessing on an allergen or a certification is the kind of mistake that ends up in a complaint file.
AI is added before the batch IDs are trustworthy
Searching batch histories with AI is genuinely useful, but only once the lot identifiers and movement logs are clean enough to trust. Point a search tool at inconsistent lot codes and it will return confident, wrong answers faster than a human would.
Fit the data and systems to the decisions
It is tempting to start by connecting every system. Resist that. Start from the decisions the team makes about a batch, then connect only the fields those decisions need. The systems in play usually include an ERP, a warehouse system, production records, a quality or lab system, barcode or scale scans, supplier documentation, logistics paperwork, customer order data, and the inevitable spreadsheets. You do not need all of them talking at once. You need the specific fields that let someone answer a real question.
| Decision to make | Fields it needs | Likely source | Owner |
|---|---|---|---|
| Can this ship at all? | Lot ID, quality status, hold reason, release decision | Quality or lab system, ERP | Quality |
| Can it ship to this customer? | Customer restrictions, certificate status, allergen and origin data | Customer order data, supplier records, documents | Sales ops with quality |
| How much is free to promise? | Quantity, allocation, order commitments | ERP, warehouse system, allocation sheet | Planning |
| Which stock should move first? | Production or receipt date, shelf-life window, storage condition | Production records, warehouse system | Warehouse and planning |
| Where is this batch now and where has it been? | Location, movement timestamps, traceability reference | Warehouse scans, ERP, traceability log | Warehouse |
If a field the team needs is not reliable yet, mark it as a known data-quality issue rather than hiding it. A visible gap that says "we do not trust this allocation number yet" is far safer than a clean-looking figure that is quietly wrong. The team can work around a flagged gap. It cannot work around a mistake it does not know it is making.
Where AI helps inside batch visibility
AI is useful here once the batch data underneath it is trustworthy, and its job is to prepare decisions rather than make them. It can summarize the day's exceptions so the morning review starts from a short list instead of a full inventory dump. It can flag batches approaching a shelf-life threshold before anyone has to remember to look. It can classify hold reasons, draft an investigation note from records that have already been approved, and pull a batch's history together quickly during a trace review, which is often the difference between a two-hour scramble and a ten-minute answer.
What it should never do is release stock, override a quality decision, change a traceability log, or make a customer promise on its own. Those decisions carry food safety and commercial weight, and they belong to the people accountable for them. The rule that keeps this safe is simple: AI assembles and suggests, people release and commit. Point AI at a batch view that is still built on inconsistent lot codes and missing holds, and it will make an unreliable picture look more convincing, which is worse than leaving it obviously rough.
A worked example: two plants and a distribution center
This example is illustrative, meant to show the shape of the work rather than describe a real company or promise a specific result. Say a dairy processor runs two plants and a central distribution center. Plant one makes cultured products with tight shelf lives. Plant two makes longer-life items. The distribution center consolidates both and ships to retail and food-service customers, some of whom require specific certificates and audit documentation.
Today, availability for a customer order is worked out by a planner who opens the ERP for quantities, checks a quality spreadsheet for holds, glances at a shared allocation sheet, and messages a plant contact to confirm what actually cleared that morning. It works, most of the time, because a few experienced people hold the picture together. It breaks when one of them is on leave, when a lab result is slow, or when two customers want the same short-life lot in the same afternoon.
The first move is not to replace any of those systems. It is to build one batch view for a single product family, say the cultured line from plant one, that separates physical stock from what is actually sellable, and shows hold reason, allocation, shelf-life risk, source link, and an owner for every open item. In the first week the team traces one batch end to end and finds, as teams usually do, that holds and allocations are the two things nobody can see in one place. In the following weeks they connect just the ERP quantities, the quality release status, and the allocation commitments into that view, and start running a short daily look at exceptions from it. By the end of the first month, sales can ask "can I promise this lot to this customer today" and get an answer from the view rather than from whoever happens to know. The longer-life plant-two products and the wider certificate cases come later, once the pattern holds for the harder, shorter-life family first.
What to measure
Measure whether the team is making faster, cleaner batch decisions, not whether a dashboard looks complete. The signals that tell you it is working are practical ones: the share of batches with a current, trusted status; how many holds sit unresolved and for how long; how much stock is aging toward its limit by category; how often two orders collide over the same allocation; how many manual lookup requests still land on the plant contacts each week; how many shipments slip because a status was unclear; how long a trace review takes; and how much product gets written off because nobody saw it in time.
To put a number on the cost of the manual chasing the workflow removes, the AI automation ROI guide and the Workflow Readiness & ROI Calculator give you a starting frame.
Traps that keep the answer manual
A few mistakes reliably pull teams back into phone calls. The most common is showing a stock quantity without its status, age, or customer restrictions, which is the original problem wearing a nicer interface. Close behind is letting quality holds live anywhere other than the inventory view, so the number and the reality drift apart. Keeping allocations in a spreadsheet only one person maintains has the same effect, since everyone else promises against stock that is already committed.
Two more are worth naming because they feel like progress. One is adding AI search or automation before the lot identifiers and movement logs are clean enough to trust, which speeds up wrong answers. The other is trying to fix every facility and every product at once instead of getting one product family genuinely working first. The batch view earns trust by being right about something small before it is asked to be right about everything.
The first month: make one product family visible
The way to start is narrow and concrete. Choose one product family, one facility, or the single batch flow that causes the most friction today, and build the view around that before touching anything else.
| Week | Focus | What should exist by the end |
|---|---|---|
| Week 1 | Trace one batch from production or receipt through quality, warehouse, allocation, and the customer promise | A clear map of who updates what, where holds and allocations actually live, and where the current view goes dark |
| Week 2 | Agree the status model, the fields each decision needs, and the exception types | A shared set of batch states everyone reads the same way, and a short list of what counts as an exception |
| Week 3 | Connect the minimum data and stand up the batch view | One view that separates physical from usable stock, with hold reason, allocation, shelf-life risk, source link, and owner |
| Week 4 | Run the first exception review from the view and assign owners | Aging and blocked stock resolved or owned, and sales, warehouse, quality, and planning using one view for decisions |
This is the kind of contained first step described in How to Choose the First Workflow to Improve with AI. Keep going into a second product family if the team can now answer what can be used, sold, held, or traced without reconstructing it by hand. Stop and fix the basics first if the lot identifiers or the hold rules are still not trusted, because everything downstream inherits that doubt.
How Ubisar would implement this workflow
In week 1, Ubisar would choose one product family and trace a single batch flow from receipt or production through warehouse, quality, allocation, sales promise, and customer documentation. The first output would be a batch view that separates physical stock from usable stock, with hold reason, allocation status, shelf-life risk, a link back to the source, and an owner for every open exception.
In weeks 2 and 3, we would connect the minimum ERP, warehouse, quality, sales order, document, and spreadsheet data needed to keep that view current, fixing the data and the tools around this one workflow together rather than as a systems project. AI would help the team find approved records, summarize a batch history, and check whether documentation is complete, while release, allocation, and customer-promise decisions stay with the people who own them.
By week 4, sales, warehouse, quality, and planning should be able to use one live view for batch decisions. Keep going if the team can answer what can be used, sold, held, or traced without manual reconstruction; narrow or pause if the lot identifiers or hold rules are still not trusted. This is the kind of month covered by AI, Data & Tech Implementation. If inventory and batch answers are slowing your team down, tell us the workflow and we will map it with you.
Related Ubisar resources
For help deciding whether to bring in a consultant, an automation agency, or software for this kind of work, read AI consultant vs AI automation agency vs software. For budget context, What AI Implementation Costs in 2026 sets expectations, and related examples for other food and agriculture problems sit in the workflow library.