Toast Charge As Extra?: Check the Price of an Extra Modifier Portion

Toast's new pre-modifier setting charges for one more portion of a modifier, defaults included. The price comes from the modifier group's pricing method. A price-source table, a fictional $12 sandwich, and a one-item test and restore sheet.

Ryan Speier

Quick answer: turn on Charge As Extra? for a pre-modifier such as EXTRA, and when a server applies it to a modifier on the Toast POS, Toast adds a charge for one additional portion of that modifier to the check. Toast's guide says that includes a default modifier, the kind that is otherwise included in the item's price. You do not type the extra portion's price on the pre-modifier. Toast takes it from the modifier group's pricing method: the modifier's own price or its item reference price, the group's shared price, the size price, or the next price in a sequence. Find that number for your item before you turn the setting on, because once you publish, the POS uses it.

Toast announced the setting on October 7, 2026 and says it is rolling out to locations in all countries starting October 13, 2026. When we read the announcement on October 15 it was still tagged Coming Soon, All Locations, so the checkbox may not be in your Toast Web yet, and Toast has not published a POS version for it. This guide is built from Toast's announcement, its platform guide and a support article as they read on October 15. We did not run it on a live Toast account. It covers in-house orders rung on the Toast POS app only: Toast's support article says pre-modifiers are not supported in Toast Online Ordering and that items with pre-modifiers do not map correctly in xtraCHEF.

Three pieces: the modifier, the default and the pre-modifier

A fictional deli makes this concrete. Its Turkey Club is $12.00. The club uses a Cheese modifier group with Cheddar and Swiss, and Cheddar is marked as the default, so it goes on the sandwich automatically and is included in the $12.00. The Cheese group has a pre-modifier group called Sandwich Mods assigned to it, with NO, EXTRA and ON SIDE in it.

  • Modifier: the option itself, Cheddar. Every modifier sits on an underlying menu item Toast calls its item reference. If you built the modifier from an existing menu item, it can use that item's price or a modifier-specific override price.
  • Default modifier: a modifier that is added to the item automatically. Toast's guide describes defaults as otherwise included in the item's price.
  • Pre-modifier: the word in front of or behind the modifier, like EXTRA Cheddar or Cheddar ON SIDE. Pre-modifiers live in pre-modifier groups, and a pre-modifier group is assigned to a modifier group in that group's settings. Toast says any pre-modifier group can be assigned to any modifier group, so one group like Sandwich Mods may sit on many modifier groups.

Toast's pre-modifier support article, last updated September 29, describes two ways a pre-modifier can change a price: a fixed price, or Multiply Price with a factor. Its own example shows the limit of multiplying: if Pickles cost $0, EXTRA Pickles still cost $0. Charge As Extra? is different. It does not multiply anything. It adds one more portion, priced by the modifier group's pricing method.

Where the extra portion's price comes from

This is Toast's extra-portion table, with what to write down for each row and the cases its pages leave open. Check which pricing method your modifier group uses before you read across: the How are modifiers in this group priced setting on the group's page and, if that is All modifiers share the same price, the strategy in its Modifier Group Pricing section (Fixed, Size, Sequence or Size/Sequence).

Modifier group pricing methodExtra portion price, per Toast's guideWrite downWatch for
No chargeThe modifier's own price, or the item reference price if no override price existsWhether an override is set; the override price; the item reference priceNo charge does not mean EXTRA is free. Toast's table can charge the item reference price here. The same guide also says No charge ignores override prices, and it does not say which wins for the extra portion when an override exists. With an override set, the expected price is UNKNOWN.
Each modifier has a unique priceThe modifier's own price, or the item reference price if no override price existsOverride yes or no; the override price; the item reference priceFor a standalone modifier, the price you enter in the group becomes its item reference price, so both are the same number. If you added an existing modifier with an override, Toast says that price applies in every group that prices modifiers individually.
All modifiers share the same priceThe group-level priceThe group's price (Fixed strategy). If the group uses Size, Sequence or Size/Sequence, use those rows.Any override on the modifier is ignored. The number on the modifier is not the number charged.
SizeThe price for the size of the menu item the modifier is applied toThe item's size on this order; the group's price for that sizeToast's size strategy can also price by the modifier's own size. The extra-portion table only mentions the menu item's size, so a group priced by modifier size is UNKNOWN.
SequenceThe additional portion is treated as the next modifier in the sequenceThe sequence prices; how many modifiers from this group are already on the itemToast does not say whether a default modifier takes a position in the sequence. Unless you know the position, the expected price is UNKNOWN until you see it on a test check.
Size/SequenceSize matched to the menu item first, then the next modifier in the sequenceThe item's size; the sequence prices for that size; the positionSame position question as Sequence.

Two things follow from the table. A price of $0.00 in the source gives you nothing to charge, and the fix is the price source, not the pre-modifier. And a blank you cannot find is not zero. Toast notes that when modifiers are bulk-imported with an empty price, it converts that price to $0.00, so an imported menu is worth checking. If you cannot read the number, write UNKNOWN and do not predict the check.

What it does not combine with

  • Fixed price and Multiply Price. Toast says a pre-modifier can use Charge As Extra?, a fixed price or a multiplication factor, but not more than one at a time. If your EXTRA carries a $0.50 fixed price or a factor of 2 today, write that down before you switch, because you will need it to restore.
  • Substitution pricing. That is a separate limited-release feature: a guest swaps a default for another modifier and the default's value counts toward the new one. It is a credit, not an extra portion.
  • Charging the default itself. Another limited-release setting, Allow default modifiers to charge their configured price, makes the default charge its own price. If your group uses it, the cheese is already charged on the check before anyone presses EXTRA, and Toast's pages do not say how the two settings combine. Do not turn either limited-release setting on just to make this work.
  • One portion. Toast describes one additional portion. Its pages do not describe a second EXTRA on the same modifier, a DOUBLE pre-modifier, half portions, or how tax and discounts treat the extra charge. Do not promise guests any of those until you have seen them on your own POS.

If the modifier was added by the guest rather than being a default, Toast says the setting still adds one additional portion. In that case your baseline check already includes the modifier's own charge, and the extra portion is added on top of it.

Fictional example: a $12 sandwich and $1.50 of cheese

This is arithmetic from Toast's documentation, not a receipt from a Toast account. Copy it with the assumptions; the total is only right while every line above it is true.

FICTIONAL EXAMPLE - documentation-derived arithmetic, not a captured Toast receipt
Scope: Toast POS app, in-house order. Not Toast Online Ordering (Toast: pre-modifiers
  not supported). Not xtraCHEF (Toast: items with pre-modifiers do not map correctly).
  Kiosk, Order and Pay, Toast Takeout and online ordering partners: unverified, not covered.
Basis: Toast announcement Oct 7, 2026 (rollout from Oct 13, 2026) and Toast platform
  guide "Pricing modifiers", read Oct 15, 2026.

Item:              Turkey Club, base price $12.00
Default modifier:  Cheddar, included in the item price
                   ("Allow default modifiers to charge their configured price" not in use)
Group pricing:     Each modifier has a unique price
Cheddar price:     $1.50 entered in the group (standalone, so item reference = $1.50)
Pre-modifier:      EXTRA in Sandwich Mods; Charge As Extra? ON; no fixed price; Multiply OFF
Order:             one Turkey Club, EXTRA applied once to Cheddar, nothing else

Baseline (club + default Cheddar, no EXTRA):   $12.00
One additional Cheddar portion:              + $1.50
Expected check before tax and discounts:       $13.50

Not covered: tax, discounts, a second EXTRA, DOUBLE, half portions, substitutions.
Stop if: the baseline is not $12.00, Charge As Extra? is missing, or any input is unknown.

Change one assumption and the answer moves, which is why you trace the source first:

  • Cheese group set to All modifiers share the same price at $1.00: the extra portion is $1.00 and the check is $13.00, even if Cheddar shows $1.50 somewhere else.
  • Cheddar's item reference price is $0.00: the extra portion adds $0.00 and the check stays $12.00. Fix the price, not the pre-modifier.
  • Cheese group priced by Sequence: the extra portion takes the next price in the sequence, but Toast does not say whether the default Cheddar counts as the first position. Expected check: UNKNOWN until you see a test check.
  • Cheddar was not a default and the guest picked it at $1.50: baseline $13.50, and with EXTRA applied the documented expectation is $15.00. Verify it.

Before you turn it on: find everything that shares the pre-modifier

Charge As Extra? is set on the pre-modifier, inside a pre-modifier group, and Toast describes the charge as applying whenever that pre-modifier is applied to a modifier. So every modifier group with that pre-modifier group assigned can be affected wherever a server applies EXTRA. Whether that adds money depends on each group's own price source: a group whose extra-portion price is $0.00 adds nothing, and an item where nobody applies EXTRA never shows it. If Sandwich Mods is also assigned to your Salad Toppings and Burger Add-ons groups, those groups are potentially affected the moment you publish, each priced by its own group's method.

  1. Open each modifier group your menu uses and note its Pre-Modifier Group setting (in the group's settings section). The pages we read do not describe a single report that lists every assignment, so use whatever reliable list of your modifier groups you already keep and check them. For each group that uses the same pre-modifier group as your test item, write down its extra-portion price from the table above, or $0.00, or UNKNOWN.
  2. Pick one test item and its modifier group. If any other group on that list is UNKNOWN, either trace it first or test with a separately named pre-modifier group assigned only to the test modifier group. Toast's support article already recommends separate, distinctly named pre-modifier groups so each modifier group gets the right one. That reassignment is a change servers will see, so the sheet records the original assignment and puts it back if the test fails.
  3. Write down the starting state before you change anything: whether Charge As Extra? is already on, or the pre-modifier's fixed price, multiplication factor or neither, plus its Name, POS Name and Kitchen Name. There is no undo button in the pages we read; putting things back means re-entering what you wrote down.
  4. Settle when and how you will test. Toast says published prices are immediately available on the Toast POS app, and the pages we read describe no preview or sandbox. Use your restaurant's existing approved test-check procedure in a quiet window, with no payment taken and no ticket sent to the kitchen by accident.

This is where the setting lives. Toast's platform guide puts it under Menus, then Settings, then Premodifiers; the support article writes Pre modifiers; the announcement shortens it to Menus, then Pre modifiers. Open the pre-modifier group and look for Charge As Extra? on the one pre-modifier, but change nothing until Parts A to C of the sheet below are done without a stop. If the checkbox is not there, the pages we read do not tell you why. The rollout is one possibility, not a confirmed cause. Change nothing, and ask Toast rather than building a workaround.

Copyable audit and test sheet

TOAST CHARGE AS EXTRA? - ONE-ITEM AUDIT AND TEST SHEET
Applies to: orders rung on the Toast POS app, in-house.
Does not apply to: Toast Online Ordering (Toast: pre-modifiers not supported) or
  xtraCHEF recipe/inventory costing (Toast: items with pre-modifiers do not map correctly).
Unverified, not covered: Kiosk, Order and Pay, Toast Takeout (Local by Toast), online
  ordering partners. Do not extend this test to them.
Basis: Toast announcement Oct 7, 2026 (rollout from Oct 13, 2026); Toast platform guide
  "Pricing modifiers"; Toast Support "Create and Assign Pre-Modifiers" (updated
  Sep 29, 2026). Read Oct 15, 2026. This sheet is a plan, not a completed device test.
All money: dollars, before tax and discounts. Blank or unreadable is not $0.00.

Stop rules: each line says what its answers mean. There are three ways out.
  PREFLIGHT STOP (Parts A-C, D0): nothing has been changed. Do not save or publish
    anything; there is nothing to restore. Resolve the open item, then start a new sheet.
  ROLLBACK (Part E): do Part F. Put back only what Part D records, nothing else.
  INCIDENT (a payment taken, or a kitchen ticket sent by accident, at any point): stop
    testing and handle it through your restaurant's approved procedure. Putting
    settings back does not undo a payment or a ticket. If Part D was done, also do Part F.
  Do not cover a wrong price with open items or manual charges.

PART A - STARTING STATE (look only; change nothing)
Location: __________  Date/time: __________  Done by: __________
Test item: __________  Modifier group: __________  Modifier: __________
Modifier is:  default on this item / guest-selected
Pre-modifier group assigned to the test modifier group: __________
Pre-modifier: _______  Name: _______  POS Name: _______  Kitchen Name: _______
A1 Charge As Extra? checkbox visible on this pre-modifier?
   Y = continue.  N = PREFLIGHT STOP. Why it is missing is not known (the rollout is
   one possibility); ask Toast.
A2 Starting mode, exactly as set now (circle one, write the value):
   Charge As Extra? already on / fixed price $_____ / multiply x_____ / neither
A3 Default modifiers set to charge their configured price ("Allow default modifiers
   to charge their configured price", limited release)?
   N = continue.  Y or not sure = PREFLIGHT STOP (Toast does not say how the two
   combine).  Guest-selected modifier: N/A.
A4 Approved test procedure (who rings and clears test checks and how; no payment;
   no unintended kitchen ticket): __________________________________________
   Written = continue.  None = PREFLIGHT STOP.

PART B - PRICE SOURCE FOR THE TEST MODIFIER (look only; change nothing)
B1 Group pricing method (circle one): No charge / Each unique / Shared (Fixed) /
   Size / Sequence / Size-Sequence
   Fill in only the line for the method you circled. Write N/A on every other line.
   No charge:   override set?  N: item reference $_____
                Y = PREFLIGHT STOP (Toast's guide conflicts on which price applies)
   Each unique: override set?  Y: override $_____   N: item reference $_____
   Shared:      group price $_____
   Size:        priced by the menu item's size?  Y: size on this order _____
                price for that size $_____    N (modifier's own size) = PREFLIGHT STOP
   Sequence / Size-Sequence: size, Size-Sequence only _____
                position of the extra portion known for certain?  Y: price at that
                position $_____    N = PREFLIGHT STOP (Toast does not say whether a
                default takes a position)
   A needed value on your line blank or unreadable = PREFLIGHT STOP.
B2 Expected extra price: $_____
   $0.00 is a real price: EXTRA will add nothing to this item. If that is what you
   want, continue. If you meant to charge, PREFLIGHT STOP: correct the price through
   your normal menu process first (this sheet changes no prices), then start a new sheet.
B3 Baseline as priced today (item + modifier, no EXTRA): $_____
B4 Expected one-EXTRA check with Charge As Extra? on = B3 + B2 = $_____

PART C - SHARED GROUPS AND BEFORE-CHANGE CHECKS (no setting changes)
C1 Other modifier groups with the same pre-modifier group assigned, each with the
   extra-portion price from its own pricing method ($0.00 or UNKNOWN allowed):
   none / __________ $_____ / __________ $_____ / __________ $_____
   Each can be affected wherever this pre-modifier is applied; a $0.00 group adds
   nothing. Any UNKNOWN: use D2 in Part D, or PREFLIGHT STOP.
C2 Ring on a test check, following A4:
   Baseline (item + modifier, no EXTRA) observed $_____   equals B3?
     Y = continue.  N = PREFLIGHT STOP (the price source was misread; redo Part B).
   One-EXTRA observed $_____   How EXTRA shows today: ______________________
   C2 is the starting behavior a rollback has to get back to.
C3 Test checks cleared per A4?  Y = continue.  N = finish clearing, then answer again.
C4 Payment taken?  N = continue.  Y = INCIDENT.
C5 Kitchen ticket sent by accident?  N = continue.  Y = INCIDENT.
C6 A2 = Charge As Extra? already on: one-EXTRA observed equals B4?
     Y = done. Already working as documented for this item; skip Parts D-F.
     N = PREFLIGHT STOP. Do not turn it off from this sheet; take C2 to Toast.
   Any other A2: N/A, continue.

PART D - ONE CHANGE (only after Parts A-C with no stop, and A2 not already on)
D0 Parts A-C saved where someone else can find them?
   Y = continue.  N = PREFLIGHT STOP.
Do one of these, then save and publish:
D1 Same group: on the Part A pre-modifier, Charge As Extra? on; fixed price and
   multiply cleared. Changed: mode, from A2 to Charge As Extra?.
D2 Separate group (required if C1 has any UNKNOWN): new pre-modifier group
   named __________ with the same pre-modifiers, names and settings as the Part A
   group, except Charge As Extra? on for this pre-modifier only. Test modifier
   group's pre-modifier group changed from __________ (Part A) to __________.
   Part A group not edited.
Anything else changed (should be none): __________  old value: __________
Published at _____ (published prices go live on the POS immediately)

PART E - CHECK ON THE POS AFTER THE CHANGE (following A4)
E1 Baseline observed $_____   equals C2 baseline?   Y = PASS.  N = ROLLBACK.
E2 One-EXTRA observed $_____  equals B4?            Y = PASS.  N = ROLLBACK.
   How the extra shows on the check: ______________________
   Kitchen text, only if A4 sends a test ticket: ______________________
E3 D1 used and C1 not "none": one other item from C1 __________ rung with its
   modifier and no EXTRA $_____, then EXTRA once $_____. Difference equals its C1
   price?  Y = PASS.  N = ROLLBACK.   D2 used, or C1 = none: N/A.
E4 Test checks cleared per A4?  Y = PASS.  N = finish clearing, then answer again.
E5 Payment taken?  N = PASS.  Y = INCIDENT.
E6 Kitchen ticket sent by accident?  N = PASS.  Y = INCIDENT.
Answer E4-E6 even after a ROLLBACK answer.
Result: E1-E6 all PASS (E3 may be N/A) = test complete. Leave the change in place,
  brief the servers and keep this sheet. Any ROLLBACK or INCIDENT = not complete.

PART F - ROLLBACK (only after Part D, on a ROLLBACK or INCIDENT)
Put back only what Part D records, using the Part A values:
F1 D1 used: Charge As Extra? off, then the A2 starting mode and value re-entered
   (fixed price $_____ / multiply x_____ / neither). Part D is skipped when A2 is
   already on, so this never turns off a setting that was on when you started.
F2 D2 used: test modifier group's pre-modifier group set back to __________
   (Part A). Leave the Part A group as it is; leave the new group unassigned.
F3 Anything else listed in Part D: put back the old value written there.
Saved; published at _____
F4 Re-ring per A4: baseline $_____ and one-EXTRA $_____ equal the C2 values?
   Y = restored.  N = make no further changes; escalate per A4 and to Toast.
F5 Incident from Part E handled through the approved procedure?  Y / N / none
   (F1-F4 do not resolve it.)
Send Toast: what was set, what you expected, what the POS showed (B, C2, E).

Test one item, then decide

  1. Fill in Parts A, B and C before you touch any setting. A PREFLIGHT STOP in any of them means nothing has changed, so there is nothing to undo: do not save or publish, sort out the open item (trace the price, ask Toast), and start a fresh sheet.
  2. Ring the before-change checks in Part C: the item with its modifier and no EXTRA, then with EXTRA once, as your menu is set up today. Those two numbers are what a rollback has to get back to.
  3. If Charge As Extra? was already on when you started, Part C has already checked it. Skip the rest: nothing in this sheet turns it off.
  4. Otherwise make one change in Part D, publish, and note the time.
  5. Ring the Part E checks. Write down exactly how the check shows the extra charge. Toast's announcement says to confirm the check displays the charge for the additional portion; it does not show what the line looks like, so record what you see. If your test procedure sends a ticket, read the kitchen text. Toast prints pre-modifiers on kitchen tickets and uses each pre-modifier's Kitchen Name there.
  6. Every Part E line PASS, with E3 N/A where the sheet allows it: the test is complete and the change stays. A price that does not match: Part F puts back only what Part D says you changed, then you re-ring both checks against Part C and take the filled-in sheet to Toast support.
  7. A payment taken or a ticket sent to the kitchen by accident is an incident, not a pass, even if the prices matched. Handle it through your restaurant's approved procedure; putting the settings back does not undo a payment or a ticket. If you had already made the Part D change, do Part F too before you test again.

Brief the servers before service: what EXTRA now charges, on which items, and that it is one extra portion. A guest who asks for double or triple cheese is outside what Toast has documented, so the server should check with a manager rather than improvise a charge.

What this setting does not do

It charges for a portion. It does not cost it. Toast's support article says items with pre-modifiers do not map correctly in xtraCHEF, so do not count on xtraCHEF to cost the extra cheese, and nothing in Toast's pages says the setting touches stock counts. If you want to know whether $1.50 covers a portion of cheese, work that out from your own recipe cost; our food cost percent guide explains the difference between what you bought and what you used. It also does nothing for online guests, who cannot choose pre-modifiers in Toast Online Ordering at all.

If you are also changing prices by time of day, that is a different setting with its own channel limits: see Toast time-specific pricing in Menu Manager. Toast's channel-support page for advanced pricing does not list pre-modifiers or Charge As Extra?, so it is not evidence that the setting works on any channel beyond the POS.

Sources

More on technology

All technology posts · Free restaurant calculators · Opening planner