Building it right from the start costs less than fixing it later.
We define how the group should operate, build the data foundation and connect sales, operations and finance before go-live.
Almost no one starts with the information organised.
- Lists, recipes, suppliers and prices scattered across people and files.
- The POS is configured before deciding how sales should be read.
- Each site names and classifies products its own way.
- Loading everything without an architecture creates data debt from day one.
- Training arrives after the errors are already in.
- No one is formally responsible for maintaining the foundation.
What we build
Chart of accounts, cost centres, warehouses and analysis accounts consistent across units.
Canonical catalogue, free of duplicates, with a clear separation between products, recipes, cuts and materials.
Supplier items linked to the approved catalogue, with traceable formats, units and costs.
Recipes, sub-recipes, production and traceability defined before operating, not on the fly.
We define how the sale must leave the POS so it can be interpreted and linked to actual consumption.
We design the flow between operations and finance and coordinate the integration with the project's specialists.
Who maintains what, under which criteria and how often. The structure only holds if it has an owner.
Eight steps to go-live.
- 01Understand the operation
How each site buys, produces and sells, and who decides. If there is a central store or central kitchen, what is transferred between cost centres or business units, and in what format.
- 02Design accounts and cost centres
Target architecture before touching any data.
- 03Build the canonical catalogue
A single reference per real product, with no duplicates or names copied from the supplier. Each reference with a family, analysis account, warehouse and allergens under the European regulation, no traces. Separation of what is not catalogue: cuts and preparation states, intermediate preparations and materials.
- 04Configure suppliers, formats and costs
Associations, purchase units and costs with traceable origin.
- 05Digitalise the food and beverage offer
Intermediate preparations (recipes) and final preparations (what is sold), costed. For a central store or central kitchen, what is sold to each unit and in what minimum format: that definition is what enables transfers.
- 06Review how the sale arrives from the POS
Open items, modifiers, combos, channels, discounts and identifiers.
- 07Coordinate the flow to finance
Requirements and functional definition of the ERP integration.
- 08Validate, train and go live
Training by role. The client's team is responsible for digitalising its food and beverage offer, using the system every day and following the agreed steps. Veraperse teaches and validates; it does not operate on the client's behalf.
We don't load information without criteria in order to fix it later. The structure is validated before operating.
Catalogue and master data.
The catalogue is the foundation of everything else: supplier items hang off it and recipes come out of it. That's why an error there costs the most.
We start from your current list, whether it comes from other software, an Excel sheet or your own recipes, and turn it into a canonical catalogue. We separate out what is not a purchased product: cuts and preparation states, which are waste and yields; intermediate preparations, which are recipes; and materials, which are not ingredients. We merge duplicates caused by spelling, language, plural or brand, and decide the unit of each ingredient by its nature, not by how the supplier sells it: the purchase format is resolved later, in the supplier item. Each reference is delivered with a family, analysis account, warehouse and allergens under the European regulation, no traces.
Each product exists only once, with the same name across every site, and every recipe, purchase or stock count points to that reference.
A catalogue that is yours, exportable, and to which a new unit can be added without redoing anything. No merge or correction is applied without your approval, and all of them are logged.
What you get
- Documented account, cost centre, warehouse and analysis account architecture.
- Validated canonical catalogue: references with no duplicates, with family, analysis account, warehouse and allergens.
- Supplier items linked to the catalogue, with minimum purchase format, unit and price per format.
- Costed intermediate and final preparation sheets, and definition of transfers between sites where they exist.
- POS sales output resolved: items, modifiers, combos, channels and discounts linked to their components.
- Functional requirements for the finance integration, ready for the ERP specialist.
- Training plan by role and loading schedule with owners.
What we need from you
The rollout is a two-way project. For it to succeed we need:
- An internal purchasing owner who validates formats and provides information during the load.
- Access to current data: POS exports, recipe costings, supplier lists and prices.
- An operations person who knows how each site works.
- A team that takes ownership of digitalising its offer and using the system daily as part of its job.
Preguntas frecuentes
Let's start by defining the structure.
A first conversation to understand the operation and define how the foundation should be built.
Book a diagnosticIs the account already running? See the clean-up →
After go-live, control is maintained with Operational continuity →