Internal Modifier ID / Integration Name Separate from Guest-Facing Modifier Name

[BuiltByLorenzo]

Hey guys!

I’d like to request the ability to have an internal modifier identifier that is separate from the modifier name shown to staff and guests.

A real-world restaurant example:

Let’s say I have a modifier called: No Black Olives

To a guest, that’s all they need to see.

However, on the inventory side, removing black olives from a Small Pizza, Medium Pizza, and Large Pizza are three different inventory transactions because each size uses a different quantity.

For inventory systems such as Craftable (which is what we use), the modifiers may actually need to be:

NO_BLACK_OLIVES_SMALL
NO_BLACK_OLIVES_MEDIUM
NO_BLACK_OLIVES_LARGE

The same issue exists with Add Beef, Extra Pepperoni, Extra Bacon, Add Chicken, and many other modifiers where the quantity varies by item size.

Today, the only way to make those modifiers uniquely identifiable is to change the actual modifier name. That means we end up with guest-facing and server-facing modifiers like:

Add Beef Small
Add Beef Medium
Add Beef Large

or

No Black Olives Small
No Black Olives Medium
No Black Olives Large

which creates unnecessary clutter in POS ordering screens, online ordering, receipts, and menus... and.... it tweaks my OCD seeing backend info on the server pads 😉

It would be extremely helpful if modifiers had an optional Internal ID, SKU, or Integration Name field that is passed through APIs and integrations but is hidden from guests and staff.

Example:

Visible Modifier Name:
Add Beef

Internal Integration Name:
ADD_BEEF_SMALL

Visible Modifier Name:
Add Beef

Internal Integration Name:
ADD_BEEF_MEDIUM

Visible Modifier Name:
Add Beef

Internal Integration Name:
ADD_BEEF_LARGE

This would allow restaurants to maintain accurate inventory depletion and recipe costing while keeping the ordering experience clean and simple.

The need for this becomes especially important in pizza, sandwiches, salads, bowls, and other menu categories where modifier quantities change based on item size.

Thanks! Loving all the new features and updates lately! Super exciting!

Lorenzo

[Donnie-M]

@BuiltByLorenzo  Lorenzo, before I point you at a fix, let me put a hypothetical to you so I'm aiming at the right problem.

Items already carry a discrete operational name that the guest never sees and that lives in its own field, separate from the menu name. So here is the question. If a modifier could carry that same kind of thing, a discrete operational identifier, hidden from the ordering screens and receipts, but addressable through the API in a way Craftable could reliably key on, would that actually close the issue for you?

I ask because I want to know whether what you need is a naming and identifier problem, or whether it is living one layer deeper than that. Your answer tells me which one we are really solving.