Recalls are about speed and accuracy. The platform's batch and origin layer means every shipment event is tied to a lot, every lot is tied to a GTIN, and every GTIN has a public passport. When something needs to come off shelves, the path from internal alert to consumer-facing notice is short.
Each row maps to a real workflow in the dashboard.
Identify the affected lots, narrow to the GTINs involved, push a recall flag onto the public passport for those products.
The /01/{gtin} URL can route to a recall-safety section on the passport, addressable by the same 2D code already on the pack.
Tracking users with field-app access can update event records as recovery progresses. Workspace owner sees the full picture.
Track activities timeline preserves the recall's chain of events for audit and post-mortem.
A real recall is fast, accurate and consumer-facing. The platform connects all three. Speed comes from the fact that batch lots are already structured and tied to the GTIN; identifying the affected SKUs and lots is a query, not a forensic exercise. Accuracy comes from the per-batch best-before, manufacturing date and shipment events being explicit fields rather than free-text notes. Consumer-facing notice comes from the Digital Link URL on pack already resolving to your passport; flipping a recall-safety section to public means the existing 2D code immediately surfaces the alert.
The platform's tracking-user model lets ops, QA and field staff update recovery progress in real time, with per-user attribution on the activity timeline. Workspace owners see the consolidated picture. Public-facing recall content updates immediately on next scan, no cache lag. Historical records preserve the full chain of events for post-mortem and audit. What the platform does not do today: automate retailer notifications, push SMS alerts to consumers, or trigger recall actions across third-party systems. Those still need integration outside this platform.
Five active product pages on the free plan. No credit card.