Skip to content
Warehouse, shipping & traceabilityPlastics & PackagingCleaning & Facility ServicesChemicals & Process IndustryFood & Beverage+1

Manage shelf life in the warehouse (FEFO)

demi tracks remaining shelf life per batch, checks your customers' requirements and proposes where each batch goes before it expires.

Today

Older batches expire in the warehouse while newer ones ship first, because they stand at the front or because the warehouse system picks by receipt date instead of expiry. Retail customers reject goods below their required minimum remaining shelf life, and which requirement applies to which customer sits in supplier manuals and e-mails, not in the system. The write-off shows up only at stocktaking or when goods come back.

An example

On Monday morning the agent shows at Tarvina: in nine days, 23 pallets of herb dip SC 250 g from two batches will fall below the 28 days of remaining shelf life that the largest retail customer requires at delivery. Yet since Friday, picking has been taking the younger batch because it stands at the front of the cold store. The agent switches this week's deliveries to the retailer to the older batches, 15 pallets, and assigns the other 8 to two food-service customers who require only 14 days; 4 of them sit in the external warehouse, and it proposes moving them to the main site. A batch of mayonnaise base expires in six days, so it proposes using that batch first in production. Planning confirms, and sales offers one food-service customer a promotion.
Fictional company, typical workflow.

Your data, wherever it lives

Shelf lives sit today per batch in the ERP and the warehouse system, blocks and lab releases in the quality system, and the remaining shelf life each customer requires at delivery in supplier manuals as PDF, in spreadsheets and in e-mails. demi reads, understands and links it per batch and customer, with your rights. Every morning the AI sees which batch is running short and where it still fits, and planning decides.

Where the data lives today

  • ERP
  • Databases
  • QM system
  • E-mails
  • PDFs
  • Office files
Data LayerOne view of everything, with your rights

How demi solves it

Three layers in this order: connect the data first, then the rights, then the AI.

  1. 1 · ConnectData Layer

    Data sources in this case: the ERP, the warehouse management system, the quality system, customer requirements as PDF and e-mail. demi replaces nothing and links, per batch, production and expiry dates, stock and bin location, blocks and lab releases with open orders and with the minimum remaining shelf life each customer requires.

  2. 2 · PermitPermission Layer

    Warehouse and planning see batches, dates and bins; sales also sees its customers' requirements and terms. Only quality decides on blocks and on extensions after a re-test, sales management releases promotional prices for a sell-off, and every decision is recorded.

  3. 3 · ActIntelligence Layer

    The agent calculates each batch's remaining shelf life exactly from its expiry date and the delivery day and checks it against the requirement of every customer with an open order. It proposes which batch fits which order and, for batches running short, use in production, a sell-off or relocation. It reads customer requirements from the documents and has them confirmed once; the language model only explains the proposals.

How it runs

  1. 1

    demi reads batches, expiry dates, stock and bins from the ERP and the warehouse system, and your customers' requirements.

  2. 2

    For each batch, the agent calculates the remaining shelf life on the delivery day and checks it against every open order.

  3. 3

    It assigns the oldest suitable batch to each order and shows when the warehouse picks a younger one.

  4. 4

    For batches running short, it proposes use in production, sale to customers with a shorter requirement or relocation.

  5. 5

    Planning confirms the assignment, and quality decides on blocks and re-tests.

What changes

  • Less expired stock and fewer write-offs

  • Fewer rejections for short remaining shelf life

  • Every morning a list of batches running short, with a proposal

What does it bring you?

Check it with your own numbers

Every starting value is an assumption you can change. The calculation sits right below, step by step.

Assumption, editable

Your numbers

Result

+144 hfreed per year

Assumptions and calculation

demi checks remaining shelf life against customer rules and proposes where batches go; planning decides.

15 min → 9 min per case

How does it run today?

What is already digital saves less: the factor lowers the share demi brings.

How we calculate

120 batches with short remaining life × 15 min × 40% × 1.0 (manual) × 12 months = 8,640 min = 144 h

Value per year, before demi costs

Freed per year+144 h

Assumption: labor cost of $48.62 per hour in US manufacturing in June 2026 (BLS), plus workplace, IT and overhead.

= Value per year, before demi costs

+$9,360

gained per year

144 h ÷ 1,760 h per role = 0.1 full-time roles

An estimate, not a promise. The starting values are assumptions for an industrial company with 150 to 500 people.

Combine with more cases and get the package

Questions about this use case

How does demi know each customer's minimum remaining shelf life?

From your customers' supplier manuals, contracts, specifications and e-mails. The agent extracts the requirements, shows where it found them and has sales confirm them once; from then on they apply to every order of that customer. If a requirement is missing, the customer goes on a list instead of demi assuming a value.

Does demi replace the picking strategy of our warehouse system?

No. Your warehouse system keeps picking; demi proposes the right batch per order and shows when a different one is picked. Once planning confirms, the proposal can go into your system as a batch instruction; how, we clarify in conversation.

Does this also work for raw materials with a re-test date?

Yes. For raw materials and chemicals with a re-test date and for sterile goods with an expiry date, the agent treats the date like a shelf life, schedules due re-tests with the lab in time and proposes use in production on a first-expired, first-out basis. Whether a raw material may be used longer after its re-test, quality decides.

What happens to goods that are too short for any customer?

The agent flags them early enough, while options remain: customers with a shorter requirement, the factory shop, donation or use as raw material, depending on what your rules allow. Sales and quality decide what happens to the goods, and the decision is recorded.

See this case with your data

In the demo we show you the workflow on your own systems.

Your configurator

No use cases yet

Your configurator is still empty

Add a use case from any card or case page and see what it brings per year, with the calculation. Free, no sign-up, no commitment: try it out and change any number.

Browse use cases