Modifiers"Kitchen-Proof"
Real examples to make your tickets clean and keep the kitchen flowing. Part of Shift4 Dine's menu management system.
modifiers-kitchen-proof.mp4 · 7:12
Key Takeaways
- Kitchen Print Names: under 12 characters
- Pre-Modifiers: NO, EXTRA, SUB, ADD, SIDE
- Group by choice sets, limit selections
- Price adjustments tracked in reports
- Avoid infinite tickets with max caps
Before vs After: Same Order, Different Ticket
The same two items. The left ticket slows the line. The right one flows.
Cheeseburger
Please Remove Onions From The Burger
Add Extra Cheddar Cheese On Top
Substitute Sweet Potato Fries For Regular Fries
Medium Well Done Please
Extra Mayo On The Side In A Cup
Caesar Salad
No Croutons Please
Add Grilled Chicken Breast
Dressing On The Side In A Ramekin
Cheeseburger
NO Onion
EXTRA Cheddar
SUB Sw Potato Fr
Med Well
SIDE Mayo
Caesar Salad
NO Croutons
ADD Grll Chicken
SIDE Dressing
Same order. 10 fewer lines. The kitchen reads it in half the time. Pair this with a Kitchen Display System for even faster reads.
Short Names vs Long Names
The "Kitchen Print Name" field is what the line cook sees. Make it count.
- Shift4 Dine shows the "Kitchen Print Name" (set in the Advanced tab of each item). Keep it under 12 characters.
- "No Onion" not "Please Remove Onions From The Burger"
- Pre-Modifiers prefix the modifier name on tickets/KDS: "EXTRA Cheese", "NO Tomato", "SUB Fries"
- Every character on a ticket costs the kitchen a fraction of a second. Multiply that by 200 tickets a night.
Please Remove Onions From The Burger
NO Onion
Group by Choice Sets
Logical grouping reduces decision fatigue for staff and the kitchen.
- Modifier Sets are assigned per item. Use the up/down arrows or alphabetical sort to control display order.
- Group logically: Protein Choice, Cooking Temp, Toppings, Sides
- Limit choices per set to reduce decision fatigue (for staff AND kitchen)
- Consistent ordering means the kitchen always reads tickets the same way, every time.
Modifier Order
Substitution and Upcharge Rules
Price adjustments that actually track correctly in your reports.
- Pre-Modifiers with price adjustments reflect on ticket totals automatically
- Price adjustments cannot reduce a modifier below $0.00
- Each Pre-Modifier/modifier combo is tracked separately in reports (quantity, avg price, totals)
- This means you can see exactly how many EXTRA Cheese orders you sold last month, and at what margin.
Report Preview
| Modifier | Qty | Rev |
|---|---|---|
| EXTRA Cheese | 142 | $213 |
| SUB Sw Pot Fr | 89 | $178 |
| ADD Bacon | 67 | $201 |
| NO Onion | 54 | $0 |
How to Avoid Infinite Tickets
The #1 complaint from kitchen staff: tickets that scroll off the screen.
- Cap modifiers per set (max selections). If a burger has 15 topping options, limit to 5 max.
- Use Pre-Modifiers instead of creating duplicate modifiers ("EXTRA Mayo" vs creating a separate "Extra Mayo" item)
- When Pre-Modifiers are enabled with red/bold formatting, they stand out on KDS
- Fewer lines per ticket = faster reads = fewer mistakes = happier kitchen.
Max Selection Rules
Good to Know: Pre-Modifier Limitations
Keep these in mind when planning your modifier structure.
- Pre-Modifiers are set up in Lighthouse Business Manager, not on the POS directly
- Pre-Modifiers only work on items that have at least one assigned modifier set
- Pre-Modifiers do NOT appear on online ordering, third-party delivery, kiosks, or mobile apps
- Configure which modifiers show on KDS via the KDS assignment after sending config
Download the "Modifier Standard" Template
Naming conventions, grouping rules, modifier limits per item. Plug in your menu and hand it to the kitchen. Not sure which POS fits? Read our guide on what to look for in a POS.
Clean tickets. Fast kitchen. Happy cooks.
Get the modifier template, watch the tutorial, and stop printing novels on your tickets. Explore all menu management features in Shift4 Dine.