How to Build Custom Modifiers, Split Bills, and Conditional Logic for Your Restaurant POS

Watch a new server try to ring in a four-top's dinner order on a Friday night at 7:15 PM. Table 12 wants a ribeye medium-rare, substituting mashed potatoes for truffle fries, with peppercorn sauce on the side, plus a kids' combo where the drink needs to come out with the appetizers. On a rigid system like Clover or Square, that single order takes 14 screen taps across three sub-menus. Tap the wrong nested folder, and the server has to cancel out and start over while the line at the host stand grows.

Most restaurant owners end up bending their service style to fit whatever menu structure their software allows. We built Final POS so the software bends to you instead. Final is the world's most customizable POS, and Flow Studio is how you customize it. Most restaurants grab a ready-made layout from the Flow Library and adjust it to match their floor plan, menu rules, and kitchen routing. Or you can just describe your workflow in Build and let Flow Studio generate it from scratch.

Why Do Nested Modifier Menus Slow Down Table Turnover?

A custom modifiers POS setup organizes product add-ons, substitutions, and cooking instructions into guided checkout steps rather than static button grids. When your point of sale dumps every possible option onto the screen at once, servers spend more time hunting for buttons than talking to guests.

Standard POS setups from Lightspeed or Shopify POS usually treat modifiers as flat lists attached to items. Offer 12 salad dressings, 8 protein add-ons, and 6 allergy flags, and your server has to scroll through all 26 buttons every time someone orders a Caesar salad. During a Friday rush, those extra seconds at the terminal add up fast and keep staff off the floor.

In Manage, our back-office dashboard, product modifiers and composite products get strict rules before they ever hit the dining room. You create modifier groups with unique names (if a name already exists, Manage points you to the existing modifier) and specific answer types:

• Pick One: Radio buttons for mandatory single choices like steak temperatures or dressings.

• Pick Many: Checkboxes for burger toppings or pizza add-ons when guests want multiple items.

• Quantity: Steppers at the till so a cashier can tap "+2" on extra espresso shots or side sauces.

Combine those catalog rules with custom screen logic, and the register stops acting like a giant spreadsheet. It guides the server through the ticket like a seasoned shift manager.

The Problem with 'Ask Server' Buttons and Handwritten Kitchen Notes

Walk into almost any independent restaurant running an inflexible terminal from Clover or Lightspeed. You'll spot yellow sticky notes taped to the bezel, or an overused "Open Food / Ask Server" button on the screen. Servers rely on open-text notes because the POS can't handle the restaurant's actual rules.

Yellow sticky notes and open-text kitchen instructions are a clear sign that your restaurant software can't handle your menu rules.

Typing "sub fries +$2" into a special instructions box instead of tapping a real modifier breaks three things immediately:

1. You lose the upcharge revenue: Text notes don't add $2.00 to the bill unless the server also remembers to hunt down a separate "Misc Upcharge" button.

2. Your inventory drifts: Manage tracks stock across your catalog, but a free-text note for truffle fries won't deduct a portion from kitchen inventory.

3. Your [End of Session report](/help/read-your-end-of-session-report) is wrong: Wired properly, your End of Session report breaks down Gross Modifiers Sold, Modifiers Refunded, and Net Modifiers right below your Sales Summary. Handwritten kitchen notes and verbal pass-downs vanish from your financial reporting.

To get rid of manual workarounds across your whole operation, see our guide on how to build your own POS with custom no-code checkout flows.

Using WHEN/THEN Logic in Build to Guide Servers

Conditional logic in a restaurant POS automatically shows, hides, or requires specific checkout steps based on what the server just tapped. Instead of forcing new hires to memorize which entrees include a soup or salad and which ones cost extra, you wire the rules directly into your flow.

Conditional WHEN/THEN rules ensure every substitution, cooking temperature, and side sauce routes cleanly to the kitchen.

You don't need to write code or hire a developer to set up conditional logic restaurant POS workflows in Build. Start with a hospitality template from the Flow Library and tweak it, or describe what you need in plain English using Build, Plan, and Ask modes.

Take a classic dinner combo or composite product. When a server adds a burger combo to the cart in Final Station, a selection screen displays the choice groups and included items, pre-selecting the cheapest option in each group to keep the line moving. Each component inside a composite product keeps its own modifiers, even though the composite itself doesn't have modifiers of its own. Choosing the burger automatically triggers the meat temperature prompt and topping checkboxes. Choosing a latte as the drink brings up milk options. Everything nests cleanly under one line item in the cart, updating the total live as upcharges are tapped.

With WHEN/THEN automations in Build, you can push this further across any step of the order:

• Step-by-step guardrails: WHEN a server selects any item in the "Steaks & Chops" category, THEN require the "Cooking Temp" modifier group and display the "Steak Sauces" upsell prompt before letting them return to the main menu.

• Smart kitchen routing: WHEN an order contains items tagged "Bar" and "Patio Station," THEN route drink tickets to Final Print at the service bar and food items to your Final KDS in the kitchen.

• Automatic fee calculation: WHEN a table's guest count is 6 or higher, THEN apply an 18% service charge and flash a reminder on the server's screen.

Every account gets 1,000 free build credits per day (up to 5,000 a month), with zero monthly software fees for Build, Manage, or Run. If you want to overhaul ten different flows in a single afternoon, one-off credit top-up packs start at $10 for 2,000 credits (Spark) and never expire.

Building Custom Combo Rules, Dynamic Happy Hour Pricing, and Allergen Alerts

We talk to restaurant owners paying $109 a month or more for Lightspeed, or sitting in a 3-to-5-year processor contract with Clover, who still can't run the Tuesday night promo they want because their software only handles basic percentage discounts.

Build includes custom forms with calculated fields and conditional logic on any step, so you can set up the exact rules your dining room runs on.

Hard-Stop Allergen Workflows

Standard POS systems let a server tap a small "Gluten Allergy" button that prints in tiny font at the bottom of a kitchen ticket. In Build, you can create a hard stop: WHEN the "Severe Allergy" toggle is tapped, THEN open a mandatory custom form requiring the server to select the specific allergen, highlight the kitchen ticket header in red on Final KDS, and block items flagged with that allergen from being added to the seat without a manager PIN override.

Time-Based Happy Hour Screens

Stop relying on bartenders to watch the clock for happy hour. Set conditional rules in your flow so that between 4:00 PM and 6:00 PM on weekdays, the "Happy Hour" category button jumps to the top of the screen, draft beer modifiers automatically drop by $2, and the bar snack bundle unlocks.

Designing a Stress-Free Split Bill and Tip Flow for Friday Night Rush

Four people at a table want to split the appetizers three ways, keep the wine bottle on seat one, and pay the rest on separate cards. Nothing kills table turnover faster. On rigid systems, splitting a check after modifiers are applied is a minefield. Servers easily split a $24 pizza while leaving the $4 pepperoni modifier on the first guest's tab, creating awkward math at the table.

Keeping modifiers nested under their parent items makes splitting checks across multiple cards fast and accurate at the table.

Customizing your checkout in Flow Studio lets you design a custom split bill workflow that matches how your staff actually takes payments. Because composite products and attached modifiers stay nested under their parent item in the cart, moving a customized entree to Seat 3 brings all of its upcharges along with it.

For payment collection, Final Pay is built directly into every flow with one transparent rate and zero monthly terminal fees:

• Canada: 1.99% + $0.10 CAD in-person (Interac debit is 0.5% + $0.07 CAD).

• United States and worldwide: 2.49% + $0.10 in-person.

• Europe: 0.99% + €0.10 in-person.

• Cash: Always $0.

Compare that to Square's 2.6% + $0.10 flat rate, or Clover's 2.3% to 3.5% tiered processing contracts that climb once non-qualified reward cards show up. If your Canadian restaurant processes $60,000 a month in card volume, dropping from a 2.8% blended rate to Final Pay's 1.99% saves you nearly $500 a month.

Servers can take those split payments at the table using Final Move handhelds, or use Tap to Pay on iPhone and NFC Android phones without an external reader. Tips and on-reader signatures happen on the same screen, settling through one built-in dashboard.

How Can You Change Your Restaurant POS Menu Instantly Across All iPads?

You can change your restaurant POS menu instantly by editing your catalog in Manage or adjusting your layout in Build, then deploying the update live through Run. Every registered Station gets the new buttons, prices, and modifier rules in seconds, without waiting for an App Store review.

If the kitchen 86s halibut at 8:00 PM on a Saturday, or you want to launch a rainy-day soup combo ten minutes before lunch service, you shouldn't have to file a support ticket or reboot every terminal in the building.

Final Station runs natively on iOS, Android, macOS, and Windows. You can run an iPad POS for restaurants no contract setup using tablets you already own, or buy counter hardware like Final Touch, Final Touch Pro, Final Flex (with its desktop stand and built-in receipt printer), or the Final Register bundle with its 10.1-inch customer-facing display and Max cash drawer.

Your Next Step Before Friday Service

Pull three messy tickets from last weekend's rush—the ones covered in red pen or "Ask Server" notes. Open a free Final POS account, pick a restaurant starting flow from the Flow Library in Flow Studio, and spend 15 minutes using your free daily credits in Build to wire those modifier and split-bill rules into a real screen. Load Final Station onto an iPad or phone in your office and tap through the order yourself. You'll see right away how much faster the floor moves when the register speaks your kitchen's language.