Packhouse Software: What a Fresh Produce Packer Buys First
In short: packhouse software is a set of products, each with its own record: a packhouse or grower management system for intake, lots and grower payments, an ERP, retailer label and EDI tools, QA and residue records, a warehouse and cold store system, and OEE and light MES on the packing lines. Optical graders come with their own software. Buy first the system behind the record that fails you in peak season.
- Grower lots, bin tickets and grower returns are the packhouse system's job, and they are money records.
- Retailer labels and order messages decide what each line packs today, so the label and EDI link sits close to the lines.
- OEE and light MES show why the punnet filler, flow wrapper or weigher stood still, and what the hand-pack tables turned out.
- In the sample flow-wrap shift below, 40 recovered minutes are worth about EUR 199 a shift and about EUR 100,000 a year, or about EUR 42,000 over a five-month season.
A packhouse lives by the season. For a few months the bins arrive faster than the lines can take them, crews double, and retailer orders change by the hour. Then volumes drop, lines stand, and the people who knew the routine go home until next year.
Every hour of that matters twice, because fresh produce loses value while it waits. The FAO estimates that around 14 percent of food produced is lost between harvest and retail, and fresh produce is part of that loss. A packing line that stands is not only lost packs; it is bins warming in the yard.
Packhouse software and packhouse management software cover very different jobs: grower accounts, grading, labels, cold store, line performance. Below is which system keeps which record, what to buy first, and one packing shift priced in euros. Fabrico makes the line layer, OEE and light MES; the other rows are categories, with no software vendor named.
The packhouse software map: which system keeps which record
Some packhouse systems prove where produce came from, how it was graded and labelled, and what the grower is owed. Others show where packing line hours went.
| System | What it does in a packhouse | Owner | Link to line data |
|---|---|---|---|
| Packhouse or grower management system | Intake, bin tickets, grower lots, pack-out per lot, consignments, grower payments or returns | Packhouse manager, finance | Shows which lot was running when the line stopped |
| Optical grader software | Grade, size and colour results from the grading line | Grading line, QA | Grader stops explain why the pack lines starved |
| ERP | Orders, stock, costing, invoicing | Finance, commercial | Sends pack formats and rates; gets good packs and losses back |
| Retailer label and EDI | Order messages, despatch notices, pack and pallet labels with class and origin | Commercial, line leaders | Each order change shows as a changeover on the line |
| QA and residue records | Residue tests, grower certificates, audit files, intake checks | QA, technical | Held packs counted once QA decides |
| Warehouse and cold store (WMS) | Pallets, locations, cold room temperatures, stock rotation | Logistics | Pallet count per packing run, if the WMS asks |
| Labour and time systems | Clocking, crews, piece rates for pickers and packers | HR, finance | Crew hours meet line hours in the pack cost |
| OEE and light MES | Line stops, pack counts and reasons on fillers, wrappers, weighers and tables | Operations, CI | This is the line layer Fabrico makes |
The last row is the one that most often has no owner: why line 3 lost an hour on the Tuesday of a heatwave, and what that cost. Measuring the line means a timeline per machine and shift: when the flow wrapper or punnet filler ran, stood or ran slow, when it waited for bins or grade, and the reason the line leader gave. That is where OEE and a light MES start, and the walkthrough below shows the screens.
What you see: a shift timeline, unclassified time waiting for a reason, and the operator's line-down screen, on sample lines rather than a packhouse. Book a demo.
Plays from YouTube. Google may set cookies when you press play. Privacy policy.

Text version of this infographic
- Grower lots, bin tickets and returns: packhouse or grower system.
- Grade and size results: optical grader software.
- Retailer orders, labels and ASNs: retailer label and EDI.
- Residue tests and audit files: QA records.
- Pallets, temperatures and rotation: WMS and cold store.
- Orders, costing and invoicing: ERP.
- Filler, flow wrap and weigher stops: OEE and light MES.
- Packs off hand-pack tables: camera add-on count.
- A pack count is not a lot record. Lot codes stay in the packhouse system.
Where packing line hours and produce go
Machine ratings set the ceiling, and the produce sets the clock. Three published figures and one line rule show why packhouse line data needs both:
| Topic | Published figure | What it means for the line data |
|---|---|---|
| Cooling delay | Ontario's agriculture ministry gives, as a rough guide, that a 1-hour delay in cooling reduces a product's shelf life by 1 day, mostly for very perishable crops in hot weather | When the line stops, bins wait. Line stops at peak are shelf life as well as packs |
| Retail shrink, vegetables | USDA ERS puts the average supermarket loss rate at 11.6 percent for 31 fresh vegetables, from 2,900 US supermarkets in 2011 to 2012 | Shelf life lost in the packhouse shows up later as retailer shrink and claims |
| Retail shrink, fruit | ERS's food loss page gives supermarket loss rates from 4.1 percent for bananas to 43.1 percent for papayas across 24 fresh fruits | The more perishable the crop, the more a waiting bin costs |
| Flow wrapper | A wrapper's rated speed is a ceiling, and a hand-loaded infeed rarely brings the line near it | The wrapper is rarely the limit; the infeed, the weigher or the hand loaders set the real rate |
On the packing side, the hours slip away after the grader. Lines wait for bins or for the right grade, retailer changes swap film, labels and punnets several times a shift, and weighers starve when the infeed is uneven. Hand-pack tables run as fast as the crew on the day, which is why new seasonal crews show up as slow running. Grade-out is not a line quality loss: fruit graded to juice or class II never reached the line. Ideal rates per pack format are in OEE for fresh produce packing, the split between short stops and slow running in reduced speed loss vs minor stops, and camera stations in computer vision for fresh produce packing.
Packhouse failure modes and their early signs
What goes wrong, what the line data shows before anyone complains, and the usual fix:
| Loss | Early sign in line data | Fix |
|---|---|---|
| Line starved by the grader or bin supply | "No product" stops that cluster at shift start, after lunch or when the grader changes lot | Stage bins by pack plan and log grader stops on the same timeline as the pack lines |
| Retailer changeover overruns | Changeover minutes per retailer spread wide, with the first good pack well after the restart | One change standard per pack format (film, label, punnet), as in changeover standards for FMCG lines |
| Weigher starving or overfilling | Speed drops in short steps while the line shows as running; give-away rises | Even the infeed and track weigher speed as its own loss, apart from stops |
| Film and label short stops | Many stops under two minutes after a new film reel or label roll | Reel and splice checks at the change; film, label and jam as separate reasons |
| Slow hand-pack tables in week one | Packs per table hour well under the format's standard while the crew is new | Count the tables, pair new packers with experienced ones, and track the curve by week |
| Bins waiting in the heat | Long line stops on hot afternoons while full bins stand at the tipper | Move waiting bins to the cooler when a stop passes a set time, and log it |
Worked example: one flow-wrap shift in money
Sample figures for illustration only; the packhouse below is not a real one.
A year-round prepacker flow-wraps whole cucumbers for retailers, with glasshouse and imported supply. The wrapper could run far faster, but the hand-loaded infeed sets the line's ideal rate at 60 packs a minute. A shift is 8 hours with 30 minutes of planned breaks and cleaning, so planned production time is 450 minutes.
In one shift the line data shows:
- 45 minutes for three retailer changeovers (film, labels, cartons);
- 30 minutes waiting for bins and for the right grade;
- 15 minutes of longer wrapper and weigher stops;
- 18,360 packs counted, of which 459 were rejected for weight or label.
| Step | Calculation | Result |
|---|---|---|
| Run time | 450 planned minus 90 lost (45 + 30 + 15) | 360 minutes |
| Availability | 360 / 450 | 80.0% |
| Performance | 18,360 counted / (360 x 60 ideal) | 18,360 / 21,600 = 85.0% |
| Quality | (18,360 minus 459) / 18,360 | 17,901 / 18,360 = 97.5% |
| OEE | 0.800 x 0.850 x 0.975 | 66.3% |
| Check | 17,901 good / (450 x 60 = 27,000 possible) | 66.3% |
Now price it. With a sample contribution margin of EUR 0.10 per pack, one minute of run time at this shift's performance and quality gives 60 x 0.85 x 0.975 = 49.725 good packs, or about EUR 4.97. An hour of downtime costs EUR 298.35 in lost margin, before any shelf life lost in the yard.
The fix in reach is not all 90 minutes. A change standard per format cuts the three retailer changes from 45 to 30 minutes, staging bins by pack plan cuts the waits from 30 to 10, and reel checks cut the long stops from 15 to 10. That recovers 40 minutes a shift:
- Per shift: 40 x 49.725 = 1,989 good packs, x EUR 0.10 = EUR 198.90.
- Per month: two shifts a day on 21 production days is 42 shifts, so EUR 198.90 x 42 = EUR 8,353.80.
- Per year: 12 months of 42 shifts is 504 shifts, so EUR 198.90 x 504 = EUR 100,245.60.
OEE rises from 66.3% to 73.7% (17,901 + 1,989 = 19,890 good packs out of 27,000). A seasonal packhouse should price its own season instead: five months of 42 shifts is 210 shifts, or EUR 41,769 a season on the same line.
Two checks. The money only counts if retailers take the extra packs; if the line already meets orders, price the minutes as overtime not paid instead. Sensitivity: at EUR 0.06 a pack the same minutes are worth EUR 119.34 a shift and EUR 60,147.36 a year. The calculation itself is the standard one in OEE calculation.
Which packhouse management software to buy first
Pick the record that fails worst at peak. If grower statements or lot codes are wrong, nothing else matters yet. If the records are sound and the lines still miss orders, the line layer comes next.
The kind of packhouse changes the order.
| Packhouse | Usually first | Then |
|---|---|---|
| Grower-owned, own crop only | Packhouse system and labels | OEE on the busiest pack line |
| Marketing packhouse for many growers | Grower system with lots and returns | Grader link, then line OEE |
| Retail prepack with many formats | Label and EDI tied to the lines | OEE with a reason code per change |
| Year-round, several sites | A single ERP and one lot code format | The same stop reason list at every site |
Set up before the season, not in the first week of harvest, and start the line layer on the line that misses the most orders, then add the hand-pack tables. Book a demo to see a retailer change, a weigher starve and a hand-pack table on one timeline, with the lost minutes priced by line.
What moves between packhouse systems
The lot code is the thread. It starts at intake, has to survive the grader, and must reach the pack label and the pallet. Every place it is typed again is a place a trace can fail.
The label carries legal weight too. In Great Britain, the government's guidance on marketing standards says the label on packages of produce under the specific standards must include the quality class and the country of origin in full, with no abbreviations or flags. A retailer asking for every pack from one grower's Tuesday pick shows where the thread breaks:
| Record | Held in | Where the hand-off breaks |
|---|---|---|
| Grower, block, pick date, bins received | Packhouse or grower system | Bins tipped before the intake ticket is booked |
| Traceability lot code | Packhouse system | Lot changed on the line without a new code |
| Grade results for the lot | Grader software | Grader run not tied to the lot |
| Pack label with lot, date and origin | Label and EDI tool | Label printed from the previous order |
| Pallets and cold room location | WMS and cold store | Mixed pallet booked to one lot |
| Line run and pack counts | OEE and light MES | Run times and counts, not lots |
The weak point is the lot change on a busy line, when the next grower's bins are tipped before the code is changed. The data model behind a clean trace is in lot traceability data model.
US traceability rules and the packhouse record
US rules now spell out what an initial packer of listed produce must keep, which makes a clear test for any packhouse system. Plants outside the US work under their own rules, so check which apply to your buyers.
- What the initial packer records. 21 CFR 1.1330 lists the data to keep for each traceability lot, starting with the commodity and variety received, the date received, the quantity and unit of measure (its own example is "75 bins, 200 pounds"), the farm where it was harvested, and the traceability lot code the packer assigned.
- How fast. The FDA's page on the rule says that, unless a business is exempt, an electronic sortable spreadsheet of the relevant traceability information must be given to the FDA within 24 hours of a request when needed during an outbreak, recall or other threat. The same page says Congress directed the FDA not to enforce the rule before July 20, 2028.
Every one of those records belongs in the packhouse or grower system. Bin counts at the tipper and pack counts at the line are run data that sit beside them.
Eight questions for any packhouse software vendor
A quiet-day demo proves little. With last season's intake tickets and one peak week of line reports open, put these to every product you are still considering. For where a light line layer stops, see light MES vs full MES.
| Question | What a good answer shows |
|---|---|
| How does a grower lot follow the fruit through the grader? | One lot split over two lines and three retailer formats, with grade results, pack-out and the grower statement that come out of it. |
| What happens at a lot change mid-run? | The code change on the line and the label change with it. |
| Can grower returns be built from the system alone? | One grower's statement for a week, with no spreadsheet step. |
| How do retailer order changes reach the line? | A late change to pack date and origin while the line runs. |
| Where does a residue hold show up? | At intake, in the cold store and on the line plan, from one entry. |
| How is a pallet built from two grower lots labelled and booked? | Both lots on the pallet record, with the cold room location. |
| What does the ERP send to the line layer, and what comes back? | Pack formats and quantities go down; good packs and lost minutes return. Ask who maintains it. |
| How fast can a new seasonal crew log a reason? | A new packer picks a reason on a phone, in their own language. |
What a packhouse manager can do this week and this quarter
This week, with paper and the data you already have:
- Pick the pack line that missed the most orders last week.
- For five shifts, write the time of every retailer change next to its stop sheet, from the last good pack of the old order to the first good pack of the new one.
- Mark every "no product" stop with what it waited for: bins, the grader or a grade.
- Split short stops into film, label, weigher and jam. Four reasons are enough to start.
- Put your own margin per pack into the worked example above and price one shift.
This quarter, before or early in the next season:
- Measure the chosen line automatically, by machine signal, and count the busiest hand-pack tables with the camera add-on.
- Write one change standard per pack format and compare changeover minutes before and after.
- Agree a rule with the cooler: full bins waiting past a set time on a stopped line go back to cold.
- Send measured changeover and run times to whoever plans the packing day, instead of estimates.
Fabrico in a packhouse: the packing lines and the tables
Fabrico makes cloud OEE and light MES software. In a fresh produce packhouse it covers three things:
- Machine lines: stops and counts come from the punnet filler, flow wrapper, weigher and bagger signals, and the line leader adds why it stopped, which keeps waiting for bins or grade apart from a film fault or a retailer change.
- Hand-pack tables: tables give no machine signal, so the camera add-on counts the packs at the table outfeed. Video is streamed on request, not stored in Fabrico.
- Peak season view: OEE, lost minutes and good packs by line and shift, in money, so the packhouse sees which retailer changes and which lines cost most during the weeks that matter.
Grading, lot codes and traceability records, grower payments, labels and EDI, residue results, cold store control and piece-rate pay stay in the systems that own them. Quality inspection is not part of Fabrico. Production planning and scheduling are not part of Fabrico today. More on the OEE software page, the computer vision add-on page and in the FMCG camera guide; food plants beyond produce are in food manufacturing software.
Questions packhouse managers ask
What is the difference between packhouse software and grader software?
Grader software runs the optical grader and records grade and size results. Packhouse software books those results to grower lots, along with intake, packing, stock and grower payments. They are usually separate products joined by a link.
Who assigns the lot code in a packhouse?
The packhouse or grower management system, at intake or at initial packing. Under US rules, the initial packer of listed produce assigns the traceability lot code. Line software only shows which lot was running.
Does OEE software replace the packhouse system?
No. The packhouse system holds lots, grower accounts and consignments. OEE software holds stop minutes, counts and reasons on the packing lines. A packhouse with busy pack lines needs both.
Can OEE software pay piece rates?
No. Piece rates and crew hours belong in the labour and time system and payroll; OEE software counts packs, not people.
When does a small packhouse need line software?
When the pack lines run most days in season and orders are missed without a clear reason. A grower packing a few pallets a week usually gets more from a packhouse system and labels first.
Book a demo to see a peak week of retailer changes and line stops priced in lost minutes and money.
Related articles
Latest from our blog

Real Fabrico tiles, sample data.











