Clear answers for UK food businesses.

Add the legal business and premises details, select the correct UK nation, record the local authority or district council, then add responsible users, equipment and the opening and closing routines used at that premises.

No. Haccora structures hazards, controls, monitoring, corrective action and approval, but the food business must choose procedures that fit its activities. Use the relevant official approach, such as SFBB, CookSafe, Safe Catering or a suitable HACCP system, and obtain competent advice where needed.

Authorised tenant users can use approved templates as a starting point for another premises. Each site still needs its own equipment, responsible people, local context, limits and documented approval before the copied workflow is relied on.

Managers schedule the checks for a premises and assign responsibility. Staff see due work in Today, record the result and add a correction when a check fails. Completion, user and server evidence are retained in the audit history.

The reading is retained, marked as a deviation and linked to corrective action. Configured responsible users can receive in-app, email or push notices after the production notification providers and schedules have been enabled.

A queued item is stored on the device but is not yet server-confirmed evidence. Native core flows synchronise when connectivity returns and show whether a record is queued, sending, confirmed or needs attention.

Tenant roles include owner, manager, chef, staff and time-limited inspector. Platform owner, support and auditor roles are separate from tenant evidence. Subscription limits and database row-level security are enforced independently of the screen navigation.

An authorised tenant user can create a role that removes permissions from an allowed built-in baseline. A custom role cannot grant more access than its baseline or bypass subscription entitlements, premises scope or row-level security.

Store the training type, provider, completion and expiry dates with private supporting evidence. Expiry rules can create reminders for responsible users. Health and training data must be collected lawfully, kept private and retained only as long as needed.

No. Haccora records ingredients, supplier declarations, recipe allergens and review evidence. The business must verify current source information, control cross-contact, train staff and give accurate information to customers. Do not rely on a generated matrix when a supplier, ingredient or process has changed but has not been reviewed.

The product record can link recipes, ingredients, the 14 regulated allergens, supplier evidence and label review. The food business remains responsible for deciding whether a product is prepacked for direct sale and for checking the complete label against current UK requirements before sale.

Authorised users can connect suppliers, deliveries, lots or batches, recipes and incident or recall actions to support one-step-back and one-step-forward evidence. The business must test its traceability and withdrawal or recall procedure and preserve any additional records required for its products and supply chain.

No. Haccora does not require background location tracking. Where a customer enables location evidence for a specific foreground action, it must explain the purpose to staff, select a lawful basis, limit access and retention, and assess whether the collection is necessary and proportionate.

The customer normally decides why and how its workforce data is used and must provide clear privacy information. Haccora (a trading name of iTechLounge) processes customer data under the signed terms and data-processing agreement. Customers should document their lawful basis and complete a data-protection impact assessment where the processing is likely to create high risk.

Platform support does not automatically bypass tenant row-level security or private evidence storage. Any exceptional support access must use an authorised, time-bounded and audited route with a recorded reason; it must not be granted merely by hiding or showing a screen control.

The label carries a protected QR reference and human-readable asset details suitable for the label format. Scanning resolves the current asset and premises in Haccora; confidential history is never encoded directly in the QR image.

The protected scan can record the asset, premises, user, server time, device time and the resulting action. Foreground GPS may be added only where the business has enabled it, explained the purpose and has a lawful reason to collect it.

Yes, for a signed-in user whose role and premises scope allow it. The asset screen shows previous scans, checks, readings, maintenance, calibration and corrections, then allows an authorised user to add the next time-stamped record.

An authorised user selects the premises, period and evidence categories, then creates a time-limited read-only view. Review the scope before sharing it. Haccora does not decide what an authorised officer requires or guarantee an inspection result.

Authorised users can generate a pack for the chosen period and scope. Exports should show their generation time and source context. The business remains responsible for checking completeness before relying on or sharing the pack.

Operational records are corrected by adding attributable follow-up evidence rather than silently rewriting history. Security-sensitive changes and exports are logged so authorised reviewers can understand who did what and when.

Plan entitlements set limits such as premises, users and available modules. A downgrade must not erase existing evidence; restricted features become unavailable according to the subscription state and the customer is given an export path.

Tenant billing is limited to authorised tenant owners or billing users. Haccora platform financial metrics are limited to the permitted platform roles. Support access does not grant direct access to customer food-safety evidence.

Customers should export required evidence before closure. Access, retention and deletion follow the signed terms, data-processing agreement and configured retention policy; statutory or dispute holds may require specific records to be retained for longer.

The responsive web app supports current phone, tablet and desktop browsers and can be installed as a PWA. Native iOS and Android builds cover high-frequency core flows; store availability depends on signed Apple and Google release approval.

Sensor ingestion has a defined production boundary. Email, push, payments, malware scanning and monitoring work only after their named production providers and credentials are configured. POS and supplier connectors remain roadmap items until a provider is contracted and tested.

Use the verified support channel shown in Haccora. Do not include passwords, full payment details or unnecessary personal data. Urgent food-safety incidents must still follow the business's incident procedure and any authority reporting requirement.

Not unless that service is expressly included in a signed order. The software records training, certificates, plans and approvals, but Haccora must not imply that a software subscription includes accredited courses, a food-safety hotline or business-specific consultancy. Use a competent adviser or recognised training provider where your operation needs one.

Review the relevant official source, assess the change for each affected premises, update the controlled procedure or HACCP version and record competent approval before relying on it. Haccora can preserve source and review evidence, but it does not automatically turn general guidance into a safe business-specific decision.

No. In-app, email and push reminders help responsible people see due work and exceptions after the providers are configured, but connectivity, device settings and provider delivery can fail. The business must maintain suitable supervision, escalation and contingency arrangements instead of treating a notification as proof that a control was completed.