Restaurant Menu Modifier Matrix: Map Choices Before You Publish

1. Separate the item from its choices

Start with one dish that creates questions during service. Write down what the advertised starting price includes, then list every permitted change. Keep separate decisions in separate groups: a guest choosing a grain is answering a different question from a guest adding an extra topping.

Your POS may distinguish fixed variations from modifiers. For example, Square documents sizes as a use for variations and customizations such as adding cheese as a use for modifiers. Check your own platform's terminology before translating your worksheet into settings. Square's modifier documentation also describes selection requirements, defaults and quantity controls.

The worksheet comes first because a software setting cannot resolve an undecided offer. If the kitchen has not decided whether two proteins can be combined, mark that question unresolved rather than choosing a convenient setting.

2. Give every group an explicit rule

Use one row per option. Repeat the group rule on each row so it survives copying or sorting.

Keep three concepts distinct. A choice can be required without having a default. A choice can cost nothing without being optional. An optional group can permit one extra while prohibiting two.

For a worksheet, minimum 1 and maximum 1 means choose exactly one. Minimum 0 and maximum 1 means skip the group or choose one. Minimum 0 and maximum 2 means up to two; add a separate rule if choosing the same option twice is allowed. These are planning conventions, not a promise that every ordering platform implements them identically.

3. Work through a complete example

The following café, dish, rules and USD prices are fictional. They demonstrate the method and are not pricing recommendations. The example calculates item subtotals only; it does not model tax, service, delivery or other charges.

The café sells a Market Bowl starting at $13.50. Every bowl contains roast vegetables, one grain, one protein and one sauce. The kitchen has approved every combination of the listed choices. Optional extras are limited to one portion of either feta or avocado.

The rules below apply to the whole example:

These statements prevent two different interpretations of the same row. In particular, “chicken +$3.00” is incomplete without saying whether it replaces chickpeas or adds a second protein.

• No group is preselected; the three required choices must be confirmed
• A selected protein replaces the other protein; chicken is not an extra portion on top of chickpeas
• Extras cannot be repeated, and feta plus avocado is not an available combination
• There are no conditional exclusions between groups
• Every selected option must reach the kitchen; an included option still matters

Count the possible orders

With two grains, two proteins, two sauces and three extra states, the example allows:

2 × 2 × 2 × 3 = 24 distinct combinations

The three extra states are no extra, feta, or avocado. Counting only the two paid extras would incorrectly exclude every order without an extra.

If avocado becomes unavailable, there are two extra states left: no extra or feta. The count becomes 2 × 2 × 2 × 2 = 16. Eight combinations disappear.

This multiplication works because the groups are independent and each choice is used at most once. If one sauce is unavailable with one protein, list the allowed paths separately. Do not multiply every group and treat prohibited combinations as valid.

The count is a check on the offer's complexity, not a sales forecast or an instruction to prepare 24 bowls. It helps you notice when a short-looking menu creates many different orders.

Reconcile the arithmetic

Check both the lowest-priced valid order and a fully upgraded valid order. A neat base price does not establish that the rest of the choices have been configured correctly.

4. Translate the matrix into guest-facing wording

The internal worksheet contains more detail than a guest needs. Translate it into short instructions that preserve the actual choices:

Market Bowl — from $13.50

Roast vegetables with your choice of grain, protein and dressing.

Choose 1 grain: rice included; quinoa +$1.00.

Choose 1 protein: chickpeas included; chicken instead of chickpeas +$3.00.

Choose 1 dressing: lemon or herb, included.

Optional extra, choose up to 1: feta +$2.00 or avocado +$2.50.

The currency convention and any other required price information must match the restaurant's actual operation and location before this becomes a real menu.

On an ordering screen, the group instruction should remain visible beside the choices. W3C's form-instruction guidance calls for identifying required and optional input and explaining relevant rules. Its grouping guidance addresses making related controls understandable both visually and programmatically. Clear copy helps, but the implementation still needs its own accessibility review.

For a static QR or printed menu, staff take the order and confirm the choices. Printing “choose one” does not enforce a selection rule in a separate checkout. Likewise, a document generator does not configure your POS merely because it writes a convincing menu.

For the visual treatment of prices, use the separate menu price-display guide. The matrix's job is to settle which orders exist before their presentation is polished.

5. Run valid and invalid order tests

Use a draft, preview or authorized test environment. Do not submit paid customer orders simply to proofread a menu.

For each test, record the expected result, observed result, channel and reviewer. If the platform cannot express a rule, return to the menu owner. The restaurant may need a simpler offer, separate items, or a supported configuration. An explanatory footnote cannot repair an ordering flow that accepts an unfulfillable order.

6. Use AI to review the specification

AI can organize approved facts and point out gaps. It should not decide your kitchen's capabilities, invent prices or approve dietary claims.

Copy this prompt with your completed matrix:

Review this restaurant menu modifier matrix as a drafting assistant. Use only the supplied item facts and approved rules. First list missing or conflicting fields. Do not resolve them by assumption. Then create concise guest-facing menu copy, an internal choice summary, and valid/invalid order test cases. Preserve required versus optional status, selection limits, defaults, repetition rules, replacements, dependencies, prices and availability. Calculate example item subtotals transparently. Count combinations only when the assumptions are explicit; explain the method. Do not invent ingredients, portions, prices, allergens, dietary labels or kitchen capabilities. Do not claim to configure, synchronize, test or publish anything. Mark the output for human review.

Keep allergy requests on the restaurant's established safety process. A “no cheese” selection alone does not establish that a dish is suitable for someone with a milk allergy. Recipe information and preparation conditions need qualified review.

Turn the approved rules into a menu draft

Explore MenuCrafters' menu studio capabilities when you are ready to turn your approved item facts and choice rules into an editable menu brief. Its public feature page describes editable menus, PDFs, public QR links and menu-related worksheets. Use the matrix as source material and review the result against it before publication.

The worksheet also gives whoever maintains your POS a concrete specification. Configure and verify that system separately; this tutorial makes no claim of a MenuCrafters POS integration or automatic modifier enforcement.