Local Overrides and Locked Fields

When a menu is published from the chain template to a local restaurant, each local menu item gets a list of locked fields controlling what local admin can edit. This mechanism enables "central control with local flexibility".

The concept

Which fields can be locked?

All editable menu item fields: name, price, VAT, category, cost price, emoji, image, description, note, active status.

Default locking

At first publish: name, VAT, and category are always locked by default. Price, image, description free per unit.

UI effect for local admins

In /admin/meny: locked fields have 🔒 icon, "Locked by chain" tooltip, input disabled. Permissions also validated at database level.

Example: "Price override per restaurant"

Chain menu has "Classic burger" at 24.95 with price unlocked.

Local admin in Gothenburg wants 29.95 due to higher rent:

1. Opens /admin/meny
2. Clicks "Classic burger"
3. Changes price to 29.95
4. Saves

Effect: Local price is 29.95. At next publish (price still unlocked): 29.95 preserved. If chain locks price later: Gothenburg loses override.

Example: Central control of critical fields

Franchisor wants same name (brand), same VAT (legal), price centralized, but images/descriptions can differ. Locks name, vat_rate, price. Leaves image_url, description unlocked.

Change locks over time

Mark description as locked in template → re-publish → local descriptions overwritten.

Unlock a field

Unmark price as locked → local admins can adjust freely.

"Local change" badges

The system knows which unlocked fields differ from the template and shows "Local change" badges so you can see where units deviate.

Local-only items

Products created directly in the local menu (without a link to the chain template) are fully free. Can be created freely, never overwritten on publish, and removable anytime. Typical: seasonal dishes, weekly lunch, local specialties.

Conflict scenario

Stockholm has local price 29.95. Chain re-publishes with price locked and template 24.95. Result: Stockholm → 24.95. Local info lost.

Recommendation: Export local values before locking previously unlocked field.

Category change gotcha

If template product changes category and category is locked → all local copies change category. May break POS layout. Coordinate before publishing.

Best practice

• Name and price: locked (brand + economy consistency)
• Image: unlocked if different photo standards exist
• Description: unlocked for local personality
• Cost_price: never locked (different suppliers)

Next step: Brand Lock – same pattern for restaurant fields.