Compliance
HACCP, food-waste law and allergens without a legal team.
Per-equipment temperature logs. 2-phase recall. Exportable reports. Compliance handles itself; you sign.
What do you hand an inspector?
A report, and the trail behind it. Temperature is logged per piece of equipment, a recall quarantines first and notifies second, and every measure is written as it happens into a hash-chained audit trail. A record changed afterwards is detectable rather than deniable — that is the integrity claim, not a signature.
Every measure — temperature, recall, check-in — is recorded as it happens. The export is a PDF or a structured file backed by a hash-chained audit trail, so a changed record is detectable rather than deniable.
Compliance coverage
Compliance is a framework here, not a country.
Regulatory obligations are delivered as jurisdiction packs on top of one shared audit, traceability and evidence layer. Spain is live; further markets are built on the same machinery.
- Veri*factu / SIIGap-free sequential invoice numbering with AEAT-aligned reporting. The two regimes are mutually exclusive and resolved per tenant.
- TicketBAI + LROEXAdES-signed invoice chain for the Basque provincial tax authorities.
- B2B e-invoicing (RD 238/2026)Structured business-to-business issuance with delivery and payment status reporting.
- Per-rate VAT (RD 1619/2012)4% / 10% / 21% / 0% brackets frozen at delivery and consolidated per bracket at month-end.
- Ley 1/2025Food-waste prevention records and hierarchy-of-use reporting, plus worker time-tracking evidence.
- ATP RD 237/2000Transport temperature evidence across refrigerated delivery legs, exportable for inspection.
What does this cost today?
- Auditor every 6 monthsArrives with a form. Asks for temperatures, recalls, traceability, Ley 1/2025. Takes you 2 days preparing.
- Freezer at -15°C at 3amNobody knows. Par-baked bread partially thaws. Batch contaminated in 6 hours. You find out when the customer walks in.
- Impossible recallSupplier alerts about contaminated batch. You need to know which customers received it in <24h. Without a system: impossible.
Before / After
And what changes on an ordinary Monday?
Reactive compliance vs. invisible compliance.
| Today | With BakeWise |
|---|---|
| Temperatures logged by hand. | IoT sensors or mobile app log automatically. |
| Recall = 3 days of detectives. | Recall = 2 clicks, notification to customers in background. |
| Audit = 2 days preparing PDFs. | Audit = PDF export in 10 seconds. |
| 'Which shops did that lot reach?' — nobody knows. | The recall names the destinations, and says which of them it is sure about. |
Which numbers can you check?
6
HACCP zones monitored
2s
Recall sync quarantine
10s
Auditor-ready export
7 years
Max retention
What is underneath?
- Continuous HACCPPer-zone, per-equipment logs, configurable thresholds. Real-time out-of-range alerts.
- 2-phase recallSync quarantine (<2s) + async customer notification. Rate-limited 3/24h.
- Complete traceabilityForward (batch → customers) + backward (batch → ingredients → supplier).
- Audit-ready exportsPDF or structured data with 6, 12 or 24 months of records, backed by a hash-chained audit trail. It serves as evidence before an inspection because the chain, not the file, is what proves nothing was edited after the fact.
- Cold rooms that log themselvesConnected chambers and freezers write their own readings into the food-safety record over MQTT, OPC-UA or Modbus. A breach opens an alert and estimates the shelf life lost, so the decision on the affected stock is taken with a number rather than a shrug.
- Which shops received the lotThe recall names its destinations: the transfers and shipments that carried that lot, each with its certainty — exact when the line or the stock names the lot, probable when the same product travelled inside the window and cannot be ruled out. If a source does not answer, the scope is marked incomplete rather than showing a smaller network. Calling each destination is yours to do: nobody is reported as notified who has not been. Chain+.
What else gets asked before deciding?
What HACCP zones does it monitor?
Freezing (-25 to -18°C), refrigeration (2 to 4°C), production, finishing zone, dry storage, delivery zone. Each zone has configurable thresholds. Automatic out-of-range alerts.
Why rate-limited to 3 recalls/24h?
Abuse prevention and alert-fatigue. A B2B customer receiving 3 recalls in 24h probably stops trusting. If you need more (major incident), you can request a temporary bump.
Does it manage cross-contamination for allergens?
Yes. R1 and R2 are active and emit alerts: R1 when a recipe's BOM contradicts its allergen declaration; R2 when two batches with incompatible allergens share equipment without a recorded cleaning cycle. Storage-proximity detection (R3) is not available yet.
Does it generate labels and a technical data sheet?
Yes. Nutritional label compliant with EU-FIC Regulation 1169/2011, calculated from the ingredients (Ciqual/USDA master catalogue, with baking loss included). Plus a downloadable B2B technical data sheet, included on both levels — the document supermarkets and HORECA ask for.
How long does it store data?
365 days included on all plans. Up to 7 years under custom SLA (Group). CSV/JSON export available any time — no lock-in.
Are Ley 1/2025 and HACCP the same?
No. HACCP is food safety (temperature, traceability, allergens). Ley 1/2025 is food-loss prevention (waste, donation, management). BakeWise covers both — separate but integrated modules.
In a recall, do you know which shops the lot reached?
Yes, from Chain. Alongside the affected lots, batches and sales, both the simulation and the execution list the destinations that received the goods: your own shops and the companies in the network, each with its certainty — exact if the line or the stock names the lot, probable if the same product travelled inside the window. If a source does not answer, the scope comes back marked incomplete. Calling each destination is yours to do: the platform reports nobody as notified who has not been.