Presets overview

A preset is a master definition you publish for a franchise — a menu category, an item, a recipe, or an expense type — that every connected store loads into its own setup. Presets are how a brand stays consistent: you decide the catalog once, and your franchisees build on top of it instead of starting from a blank slate.

But a preset is more than a starting catalog. It is the reference the rest of the console is built on: your stockhouse can only hold what the preset lists, the price a store pays comes from the preset, and every compliance alert is measured against preset values. This page explains those connections before you start filling the catalogs in.

How a preset reaches a store

There are four preset catalogs, one per area of the store app. A store connected to your franchise pulls them in from its own Settings → Franchise Connections, in one step, and each catalog lands in the matching place in the store app.

Two things are worth pointing out in that picture:

• Inventory brings an expense item with it. Every preset ingredient arrives paired with a Material expense item, so a purchase the store records flows straight into that ingredient's stock. You never add these by hand.
• Quantities are never part of a preset. The catalog defines what a store tracks, sells, and spends against — never how much is on hand, or what it sold. Stores set their own opening stock and run their own stocktakes.

When you change a preset later, connected stores are told an update is available and can re-pull it. Until they do, they keep running on the version they last pulled — so an edit on your side never silently rewrites what a store is selling today.

What a store can change, and what it cannot

A preset is a starting point, not a cage. Franchisees add their own items and adjust their own prices around your rows. What a re-pull does to a row that already exists depends on which field it is:

| | Fields | On a re-pull | |---|---|---| | Yours to keep | Unit, pack content, and order unit of a Franchisor-exclusive ingredient | Re-applied every time, always | | Theirs to opt into | Name, cost per unit, low-stock threshold | Overwritten only if the store chooses that field when loading | | Theirs alone | Inventory category, stock counts, store prices, their own items | Never touched |

Two structural rules hold on top of that: a store cannot delete a preset row from its catalog, and the ingredient lines of a preset recipe stay under your control rather than the store's.

The Franchisor-exclusive switch

Every preset ingredient carries one switch — Franchisor-exclusive — and it is the most consequential setting in the whole console. Turning it on does three separate things at once.

Leave it off (the default) and the ingredient shows Any supplier: the store restocks it however it likes, from its own suppliers or a direct expense entry, and owns its cost. Turn it on and the ingredient carries the amber Franchisor Only badge everywhere it appears.

Presets and your stockhouse

Your stockhouse is the warehouse you supply franchisees from, and it is built directly on the preset catalog: each stockhouse item is one preset ingredient. You cannot hold warehouse stock for something the preset does not list, so the catalog always comes first.

Three consequences follow, and they trip people up in order:

• An ingredient becomes orderable as soon as it has a Cost per Unit. That is the only condition. It does not need stockhouse stock to appear in a store's order form.
• That same Cost per Unit is the price the store pays. It is copied onto the order line when the order is placed, so later edits to the preset never move the price of an order already in flight. The purchase cost you record in the stockhouse is your own cost of acquiring the stock — it is what your supply-side profit is measured from, and stores never see it.
• Stock moves at two different moments. Marking an order shipped deducts it from your stockhouse. Marking it delivered adds it to the store's inventory, at the price on the order.

Presets and compliance alerts

Compliance alerts catch off-book sourcing and recipe drift. They work by comparing what a store actually does against the preset values you set — which is why the numbers you type into a preset are worth thinking about twice.

The critical detail is the threshold. A store owner can freely edit the low-stock threshold on their own copy of an ingredient — but that only changes when they get a low-stock notification. Your alerts keep measuring against the preset threshold, so raising a number on the store side cannot quiet the signal reaching you.

For recipe deviation, the amount in your preset recipe is the baseline. A store that shrinks its recipe so each sale deducts less stock than it really uses raises an alert: 15% below your amount is a warning, 35% below is critical. A recipe 50% above your amount also raises a warning.

Alerts clear themselves when the underlying problem does — stock recovers, or a recipe returns to within range. When one does not, you can Acknowledge it from the compliance screen.

The preset catalogs

Read next