System 2+ looks at the factory Every batch belongs to a declaration The evidence is created on the line

Custom app development for production control and delivery of construction products

The declaration is drawn up in the office, but it rests on something that happens in the factory: production control. Every batch that leaves the door belongs to a declaration, and in an inspection the question is which one. That link is created on the line and at the loading dock.

Where the evidence comes from

The rules are set out in Regulation (EU) No 305/2011, in the Netherlands the Construction Products Regulation, and from 8 January 2026 in Regulation (EU) 2024/3110. Both state the same principle: the performance of your product is assessed under a system that matches your product family. The new Annex IX has six, from self-verification in system 4 to full control with sampling in system 1+. In the middle sits system 2+, where the notified body focuses on your factory production control.

In every system, even the lightest, factory production control is your responsibility. It is the monitoring that ensures what you make today still delivers what the declaration states. Article 22 requires procedures that maintain the declared performance, an assessment of changes in design, process and material, and, where necessary, sampling of products already on the market, alongside a register of complaints and recalled products.

On the other side is delivery. The product must carry the unique identification code of the product type and, where applicable, a batch or serial number. A copy of the declaration accompanies every product that is supplied; for a batch supplied to a single user, one copy may be enough. If you do not tie those two together, you cannot show afterwards which declaration belonged to which delivered batch.

How we build this

The recording has to happen where the batch is created and where it leaves the gate. Anything reconstructed in the office is an assumption.

1
First define what a batch is

Not the order and not the production day. A batch is what you must be able to trace later if something turns out to be wrong.

2
Place checkpoints in the line

Which check, at what moment, with what tolerance. These points come from your standard and your quality plan.

3
Link the batch to the declaration

Product type, declaration and version are attached to the batch at the moment it is released, not afterwards on the basis of a date.

4
Carry on through to the loading dock

At loading it becomes visible which batch goes out and which declaration belongs to it. In practice, this is where it falls apart.

What the app actually does

The registration against the batch carries the whole thing. The rest depends on your number of product lines and how you deliver.

Record the check on the line

The prescribed check with the measured value next to your tolerance, tied to the batch and captured at that moment. A series shows that a process is drifting before it falls outside the limit.

Scan the batch, declaration attached

A code on a pallet or batch opens the right record and shows which product type and which declaration are linked to it.

Out of tolerance is a status

A deviation blocks the batch and keeps it blocked until someone with the authority releases or rejects it. That decision is recorded with name and timestamp.

Photos linked to batch and delivery

A sample, damage, the loading. A timestamped photo makes a record verifiable rather than disputable.

Works on the shop floor and on site

In a production hall and on a building site, coverage drops out. Everything is stored locally and synchronised later, keeping the original timestamp.

Delivery with the right declaration

On dispatch, it is recorded which batch goes to which customer and which declaration belongs to it. The delivery note comes from your order system via integrations.

Who we build for

Where the batch originates differs per company. Four situations.

Manufacturers with their own factory

Concrete, prefab, window frames, insulation or steel, with checks built into the process. The register of declarations itself is covered in the software half; for production see joinery factory software.

Installation and on-site work

You incorporate delivered products into a building and need to be able to show what was used where. That ties in with the contractor app and with software for construction companies.

Storage, transhipment and distribution

You don't produce the declaration but pass it on. Recording what comes in on receipt saves searching with your supplier; customers can follow along via a portal.

Assemblers and installation companies

You build an assembly from third-party components. The question is which batches went into it; see also software for steel construction.

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

Control points, tolerances and product lines differ per company and change with the standard. They should be configurable rather than hard-coded in the app.

React Native or native iOS and Android Offline storage with synchronisation QR or NFC codes on batch and pallet Configurable control points per line Measured values with tolerance Batch linked to declaration and version Photo with timestamp and location Blocking and release with authority Delivery note referencing the declaration Integration with order and production systems Roles for operator, quality and dispatch Export for the notified body Audit logging Hosting in the EU

Why Appfront

A code makes the connection

We code batch and pallet so that product type, declaration and checks stay together. Without that code, linking them later is a reconstruction.

Your inspection is the evidence

Under system 2+, the notified body assesses your factory production control. We build that record where the action takes place, not as retyping afterwards.

The declaration travels with the product

Every delivered product comes with a copy of the declaration, in the language of the country you deliver to. We attach it to the batch, not to a folder named after the customer.

We don't determine your system

Which assessment system applies and which checks your standard prescribes is something to discuss with your notified body. We build the record that assessment relies on.

Security and privacy

A production record shows how your process runs and where it deviates. That affects your margins and your position in a claim. We set access per role and per location, give a notified body or external inspector only their own scope, and log every view.

For this subject, the reliability of the record is the whole point. A measurement that can be altered afterwards is exactly the item that gets disputed when there is a disagreement over a delivered batch. We record inspections, releases and integrations immutably with timestamp, location and person, even when synchronisation happens later. How we handle security ourselves is described in our information security policy; external reports go through our CVD policy.

Frequently asked questions about inspection and delivery

Regulation (EU) No 305/2011, known in the Netherlands as the verordening bouwproducten and internationally as the CPR. The document is called the declaration of performance. From 8 January 2026, Regulation (EU) 2024/3110 sits on top of it, calling it the declaration of performance and conformity.

The new regulation becomes applicable and 305/2011 is repealed, apart from a series of articles that continue to apply until 8 January 2040 for products under the old standards. The switchover happens per product family: the new obligations only apply one year after the implementing act for that family.

The monitoring that ensures what you make keeps delivering what you have declared. In every assessment system it is the manufacturer's responsibility, even when a body assesses it. What exactly you measure and how often is set out in the harmonised standard for your product, and those standard texts are not publicly available.

That depends on the system. Under system 4, you verify and certify yourself. Under 3, the notified body focuses on determining the product type; under 2+, on your factory production control, with an initial inspection and continuous surveillance. Under 1, type examination is added, and under 1+, sample testing as well before the product is placed on the market.

A copy of the declaration accompanies every product made available on the market. If you supply a batch of the same product to a single user, one copy is enough. The language is that of the member state where you deliver; in the Netherlands, the Besluit bouwwerken leefomgeving requires Dutch.

Then you take corrective action and, if necessary, withdraw or recall the product. If this poses a risk, you notify the economic operators concerned and the competent authorities, within three working days at the latest. For that, you need to be able to look up where the batch has gone.

The app records what happens on the shop floor: the inspection, the batch and the link at delivery. Managing the declarations themselves, with standard versions and publication to customers, is covered in the software half. KOMO and the assessment guideline are a different matter again: certificate management for KOMO and BRL.

That depends on the number of product lines and inspection points, whether batches will get codes, and whether it needs to integrate with your production system. Batch registration is usually usable quickly; the integration with dispatch takes more effort. We give a well-founded estimate after the discovery phase.

Can you show the right declaration for a batch?

Take a delivery note from last quarter and ask which batch was on it and which declaration applied at the time. If you can only get as far as the product type, the link doesn't exist. We build this as a standalone app and as part of a broader project of building an app, alongside the inspection app.

Edit content