What is FEFO and why does a food distributor need it?

FEFO means first expired, first out. The warehouse picks the batch with the earliest expiry date rather than the oldest receipt. For short shelf-life goods it is the difference between selling stock and writing it off, and the ERP should enforce it at picking, not leave it to the picker.

How fast should a food ERP be able to run a recall?

Fast enough that you can name every customer who received an affected batch, and the quantity each received, within the hour. That needs batch numbers captured at receipt and at every dispatch. If the system can only answer by exporting delivery notes to a spreadsheet, it will not hold up on the day it matters.

Which ERP platforms handle batch and expiry tracking well?

Odoo, SAP Business One, Microsoft Dynamics 365 Business Central and NetSuite all support lot or batch tracking with expiry dates. The differences show up in FEFO enforcement, catch weight, van sales and promotion handling, and in how much configuration each needs. Test them with your own products and a mock recall before choosing.

ERP for Food and FMCG Distribution in the UAE

Q: Does UAE e-invoicing apply to food and FMCG distributors?

Yes, like any VAT-registered business. Businesses with revenue of AED 50 million or more must appoint an Accredited Service Provider by 30 October 2026 and go live on 1 January 2027, and the remaining VAT-registered businesses follow from July 2027. Distributors issuing hundreds of invoices a day should treat it as a selection requirement.

Food and FMCG distribution in the UAE looks like trading with a clock attached. Almost everything is imported, margins are thin, and the stock you hold is losing value every day it sits in the warehouse. A chilled SKU with a 21 day shelf life that spends 8 of those days in transit and receiving has less than two weeks to reach a shelf. The retailer on the other end will usually refuse anything with less than a set share of its life left.

That is why a generic accounting package, or a trading system with batch tracking bolted on, tends to fail food businesses in the same places: stock written off because nobody saw the expiry coming, promotions agreed with a supermarket and never claimed, and recalls answered with a weekend of spreadsheet work. If you are choosing a system for a food or FMCG operation, these are the things it has to do and the tests that prove it.

Key takeaways

Batch and expiry have to be captured at receipt and carried through every movement, or nothing downstream works.
FEFO picking should be enforced by the system. A picker choosing the nearest pallet is how expiry write-offs start.
A recall test is the fastest way to judge a platform: name every customer who received one batch, with quantities, in under an hour.
Trade promotions and retailer rebates are a margin line in their own right. If the system cannot track them per agreement, you will leave money unclaimed.
Catch weight and van sales are where platforms differ most. Test both with your own products before you sign.

Batch and expiry control from the receiving dock

Everything in food distribution depends on one habit: every unit that enters the warehouse is received against a batch number and an expiry date. If receiving skips it, or records it on paper to be keyed in later, the gap never closes. The system should refuse to receive a batch-tracked item without both, and should read them from the supplier's barcode where the label carries them.

Once the data is there, the system should do the watching for you:

A near-expiry report by warehouse, bin and customer channel, run daily, with the threshold set per product rather than one number for everything.
A minimum remaining shelf life per customer, so an order for a hypermarket that demands two thirds of life remaining cannot be picked from a batch that does not qualify.
Automatic blocking of expired batches, so they cannot be sold or transferred, only moved to a write-off or return location.

FEFO picking and the warehouse floor

FEFO, first expired first out, is the rule every food warehouse agrees with and few actually follow without help. On a busy morning a picker takes the pallet that is easiest to reach. The system has to direct the pick to the right batch and location, and the handheld scanner has to reject the wrong one. Anything less is a policy on paper.

For chilled and frozen goods, the system should also know which locations are ambient, chilled and frozen, and should not suggest a putaway or transfer that breaks the chain. Temperature logging itself usually lives in dedicated sensors and fleet systems, so the practical question for the ERP is whether it can hold the reference to that log against the delivery, not whether it replaces it.

Recalls and traceability

A recall is the moment a food business finds out whether its system is real. The supplier notifies you that a batch is affected. The questions are immediate: how much of it do you still hold, where, and which customers received the rest, in what quantities, on which delivery notes.

A system that captured batches at receipt and at every dispatch answers that in a single report. One that did not leaves you reading delivery notes. When you evaluate platforms, run a mock recall on a demo loaded with your own data. Pick one batch, ask the vendor to trace it forward to customers and back to the supplier invoice, and time it. It is the most honest test in the whole selection.

Catch weight, units of measure and pricing

Meat, poultry, fish, cheese and many fresh lines are sold by the piece but priced by the kilo, and no two pieces weigh the same. This is catch weight, and it is where platforms diverge most. Some handle it natively, some need a dedicated module or partner add-on, and some leave you to fudge it with manual weight entries on the invoice.

We have seen what getting the basics right is worth. At a multi-branch UAE butchery and food retailer we implemented, unifying stock across branches on one system cut order processing time by 60 percent. The gain did not come from a clever feature. It came from every branch counting, weighing and selling against the same live stock instead of reconciling separate records at the end of the day.

Alongside catch weight, check that the system handles the unit conversions your business actually uses, carton to piece to kilo, and customer-specific price lists that change by channel: hypermarkets, independent groceries, HORECA and online.

Route to market: van sales, returns and trade promotions

Many UAE FMCG distributors still sell a large share of volume through van sales to groceries and cafeterias. That needs a mobile flow where the salesman loads the van as a moving warehouse, invoices at the counter, collects cash or cheques, and settles at the end of the route. The ERP either includes this or integrates with a van sales app, and the integration is where most problems hide: stock, invoices and cash have to land back in the ERP the same evening, not at month end.

Returns need the same discipline. Near-expiry and damaged returns from retailers should come back against the original batch, be graded as resaleable, return to supplier or write-off, and be credited against the right invoice.

Trade promotions deserve their own line in the selection. Listing fees, rebates, off-invoice discounts and promotional pricing agreed with retailers are real money. If the system cannot record each agreement, accrue what you are owed or owe as sales happen, and report on it per retailer, the claims are missed, and nobody notices because the money was never on a report.

Compliance: VAT and e-invoicing

Food and FMCG distributors issue high volumes of B2B invoices, which makes them exactly the profile the UAE e-invoicing mandate targets. Businesses with revenue of AED 50 million or more must appoint an Accredited Service Provider by 30 October 2026 and go live on 1 January 2027, and the remaining VAT-registered businesses follow from July 2027. The penalty for failing to implement the system is AED 5,000 for each month or part of a month. Make sure your chosen platform, and the ASP connection behind it, can produce compliant invoices from every channel, including van sales, before you commit.

How to run the selection

Write down eight flows before any demo, and make every vendor run them with your data:

Receive a mixed chilled shipment with batches, expiries and landed cost.
Pick an order for a customer with a minimum remaining shelf life rule, with FEFO enforced.
Invoice a catch weight line priced per kilo.
Run a van sales route, including a cash collection and a return.
Book a near-expiry return from a hypermarket against the original batch.
Accrue and report a retailer rebate for the month.
Run a mock recall on one batch, forward and back.
Issue an e-invoice from a van sale and a warehouse order.

Score each platform on those eight, not on a generic demo. Odoo, SAP Business One, Dynamics 365 Business Central and NetSuite can all serve a food distributor, and each fits a different size and complexity of business. A vendor-neutral view matters here, because a firm that only sells one platform will always find that platform fits. KAIDO takes no vendor commission on any of them, so the recommendation follows your flows, not a margin.