Complex EU regulatory frameworks — transformed into clear, effortless software solutions. Transparent pricing. Primary and secondary repository management included. We orchestrate every handshake so your team never has to.
Sub-60-second router submissions · CIR 2018/574 Article 33 aligned
The hard part of EU tobacco compliance is not the scanning. It is the routing. We focus the platform on getting every event to the right place at the right time.
Each manufacturer has its own primary repository, each with its own protocol variant. We identify the correct destination for every event you submit and format the payload to that repository's specification automatically — no need to maintain N integrations.
The secondary repository's router accepts every event in parallel. Our queueing pipeline guarantees sub-60-second delivery in the steady state and surfaces any backlog before it becomes a regulatory issue.
Article 32 / 33 message shapes are validated against the published schema before transmission, so misformatted events are corrected at source — not silently rejected by the router after the fact.
Every failed handshake is logged with the regulator's error code, the offending payload and operator-readable context. Replay is one click. Audit retention defaults to the regulatory minimum and can be extended.
Most teams hit Track and Trace without a clear picture of the two-layer storage model the regulation imposes. Here is the bare minimum you need to know — and what the platform handles in your place.
Per Article 26 of CIR 2018/574, each manufacturer or importer contracts a primary repository to store the traceability data for its own products. Our platform negotiates the protocol differences between primary repositories so your team submits to a single, consistent API surface — no per-manufacturer connectors to write or maintain.
Per Articles 27 and 28, a single secondary repository — operated in the EU by Dentsu — mirrors all primary-repository data and routes it to consumers. Its router is the single endpoint to which every event is sent. We hold a verified connection to this router and submit on your behalf with your registered identifier in every message.
After your scan, the platform formats, signs and submits the event. The router's response is captured, attached to the audit log, and either confirms acceptance or surfaces the exact regulatory error to your operator. Steady-state latency from scan to acknowledged submission is under 60 seconds end-to-end.
Every term used above is defined in the open EU Tobacco Track & Trace glossary — primary repository, secondary repository, router, EOID, FID and the Article 33 timing windows.
We bill the routing service itself transparently. Pay-per-shipment for operators with seasonal load; annual subscription for distributors who want a flat predictable line on the budget. No router-fee passthrough, no markup on per-message charges.
Tell us about your shipment volumes and supplier portfolio — we'll come back with a routing plan that maps to your real-world flows.