Building a Menu in a POS: Categories, Modifiers and Pricing Rules

Counter touchscreen register with a blurred grid of colored tiles beside a spike of paper order tickets.

A POS menu is a database before it is a list of dishes, and the structure chosen on day one decides how fast servers ring orders, where tickets print and what the sales reports can say later. Square and Toast both organize a menu into layers: containers that group items, the items themselves, and modifier groups that attach to items. The layers are named differently in each product, and the settings inside them behave differently enough that a build copied from one system to another usually needs rework. What follows draws on the vendors’ own help pages as read at the time of writing; product screens and limits change, so the pages linked below are the reference.

Set Up Item Modifiers with Square, Square on YouTube

Containers: menus, groups and categories

Toast: menu, group, subgroup, item

Toast’s Menu Manager displays a full menu view as a hierarchy of menus, menu groups, subgroups and items. A menu is the top level (Lunch or Dinner, for example), a group organizes items within it, a subgroup divides a group further, and an item can sit in a menu, group or subgroup. Elements can be reordered with drag handles, and modifiers are listed in a separate view that shows which item or group each applies to. The hierarchy matters beyond tidiness, because settings attached to a group apply to every item beneath it.

Square: categories and printer routing

Square for Restaurants uses categories in a way that is easy to underrate. Its help article on assigning categories is about kitchen printers: categories route items to specific printer profiles, a new category automatically routes to every printer profile that has order tickets enabled, and a profile’s “Include future categories” setting decides whether that happens automatically or by hand. A category called Cold Prep, assigned to the garde-manger printer, keeps a salad off the grill station’s tickets. A catch-all category called Food sends everything everywhere.

In the item library, Square’s item creation article says retail items use categories while food and beverage items use menus, so the category choice on a restaurant item and the menu choice are two separate decisions.

Building for the reports

Categories and groups also become the rows of the sales reports, which makes naming a reporting decision. A split between Appetizers, Entrees, Sides, Desserts, Non-Alcoholic Beverages and Beer, Wine and Liquor produces a mix report that reads like a menu. A split built only around printers can make the report unreadable. The post on reading a restaurant sales report covers what those rows are used for once they exist.

Items: one name for the guest, one for the kitchen

The fields on an item

Square’s item form takes a name, price and description, an item type (prepared food and beverage, physical good, event, digital or other, which determines which fields appear), a category, taxes, and the locations and sales channels where the item is sold. In the POS app version, the form asks for a customer-facing name and a separate kitchen name.

That second name earns its place. A guest-facing line such as “Grandmother’s Sunday Gravy Rigatoni” is useful on a printed menu and a nuisance on a ticket pinned above a pass at 7 p.m. A kitchen name like “RIGATONI” with modifiers beneath it costs a few seconds of setup per item. Matching the printed menu is a separate task, covered in the post on printing a menu that matches the online one.

Channels and tax

Items and modifier sets each carry their own channel visibility in Square, and a warning appears when a modifier set is not assigned to a channel the item uses. An online-ordering item with a modifier set missing from the online channel produces orders that look complete on the website and arrive incomplete in the kitchen. Tax settings sit on the item as well, so a taxable entree and an exempt grocery-style item need their own tax assignments from the start.

Kitchen pass with clipped order tickets above plated food on a stainless steel shelf.

Modifier groups: required, optional and limited

What each system calls them

Square calls a collection of options a modifier set. Toast calls it a modifier group, and defines it as “a named collection of modifier options”. Clover’s developer documentation describes the same structure: a modifier group such as “Salad Add-in” holds modifiers such as Tofu and Avocado, and the Clover documentation lets a group define minRequired and maxAllowed limits.

Required versus optional

A required group forces a choice before the order can go to the kitchen: the temperature on a steak, the side with a sandwich, the dressing on a salad. In Toast, required means at least one selection. In Square, the Selection Rules setting controls it, and a minimum above one is possible for a required set. A maximum is available in Square only when “Allow more than one modifier to be selected” is turned on, and Toast works the same way, with a separate help page citing a ceiling of 24 modifiers.

An optional group does not block the order. Toast’s “Include a POS prompt” setting makes an optional group appear on the screen automatically, and staff can skip it.

Defaults

Square lets each modifier in a set be pre-selected, with an item-level override. Pre-selection suits the choice most guests make, such as a regular cup size, and it saves taps. It also produces a quiet error: a default that nobody notices gets charged and cooked.

Where to attach

In Toast, a modifier group can attach to a menu group, a subgroup or a single item, and groups attached at a higher level apply to every item beneath. Attaching “Burger Temperature” at the Burgers group covers every burger added later. In Square, a set can be applied to several items at once from the Modifiers page, but a limitation worth knowing is that once an item-level customization is made, later changes to the modifier set do not reach that item until the customization is reset. A price change to a set can leave one item behind.

Pricing a modifier

Three choices in Toast

Toast prices options at the group level, with “No charge,” “All modifiers share the same price,” or “Each modifier has a unique price”. Its pricing strategies article offers dressing on a salad as the typical no-charge case. A shared price suits add-ons that cost about the same, such as extra cheese, bacon or an extra egg. Unique pricing suits a group where avocado and a fried egg differ in cost.

Negative prices in Square

Square allows negative modifier prices. Its modifier article gives the example of entering a negative price such as -$1.00, and the discount applies to the item total at checkout. That fits a “no cheese” credit or a swap to a cheaper side, though a credit on every removal can quietly bleed margin, so the amount should come from the item’s ingredient cost. The method for working that cost out is in the post on writing a recipe costing card.

Limits worth knowing before the build

Square’s article lists several. Nesting is limited to three levels with a maximum of five child sets per modifier, circular nesting is not allowed, and modifiers are not compatible with barcode scanners. Toast notes that open pricing is not supported for modifiers and that time-specific pricing cannot be applied at the modifier level. A happy-hour discount on an add-on therefore has to be built another way.

Blank printed menu draft beside a pen and tablet on a wooden table.

Pricing rules beyond the base price

Toast’s pricing strategies

Toast’s platform guide, in its pricing section lists the strategies in one table. A base price is the default. A time-specific price changes an item’s cost during set hours, with the guide’s example of $10 between noon and 2 p.m. and $12 the rest of the day. A menu-specific price varies by menu, a location-specific price applies only to enterprise customers, and a size price depends on the size chosen. An open price lets staff type a price at the time of ordering. Sequence pricing prices modifiers by the order added, substitution pricing charges only the difference when one default modifier replaces another, and price levels let a collection of groups or items share one price.

Size pricing in practice

Toast’s size price documentation gives the cleanest example: a small pizza at $10 and a large at $14, with a toppings group set to follow the item’s size so toppings cost $2 on the small and $3 on the large. The same page warns that sizes must match exactly in both number and text when a modifier follows the item’s size, so “Small” on the item does not match “Sm” on the modifier. A mismatch fails quietly, which is why a test order for every size belongs on the checklist.

Open prices and open items

Open pricing suits a daily special or a market-price fish, and it removes a control in exchange. Anyone with access can type a number. A written special in the system with a real price, as in the post on using the specials board to move inventory, keeps the sales report honest.

Pizza on a wooden peel beside small bowls of toppings on a prep counter.

Testing before the menu goes live

Draft, publish, repeat

In Toast, changes in the full menu view save automatically, but they must be published to reach the POS, and pricing or visibility edits need a save and then a publish for every affected location. Square sets items by location and channel, and an item left unassigned simply does not appear where expected.

A test pass

A useful test pass is short. Ring one of everything at each size. Add every required modifier, then try to skip one. Send a ticket to each printer and confirm that the right station receives it. Check the tax on a taxable item and an exempt one, and look at the receipt. Staff should see the same menu on a quiet afternoon, well before a Friday night.

For informational purposes only — consult a licensed attorney, tax professional or financial advisor.

Sources

All pages fetched at the time of writing.