Feature Request: Naming of menu items, modifier groups, modifiers, & retail items

mercimarketnyc — Mon, 09 Nov 2026 19:12:04 GMT

This topic overlaps with multiple community boards so tagging them all here: #Restaurant Operations #Guest Experience # Back Office & Team. Also, this is something that I request from implementing toast into my NYC deli-grocery (which has many customizations for ordered food, and some packaged goods items).

It would be helpful to have the following NAME FIELDS available on TOAST OBJECTS. Each one of the names I requested are for each of the different interfaces that the Toast ecosystem displays (POS, Kiosk, Kitchen, Online, Database [for admins], Retail) and often times, different names are best suited for the different users:
*names are already available with Toast

NAME FIELDS:
1) Database (backend) Name: internal-only name where admins can include for organization and quick menu editing (i.e. 100_Breakfast Section_Bread Type, 200_Lunch Section_Bread Type, 300_Dinner Section_ Bread Type)
2) Kiosk Name: Kiosk-only name that shows up only on the Kiosk. Useful for labeling modifiers differently from the Database Name (i.e. if the Database Name is "100_Breakfast Section_Bread Type" the Kiosk Name that the customer sees could be "Add a Bread?")
3) Online Name: Online-only name that shows up only on Toast Online Ordering and 3rd parties.
*) POS Name
*) Kitchen Name
*) Retail Item Name

TOAST OBJECTS:
1) Menu Items
2) Modifier Groups
3) Modifiers
4) Retail Items

Currently, Toast applies one name to multiple interfaces which makes an admin's job very difficult for keeping track of what TOAST OBJECTS are used where. Listing just a few cases below:
1) The "Name" of a modifier group shows up on the Kiosk and Toast Online Ordering. If a simple name, like "Bread Choice" is used for a set of bread options, but the restaurant has different bread selections or different bread pricing depending on the way a sandwich is ordered, every set of "Bread Choice" options will have the same name despite being different, making an admin's job nearly impossible for making edits once a modifier group is created.
2) The "Retail Item Name" should have a detailed 'database-like' name (i.e. Coca Cola - Original - 20 fl oz), but if I add that item to my Toast Online Ordering site to sell Coca Cola on my site, I don't want to show the 'database-like' name to customers. I want it just to be called 'Coca-Cola Original,' which I can't do without changing the "Name" field of the item. I need multiple name fields for the item with one GUID. Otherwise, it will either not be possible to track inventory in Toast Retail or I will have to use the 'database-like' name on my Toast Online Ordering platforms which is messy and bad for customers/sales.

Having the NAME FIELDS for each of the TOAST OBJECTS I listed above would solve all of these issues. This has been requested in some manner in previous threads listed below, but I believe my request in the post covers the issues more comprehensively:
https://community.toasttab.com/t5/restaurant-operations/feature-request-internal-name-field-for-items-amp-modifiers/m-p/2580#M843
https://community.toasttab.com/t5/restaurant-operations/guest-facing-item-names/m-p/18845#M7879

Thanks for considering this request and I encourage any operators to reply if they have had a similar issue!

topic Feature Request: Naming of menu items, modifier groups, modifiers, & retail items in Restaurant Operations

Feature Request: Naming of menu items, modifier groups, modifiers, & retail items