Skip to content
Skip to content

Horticulture & ViticultureBay of Plenty

Bin-to-pallet traceability for a post-harvest operator

A packhouse that could tell you what shipped but not which block it came from. We built traceability that survives the pace of the packline and holds up in a recall.

added per bin at scan
< 2 s
recall granularity
Block-level
peak season run without downtime
6 weeks

Comparable to: Radfords or Hectre, built to one packhouse's actual line

01The work

What actually happened

The client is not named here at their request. If a reference would help you decide, ask on the call — several are happy to take one.

The operator ran a six-week season at a volume that made manual recording impossible, and a traceability obligation that made not recording unacceptable. The existing process captured grower and date but lost the link to block and pick once fruit merged on the line — which meant that in a recall, the recall would have been everything.

The build was constrained by the line itself. Scanning had to add no time at all, in a cold, wet environment, with gloves. We used fixed scan points and inferred the rest from timing and line position rather than asking anyone to do anything extra, and validated the model against a season of historic data before it ran live.

It went in mid-season, which was not the plan but was the only window available. The rollback path was tested more carefully than the feature, and it was not needed.

02Shipped

What was built

  • 01

    Fixed-point scanning that adds no manual steps on the line

  • 02

    Bin, block and pick-date lineage retained through to pallet

  • 03

    Grower portal showing consignments, grades and payments

  • 04

    Recall query that resolves to affected pallets in seconds

Built with

  • Next.js
  • PostgreSQL
  • Node.js
  • Zebra scanners
  • AWS Sydney
Sector
Horticulture & Viticulture
Region
Bay of Plenty

Next stepFree · no obligation

If any of that sounded familiar, it is worth a conversation

Free 45-minute call with the person who would run the build. No sales script, no obligation.

  1. 01

    You tell us what hurts

    Forty-five minutes, no preparation needed. Bring the process that is costing you time.

  2. 02

    We tell you what we think

    Including when the answer is a setting in software you already own, or nothing at all.

  3. 03

    You decide, in your own time

    No follow-up sequence, no pressure. If it is worth doing, we will scope it properly.

Free 45-min
scoping call

Book a call
Bin-to-pallet traceability for a post-harvest operator | LoomInfo