
Batches that carry a CE mark
Declare the performance you measured, so the mark is backed by the run.
A strength result hops from rig to sheet to DoP template to CE label, and every hop can mis-declare a performance a specifier is relying on. Bulk captures it once, and the Declaration of Performance leaves with the load.

Declare the performance you measured, so the mark is backed by the run.

Cement, aggregate and admixture lots tie to the batch from the mixer.

Surveillance evidence assembles as work happens, not the week before the visit.

Bulk holds the factory's compliance record between the line and your accounts.

Goods-in ties the cement, aggregate and admixture lots to the batch; nobody re-types.
See data threadCement C-2291 · aggregate A-118 · admixture AD-07 · 3 lots

The FPC plan drives the run; a missed check or bad reading blocks sign-off.
See productionSlump 75 mm, within 60–90 · cover check not yet logged

Cube strength, dimensions and density land once and flow unchanged to every document.
See quality52.4 N/mm² against declared C40/50 · density 2,380 kg/m³

The Declaration of Performance builds from the batch record and leaves with the delivery.
See documentsEN 13369 · AVCP 2+ · cube result and FPC record attached

Every hop from rig to CE label can mis-declare a performance.
A week lost in binders proving the FPC held all year.
Linking a batch to its cement lots and sites is a trawl.

Mixer to site on one thread, ready for a recall or a query.
Data threadRoutine checks sequenced and enforced; sign-off waits on every one.
ProductionStrength and density captured once; out-of-tolerance readings raised on the spot.
QualityThe DoP builds itself from the batch record, out in minutes.
DocumentsSurveillance evidence already assembled on one queryable thread, not in binders.
AuditsPlan runs against moulds and mixers; give a contractor a real date.
SchedulingNo, and that's deliberate. An ERP wants your whole business re-platformed; Bulk runs the factory floor and its records: batch traceability, Factory Production Control, test results, the Declaration of Performance and the CE/UKCA certificate. Keep your ERP or accounts system. Most makers our size are replacing spreadsheets and binders, not their finance stack.
The DoP and certificate assemble themselves from the production record: batch, declared performances, test results and the harmonised-standard reference. Because every value is captured at source under the Construction Products Regulation, the declaration matches what actually happened on the line, and re-issuing after a change is a click, not a rebuild.
Yes. Bulk holds the FPC plan for your product and standard (EN 13369, EN 771, EN 14351-1 or whichever applies) and drives it on the line: routine tests, tolerances, calibrations and non-conformities logged as work happens. It's configured to your AVCP system, whether that's a self-declared 4 or a notified-body 2+.
Every run is tied to its incoming lots (cement, aggregate, admixture, components) and forward to the destinations it shipped to. A suspect batch traces both ways in a couple of clicks, so a containment or a customer query takes minutes, not a day in the archive.
No. Bulk is the layer between the floor and the back office: production, quality and compliance records. Invoicing can draw from the same batch and delivery data, but your accounts platform stays. This is the traceability and compliance layer without the rip-and-replace.
One product line end to end first (batch to DoP), proven on real runs in weeks, then the rest of the range follows the same pattern; never a big-bang cutover. Pricing is one per-site figure with every module included, no per-module upsell, hosting and rollout in the number. Early-access makers work directly with the build team.