
Superintelligence for Dairy Producers: Batch, Expiry and Temperature
How dairy producers can record batch, expiry and temperature at delivery, with traceable orders and batch release checked by the technical manager.
Want to apply this in your company?
Book a call with Juan →When a dairy order is traced, every product should leave the warehouse with its batch and expiry date identified, every delivery should keep the temperature measured at dispatch and at arrival, and every complaint should be linked to that data. An AI agent can collect, organize and cross-check this information against the order and the customer, but batch release and any technical answer about a suspected problem must go through the technical manager. Without that record, the company answers the customer from memory instead of from facts.
Key takeaways
- Every order should carry the batch, manufacturing and expiry dates, and the temperature recorded at dispatch and at delivery.
- The AI agent collects and organizes the data, but it does not decide on batch release, replacement, refunds or product safety on its own.
- A complaint is handled only with a complete trail: order, batch, photos, timestamps and temperature readings.
- The technical manager reviews cases before any batch release or technical answer goes to the customer, and that review is recorded.
- Start with one product and one delivery route, record for an agreed period, and only then expand the flow.
Why batch, expiry and temperature must be tied to the order
Dairy products are perishable, and most problems show up after delivery. A complaint about a swollen package or an altered taste can arrive hours or days later, and in that gap the team often depends on the memory of whoever packed the order or drove the vehicle. When the batch is not linked to the order and the temperature was not measured along the whole route, the investigation becomes guesswork.
In this context, traceability means being able to rebuild the path in both directions: from the customer back to the batch, and from the batch forward to every customer who received products from it. In software terms, this is an event trail, where each step creates a record with a time and a responsible person. The general logic of logs, metrics and traces from observability practice applies well to physical processes when they are recorded with care.
The sanitary parameters for each product, such as temperature ranges, deadlines and labeling requirements, come from the applicable legislation and the competent authorities, and they are defined by the company's technical manager. This article does not set those values. What it covers is how to store the information so that whoever makes the decision has what they need.
Which data to record at each delivery
The list below is a starting point for mapping. Each company adjusts the fields to its product and its operation, and should separate what is mandatory from what is optional.
- Order number, customer identification and the channel through which the order came in.
- Product, production batch, manufacturing date and expiry date.
- Temperature measured when leaving the warehouse, with the instrument used and the time of measurement.
- Temperature during transport and on arrival, at the points where the route calls for a reading.
- Condition noted at receiving, with a photo whenever the packaging is damaged or a visible change is present.
- Who made each record and when, without generic fields such as "team".
As important as the list is deciding where this data lives. In practice, the record should sit in a reference system, which can be an ERP, a controlled spreadsheet or a quality management system. The AI agent should read and write only the fields it has been permitted to use, and every change should leave a trace. Photos of packaging and of people, when they appear, should be kept only as long as needed and with restricted access. This fits the data minimization principles of Brazil's data protection law (LGPD), whose guidance is published by the national data protection authority (ANPD).
How the AI agent takes part without deciding alone
The most useful flow starts on WhatsApp, the channel where customers already ask about orders and expiry dates. The agent identifies the order, checks the record, asks for a photo when needed, and logs the report with a timestamp. From there, it follows clear rules about what it can answer and what it must hand over. The same logic applies to AI customer support, where you need to separate what to automate from what stays with people.
A simple decision guide makes that separation explicit:
- Routine question about expiry or batch for an order already on record: the agent answers with the system data and logs the query.
- Temperature recorded outside what the protocol allows: the agent opens an incident and alerts the technical manager.
- Report of illness, foreign object or suspected contamination: immediate transfer to a person, with the full case and without asking the customer to repeat the story.
- Request for replacement or refund: the agent collects the details and passes them to the team that approves these, without promising amounts or timelines.
The agent must not state that a product is safe, nor explain technical causes that only the responsible person can assess. That boundary needs to be written into the agent's instructions and tested before the operation goes live.
The person qualified to speak about food safety is the technical manager, not the agent.
Illustrative scenario: a yogurt that arrived with a swollen package
Illustrative scenario: a customer writes on WhatsApp saying a yogurt arrived with a swollen package and asks for an explanation. The agent asks for the order number, the batch printed on the package and a photo. With those details, it checks the record and finds the batch, the dispatch date with its measured temperature, and the route. It notices, however, that there is no reading for the last leg of the delivery, which is already a relevant finding for the process.
The agent logs the incident with all the data and tells the customer that the case has been passed to the technical manager and that the company will reply after the review, without saying whether the product is safe or not. The technical manager checks the batch, looks at other deliveries from the same batch, decides whether the remaining stock should be blocked, and records the decision with a name and a time. The customer receives the answer from the person, not from the agent.
The bigger gain in this case is not the reply to the customer. It is that the company found a gap in its process: the last leg of the route had no temperature reading. That is the information that changes the operation.
Who checks before release
Batch release is a control point, and it must have a named owner. The technical manager reviews the records, the lab results when they exist, and any open incidents before releasing the batch for sale or giving a final answer to the customer. The company decides whether the batch stays blocked in the system until that review is done, and the block must be visible to both sales and customer service.
The AI agent can prepare the case summary for that review: a list of affected orders, the available readings, gaps in the records and attached photos. This reduces the workload of the person reviewing, but it does not replace the review. The NIST AI Risk Management Framework from the United States supports the idea of human oversight proportional to risk, and in food the risk is high enough that the final decision stays with a qualified person.
How to apply the method gradually
At Juan Carlo, the work follows four steps: map, limit, pilot and transfer. Applied to a dairy operation, mapping starts with the current process, including how a batch is identified today, where temperature is measured, how long it takes to answer a complaint, and how many incidents lack a complete record. This baseline is what lets you tell later whether the pilot improved anything.
Next comes the limit: which data the agent can read, which fields it can write, and which actions stay out of its reach, such as releasing a batch or issuing a refund. The pilot should cover one product and one route, with a log of every interaction and an agreed metric defined before it starts, for example the time between the complaint and its correct handoff. At the end, the company decides whether to expand, adjust or stop the flow. When the operation needs continuous management, that part can be handled with Be Human, which covers monitoring and maintenance of agents.
To see how this way of working fits into a company's routine, read about how Juan Carlo works with companies. If your operation also involves technical recipe sheets and raw material purchasing, the link between that data and batch records is covered in superintelligence for restaurants, with recipe cards and purchasing data.
Frequently asked questions
Can the AI agent release a batch for sale? It should not. Release is a decision for the technical manager, who reviews the records, incidents and available analyses before authorizing it. The agent can show the batch status, prepare the case summary and let the customer know the decision is under review.
Which data is essential in a delivery record? At minimum, the order number, the product, the batch, the manufacturing and expiry dates, and the temperature measured at dispatch. Temperature readings for transport and arrival should be recorded when the route includes those points. The exact parameters come from the applicable legislation and from the technical manager's definitions.
How does recording customer data and photos relate to the LGPD? Customer identification data and photos that show people or personal information should be handled with a defined purpose, restricted access and a limited retention period. The company needs to know who accesses this data and why. For correct interpretation of the law, consult a legal professional and the guidance published by the ANPD.
Where should a dairy company start without replacing its whole system? Start by mapping how batches and temperatures are recorded today, even if it is in a spreadsheet or a form. Choose one product and one route for a pilot, define who reviews cases and what the agent is allowed to do, and log everything. Then decide whether the flow should be expanded, adjusted or ended. It is also useful to review how public and private complaints are answered with history and review, so the response standard stays the same across every channel.