About 180 of Mado's 750 branches listed Maraş ice cream as "Traditional Maraş," 90 as "Classic Ice Cream," and 40 simply as "Ice Cream." Same product, same recipe, three names. When a customer who loved the dessert in Konya can't find it on the menu in Istanbul, brand perception cracks.
A brand-guideline JSON for centralized terminology
If every branch admin edits the menu independently, terminology entropy spirals within three months. The fix is to keep the master brand guideline in a machine-readable JSON: canonical name, allowed aliases, description tone-of-voice, image aspect ratio, price format for every product.
In thMenu, the central admin uploads this JSON. When a branch admin adds a product, the system auto-suggests the canonical name and flags deviations. In the Mado pilot, term variance dropped from 62% to 4% in six months.
Visual diff: master vs. branch
Text alone is not enough. About 30% of branch photos were shot in poor light or on different plates. A visual diff tool puts each branch image next to the master; if similarity drops under 85%, the brand team gets a notification.
- Aspect-ratio mismatch (4:3 uploaded instead of 1:1)
- Background color drift (yellow instead of brand white)
- Plate/presentation gap (plastic instead of porcelain)
A practical checklist for franchise owners
Adding the brand guideline to the contract is not enough by itself. A monthly automated audit report, a 14-day correction window for offenders, then automatic locking — this three-step chain keeps the chain consistent. The franchise contract should treat "menu design discipline" as its own clause.
For new branch openings, the first menu should stay in "pending approval" mode for 30 days. Central team must clear visual and text audits before the menu goes live. Three extra hours at launch saves years of brand drift.
FAQ
Can branch admins change the term? No, canonical names must be locked by central admin. Branches can only edit translations and optional sub-descriptions.
How are regional products handled? A "regional_addons" list in the brand-guideline JSON. Branches add from there. Core menu stays untouched; regional items live in a separate category.
What's a sensible threshold for visual diff? 85% similarity is our gold standard. Below that, auto flag; under 70%, mandatory update request fires.
Found this helpful? Share it.
Related articles
Why Digital Menus Increase Restaurant Revenue by Up to 30%
Studies show restaurants using digital QR menus see measurable increases in aver…
When a Customer Downgrades, What Happens to Old Features? — The Silent Feature-Drift Problem in SaaS
Most SaaS apps run a single line of code when a customer downgrades — but old fe…
JWT alg-confusion attack — why Supabase's HS256 → RS256/JWKS migration breaks legacy verifiers
Verifiers that never decode the JWT header are wide open to `alg=none` and alg-c…