Not “process manufacturing.” Juice with origin and organic certs on the lot. Cheese with aging lots. Frozen seafood with catch-weight. Olive oil whose landed cost differs by warehouse. Lucian is named for those operations.
Retailers like Kroger and Costco expect lot data, advance ship notices, and EDI as a baseline. Regulators and organic certifiers audit food companies more closely than almost any other industry. And the chain from manufacturer to shelf crosses freight forwarders, customs brokers, warehouses, and truckers, so traceability has to span all of them, not just what's inside one piece of software.
Cases, pallets, containers, and lots aren't interchangeable. If your system only understands one of them, it will fail the moment you need to split a lot across two customers or hold part of a container for FDA review. Lucian tracks sell units, lots, and containers as distinct, linked records.
Large platforms are built for billion-dollar manufacturers. Mid-size importers end up paying for recipe management, production scheduling, and shop-floor tools they'll never use, with contracts to match, and often still can't answer the basic question of where a lot went. Lucian is built for the distributor's actual workflow.
Retail buyers track on-time delivery, chargebacks, and rebate programs closely. Lucian's dashboard shows open orders, at-risk shipments, and on-time performance so you know where you stand before your customer tells you.
Bottled juice, concentrates, and related grocery: origin, organic certs, and FDA holds at lot level.
Lot genealogy, FDA holds on a single entry, and aging inventory that still has to be FIFO-true.
Catch-weight, cold-chain documents, and containers that split across more than one warehouse.
Harvest year, origin, and landed cost that is never the same at one warehouse as it is at another.
Hundreds of SKUs, tight lot recalls, and specs that have to travel with the case.
Shelf life, perishables, and a clock that starts when the container clears, not when someone updates a sheet.
Case-level custody for FSIS/FDA questions, plus true cost when a lot is used as collateral.
Beverage importers run bottled juice, concentrates, and related grocery: tart cherry next to pomegranate, fruit spreads from the same harvest. Organic certs, origin, and juice HACCP documents sit in email while on-hand lives in QuickBooks. When FDA flags an entry, the question is which cases are sealed and which bottles already shipped, not “do we import juice.”
A cheese importer does not have a recall problem in theory. They have a specific lot, a specific warehouse, and a broker email that does not match the QuickBooks item number. Lucian links PO, container, FDA status, and remaining cases so ops can answer before the customer calls.
Frozen seafood arrives with variable weight, split containers, and cold-chain paperwork. Lucian keeps the lot whole even when the warehouse receipt and the invoice disagree on how the cases were billed, disposed, or left on hand.
When a lender asks for on-hand value by warehouse, FIFO layers are the number the bank wants; a blended QuickBooks average is not. See the worked example →
Two receipts of the same SKU are not the same inventory. Origin, harvest, and freight into one warehouse versus another change the layer a sale should draw from. Lucian tracks that without asking finance to rebuild it in a spreadsheet after every receipt.
| Event | Qty | Cost | Value |
|---|---|---|---|
| Warehouse 1 receipt | 800 | $18.40 | $14,720 |
| Warehouse 2 receipt | 800 | $16.10 | $12,880 |
| Sold FIFO / Warehouse 1 | −200 | $18.40 | −$3,680 |
Ingredient importers live in SKU count. A recall lives in lots. Lucian starts from the lot number: customers billed, cases still on hand, documents as filed, so QA is not reconstructing the chain from invoices after the fact.
Recall readiness briefHigh SKU count is why a generic ERP module list fails here. The job is not “inventory management.” The job is “which customers received LOT-2291-JC, and what is still in the warehouse?”
Perishables punish lag. If clearance lives in the broker portal and on-hand lives in QuickBooks, the available number is already stale. Lucian mirrors both so ops sees held vs cleared vs billed in the same status language.
Domestic or non-broker purchases still get a manual-entry path. You are not forced to route every load through the broker to keep the record complete.
Meat importers need the same chain as cheese, plus case identity when a customer or inspector asks what left the building. Lucian keeps billed vs on-hand vs disposed on the lot, with documents attached at the step they belong to.
Book a demoIf inventory is collateral, FIFO layers matter as much as the hold. Finance and QA are looking at the same lot, not two exports.
Bring one case number from juice, cheese, seafood, oil, or spices. We'll trace it.