Skip to main content
Industries // Agritech

Farm-to-fork traceability, without the clipboard.

Track produce from origin to shelf with lot tracking, cold-chain data, and recall tools that answer 'which batches?' in minutes, not days.

Lot

AG-138412

Traceable
  1. Harvest
  2. Intake
  3. Pack
  4. Ship
Traceability
Lot & serial tracking
Sensors
Cold-chain IoT
Quality
Supplier scoring

Every batch traceable, every temperature logged, every recall scoped instantly.

Perishable goods leave no room for guesswork

Agricultural and food businesses juggle short shelf lives, variable supply, quality that changes with weather and season, and customers and regulators who expect full traceability. When a quality issue appears, the question is always the same: which batches, from which supplier, went to which customers?

Answering that from paper records and spreadsheets takes days. With lot tracking in the ERP, it takes minutes: every receipt, transformation, and shipment is linked to a lot, so you can trace forward to customers and backward to origin.

Odoo's inventory supports lots, expiration dates, and traceability reports as standard. We extend it with quality checks at receiving, cold-chain sensor data, supplier scoring, and recall workflows.

What we build for agritech

Batch traceability

Lots followed from harvest or supplier through processing to customer.

Cold-chain compliance

Temperature sensor data attached to lots, with alerts on excursions.

Supplier quality

Inspection results build a quality score per supplier over time.

Recall management

Trace a lot forward and backward and identify affected customers instantly.

Expiry management

First-expired, first-out picking and alerts on stock nearing expiry.

Grower purchasing

Purchase orders, deliveries, and payments for growers and cooperatives.

From workflow to Odoo

WorkflowOdoo appsTypical extension
Receiving from growersPurchase, Inventory with lotsGrading and quality inspection at intake
Processing & packingManufacturing with lot trackingYield and loss recording
Cold storageInventory locationsTemperature sensor integration and alerts
Picking & dispatchInventory with expiry-based removalCustomer-specific labeling
TraceabilityLot traceability reportRecall workflow and customer notification
Supplier managementPurchase, QualitySupplier scorecards

A typical rollout

  1. Stage 01

    Define the lot model

    Decide where lots are created, how they're labeled, and how they flow through processing.

  2. Stage 02

    Intake first

    Receiving with lots, grading, and quality checks, so traceability starts at the source.

  3. Stage 03

    Processing & storage

    Transformations recorded with input and output lots; storage locations mapped.

  4. Stage 04

    Sensors

    Temperature data connected to locations and lots, with alert thresholds agreed with quality.

  5. Stage 05

    Recall drill

    Run a mock recall end to end before go-live, and time it.

KPIs you can finally trust

Time to trace a lot
Measured fromTraceability report from lot to customers
Spoilage and write-offs
Measured fromScrap recorded by reason, product, and location
Supplier quality score
Measured fromInspection results per supplier over time
Temperature excursions
Measured fromSensor alerts by location and duration
Yield per batch
Measured fromInput versus output quantities in processing
Stock nearing expiry
Measured fromLots by remaining shelf life

See it in practice

Our agritech ERP case study shows how spreadsheet-based operations moved into an integrated Odoo environment.

Questions we'll ask in discovery

  • Where do lots start: at the field, at intake, or from suppliers?
  • Which certifications or standards do customers require?
  • Which locations need temperature monitoring?
  • How do you grade produce at intake?
  • How fast can you run a recall today?
  • How do you pay growers?

Traceability, before and after

Before

  • Lot numbers written on paper at intake
  • Temperature logs on clipboards
  • Supplier quality remembered, not measured
  • Recalls traced through filing cabinets
  • Expired stock discovered too late

After

  • Lots created and labeled at intake
  • Sensor readings attached to locations and lots
  • Supplier scores calculated from inspections
  • Recalls scoped in minutes from the system
  • Expiry alerts and first-expired-first-out picking

Systems we typically connect

Sensors

  • Temperature loggers
  • Humidity sensors
  • IoT gateways

Field

  • Mobile intake apps
  • Scales

Partners

  • Certification bodies
  • Retail customer portals

Common pitfalls

Traceability breaks wherever a lot can be mixed without being recorded, such as consolidating crates or repacking. We map every point where lots merge or split, and make recording them part of the normal workflow.

Sensor projects also fail when nobody owns the alerts. Every alert needs an owner, a response, and a record of what was done.

What you receive

  • A documented lot model from intake to dispatch
  • Intake, grading, and quality workflows
  • Sensor integration with alerting
  • Recall procedure and a completed mock recall
  • Supplier scorecards
  • Training for intake, processing, and dispatch teams

What to plan for

Seasonality shapes everything: intake volumes, storage capacity, labor, and cash flow swing with the harvest. Plan the rollout outside your peak season, and size scanning, labeling, and storage processes for peak days. Agree how lots behave when produce is graded, mixed, or repacked, because that's where traceability most often breaks.

Data flows with other systems

SystemInto OdooOut of Odoo
SensorsTemperature and humidity readingsLocation and lot context
Field appsHarvest and intake recordsGrower and field references
CustomersOrders and specificationsLot, quality, and traceability data
Certification bodiesAudit requirementsRecords and reports

Common mistakes we help you avoid

The most common is starting traceability at the warehouse instead of at intake. If lots aren't created when produce arrives, every later record inherits the gap, and a recall still relies on paper. The second is collecting sensor data without agreeing what happens when a threshold is breached. An alert nobody owns is noise; we define who is notified, what they do, and how the action is recorded. The third is ignoring partial and mixed lots, which is exactly where real-world traceability tends to fail.

Traceability with standard tools first

Odoo's lot tracking identifies batches of products that were received, stored, shipped, or manufactured, and supports end-to-end traceability that matters for recalls and expiry datesSource [1]. For perishable goods, that's the backbone: when something goes wrong, you can find exactly which batches went where, instead of recalling everything.

Much agricultural data is captured where connectivity is poor: in fields, barns, and trucks. Apps for that work should save locally first and sync later. The local-first principles of no spinners and an optional network describe the goal wellSource [2], and they're how we design field apps that feed lots and quality data back into Odoo.

Frequently asked questions

Can we manage certifications like organic or GlobalG.A.P.?
Yes, as attributes on suppliers, fields, and lots, so certified and non-certified stock stay separate and certificates can be attached as evidence for audits.
Does it work in sheds and fields with poor connectivity?
Scanning apps can be designed to work offline and sync when a connection returns, so intake doesn't stop when the signal drops.
Can we print our own lot labels?
Yes. Labels with lot numbers, dates, barcodes, and customer-specific layouts can be printed at intake, packing, and dispatch.
Can growers see their deliveries and payments?
Yes, through a portal showing deliveries, grades, and payment status, which cuts down on calls to the office.
Can we label lots at intake?
Yes. Lot labels with barcodes can be printed at receiving, so every following step scans them.
Does this help with certifications?
Traceability, quality records, and recall procedures support the evidence many certification schemes require. Your certification body confirms what's needed.
Does Odoo support lot and expiry tracking?
Yes. Lots, serial numbers, expiration dates, and expiry-based removal strategies are standard inventory features.
Can we trace a lot to every customer who received it?
Yes. Traceability reports follow a lot forward to deliveries and backward to its origin.
Can temperature sensors feed Odoo?
Yes, through IoT integrations that attach readings to locations and lots, with alerts when thresholds are breached.
How do recalls work?
A recall workflow identifies affected lots and customers, blocks remaining stock, and records the actions taken.
Can we record yields and losses in processing?
Yes. Manufacturing orders record input and output lots, so yields and losses are measured per batch.
Do you support cooperatives and many small growers?
Yes. Grower records, purchasing, quality, and payments can be adapted to cooperative structures.
Can quality checks block stock?
Yes. Failed checks can hold stock in a quarantine location until released.
Where should we start?
With the lot model and intake. Traceability is only as good as its first step.
Can we trace a batch from farm to customer?
Yes. Lot tracking in Odoo follows batches through receipts, production, and deliveriesSource [1]. Field apps capture the data at source.
Will field apps work without signal?
Yes. We build them offline-first, so records are saved on the device and sync when the connection returnsSource [2].

Sources

  1. [1]Lot numbers, Odoo 18.0 documentation (opens in a new tab)Odoo S.A.
  2. [2]Local-first software: You own your data, in spite of the cloud (opens in a new tab)Ink & Switch (Kleppmann, Wiggins, van Hardenberg, McGranaghan), April 2019