All modules Backoffice

The restaurant's ERP: ten modules, one database, one window

From staff to payroll, from supplier to plate, from order to report: one database and one session instead of separate programs.

Web (in the browser)Owner · Area manager · Accountant

What it does

Backoffice replaces the separate programs: staff and payroll, products and recipes, orders and tables, stock and purchasing, finance and invoicing, reports, tasks, customers and campaigns — all in one database, in one session. When a record changes in one module the others read it, and the question of which file is current stops being asked.

What you get

HR

staff, branches, shifts, timesheet approval, leave, advances, holidays, live attendance and payroll; DIMONA and CAO 302 for Belgium

Products

category, menu card, variants, extras, removable ingredients, kitchen station, product tags, tax class and allergens

Recipe-to-allergen chain

a menu item is attached to its ingredients, and the allergen declaration is derived from the recipe itself

Orders

dine-in, takeaway, online and QR in one queue, with reservations, tables, floor plan and floor-plan analytics beside them

Stock

supplier, purchase order, ingredient, lot, inventory count, transfer, expiry, cold-chain breach and demand forecast

Finance

expenses and recurring expenses, invoicing, banking, cash management, tax classes, currencies and rates

Reports

profit and loss, revenue, expenses and a dashboard; product, discount and order reports live in their own modules

Tasks

opening and closing lists are generated from templates, and the shift handover becomes a written record

CRM

customers, company accounts, the loyalty programme and loyalty rewards

Campaigns

time-bound discounts, second-item offers, combos and segment-based promotions

The operational screens open from inside

till, kitchen, takeaway board and courier dispatch run embedded in the manager's session

Settings

payment providers, fiscal devices, receipt template, printers, GDPR, country settings and the audit log

Multi-branch and role-based access

the accountant sees finance only, a branch manager sees their own branch only

It does not slow down as the data grows

paging and filtering run server-side

Frequently asked

Which modules does Backoffice cover?

Ten: HR (staff, shifts, timesheets, leave, payroll), Products (category, menu card, recipe, allergens, tax), Orders (dine-in, takeaway, online, QR, reservations, tables), Stock (supplier, purchasing, lots, counts, cold chain), Finance (expenses, invoicing, banking, cash), Reports, Tasks, CRM, Campaigns and Settings. The till, kitchen, takeaway and courier dispatch screens also open embedded in the manager's session.

Does it handle several brands and sites?

Yes, on one licence. Each site keeps its own menu, tax regime and staff, while the board puts them side by side so a site having a bad week shows up the same evening. Menus, price lists and staff records clone between sites in a few clicks.

Are GDPR exports supported?

Yes. Export and erasure requests are handled from the backoffice, retention windows are set per country, and every change lands in the audit log with the user and the timestamp attached, which is the first thing an auditor asks to see.

Service starts at six.
Are you ready?

A live demo, thirty minutes. No slides: we build a scenario from your own restaurant, answer what you ask and talk pricing straight.

hello@sterkchef.com