---
title: "Le Bistroy"
description: "A franchise network's whole operation in one system: applications, quality assurance, contracting, partner ordering, invoicing and multi-site warehousing with lot-level tracking."
url: https://milcomp.hu/en/projects/le-bistroy/
locale: en
published: 2026-08-05
modified: 2026-08-10
author: Márton Molnár
---

Projects

# Le Bistroy

A franchise network's whole operation in one system: applications, quality assurance, contracting, partner ordering, invoicing and multi-site warehousing with lot-level tracking.

Written by Márton Molnár

Founder and developer at Milcomp.

5 August 2026

## About the project

We've been building the Le Bistroy franchise network's platform since the summer of 2025, and by 2026 the network's operation runs paperless, in one system: partner applications, quality assurance, contracting, ordering, invoicing, warehousing. What it grew into is really an ERP shaped for a network, because that's what a franchise is once you look inside: many independent outlets working under one brand, with shared rules and shared suppliers.

### The whole lifecycle, without paper

Anyone who wants to become a partner applies on the public site, and from there everything happens inside the system. Quality audits run digitally and documented, contracting happens here too, and a handed-over outlet is tracked together with its equipment. The system has 3 surfaces (public site, partner portal, admin), and head office can see at any moment which outlet stands at which step. Opening a new outlet is therefore not a pile of folders and e-mail threads spread across three inboxes, it's one process with a state.

### Ordering, warehousing and lot numbers

In the partner portal the outlets order their own stock: they pick a delivery day and time slot, pay, and see where their order stands. Behind it, the order becomes an invoice, the invoice becomes stock movements, and those become handover documents for logistics. The warehouse system handles multiple locations and tracks goods at batch level, by lot number, so you can always trace which batch left where and reached which outlet. In a network that works with food that's not a nice-to-have, it's table stakes: it decides whether a batch can be traced back when it really has to be. That kind of [process automation](https://milcomp.hu/en/services/) is what lets the network grow without head office growing with it, and it's the same shape of system our [Echo Poster ERP](https://milcomp.hu/en/projects/echo-poster/) follows.

### The decision I made first

Meanwhile the system's most important property is invisible on screen. Every business-significant step (did the invoice go out, did the stock movement run, did the partner get notified) has its own queryable state, and when a step stalls, the system speaks up. I took that this seriously because of one very simple situation: head office must never learn about a missed partner invoice from the partner's phone call.

### The silent failure is the expensive one

If you're having a similar system built, hold it to two things. The first is the rule above: the important steps get their own state, and the system speaks up on its own, not your customer. The second is authorisation: in a multi-party system the list queries have to be scoped too, closed by default, so a user with no partner attached sees nothing rather than every outlet's data. That's what decides whether a mistake stays a permissions bug or becomes a data breach.

Planning something similar?

Tell us what you need and we will tell you how much work it is, how long it takes and what it costs. Including when we think it is not worth building.

Let's talk about it