Bulk

Food and beverage manufacturing software. Recall in minutes.

A supplier flags a lot and the mock recall is a day of batch sheets and phone calls. Bulk traces it to every pallet before the call ends, and the CCP checks are signed where they happened, so the auditor sees what the line saw.

  • Batch & lot traceability
  • CCP capture at source
  • Recall in minutes
  • Inventory & shelf-life

This is your plant. These are the modules on it.

Where Bulk fits best.

Operator checking sacks of ingredients on a pallet at a goods-in bay

Ingredient lots you must answer for

Goods-in books the lot, cert and best-before; a supplier alert traces forward in seconds.

Operator taking a probe temperature reading from a cooking kettle

Checks the folder cannot hold

CCP temperatures and metal-detector checks signed where they happen, held against the batch.

Operator washing down a stainless filling line between products

Changeovers where memory is the control

The allergen matrix and cleandown sign-off go on the record, not one person's head.

Technical manager at a desk terminal overlooking a packing line

Spreadsheets beside a working ERP

Keep the accounts system; Bulk runs the plant floor between the lines and it.

From goods-in to genealogy, one thread.

Book the ingredient in

OCR reads the delivery note and COA; lot, cert and best-before land on the batch.

See data thread
Delivery note readGoods-in · Batch 4810 · today 06:40

Lot FL-2291 · COA attached · best-before 14 Nov · 24 sacks

Lot FL-2291 booked

Today's reality: built on paper.

Illustration of a food plant's day on paper: CCP clipboard, batch sheet, allergen matrix and a sticky note
  • A recall takes a day

    A supplier alert means a day of batch sheets and phone calls.

  • CCP logs on clipboards

    A missed temperature check surfaces at the audit, not at the line.

  • Allergen and cleandown risk

    The changeover sign-off rides on whoever knows the line today.

Cobalt 3D render of a sealed food jar with a lot tag

The blocks that hold a food plant.

  • Batch & lot traceability

    Ingredient lot to pallet, one genealogy, no batch-sheet archaeology.

    Data thread
  • CCP capture at source

    A failing check holds the pallet now, not weeks later at audit.

    Quality
  • Recall in minutes

    Trace a lot forward or a pallet back in one query.

    Data thread
  • Inventory & shelf-life

    FEFO and a shelf-life risk warn before the write-off reaches the dock.

    Inventory
  • Audits & BRCGS

    The audit becomes an export, not a fortnight of folder-hunting.

    Audits
  • Line & asset OEE

    A slow changeover shows on the wall TV while you can still act.

    OEE & analytics

Every batch. Traceable to the pallet.

MinutesMock recall time at Wrenfield Foods, down from a day
100%Batches with full lot & pallet genealogy
99.4%Right-first-time at final QC release
“A supplier alert used to be a day walking batch sheets to work out which pallets to hold. Now it is one search: every batch off that lot, every customer it reached, on screen in minutes. The BRCGS audit went from a fortnight of prep to an export.”
WF
Technical Manager at Wrenfield FoodsFood & beverage, chilled ready meals & sauces

Questions, answered.

01

Is Bulk an MES or an ERP for food and beverage?

Neither, on purpose. An MES assumes an integrator and a PLC network; an ERP wants your whole business re-platformed. Bulk is the batch-traceability, production-tracking and food-safety layer for the plant floor. It captures lot genealogy, drives the recipe and CCP checks and holds the audit record, and sits alongside whatever ERP or accounts system you already run. Most plants our size are replacing clipboards and spreadsheets, not systems.

02

How fast is a recall or mock recall?

Minutes, not a day. Every batch carries the ingredient lots booked at goods-in and every process step, so you trace a suspect lot forward to every batch, pallet and customer it reached, or a finished pallet back to its ingredients, in one query. A mock recall is timed against that, and the real one is contained before it spreads.

03

Does it capture HACCP and CCP evidence?

Yes. Critical control points, metal-detector checks, temperatures and QC results are captured in line and stay attached to the batch. A failed or missed check holds the pallet on the spot and escalates, and the food-safety record an auditor asks for assembles from the production record rather than a folder of paper.

04

Will it help with a BRCGS or SALSA audit?

Yes, that is a side effect of holding the work on one record. The genealogy, CCP logs, allergen checks and cleandown sign-offs an auditor wants are drawn from the same live data, so preparing for a BRCGS, SALSA or customer audit becomes an export instead of a fortnight of reconstruction.

05

Do we have to replace our ERP or accounts system?

No. Bulk runs the plant floor and its records; inventory and dispatch draw from the same batch data, but your ERP or accounts platform stays. This is the layer between the lines and the back office, not a rip-and-replace project, and not a big-bang cutover.

06

How long does rollout take?

One product, end to end first (goods-in to dispatch, proven on real batches in weeks), then the rest of your lines follow on the same pattern. You are an early-access customer, so you work directly with the build team and the configuration is shaped around your HACCP plan and your plant, not a template.

Let's run one batch through.