Record it at the moment itself Rework is where it breaks Scan instead of type

Custom app development for batch linking on the production line

A traceability test can only succeed if someone on the line has recorded which batch ended up in which batch. That is not a reporting question but a three-second action, a hundred times a day, performed by people wearing gloves. If that action fails, nothing can be salvaged afterwards.

Why it goes wrong on the line

The chain is only as strong as its weakest link, and it is almost always the same link. Receiving goes well, because there is a weighbridge and a system. Shipping goes well, because there is an order attached. In between is the moment a bag is cut open and its contents disappear into a mixer, and that moment is rarely recorded.

Rework is the sharpest example. A leftover batch from yesterday goes back onto the line this morning. That happens in practice, it is permitted, and it is exactly the step nobody records. The result: the mass balance doesn't close, and in a recall it is impossible to say which end products contain that leftover batch. That is a bigger problem than a mass balance that doesn't close.

The reason it doesn't happen is rarely unwillingness. It is an environment of gloves, wet hands, a splash guard and a pace that doesn't stop for an input screen. Any action that takes more than a few seconds or needs two hands gets skipped as soon as it gets busy. And that is exactly when the most material comes through.

How we build this

The design starts with the action, not the data model. What doesn't work on the line never ends up in any report.

1
Walk the line first

Where a batch is opened, where things come together, where things split apart. Those moments shape the design, not whatever structure the office system happens to have.

2
Scanning instead of typing

A code on the pallet, the bin or the label. Picking from a list of two hundred batches works at a desk, not at a mixer.

3
Rework as its own action

Leftover batches get their own record showing where they came from. As long as that is treated as an exception someone has to report later, it won't happen.

4
Working without a connection

A production hall with a lot of steel has spots with no coverage. The app records locally and syncs later, keeping the original timestamp.

What the app actually does

Batch linking carries the whole thing. What you add on top depends on how many steps your process has and how often rework takes place.

Linking by scanning twice

The incoming batch and the outgoing order, nothing more. That is the action that carries the whole trace, and it has to be quick enough that it always gets done.

Rework with its origin

A leftover batch gets its own code and keeps hold of the batches that went into it. Without that, the balance doesn't close and a recall is incomplete.

Works without coverage

In a hall full of steel, reception drops out. Everything is recorded locally and synced later, with the time of the action rather than the time of the sync.

Weights and quantities at the point of action

What went in and what came out, recorded where it happens. These are the figures the mass balance later relies on.

Blocking what must not go through

A batch that is awaiting a result must not simply enter the line. The app can enforce that block at the moment of scanning.

Photos with a finding

You record damaged packaging or an illegible label with a photo. That saves a discussion afterwards about what exactly was wrong.

Who we build for

The point where the chain breaks differs per process. Four situations.

Production and processing

Mixing, cutting and packaging. This is where batches come together and split apart, often within the same order, and that is where the registration needs to happen. See also software for the food industry.

Repacking and distribution

A batch is split into smaller units for many customers. The challenge is keeping the outgoing side complete without slowing things down.

Sites with multiple lines

A batch that switches lines or moves between sites is where the chain usually gets broken. Handover moments therefore deserve an action of their own.

Fresh products with a short lead time

With a short shelf life, traceability is mostly about speed. A three-day reconstruction is too late in a recall, even if it is correct.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Technology and integrations

Processes change more often than software does. Everything to do with steps, code types and blocking rules should be configurable rather than hard-wired into the app.

React Native or native iOS and Android Offline storage with sync Barcode and QR scanning with the camera Support for handheld scanners Batch linking from incoming to outgoing Rework with origin Weights and quantities at the point of action Blocking based on release status Photo with timestamp Integration with production and stock Configurable process steps Glove-friendly operation Audit logging Hosting in the EU

Why Appfront

Three seconds or it doesn't happen

We design the action first and the screen second. A data-entry form on a production line gets skipped as soon as things get busy.

Rework is where the chain breaks

We make it an ordinary action instead of an exception someone has to report. That is what most balances fall apart on.

A hall full of steel has no reception

We build offline-first, keeping the original timestamp. The latter determines whether the record counts as evidence.

We walk the line first

Where a batch gets split open can't be deduced from a data model. You have to see it to build it properly.

Security and privacy

Batch data reveals your recipes and your suppliers. We set access per role and per line, so an operator sees what they need and not the whole picture, and we log every access. For agency and temporary staff, we let access expire automatically.

For traceability, the record itself is the evidence. A batch link that can be altered after the fact makes the whole chain worthless; in a recall, it is the first thing a regulator looks at. We record links immutably with a timestamp and the person responsible, even when synchronisation happens later, and we turn a correction into a visible correction alongside the original value. How we handle security ourselves is set out in our information security policy; reports from outside go through our coordinated vulnerability disclosure policy.

Frequently asked questions about the batch linking app

The production system remains the source; we don't replace it. The difference is where the work happens: the link is made on the line, not behind a desk. We retrieve orders and batches through an integration and write the registration back, so there remains a single source of truth.

That is the core of the design. Large touch targets, few steps and, where needed, a handheld scanner instead of the camera. We test this in your own facility, because a demo on a clean desk tells you nothing about a wet cutting department.

Then the app keeps working. Everything is recorded locally and synchronised as soon as there is coverage again, with the original timestamp preserved. That last part is essential: a link that gets the time of synchronisation no longer matches the production order.

As a normal action with its own code. The remaining batch retains which batches went into it, so the origin travels with it when it goes back onto the line. As long as it is an exception that someone has to report afterwards, it doesn't happen and the balance doesn't close.

Yes. A batch that is waiting for a laboratory result or has been blocked can be rejected at scanning, with the reason shown. That is stronger than a list on a noticeboard, because it works at the moment someone is about to cut open the bag.

The BRCGS software handles the trace, the mass balance and the follow-up after an audit. This app supplies the data that this relies on. Without the registration on the line, there is nothing to trace, whatever software you use.

The IFS app is about inspection rounds: temperatures, hygiene and visual checks. This app is about batches and how they relate to each other. These are two different tasks, often carried out by the same people, and they can live in a single app.

That depends on the number of process steps, whether codes are already in use and whether there is a production system to connect to. The scanning action with the batch link is usually usable quickly; rework and blocks cost more. We give a well-founded estimate after the discovery phase.

Find the missing link?

Walk through your process and point out the place where a batch is opened without anyone recording anything. That one spot determines whether your traceability test succeeds. We build this as a standalone app and as part of a broader app development project.

Edit content