Abundance of food Autonomous packhouse

How to build the world’s first autonomous packhouse

Packhouses are the quarterbacks of food supply chains. Receiving the product, making a judgement on quality, safety, logistics, and sending it. Except it can't actually see what decides quality and safety. The actual microbiology.

The packhouse of the future will see and make decision based on this biology.

Every fruit is a running biochemical reaction.

PACKHOUSE
3 days left
Town · 40 mi · in state
12 days left
STATE LINE
Out of state · 900 mi
Two identical trucks, two identical crops. What differs is biological rate of reaction.

What is a packhouse? Fundamentally, a packhouse does three things. Product comes in, something gets done to it, it goes out with instructions about where to go. In, process, out. Every job on the floor is one of those three.

This is about two of them, process and out. Specifically, what they look at before they decide.

The three verbs of a packhouse
FIG 1   The whole machine. Process decides what a lot is; dispatch decides where it goes. Both turn on one input the building barely reads.

· the plant today

BLIND TO BIOLOGY?

Here’s the list of jobs on a fresh-cut line. Third column is what each job actually reads. It’s almost always one of two things: how the product looks, or a chemical stand-in. The biology never gets read while you can still do something about it. The blanks are the point.

// current tasks, by verb, and what each one actually reads
TaskVerbWhat it reads todayBiology?
Receive & tip totesintakeranch ID, harvest datenone
Vacuum / hydro coolintakepulp temperature (a proxy)none
Core, trim, shredprocessblade spec, cut sizenone
Flume wash & sanitizeprocessfree chlorine / PAA / ORP (a proxy)none
Optical sortprocesscolour, defect, foreign materiallooks only
Spin dry & bag (MAP)processmoisture, fill weight, film specnone
Line QA inspectionprocessa person, glancinglooks only
Assign to orderdispatchcustomer order + pack datenone
Sequence shippingdispatchpack date (FIFO)none
Finished-product testcontinuouscomposite sample, lab culturereal, but late

One row reads real biology. It’s also the row that does the least. A finished-product test pulls a composite of a few pounds out of a lot running to tens of thousands. Less than one percent. And it’s hunting an organism that sits in clusters, not spread evenly, so missing it is the default outcome. Then it spends a day or two growing the sample before it says anything.

So: under one percent, two days late, against a product that leaves the building in six hours.

The plant is not lightly instrumented. On the one question that matters it isn’t instrumented at all.

· the two failures

TWO FACES OF THE SAME PROBLEM

Two things go wrong in produce. Product rots, and once in a while it makes people sick. These sit in different departments with different budgets. They’re the same failure.

Rot: cut greens ship in pack-date order, so a lot that was warm at harvest and already carrying load sits behind a lot that would have kept another week. Shrinkage.
Safety: you dose to a chlorine number, ship in six hours, hear from a lab two days later. Shipment’s gone by then. Recall.

Same blindness, twice.

// two failures, one root cause
Shrink and spoilageOutbreak and recall
What’s measuredappearance, then ship by pack datesanitizer proxy, then a thin sample, days later
What goes wrongshort-life lots travel furthest; long-life lots get sold firstthe truck leaves before anyone knows
Root causeBiology that decides each lot’s fate is never measured in time to act on it. Microorganisms.

· FOOD IS A BIOREACTOR

FOOD IS ALIVE

A bag of shredded romaine is a few thousand wounded pieces of living tissue, still running in a way. Respiring, senescing, losing water, leaking sugar out of every cut edge into a film of water that is full of bacteria and other microorganisms.

Several clocks, all ticking. Each has a state and a rate. The rate is set mostly by temperature. Cold slows every clock, warm speeds them all up together. Cutting speeds them up permanently, which is why a whole head keeps for weeks and the same head shredded keeps for days. Drag the temperature:

leaf
predicted remaining life
{{ life }} days
respiration · burning sugars{{ r0 }}
senescence · yellowing, browning{{ r1 }}
transpiration · wilt{{ r2 }}
microbial load · soft rot & safety{{ r3 }}
{{ tval }}

{{ take }}

One number moves and all four clocks climb. The microbial one climbs fastest.

What spoils bagged greens is mostly Pseudomonas, which turns cut edges soft and ends the product. What causes people sick is E. coli O157:H7, Listeria, Cyclospora. Different organisms. Same water.

· A new WAY OF ORGANIZING

Sorter vs. router

Today the building reads looks, ejects defects, ships in pack-date order. The version I want reads the water, estimates remaining life per batch, sends each batch where its clock allows. Short-life to the near DC, or foodservice that turns in two days. Long-life to the far account. Unsafe nowhere. Same greens, same building, different question.

Sorter versus router
FIG 2   Same greens and the same building, asked a different question. The sorter asks “what does it look like?” The router asks “how long does it have, and where should it go?”

In order. Each step stands alone. The safety work in steps 2 and 7 pays for the routing work in 3 through 5.

1 Buy the boring 80%, then delete

Most of a packhouse is already automated and isn’t new. Fresh-cut lines are a mature market. Turatti, Sormac and FTNON build the coring, trimming, washing and drying lines. Urschel makes the cutting equipment most of the industry runs. TOMRA and Key Technology make the optical sorters. Integrators bolt these into working plants right now.

Drizzle has now built the sense organ. Add AMRs, forklifts, vacuum cooling and ORP dosing and you have everything.

// bill of materials
ComponentExample vendorsStatusRole
Tote tipper, core & trimTuratti, Sormac, FTNONoff-the-shelfintake
Cutting / shreddingUrscheloff-the-shelfprocess
Flume wash + ORP / PAA dosingline integratorsoff-the-shelfwash & real-time kill
Optical defect sorterTOMRA, Key Technologyoff-the-shelflooks only
Continuous water biosensorDrizzlepartnerthe microbial clock
Spin dry, MAP bagger, case packline integratorsoff-the-shelfpack
Batch gating & diverterscontrols integratorsconfiguretemporal separation
AMRs / autonomous forkliftswarehouse roboticsoff-the-shelfmovement
Per-batch load → remaining-life modelsDrizzlepartnerturns a reading into a number of days
Routing engine + dispatch integrationsoftwarebuildturns days into destinations
Remote ops + PCQIserviceoff-the-shelfthe off-floor human

If you design around per-batch measurement from scratch, several jobs don’t get automated but stop existing altogether. Why? Because they were only ever there to compensate for not knowing.

// steps that stop existing, and why
Step todayExists becauseAfter
Line QA inspection stationa person is the only available judgementdeleted the water reads every leaf; a glance read a few
Finished-product composite testit is the only direct read anyone hasdemoted kept as periodic verification, not as the gate
FIFO dispatch rulepack date is the only number availabledeleted replaced by remaining life
Grade lanes as fixed categorieshumans need legible bucketsdeleted destination assigned per batch, continuously
Blanket hold since last water changeyou cannot tell when the water turneddeleted replaced by a bracketed batch window
Region-wide withdrawal after an incidentresolution stops at the growing regionrare replaced by a per-batch hold

Automation moves a person off a task. Deletion means the task was an artifact of not knowing the underlying biology that is central to decision-making in this new type of packhouse. Most of the labour on a fresh-cut line is the second kind, which is the argument for building rather than retrofitting.

2 Put an eye on the water

A pathogen test is mostly waiting. Culture spends 18 to 24 hours growing the sample before it reads anything. Even “rapid” qPCR usually runs that growth step first. The molecular read is about 90 minutes.

So the slow part was never the test. It was waiting for a few cells to become enough cells to see.

Drizzle doesn’t grow them. It concentrates them. Pull the organisms out of the flow with high flow-rate capture and you hit detectable density by gathering instead of growing. Enrichment becomes obsolete. Say 90 minutes, end to end.

Cyclospora oocysts resist chlorine and the sanitizers the industry doses to. You can hold ORP setpoint perfectly all shift and still ship them, so for that organism the sanitizer number carries no information at all.

It does not have an enrichment step to lose, and there is also no established way to tell a live oocyst from a dead one by PCR. A positive result doesn’t establish that anything was viable. Still unresolved in the literature.

Either way the failure mode is the same. Get the viability call wrong and the assay over-counts, holds product that was probably fine, and you pay in wasted greens instead of sick people. The bench test is a week. Spike live and heat-killed organisms into flume water at known ratios, run with no enrichment, count the dead-cell false positives.
Inside the no-enrichment assay
FIG 3   Inside the sensor. Draw the whole wash water rather than a grab sample, concentrate it instead of growing it, then the one new burden: a viability gate that tells live organisms from leftover DNA without the enrichment step that used to do it for free. The whole-flow draw is what makes the census argument hold. The gate is the open question above.

Let's compare two events.

In 2018, E. coli O157:H7 in Yuma romaine infected 240 people across 37 states. 104 hospitalised, 28 in kidney failure, five dead. The traceback got to 23 farms and 36 fields and stopped there, because comingling and missing lot codes stopped it. So the advisory went out against romaine. All of it, nationally.

Last week FDA and CDC linked 1,644 Cyclospora cases to shredded iceberg at one restaurant chain across five states, part of a bigger national count. Product shipped into 27 states between 29 June and 16 July.

FDA reported a positive product sample on 18 July, then withdrew it a day later as a false amplification. The supplier could then say, accurately, that no product test had come back positive at all. The recall went ahead on epidemiology. The remedy was to stop sourcing an entire growing region for the rest of the season.

So the detection instrument was in-effect 1,644 sick people. The one lab result that entered the story was wrong. And the fix got applied at the resolution of a region and a season, because that was the finest resolution anyone had.

· CAN BIO BE MEASURED?

Census, not sample

The obvious objection to reading the water: the water is shared. Every leaf floats through the same flume, so a reading belongs to the tank, not to any one batch. 

Compare what the two measurements cover. A finished-product test reads a few pounds out of tens of thousands. Under one percent, hunting something that sits in clusters. Miss the cluster and the lot passes quality and safety checks.

The flume touches every leaf in the lot. Whatever is on the product has one place to go, and that’s the water.

Sampling the product is a lottery ticket. Sampling the water is a census. And the plant already built the machine, it just uses it as somewhere to pour chlorine.

Census versus sample
FIG 5   The asymmetry the design rests on. A composite product test reads a fraction of a percent and can miss a rare, clustered contamination entirely. Every unit passes through the flume, so the water carries a signal from the whole lot. Dilute, and complete.

Dilution is real. That’s the price of the coverage. It’s also the half you can solve, because dilution is beaten by concentrating and concentrating is already the architecture. Coverage can’t be beaten by sampling harder. The only way to test all of a lot is to destroy all of it (destructive testing methods).

What bounds the dilution is time. Run the line in discrete batches with a water break between them, so a reading belongs to a window of production instead of to a shift. Twenty to forty minutes per batch, say. Small enough to keep the held set short, short enough to fit the dispatch window.

This costs water, changeover and throughput. It’s the main compromise in the design.

And it doesn’t fix everything. Contaminated material sticks on shredders, conveyors and shaker tables long after the water event that put it there, so separating batches in water doesn’t separate them on surfaces. That’s step 7.

The census argument also assumes what’s on the product actually sheds into the flume during dwell. For bacteria on cut product that’s near-certain, it’s what the cross-contamination literature is about. For Cyclospora it’s open. Oocysts are described as highly adherent, and if they prefer the leaf to the water then the tap under-reads them. They’re large and dense, so once they’re in the water they should concentrate fine. Getting in is the question.

· BALLPARKS

PILOT PARAMETERS

// parameters to fix for a demonstrator
ParameterBallparkWhy it matters
Throughput~5,000 to 15,000 lb/hr, single lineone line, one flume, one sensor; start there
Batch window20 to 40 min of production, water break betweenthe single most important number: it sets the size of the held set
Cut to dock~6 hoursthe entire budget the verdict has to land inside
Sample cadenceevery 3 to 5 min; verdict ~90 min latercadence sets resolution, latency sets slack
Shelf life14 to 17 days from pack, cut greenswhat you are allocating; the thing you sell
Sanitizerchlorine or PAA to ORP, PAA under 80 ppmreal-time kill, and useless against Cyclospora
False-positive budgetthe operational core, see below200+ assays per line per day; 1% means two holds a day
The six-hour window
FIG 6   Why a slow test still gates a fast line. Cut to dock is about six hours. A 90-minute verdict lands inside that window with roughly four and a half hours in hand, which is enough to hold a pallet in the cooler. A two-day culture lands when the only remaining instrument is a recall. In apples the storage buffer was weeks; here it is hours, and hours are enough.

3 Read it, don’t look at it

With the sensor in, “process” shifts from “eject the defects” to “measure & route”. The same instrument reads two things out of the same water, because spoilage and safety live in the same habitat. Total and Pseudomonas load on one channel gives you how long the product has. Pathogen targets on another decide whether it goes anywhere. One architecture, multiplexed.

// the clocks, what reads them, what they route
ClockInstrumentRoutesStatus
Respiration
cut-surface metabolic rate
time-at-temperature model from harvestoverall remaining-life estimatemodeled
Senescence
yellowing, cut-edge browning
optical / colour at the sorternear account vs. far accountpartial
Transpiration
wilt
moisture and weight, modeledship soonermodeled
Spoilage load
Pseudomonas, soft rot
water assay, load channelremaining life → destinationnew
Pathogen load
O157, Listeria, Cyclospora
water assay, target channelrelease or holdnew

Reading state is bounded engineering. Turning state into a per-batch countdown, “this one has eleven days,” is the frontier and the models will get there with enough labelled biology in the plant.

Whatever model you use starts coarse and sharpens on the record the plant feeds back to it. 

Two eyes feeding one per-batch record
FIG 4   The line already writes a per-batch record for traceability. Add the sensor and that record becomes a biological passport, with four actions running off it. Safety is only one.

4 Route on the clock

Now “out” changes. Instead of pack-date order, every batch leaves with a "passport": clocks, estimated remaining life, where that life lets it go, priority. Short life to the DC two hours away, or foodservice that turns stock in a day. Long life to the far account. The plant ships product and an instruction set.

Five decisions off based on that passport.

  1. Routing. High-load batches go to short-shelf channels: the near DC, foodservice, anything that turns in two days. Not onto a truck crossing three states.
  2. Ship order. Move the short-life batches first and hold the clean ones. Pack-date order ignores which batch is actually about to go.
  3. Customer tiering. Your longest-life batches go to the accounts that charge back hardest. Fewer rejections at the dock.
  4. Water management. Break and change the flume when the load says it is spent, not when a timer says so.
  5. Hold. When the pathogen channel says a batch’s remaining safe life is zero, its destination is nowhere.

Food safery verdicts can land ninety minutes into a six-hour window, so you hold a pallet in the cooler instead of chasing it through 27 states.

Per-batch dispatch decision
FIG 7   The hold is just the hardest routing decision. Clear batches route on life; the implicated batch window is held and reviewed, never a blanket withdrawal.

5 PACKHOUSE IS the quarterback

A quarterback needs two things at once. Information, and choices still open.

Ranches have choices and no information. Retailers have information and no choices. They learn about a bad lot as shrink, at the end, attributed to nobody.

The packhouse plant holds both at once. It’s the only place where every unit converges, stops, gets identified, and still has somewhere else it could go. That window is about six hours for lettuce.

Why the packhouse is the quarterback
FIG 9   Why it has to be the packhouse. Upstream has choices and no information. Downstream has information and no choices. Only the middle has both, and only for as long as the product is standing still.

Regulation are already putting the plant in that seat. Under FDA’s proposed Food Traceability Rule, leafy greens sit near the top of the Food Traceability List, and packing is where the traceability lot code gets assigned. Everything downstream inherits identity from that. Compliance was pushed to July 2028, but the commercial deadline passed a year ago, because major retailers started requiring lot-level data in 2025.

So the per-batch record is getting built anyway. This adds biology to that record.

Four things follow, roughly in the order they would actually happen.

  1. Sell shelf life instead of lettuce. Today a case ships with a date derived from pack date, which is a guess dressed as a fact. With a measured per-batch estimate you can commit to days-of-life on arrival and stand behind it. Shrink is the buyer’s problem right now, and a supplier who can move that risk onto their own balance sheet, priced, is not selling the same product as the plant next door. You are the only party who can underwrite that contract, because you are the only one that has that information.
  2. Turn dispatch into an optimisation. You have batches with estimated lives and orders with known transit times and turn rates. Today the rule is pack date. With remaining life it is an assignment problem, and assignment problems have solutions worth several points of margin. No new equipment, easy money.
  3. Call the audible upstream. This is the real power and the least obvious. You are the only entity that measures every grower’s output on the same instrument under identical conditions. The grower sees only their own product. The retailer sees only failures, late, attributed to nobody. So you become the scorer, and the score is actionable agronomy: this block, harvested after eleven, carries a heavier load and delivers four fewer days. Over a season that can change harvest hour, cooling protocol, crew practice, water source. Over several seasons it can change what gets planted where. The plant stops taking whatever the field sends and starts specifying it. This is also part of the model thesis.
  4. Survive the incident that takes out everyone else. Yuma resolved to a region. July 2026 resolved to a region and a season. In both cases the remedy was applied at the coarsest available resolution, because when you cannot resolve you have to over-include, and over-including is the responsible choice. A plant with separated batches and per-batch biological records can show which batches were clean. It keeps selling while its competitors are pulled from shelves. That reorganises a category in a season, which is a different order of thing from a cost saving.

And the loop compounds. Every batch you route and then watch is a labelled example. Measured this, sent it there, here’s what happened. Nobody else closes that loop, because nobody else sees both the biology at pack and the outcome at retail. Prediction improves with volume, so the lead widens.

The big fresh-cut processors are already vertically integrated, so for them this is an internal upgrade, not a seizure of anything.

(Grower scoring creates adverse selection. Score growers, pay them less, and they’ll resist the measurement or send weaker lots to whoever isn’t looking. Probably you pay a premium for measured-good product instead of penalising the rest.)

6 Two clocks

Dose sanitizer will still have a hard time working on a 90 minute run-time.

So the real-time kill stays on the fast proxy, ORP dosing in seconds, and the assay runs slow, certifying each batch and gating dispatch. In HACCP language the dosing loop is the preventive control and the assay is verification. 

Two-timescale control
FIG 8   Two clocks. The fast loop keeps the water dosed in seconds; the slow assay certifies each batch and signs the release. Standard HACCP roles, real number replacing the proxy.

7 WOULD THIS REMOVE ALL HUMANS?

1. FSMA wants a qualified individual owning the food-safety plan. It doesn’t put them on the floor, and one can cover several sites.

2. Machines break, which is a service contract. 

3. Manual swabbing in the facility itself. A fresh-cut plant is wet, cold, and full of the niches Listeria likes. Crevices, etc. This is probably solvable via robotics.

· the economics

WHAT IS AN AUTONOMOUS PACKHOUSE'S EDGE?

Three pools of money.

1. Recall. It’s the least interesting: rare, catastrophic, and you can’t underwrite a plant on it.

What you can underwrite is what happened last week. Not the recall, the decision to stop sourcing a whole growing region for the rest of a season, because there was no way to separate clean product from suspect product. 

2. Shrink. Cut greens have a two-week life, retail shrink on the category is ugly, and the allocation rule is pack date, which has nothing to do with whether a bag survives to the shelf. Short-life batches go on the longest trucks because nobody knows they’re short-life. Spot them at the wash, send them somewhere close, recover a slice every week.

3. Contract change in mentioned in step 5 : Selling a guaranteed remaining life, as the only supplier who can, prices differently from selling a case of lettuce.

The cheapest way to start is adding all this to a vertically integrated processor. 

But it isn’t zero shrink on day one until we create a model.

Get in touch info@drizzlehealth.com

Powered by Drizzle