Batch and origin traceability
Our customer abroad wants proof of the origin of every batch.
- What we do
- The path of each batch, from the supplier to the shipment, which your customer looks up with a code.
- How we do it
- First we follow the path of a real batch with you: which raw material comes in and from which supplier, what is recorded in production, how the batch is formed and which shipment it leaves with. Then we decide what is recorded at each step and which system each piece of data comes from, so that nothing already in the ERP or in the production system is written twice. We build the batch register and the public verification page, decide with you what someone looking up a code sees and what stays for you alone, and test it with real batches before the codes are given to your customers.
- What you receive
- The batch register and a public verification page.
- What changes for you
- When a customer asks for the origin of a batch, no one gathers documents from several offices to answer: the customer types the code and sees it. What they see comes from the batch register, not from a summary written by hand.
- What we need from you
- Access to the ERP and, if there is one, to the production system; one person in quality who knows the path of a batch; and the details you ask your suppliers for with each delivery today.
- Who it is for
- Quality and export
- How you buy it
- A project, plus a recurring fee.
Example use cases
These are examples: they do not describe a real client.
An Italian cheese maker that sells to importers in Spain and Mexico
The situation
The importers ask, for each batch, which producers the milk comes from, when the cheese was made and when it left. The information exists, but it is scattered: the milk deliveries in the ERP, the cheesemaking records on the lab's sheets and the shipments in another office. Every time an importer asks, someone in quality gathers the papers and writes a summary by hand.
What we do
Each milk delivery is recorded with its producer, and each batch of cheese with the deliveries it contains, the date it was made and the shipment it leaves with. The batch code is printed on the label. The importer types it into the verification page and sees the path of the batch, from the milk producer to the shipment, without having to ask.
A Colombian green coffee exporter that sells to roasters in Spain and Italy
The situation
The roasters want to know which farms and which region each batch comes from, because they tell their own customers. The exporter buys from many producers and blends coffee from several of them to form each export batch. The origin of each batch is scattered across notebooks and spreadsheets, and piecing it together for a roaster takes time.
What we do
Each purchase is recorded with its producer, its farm and its region, and each export batch with the purchases that form it and the container it leaves in. The roaster types the batch code into the verification page and sees which farms it comes from, without anyone at the exporter having to piece it together.
Frequently asked questions
Does this replace the certificate of origin?
No. If your shipment needs a certificate or another proof of origin for customs, it still does: the register does not replace it. What it does is show your customer the path of each batch, from the supplier to the shipment, with a code.
What does someone looking up a batch see?
What you decide: for instance, which supplier the raw material comes from, when the batch was produced and when it left. What is yours alone, such as prices or the names of your other customers, is not shown.
Do the batches have to be recorded by hand?
Only what is not recorded in any system today. What is already in the ERP or in the production system, such as supplier deliveries and shipments, goes into the register without anyone copying it.