The problem this app solves

First-expiry-first-out (FEFO) picking chooses an early-expiring lot, but that lot may not meet a customer’s required remaining life. Discovering the difference at the customer’s dock can turn a technically valid picking into an operational dispute.

Evaluate remaining days or percentage against the relevant customer and product policy. Warehouse users can compare eligible lots, correct a failed line or obtain a permitted exception before validation, then retain the completed delivery result.

Features that support your daily work

• Contractual thresholds. Set minimum remaining life in days, percentage of the product’s native shelf life, or the stricter of both.
• Deterministic policies. Scope by company, customer or tag, product or category, operation type, destination country, and active dates with predictable precedence.
• Date-aware evaluation. Evaluate on scheduled delivery, validation, customer promise, or estimated arrival including transit days.
• Eligible Lots assistant. Compare available native quants and expiry facts without replacing FEFO or silently reserving a different lot.
• Validation gate. Block ineligible or missing-expiry tracked lines and recheck date, lot, quantity, route, customer, and policy changes before completion.
• Evidence for service teams. Record immutable completion snapshots, manager overrides with reasons, a customer certificate, and a CSV/PDF audit.

A practical example

Illustrative workflow — the available actions depend on your configuration.

A customer requires a minimum number of days remaining at delivery. The selected lot falls short on the evaluation date. The warehouse compares eligible lots and selects a compliant one, or requests a permitted manager exception with a reason.

A focused delivery workflow

Configure customer and product requirements, then review policy precedence.

Reserve and select lots using native Odoo delivery flows.

See eligible, warning, ineligible, or missing-data status with required versus actual life.

Choose a compliant lot or let an authorized manager record a permitted exception.

Validate, print the compliance certificate, and retain the immutable audit snapshot.

Menus and configuration

• Inventory > Operations > Shelf-Life Exceptions
• Inventory > Configuration > Customer Shelf-Life Policies
• Inventory > Reporting > Shelf-Life Compliance
• Inventory > Reporting > Shelf-Life Override History
• Inventory > Reporting > Shelf-Life Audit PDF / CSV

Reports and exports

• Customer Shelf-Life Compliance Certificate from a completed delivery
• Shelf-Life Exception and Override Audit PDF for policy managers
• UTF-8 CSV audit export with safe formula-like text handling
• List, pivot, graph, and immutable history views

See the workflow in Odoo

Explore the screens in sequence, from configuration to daily work and reporting. Each image includes a caption explaining its place in the workflow.

Requirements and deterministic scope are reviewed before delivery use. Customer defaults provide a controlled fallback when no specific policy matches. Warehouse users compare available lot candidates without changing native allocation. A blocked delivery surfaces the lot and requirement that needs correction. Permitted exceptions retain the lot, requirement, approver, and reason. Completed deliveries leave an immutable requirement and actual-life snapshot. The customer certificate lists delivery, lot expiry, quantity, requirement, and result. Managers can retain a filtered audit report and spreadsheet-friendly CSV.

Compatibility

Target: Odoo 15.0

Required native apps: sale_stock, product_expiry

Editions: Community and Enterprise where the dependencies exist

Online: not supported; use Odoo.sh or a self-hosted server.

No other paid Corvus Nexus app is required.

Deliberate limits

• Quality laboratory testing
• Cold-chain sensor integration
• Automatic lot substitution
• Expiry discount pricing
• Recall management
• A replacement expiry-date engine