Platform · 04
Suppliers, customers and recalls
How companies connect on the platform, choose what each side shares, ask each other for missing evidence and recall lots that may be affected across companies.
Why connect
What a buyer chases its suppliers for, lot by lot, by e-mail and spreadsheets, is evidence: the due diligence data of a delivered lot, its certificates and lab results, its declared carbon footprint, the yield of the processing that made it. A connection between two companies is the channel for exactly that, one step up and one step down the chain, under each side's consent and field by field.
Connect
A company asks another to connect from Network ▸ Connections; the other accepts or declines. Each side then ticks what it shares about the lots it delivers to the other:
| What is shared | What the other company sees |
|---|---|
| Deliveries | it can deliver lots to you through the connection, and its recalls show which of your lots came from its lots |
| Certificates, Lab results | those recorded on each lot you deliver, with who stands behind them |
| EUDR statement | the reference and verification number of the due diligence statement covering the lot, its origin country and region |
| Plot geolocation | the coordinates of the lot's origin plots, for EUDR due diligence only |
| Carbon footprints, Processing yields | footprints exactly as declared, and the yield of the processing that made the lot |
A company's name, and in a recall the notice the recall needs, are always shared. Prices, quantities on offer and a company's other customers and suppliers never are.
Plot geolocation can identify a farmer. Sharing it requires a statement that the plots serve the customer's EUDR due diligence only and that the company has the consent or another legal basis, confirmed with a second factor. The customer sees coordinates, never the farm's name, and the supplier sees each time they are read.
Sharing records who declared what. It does not make the evidence true.
Received lots and their evidence
Lots delivered by connected suppliers appear under Received, each with an Evidence panel: what the supplier shares for that lot and what is missing. The view of suppliers and customers shows the whole network one step up and one step down.
Evidence requests
When a received lot lacks a certificate, a lab result, the EUDR statement or its plots, the buyer asks the supplier from the lot itself instead of by e-mail:
- The buyer ticks what is missing, adds a message and, if needed, a date to answer by.
- The supplier answers with what it shares for that lot, or declines with a note.
- The buyer closes the request, or reopens it as Still missing within 30 days.
Suppliers are reminded as the date nears; past it, both sides see Overdue. A request the assistant prepares waits as a draft until a person sends it. Messages are seen by the two companies only.
Recalls across companies
A recall starts from a lot. The company chooses Recall (the goods may have reached consumers) or Withdrawal (taken off the market before that), the reason and a contact. Every company on A-REX that holds lots made from the recalled lots is told, along the lineage, even beyond the company's own connections. Beyond its connections, the company sees counts, never names.
A company that receives a notice acknowledges it and can extend it to its own customers. Only the minimum travels: lot codes, the reason, the contact and the company's name. A recall says lots may be affected; the platform does not inform authorities, and each company records when it did.
The recall scope report lists every lot, holder and quantity the recall reaches.
Further reading
In the help: Work with your suppliers and customers, Trace a lot and prepare a recall, Prepare your EUDR evidence.