Witify Logo Witify Logo

The store orders. Cooked, logged, invoiced.

CuistotNet, the software that runs Cuistot du Marchand, rebuilt by Witify with its history carried over. Stores order, cooks produce, and each week is invoiced in one run.

Client
Sector
In-store prepared meals
Technologies
Laravel, Vue, TypeScript, MySQL

01 The numbers

Five figures on a rebuilt system

First, the size of what was rebuilt. Every figure here is counted in CuistotNet or in its code.

  • 12

    operating reports Eight export to Excel.

  • 4

    roles on a single application Cook, supervisor, manager, administrator.

  • 11

    types of store department Prepared meals, deli, bakery, fish counter, among others.

  • 20

    data tables carried over from the old system Recipes, orders, invoices, evaluations: the history came along.

  • 211

    automated tests Across the whole system.

Figures read in CuistotNet and in its code on November 13, 2026.

02 Before

Software in daily use, to rebuild without losing a thing.

CuistotNet already held the recipes, the orders, the invoices and years of history. Everything had to come across, so that on a Monday morning each kitchen would find its recipes at the same address.
  1. Analyze The old system’s code and database, read before any proposal
  2. Rebuild Screen by screen, approved by the Cuistot du Marchand team
  3. Carry over Recipes, orders, invoices: 20 data tables moved into the new system
  4. Switch One weekend; on Monday morning, the same address

03 One order

From order to invoice in four screens

The same recipe, followed from the department that orders it to the week’s invoice. Three are ordered, two are made, two are billed.

01 Order

A department orders its recipes for Tuesday

The order is entered for a store, a department and a day: a sort group, a recipe, a quantity with the plus and minus buttons. The department total and the store total follow on saving.
Fig. 01 A department’s order for one day

02 Cook

The cook works down the sheet, recipe by recipe

The day’s recipes, grouped by sort group, the ones still to do first, a tick on those done. For the selected recipe: the ingredients by sequence, the method one tap away, and two large figures, ordered and made.
Fig. 02 Worksheet of a day in progress

03 Log

Two curries out of three: the app asks why

Made less than ordered: a reason is required, and it follows the line into the reports and onto the invoice record. A recipe that can wait is postponed to the next working day.
Fig. 03 Logging what was made of one recipe

04 Invoice

Each week is invoiced by store and by department

The week runs from Friday to Thursday. Only what was made is billed: eight curries this week, Tuesday’s two included, not three. At the foot, what the kitchen took from the store’s other departments. Generating again updates the invoice; it never creates a second one.
Fig. 04 A department’s weekly invoice

04 The cost

One recipe, one cost per banner

Each store buys at its banner’s prices, so one recipe does not cost the same everywhere. CuistotNet costs it per banner, and a price change recalculates only the recipes that use that ingredient.
Fig. 05 A recipe costed for one banner: ingredients, labour, cost and transfers

05 The network

From the store to head office, the same numbers

A cook sees one kitchen, a supervisor a few, head office all of them. Every screen reads the same order lines, so nothing is re-keyed from one screen to the next.

Head office

Every store on one page

Who is in the kitchen today, what is ordered, what is made, and the average to compare against.

Store

The store’s week, day by day

What was made shows in red when it falls short of the order.

Comparison

A store falling behind shows at once

Over the chosen period, each store is set against the network average.

06 Our choices

Three choices for changing software without losing the thread

Three decisions mattered more than the rest. For each: the risk to avoid, what we chose, and what Cuistot du Marchand gains.

  1. One application for every role

    The risk
    One interface for the office and another for the kitchens: two tools to learn, to explain and to keep evolving.
    Our choice
    Together with the Cuistot du Marchand team, a single application was chosen. Its menu adapts to the role: cook, supervisor, manager or administrator.
    The gain
    The supervisor opens the same worksheet as the cook, and head office reads the orders the store has just saved.

  2. Generating an invoice again never makes a duplicate

    The risk
    A second click, a late correction, two people invoicing the same week: duplicate invoices to untangle by hand.
    Our choice
    One invoice per store, per department and per week. Generating it again updates it, and only one generation can run at a time for a given week.
    The gain
    Production corrected after the fact is invoiced again by rerunning the generation, with nothing to re-key.

  3. Averages are worked out ahead of time

    The risk
    A report that recounts years of orders each time it opens keeps its reader waiting, and weighs on the system just when the stores are ordering.
    Our choice
    Each store’s average is worked out ahead of time, twice a week. The other totals are worked out in one pass instead of being recounted line by line.
    The gain
    The short-term report fits on one page: every store, its day, its week and its averages.

07 Under the hood

What CuistotNet is made of

The components, and what has gone into service since October 2024. Development began in September 2023.
Application
Laravel, PHP, MySQL database
Interface
Vue, TypeScript, one application, one menu per role
Reports
totals computed by the database, per-store averages recomputed twice a week
Documents
PDF and Excel, invoices, evaluations, eight exportable reports
Quality
211 automated tests, rerun on every code change, error tracking
Operations
daily backups, files and database

Key milestones

  1. October 2024 Go-live Orders, worksheet, recipes, invoicing and reports, on a Monday morning.
  2. November 2024 First adjustments A sortable short-term report and a redesigned menu.
  3. December 2024 Averages and categories Production averages on the store’s home page; several categories per recipe.
  4. February 2025 Production variations Each store compared with the network average, as a list and as a chart.
  5. May 2025 Weekends Weekend production, allowed store by store.
  6. October 2026 Food safety A section of guidelines, visible to every role.

Thanks to the new solution developed by Witify, reports are now generated five times faster . This solid foundation gives us all the freedom to adapt and evolve the software according to our needs, today and for the years to come.

Benoît Pilon IT Director, Cuistot du Marchand

Your in-house software runs the business, but no longer keeps up?

Thirty minutes to see what stays, what gets rebuilt, and in what order.

Or write to us
Next case study Luminaire Authentik Read the case study

Names and figures shown in the interfaces are examples.