Hub inspection,what we find.

Why there are two inspections

Goods change in transit. Sealed pallets ride out temperature excursions, humidity swings and mechanical stress. A lot that was clean at origin can arrive with moisture creep, packaging damage or foreign-matter contamination from handling at a transit port. Origin inspection proves the lot left in spec. Hub re-inspection proves the lot arrived in spec.

Every Treviya cycle passes through both. Not as a redundancy, as two different questions.

The sample plan

Each cycle has a written sample plan set at gate 5 (logistics clearance), referenced from the cycle brief. Typical plans for bulk commodity categories sample every 20th unit, plus a random 1% layer drawn after landing. For chemistry-sensitive categories (EV olive oil, cosmetic raw materials, honey), the plan adds batch-level wet testing against the spec on the brief.

Inspectors are hub staff, not Treviya employees. The platform sets the spec; the hub team performs the inspection. This separation matters for the credibility of the record.

What the inspection checks

For most categories, the checklist is mechanical. Grade-against-spec. Moisture. Foreign matter (extraneous plant material, pests, metal fragments). Packaging integrity, seal condition, case crush, labelling legibility, destination-market compliance. For categories with documented chemistry on the brief, the lab work is repeated from a hub-drawn sample, not from the origin retain.

The inspector's report fills structured fields in the partner portal. Photographs upload against the fields. The inspector signs off. Timestamp and evidence hash write to the cycle ledger.

What we find

Most cycles pass re-inspection with zero flags. Of the ~38 cycles closed on the platform, 29 passed clean, the same result as origin inspection. The interesting data is in the other nine.

Five of the nine had minor packaging flags, case-level damage from handling, not product-level issues. Resolution is typically re-palletisation before release, with the 3PL handling line absorbing the cost. Documented as a contained exception; no effect on the allocation.

Three of the nine had destination-compliance flags, most commonly labelling non-compliance for a specific jurisdiction. Cycle #39 (Koroneiki olive oil to DACH, covered in a separate field note) is one example. Resolution is re-labelling at the hub, absorbed on the handling line.

One of the nine had a product-level flag, a moisture reading above the category threshold on a honey cycle. The affected units were quarantined. The cycle paused while the supplier's back-up allocation was released. The originally-tagged units were returned at the supplier's cost, documented on the ledger as a supplier exception.

What quarantine resembles

Quarantine is not a euphemism for "we'll sort it later." Quarantined units are physically separated at the hub, labelled with the cycle ID and the flag type and held pending resolution. The quarantine event itself writes to the ledger. Every decision after that, release, re-work, return, partial credit, writes another entry.

Cycle settlement reflects the outcome. If quarantined units are released after re-inspection, they count toward the cycle. If they are returned, the settlement statement shows the adjustment line and the exception log references the supplier record.

Why this is a second inspection, not a second opinion

Origin inspection and hub re-inspection ask different questions. Origin asks did this lot meet the specification when it left the facility? Hub re-inspection asks does this lot meet the specification for release into the channel or to the member? Both questions are necessary and neither is redundant.

A clean origin inspection followed by a hub flag does not indict the origin team. It indicts transit and the cycle record carries both inspections as evidence, not as contradiction.