Receivingmaterial lands, V5 already knows it’s coming.
Operators scan a pallet at the dock; V5 matches it to the open purchase order, attaches the vendor CoA, opens a quarantine record, and prints a GS1-128 license-plate label that drives every downstream scan.
What changes once Receiving with CoA capture & GS1 license-plate labels is live.
Indicative ranges from V5 pilot deployments. Your numbers will land near these once the workflow is operator-led and e-signed at the step.
What changes the day you switch this on.
Manual, paper-driven, and only audited after the fact.
Tribal knowledge in spreadsheets and shared drives.
Records reconciled and re-typed at end-of-batch.
Errors caught at month-end — too late to fix the batch.
PO matching, line-by-line
Vendor CoA attached to the lot
Auto-quarantine until release
GS1-128 license plate
What you actually get
Operator-led, e-signed, immutable. Engineered for regulated manufacturers — not retrofitted.
PO matching, line-by-line
Quantity, UoM, vendor lot, and expiry are captured at the bag — not at end-of-week reconciliation.
Vendor CoA attached to the lot
PDF is stored against the lot record so QC can review and release without chasing emails.
Auto-quarantine until release
Stock lands in a Q-bin; nothing in V5 will let an operator pick it for a WO until QC signs.
GS1-128 license plate
Every container gets a barcode that drives putaway, picking, dispense and ship — one identity, end-to-end.
Curious how this lands in your environment?
Where AI actually earns its place.
AI reads the goods-in scan the instant it lands, cross-checks it against the open PO and vendor history, and drafts the parts of the quarantine record a clerk would otherwise type by hand.
- 01
PO-match discrepancies flagged, not filed
When a scanned quantity, UoM or vendor lot doesn't line up with the open PO line, AI surfaces the mismatch to the receiver immediately with the likely cause — short-ship, unit mix-up, wrong lot entered — instead of letting it surface at reconciliation.
Catches PO mismatches at the dock, not at month-end.
- 02
CoA read and pre-checked against spec
AI reads the attached vendor CoA, pulls the tested values, and compares them against the component spec so QC opens the record already knowing whether anything is out of range.
- 03
Vendor pattern flags on repeat issues
If a vendor's lots have triggered quarantine holds or CoA discrepancies before, AI notes the history on the incoming lot so the receiver and QC see the pattern rather than treating each delivery as new.
- 04
Label and putaway suggestion
AI proposes the GS1-128 license-plate content and a putaway location based on existing bin occupancy and product rotation rules, ready for the operator to confirm with a scan.
AI never releases a quarantined lot and never overrides a CoA result. It reads, compares and flags; only QC can move stock out of the Q-bin, and that action is always a signed human decision.
One operator action — a complete, signed record.
What it leaves behind
- Vendor CoA inbox
- Lot expiry on every transaction
- Putaway directs to the right bin
The clauses this satisfies
What buyers ask before they switch on Receiving.
The rest of the platform this plugs into.
V5 isn't a bolt-on. Every module shares the same data, the same audit trail, the same operator. Pick where to look next.
Dispense
Live-scale dispense with tolerance bands and lot-genealogy capture at the gram. Wrong lot? The kiosk says no. Engineered for 21 CFR 211.101 and 111.40.
Production
MMR is locked and snapshotted into every WO. The eBMR fills itself in as operators work — temperature, hold time, in-process checks, all signed.
QC release
QC sees only what failed. In-process checks roll up; out-of-spec routes to deviation. Two-signature release where the regulator demands it.
Got questions, or want to see it on your shop floor?
Ask V5 — our code-aware assistant — or spin up a workspace. Both are free.