Custom app development for production control and delivery of construction products
The declaration of performance is drawn up in the office, but it rests on something that happens in the factory: production control. Every product that leaves your premises belongs to a declaration, and in an inspection the question is which one. That link is made at the production line and on 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 rest on the same principle: the performance of your product is assessed according to a system that belongs to your product family. The new Annex IX recognises six of them, ranging from self-verification under system 4 to full control with sample testing under system 1+. In the middle sits system 2+, where the notified body focuses specifically on your production control in the factory.
In every system, including the lightest, production control in the factory lies with you. 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 to design, process and materials, and, where necessary, testing of samples 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 its product type and, where applicable, a batch or serial number. A copy of the declaration travels with every product offered; for a batch supplied to a single user, one copy may suffice. Whoever fails to link these two cannot later show which declaration belonged to which delivered batch.
How we build this
The recording must take place where the batch is created and where it leaves the gate. What is reconstructed in the office is an assumption.
Not the order, nor the production day. A batch is what you need to be able to find again later if something turns out to be wrong.
Which check, at what moment, with what tolerance. Those points derive from your standard and your quality plan.
Product type, declaration and version attach to the batch at the moment it is released, not afterwards based on a date.
During loading it becomes visible which batch goes along and which declaration accompanies it. In practice, this is where things tend to fall apart.
What the app does in practice
The registration at batch level carries the whole. The rest depends on the number of your product lines and on how you deliver.
Recording inspection on the line
The prescribed check with the measured value alongside your tolerance, recorded against the batch and at the moment itself. A series shows that a process is drifting before it falls outside the limit.
Scanning batch, declaration attached
A code on the pallet or batch opens the correct record and shows which product type and which declaration are attached to it.
Outside tolerance is a state
A deviation blocks the batch and it remains so until someone with authority releases or rejects it. That decision is recorded with name and time.
Photographic evidence for batch and delivery
A sample, damage, the loading. A time-stamped image makes a record verifiable rather than disputable.
Works in the hall and on the building site
In a production hall or on a construction site, coverage drops out. Everything is recorded locally and synchronised later, preserving the original time.
Delivery with the correct declaration
At delivery it is fixed which party goes to which customer and which declaration applies. The delivery note comes from your order system via integrations.
Who we build for
Where a batch originates differs from company to company. Four situations.
Manufacturers with their own factory
Concrete, precast, frames, insulation or steel, with controls built into the process. The register of declarations itself sits in the software half; for production see joinery factory software.
Assembly and on-site work
You incorporate supplied products into a structure and must be able to show what was applied where. This aligns with the contractor app and with software for building firms.
Storage, handling and distribution
You do not 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 a whole from components supplied by third parties. The question is which batches went into it; see also software for steel construction.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we turn your idea into something tangible in one day for €1,150, so you can see whether further development is worth the investment. Decide to go ahead with the full build? Then we credit the full cost.
Explore OneDayBuild →Technology and integrations
Control points, tolerances and product lines differ per company and change with the standard. They should be configurable and not hard-coded into the app.
Why Appfront
A code links it all together
We code the batch and pallet, so the product type, declaration and inspections stay together. Without that code, the link later becomes a reconstruction.
Your control is the evidence
For systems 2+, the notified body assesses your factory production control. We build that record where the action takes place, not as after-the-fact retyping.
The declaration travels with the product
Every delivered product comes with a copy of the declaration, in the language of the country where you supply. We attach it to the batch, not to a folder named after the customer.
We do not determine your system
Which assessment system applies and which checks your standard prescribes is something you discuss with your notified body. We build the record that this assessment relies on.
Security and privacy
A production record shows how your process runs and where it goes wrong. That affects your margins and your position in a claim. We set access by role and by location, give a notified body or external auditor only their own scope, and log every inspection.
For this subject, the reliability of the record is the whole point. A measurement that can be altered afterwards is exactly what becomes disputed when a delivered batch is questioned. We record inspections, releases and links in an unalterable way, with time, place and person, even when synchronisation happens later. How we handle security ourselves is set out in our information security policy; reports from outside go through our vulnerability disclosure policy.
Frequently asked questions about inspection and delivery
Regulation (EU) No 305/2011, in the Netherlands the building products regulation and internationally the CPR. The document is called the declaration of performance. From 8 January 2026, Regulation (EU) 2024/3110 supersedes it and calls it the declaration of performance and conformity.
The new regulation applies and 305/2011 is repealed, except for a set of articles that continue until 8 January 2040 for products under the old standards. The changeover 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 performing as you have declared. In every assessment system it lies with the manufacturer, even when a body rules on it. What you measure and how often is set out in the harmonised standard for your product, and those standard texts are not public.
That depends on the system. Under system 4 you verify and certify yourself. Under system 3 the notified body focuses on determining the product type, and under 2+ on your factory production control, with an initial inspection and continuous surveillance. Under system 1 type testing is added, and under 1+ sampling before the product is placed on the market.
A copy of the declaration must accompany every product placed on the market. If you deliver a batch of the same product to a single user, one copy may suffice. The language is that of the Member State where you supply; in the Netherlands, the Besluit bouwwerken leefomgeving requires Dutch.
Then you take corrective measures and, where necessary, withdraw the product from the market or recall it. If it presents a risk, you notify the relevant economic operators and the competent authorities, no later than three working days later. To do that, you must be able to trace 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, falls under the software half. KOMO and the assessment guideline are a separate matter again: certificate management for KOMO and BRL.
That depends on the number of product lines and inspection points, whether codes go on batches, and whether it connects to your production system. Recording at the batch level is usually quick to get working; the link through to dispatch takes more effort. We give a reasoned estimate after the discovery phase.
Can you show the correct declaration for a batch?
Take a delivery note from last quarter and check which batch it lists and which declaration applied at the time. If it only shows the product type, the link doesn't exist. We build this as a standalone app and as part of a wider building an app project, alongside the inspection app.