Connect the systems your trade already runs on.
Prepare due diligence statements for EU TRACES, bring SAP records in, take supplier messages from WhatsApp and answer your buyers' GS1 systems. Practise TRACES, SAP and WhatsApp with a simulator in a sandbox; the real connections are ready for production.
In figures
- 3Ready-made connections: TRACES, SAP and WhatsAppCounted in the platform’s code.
- 15 minSAP connections syncedEvery 15 minutes, in the platform’s code.
- 116Event types a webhook can receiveCounted in the platform’s code.
- 9Retries of a failed webhook, over 75 hoursCounted in the platform’s code.
Counted in the platform’s code or measured on the A-REX test environment, November 2026. Not customer results.
The problem
From typing it twice to connected records
Traceability breaks where one system hands over to the next.
Each connection brings records in as changes a person accepts, or lets others read what you choose. Nothing reaches your records without an approval.
Typed twice
The same lot, partner and delivery are keyed into the ERP, the traceability records and the EU form.
Lost in chats
Suppliers report deliveries by phone and message, and the records never hear of it.
A format for every reader
The authority wants a TRACES statement, a buyer's system wants EPCIS, a shopper scans a QR code.
What it does
EU TRACES filing
Prepare the due diligence statement of a shipment from your records: commodities by HS code, net mass, producers, and the plots as the GeoJSON file TRACES imports. A-REX checks it the way TRACES does; you file it yourself or send it with your company's own TRACES user.
Read the full moduleSAP S/4HANA
Products, business partners, goods receipts and deliveries, read through SAP's standard APIs every hour or on demand. Each one becomes a change a person accepts, and the lot reference can be written back to the SAP batch.
Read the full moduleProducers and partners write to your WhatsApp Business number with text, photos and delivery notes. An agent sorts each message and drafts the reply; a person sends it and records what was reported.
Read the full moduleGS1 Digital Link
Each lot gets a web address built from its GTIN and lot code, printed as a QR code. Once you publish the GTIN, a scan opens the lot passport, each line declared by your company.
Read the full moduleEPCIS 2.0 queries
Your buyers' traceability systems ask for the events of the lots you delivered to them, in GS1 EPCIS 2.0, with their own key. The interface only reads, and every read is recorded.
Read the full moduleRecords anyone can check
Each day's fingerprint of your records is published on public ledgers: Bitcoin, Hedera and your company's own. Anyone checks a record against them without A-REX. In the alpha, Hedera runs on its test network.
Read the full moduleAny ERP, both ways
Inbound endpoints take your ERP's messages in its own format, and signed webhooks send events back.
Read the full moduleHow it works
From the simulator to your own accounts.
Practise with a simulator
In a sandbox company, TRACES, SAP and WhatsApp each have a simulator, named as such on every screen. Rehearse a timeout, a refusal or wrong credentials before they happen.
Connect your own accounts
Your TRACES web service user, your SAP system, your WhatsApp Business number. Credentials are stored encrypted, and saving them asks for a second factor.
Accept what comes in
Changes from SAP and messages from WhatsApp wait for a person; lots and deliveries then wait for the usual approval.
Go live
A production company connects in Live only, with its own accounts. Simulated results never count as filed or as evidence.
What each connection does
TRACES, SAP and WhatsApp each have a simulator in sandbox companies, and run Live with your company's own account in production.
| Connection | In practice |
|---|---|
| EU TRACES | Sends, amends and withdraws due diligence statements and asks TRACES for the reference and verification numbers. Test (TRACES acceptance) in a sandbox; Live only in production. |
| SAP S/4HANA | Cloud or on premise. Reads only what changed since the last sync, every hour by default, from every 15 minutes to once a day, and lists every request it made. |
| Your WhatsApp Business number, through Meta. After 24 hours only templates Meta approved are sent, and a contact who writes STOP is opted out at once. | |
| GS1 Digital Link | A scan opens the lot passport: product, lot code, production date and origin country, never people, plots, quantities or prices. Stop publishing, and scans answer not found. |
| EPCIS 2.0 | The standard query interface, filtered the way GS1 defines. A connected company reads only the lots you delivered to it, while you share traceability events with it. |
| Public ledgers | Each day's fingerprint, shortly after midnight UTC, on Bitcoin (through OpenTimestamps), Hedera and your own ledger. A-REX pays for Hedera, so you need no account there. |
| Webhooks and inbound | Signed events out to your systems, and endpoints that take your ERP's messages in its own format. |
Who uses it
Administrators connect the systems; the people who do the work decide what comes in.
Administrator
Connects TRACES, SAP and WhatsApp, and publishes GTINs.
Owner
Confirms credentials and publishing with a second factor.
Operator
Prepares TRACES statements, accepts changes from SAP, sends replies.
Partner system
Reads the traceability events you share with it, with its own key.
One business step, one EPCIS event.
Resources
The guides, the open standard and the details behind every screen.
Rehearse your integrations in a sandbox.
Tell us which systems and authorities you work with. We will connect the simulators to a sandbox with your products.
Explore more