Food Importer Lot Expiry Alerts: A Practical Automation Guide

Food importers should automate expiry alerts at lot level, using FEFO—first expired, first out—rather than generic product reminders. The workflow should capture expiry data at receiving, alert teams at defined intervals, and trigger actions such as stock rotation, markdowns, quarantine, supplier contact, or recall documentation.

What should a food importer record when goods arrive?

Expiry automation is only as reliable as the receiving data behind it. For every imported lot, capture:

Product and SKU

Lot or batch number

Production date

Expiry or best-before date

Quantity received

Supplier and manufacturer

Shipment, container, or purchase-order reference

Warehouse and bin location

Receiving date

Temperature or inspection exceptions, where relevant

Supporting certificates and supplier documents

For foods covered by the FDA Food Traceability List, the relevant traceability lot code and key data elements must remain linked to critical tracking events. The FDA says covered records generally need to be retained for two years and produced within 24 hours when requested.

A simple spreadsheet can work for a small operation, but it becomes difficult to manage when several warehouses, suppliers, currencies, or inbound shipments are involved. In those cases, a connected inventory workflow is safer than asking warehouse staff to maintain separate reminder lists.

How should FEFO expiry alerts work?

FEFO prioritises the lot that expires soonest. That is different from FIFO, which issues the oldest received stock first. A newer shipment can expire before an older one if it arrived with a shorter remaining shelf life.

A practical alert schedule is:

• 90 days before expiry: review demand, open orders, and remaining stock
• 60 days before expiry: notify purchasing and sales
• 30 days before expiry: create a clearance, promotion, or customer-allocation task
• 15 days before expiry: escalate to operations and quality
• 7 days before expiry: quarantine, approve markdown, return, or document disposal
• Expiry date: block further sale or require quality approval

The exact intervals should reflect product shelf life, transit time, customer contracts, and the cost of disposal. A short-life chilled product may need alerts at 30, 14, 7, and 2 days, while a shelf-stable product may justify a 180-day planning alert.

What should happen after an expiry alert?

An alert should create a controlled action, not just send another email. A useful workflow routes the lot according to its condition and commercial status:

1. Check remaining quantity and physical location.
2. Confirm whether the lot is available, allocated, held, or already dispatched.
3. Compare the expiry date with open customer orders.
4. Ask quality or compliance to approve sale, relabelling, return, or quarantine.
5. Notify sales when the lot can be discounted or prioritised.
6. Notify purchasing when supplier credit or replacement stock may be required.
7. Record the final disposition, including the user and timestamp.

For importers, exceptions matter as much as the scheduled alerts. Customs holds, delayed vessels, temperature excursions, split lots, relabelling, and short-dated arrivals can all change the correct action.

This is the type of customer-floor workflow Zaps Studio builds with n8n: receiving data enters one system, rules assess the lot, and the right team receives a task with the relevant evidence. Delivery usually takes two to four weeks after an audit, and clients own the n8n source, credentials, and documentation.

How can lot expiry alerts support traceability?

Expiry tracking and traceability overlap, but they are not the same thing.

• An expiry alert answers: “Which stock is nearing expiry?”

Traceability answers:

Which supplier provided the lot?

Which shipment or container carried it?

Where was it received and stored?

Which customers received it?

Which related lots were split, relabelled, or combined?

What action was taken during a hold, withdrawal, or recall?

The FDA’s FSMA traceability rule requires covered businesses to link key data elements to traceability lot codes across relevant critical tracking events. The rule does not mandate one specific software platform, but records must be legible, protected from loss, and available to the FDA within the required timeframe.

That means an importer should preserve receiving, shipment, warehouse, order, and disposition records—not merely the date an automated reminder was sent.

For a wider implementation pattern, see Zaps Studio’s Shipment Ledger for importer landed-cost operations. Landed-cost data is not a substitute for lot traceability, but linking shipment records with inventory events reduces the manual reconciliation that often causes missing lot information.

Which tools can handle food importer expiry workflows?

The right choice depends on whether the importer needs simple reminders, lot traceability, warehouse controls, or a fully integrated operating system.

Wherefour: Food and beverage ERP with lot tracking, FIFO/FEFO handling, barcode workflows, and multi-location controls. It suits manufacturers and larger food operations, but implementation can be heavier than a small importer needs.

FoodDocs: Food-safety and traceability platform for teams that need digital HACCP, monitoring, and traceability records. It is lighter than a full ERP, but it may not replace warehouse, purchasing, or landed-cost systems.

Zoho Inventory: Lower-cost general inventory platform with warehouse and order controls. It can suit smaller importers, but food-specific FEFO and recall workflows may require configuration or integrations.

Cin7: Multi-location inventory platform with stronger operational controls and integrations. Its broader feature set can increase cost and implementation effort for a single-warehouse importer.

NetSuite: Enterprise ERP with deep financial and supply-chain capabilities. It is appropriate for complex organisations, but licensing, configuration, and implementation are rarely proportionate for a small importer.

Odoo: Modular ERP that can be configured for inventory, purchasing, and traceability. Its flexibility is useful, but ongoing configuration and partner support can become the hidden cost.

Unleashed: Inventory platform suited to product businesses that need stock and batch visibility. It may need additional workflow tooling for advanced recall evidence or importer-specific exceptions.

A basic expiry-alert app may cost about $10–$32 per month. Small-business food-safety and traceability tools commonly sit around $50–$100 per month, while broader SMB inventory platforms can range from roughly $25 to $350 per month. Advanced ERP and traceability deployments can reach $600–$3,000 or more per month before implementation, integrations, hardware, and consulting.

Those are indicative 2026 USD bands rather than guaranteed list prices. User counts, warehouses, barcode scanners, integrations, support, and data migration can materially change the total.

How does custom workflow automation compare with inventory software?

Custom automation makes sense when the importer already has useful systems but the handoffs between them are unreliable.

For example, an importer might already use:

An inventory platform for stock and lot records

A freight or customs system for shipment status

An accounting system for supplier invoices

Email or Slack for internal alerts

A CRM for customer allocations

Spreadsheets for short-dated stock and exceptions

A workflow can connect those systems without forcing an immediate ERP replacement. It can also apply importer-specific rules, such as:

Alert only when remaining shelf life falls below a customer threshold

Escalate lots delayed at port

Create a sales task when inventory is available but unallocated

Block a lot after expiry unless quality approves release

Produce a recall-ready export containing supplier, shipment, location, and customer links

Zaps Studio workflow packages typically range from $1,000–$3,000 per workflow and $3,000–$12,000 per system, with retainers from $500 per month. The build is delivered in the client’s accounts, so the client retains the source, credentials, and documentation.

For context on implementation economics, the Zaps Studio automation pricing guide explains why integrations, data quality, exception paths, and ownership affect the final figure more than the number of individual steps.

Can WhatsApp and customer messaging be part of the workflow?

Yes, but messaging should be an action layer rather than the system of record.

A warehouse manager could receive an internal message when a lot reaches its 30-day threshold. A sales representative could receive a task when short-dated stock needs allocation. A supplier could receive a structured request for credit or replacement documentation.

Zaps Studio’s WhatZaps can support WhatsApp chat and voice workflows, while the underlying lot, shipment, and disposition records should remain in the inventory or traceability system.

Third-party messaging platforms have different trade-offs:

Wati — Shared WhatsApp inbox and business messaging for teams; it is not a complete food inventory or lot-traceability platform.

AiSensy — WhatsApp business messaging with a strong India e-commerce orientation; importer-specific warehouse and recall workflows still need another system.

Respond.io — Omnichannel inbox and routing platform; it can coordinate conversations but does not replace lot-level inventory controls.

HubSpot — CRM automation and routing; it is useful for customer and sales follow-up, but expiry evidence belongs in an inventory or traceability record.

Use messaging to surface the next action, not to store the only copy of a compliance-critical record.

What does a reliable implementation look like?

A practical implementation can be delivered in six steps:

1. Map the receiving process. Identify where lot, expiry, quantity, supplier, and location data currently enter the business.
2. Choose the source of truth. Decide whether the inventory platform, ERP, or a structured database owns the active lot record.
3. Define FEFO rules. Set alert windows by product family, customer shelf-life requirement, and transit risk.
4. Design exception paths. Include customs delays, damaged goods, temperature excursions, split lots, relabelling, quarantine, returns, and disposal.
5. Route ownership. Assign alerts to inventory, quality, purchasing, sales, or management instead of sending every notification to one inbox.
6. Test a recall scenario. Select a lot and confirm that the team can identify its supplier, shipment, locations, customers, and final disposition.

Before building, audit the data rather than automating a broken spreadsheet. If receiving staff enter expiry dates inconsistently, the first project may need validation rules, barcode scanning, or a simpler intake form.

For broader operational examples, see n8n workflow examples for B2B teams and five workflow automation quick wins for B2B operations.

What should food importers ask before buying a system?

Ask vendors and implementation partners:

Can the system track multiple lots for the same SKU?

Does it support FEFO rather than only FIFO?

Can receiving staff scan or validate expiry data?

Can one lot be split across warehouses or customer orders?

Are supplier, shipment, location, and customer records linked?

Can the system document quarantine, markdown, return, and disposal?

Can users export records for a recall or regulator request?

Are barcode hardware, integrations, and additional warehouses included?

What happens when a supplier sends incomplete or conflicting documents?

Who owns the workflow configuration and source code after delivery?

The best food importer lot expiry alert automation is not the system with the most reminders. It is the system that captures reliable lot data, prioritises stock by expiry, routes accountable actions, and preserves the evidence needed to explain what happened.

For a UK studio focused on operations-heavy SMBs, Zaps Studio can build that workflow around the importer’s existing tools rather than forcing a full ERP replacement. Explore Zaps Studio pricing or the food wholesalers automation service to scope the next step.