Orbit Dine Item Variants, Portion Multipliers & Modifier Groups Runbook

1. Executive Operational Brief & Capability Benchmark

In modern culinary venues, items are rarely sold as static, unalterable units. Guests routinely customize portion dimensions (Small, Medium, Large, Family Platter), request culinary preparation styles (Rare, Medium, Well-Done), choose spice calibrations (Mild, Medium, Extra Hot), and declare critical allergen restrictions (Nut-Free, Gluten-Free, Dairy-Free).

When restaurant point-of-sale systems handle variants through flat item duplication (e.g., creating separate menu entities for "Pepperoni Small", "Pepperoni Medium", and "Pepperoni Large"), severe operational friction emerges:

1. Inventory Valuation Distortion: Each duplicate item requires manual recipe BOM binding. If a chef updates the dough recipe on the Medium pizza but neglects the Small and Large entries, inventory valuations and food cost percentages immediately desynchronize.
2. Kitchen Ticket Clutter: Prep cooks on the cook-line bump bar and course pacing line receive inconsistently formatted item descriptions, increasing ticket reading time by 3 to 7 seconds per dish and causing portioning errors during peak rushes.
3. Allergen Omission Catastrophes: Freeform text notes typed by cashiers (e.g. "no nuts pls") can easily be overlooked by line cooks working over roaring grills, creating life-threatening health liabilities.
4. Cashier Speed Degradation: Cashiers forced to navigate deep, convoluted modifier sub-menus take upwards of 40 seconds to configure a single custom burger, backing up front-of-house customer queues.

Orbit Dine resolves these operational failure modes through a unified variant modeling architecture:

• Entity-Level Multi-Tier Variants: A single master menu entity encapsulates multiple dimensional sizes defined via the VariantFormItem schema.
• Dimensional Stock Multipliers: A calibrated scalar (stockMultiplier, e.g. 0.5x, 1.0x, 1.4x, 1.6x, 2.0x, 6.0x) proportionally scales raw ingredient depletion at the exact moment of order firing, preserving perpetual ledger valuation without requiring separate recipes for every portion size.
• Structured Modifier Groups: Enforces strict operational rules distinguishing mandatory single-select requirements from optional multi-select customizations with positive or zero upcharges.
• Allergen KDS Escalation Protocol: Critical dietary flags inject high-visibility chromatic alerts into station routing streams across multi-station kds routing.

2. Multi-Tier Variant Architecture & The VariantFormItem Schema

The underlying data model encapsulates item variations directly within the parent menu document, maintaining relational integrity across pricing, inventory, and order dispatch layers.

The VariantFormItem Interface Specification

interface VariantFormItem {
  id?: string;               // Unique variant identifier
  name: string;              // English title (e.g. "Large (13 Inch)")
  nameUrdu: string;          // Urdu Nastaliq title (e.g. "بڑا پیزا")
  price: string | number;    // Retail price in local currency (PKR)
  stockMultiplier: string;   // Proportional inventory deduction scalar
  isDefault?: boolean;       // Active selection on cart initialization
}

When an item defines hasVariants = true, the base menu price is overridden by the selected variant's price attribute, and all inventory depletion calculations reference the variant's stockMultiplier. Entity catalog registration and bilingual typography are configured in bilingual menu catalog and category taxonomy, while temporal discounts are calculated in dynamic pricing and scheduled happy hours and bundle pricing is managed in combo deals and promotional discount rules.

1-Click Variant Template Presets

To accelerate menu engineering during store onboarding or seasonal menu overhauls, Orbit Dine includes five calibrated 1-click variant templates:

3. Mathematical Stock Multipliers & Perpetual Inventory Depletion

The primary technical innovation of Orbit Dine variant engineering is the decoupling of portion sizes from redundant recipe maintenance. Rather than requiring chefs to author three separate recipes for Small, Medium, and Large pizzas, the culinary team authors a single authoritative base recipe tied to the Medium (1.0x) benchmark.

Proportional Depletion Mathematical Model

When a guest check is submitted and bumped on the kitchen line, the inventory depletion engine evaluates every line ingredient across the Bill of Materials (BOM):

Q_deduct = Q_recipe * Q_order * M_stock

Where:

• Q_recipe represents the measured ingredient quantity defined in the master recipe BOM for the base unit (e.g. 0.220 kg of mozzarella cheese for a 10-inch Medium pizza).
• Q_order represents the ordered quantity on the customer ticket (e.g. 2 pizzas).
• M_stock represents the dimensional stockMultiplier defined on the chosen variant (e.g. 1.6 for a 13-inch Large pizza).

Worked Calculation: Large Pepperoni Pizza (Order of 2 Units)

Through this mathematical formulation, raw material deductions scale with mathematical precision. The general ledger immediately debits Cost of Goods Sold (GL 5001) and credits Raw Materials Inventory (GL 1003) as detailed in the recipe yield and realtime depletion guide.

4. Modifier Groups Architecture: Mandatory vs Optional Rules

Modifiers represent culinary alterations, side choices, preparation preferences, and add-ons that customize a specific menu item or variant. Orbit Dine enforces structural separation between two fundamental modifier behaviors:

Modifier Group Taxonomy & Resolution Hierarchy:

For example, when a guest orders the Classic Angus Burger, the order resolution engine evaluates four distinct modifier groups:

1. Group 1: Meat Temperature
   • Type: Mandatory Single-Select (minSelect: 1, maxSelect: 1).
   • Choices: Rare (+Rs. 0.00), Medium (+Rs. 0.00), Well-Done (+Rs. 0.00).
   • Operational Enforcement: Cart cannot be submitted until exactly one choice is selected.
2. Group 2: Spice Calibration
   • Type: Mandatory Single-Select (minSelect: 1, maxSelect: 1).
   • Choices: Mild (+Rs. 0.00), Spicy (+Rs. 0.00), Ghost Chili (+Rs. 50.00).
   • Operational Enforcement: Pre-selects configured default or halts order submission until selected.
3. Group 3: Premium Add-Ons
   • Type: Optional Multi-Select (minSelect: 0, maxSelect: 5).
   • Choices: Extra Cheddar (+Rs. 80.00), Crispy Bacon (+Rs. 150.00), Fried Egg (+Rs. 60.00), Sliced Jalapenos (+Rs. 40.00).
   • Operational Enforcement: Zero or up to five items selectable with dynamic line upcharges.
4. Group 4: Kitchen Preparation Exceptions
   • Type: Optional Multi-Select (minSelect: 0, maxSelect: 3).
   • Choices: No Onions (+Rs. 0.00), No Pickles (+Rs. 0.00), Sauce on Side (+Rs. 0.00).
   • Operational Enforcement: Injects negative recipe flags into kitchen ticket chits.

Modifier Selection Enforcement Rules

1. Mandatory Single-Select (minSelect: 1, maxSelect: 1):
   • Used for essential culinary parameters where the kitchen cannot proceed without guest input (e.g., meat doneness, salad dressing choice, choice of side).
   • The user interface presents radio button selectors.
   • The terminal disallows order progress until a valid choice is highlighted.
2. Optional Multi-Select (minSelect: 0, maxSelect: N):
   • Used for optional add-ons, extra toppings, and exclusions.
   • The user interface presents checkbox selectors with clear upcharge indicators (e.g. + Rs. 80.00).
   • Selecting a modifier with an associated price immediately updates the item line total in real time.

5. Kitchen Display Routing & Allergen Escalation Protocols

Modifiers do not merely alter prices; they directly instruct culinary line cooks on how to prepare the dish.

Allergen Warning Flags on KDS Screens

When a customer specifies an allergy (e.g., "ALLERGY: PEANUT / TREE NUT" or "ALLERGY: GLUTEN COELIAC"), standard text lines are insufficient. Orbit Dine flags allergen modifiers with a critical boolean attribute: isAllergen: true.

When isAllergen: true is present on any modifier in an order item:

1. Chromatic KDS Escalation: The item card on the kitchen display unit transitions from normal slate to a high-contrast pulsating crimson border.
2. Prominent Allergen Banner: The allergy label renders in bold, uppercase white text inside a solid red badge at the very top of the ticket item.
3. Audible Kitchen Chime: The KDS audio controller sounds an alert chime (three rapid 880 Hz pulses) to notify cooks that an allergy-safe ticket has landed on the station.
4. Dedicated Sanitization Mandate: Operational SOP mandates that cooks change cutting boards, gloves, and knives before assembling allergy-flagged items.

Multi-Station Decomposition of Modifiers

If a modifier requires preparation at a separate station (e.g., adding an Espresso Shot to a dessert crepe), the modifier routing bus splits the modifier note onto the Barista KDS while maintaining the master ticket link on the Pastry KDS, ensuring coordinated tray assembly at the expeditor counter.

6. Software UI Frame: Variant & Modifier Configurator

The administrative screen below illustrates the configuration console where menu directors establish portion sizes, dimensional multipliers, and nested modifier groups:

7. Bespoke Workflow Visualization: Variant Multiplier & Modifier Resolution Flowchart

The following schematic illustrates the end-to-end transformation of an order ticket containing variants and modifiers, through mathematical inventory scaling and KDS routing:

8. Empirical Telemetry & Boundary Performance Limits

The variant evaluation and modifier resolution engine is tested under intense concurrent order loads:

9. Operational Failure Modes & Frontline Remediation Runbook

When modifiers or variant multipliers are misconfigured, service disruptions must be rapidly diagnosed and remediated:

10. Advanced SOP: Allergen Protocol & Production Calibration

Kitchen managers must enforce strict standards when onboarding complex multi-tier menus:

SOP 10.1: Standardized Allergen Declarations

1. Every modifier group that involves peanuts, tree nuts, gluten, crustacean shellfish, eggs, milk, fish, or soy must include explicit allergen flags.
2. The modifier title must include the word ALLERGY: in capital letters followed by the specific allergen.
3. The cashier must never type freeform allergy requests in general notes if a structured allergen modifier exists in the system.

SOP 10.2: Stock Multiplier Calibration Protocol

1. Whenever a new portion tier is introduced (e.g. "Monster 24-Inch Pizza"), the executive chef must execute a physical yield test.
2. The raw ingredients consumed in preparing the monster portion are weighed on a digital gram scale and divided by the base recipe weight.
3. The resulting decimal ratio (e.g. 2.75) is entered into the stockMultiplier field. Arbitrary guessing of multipliers is strictly prohibited by corporate culinary audit policy.

11. Operational Inquiries & High-Intent FAQs

Can a modifier carry a negative price deduction (discount)?

Yes. Orbit Dine supports negative modifier upcharges (e.g., "No French Fries (Substitute Salad)" with - Rs. 50.00). When selected, the billing engine decrements the line item price while adjusting the corresponding recipe BOM deduction.

How does the system handle an 86 stock-out of a specific modifier (e.g., out of cheddar cheese)?

Modifiers maintain independent availability flags. If cheddar cheese exhausts mid-service, the expeditor marks the "Extra Cheddar" modifier as 86. The master burger remains available on the POS, but the cheddar option is grayed out in the modifier selection modal across all terminals.

What happens if an operator applies the "weight" preset to an existing item with custom variants?

Applying a 1-click preset replaces the active working variant array in the modal form. The operator must confirm the warning dialog: "This action will overwrite existing variants with the Weight template." Saving the item commits the new tiers to persistent storage.

How are bilingual modifier names displayed on guest-facing customer receipts?

Customer receipts format the primary English modifier name on the main line, followed by the Urdu Nastaliq name indented on the subsequent line. For example:

  + Extra Cheddar Slice (Rs. 80.00)
    اضافی چیڈر سلائس

This guarantees complete transparency for multilingual diners reviewing their final check.

12. Structured Schema Metadata

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "TechArticle",
      "headline": "Orbit Dine Item Variants, Portion Multipliers & Modifier Groups Runbook",
      "description": "Tactical operational SOP detailing multi-tier item variant configuration, mathematical stock multipliers for proportional inventory depletion, modifier groups, and allergen kitchen routing.",
      "proficiencyLevel": "Advanced",
      "articleSection": "Menu Engineering & Pricing",
      "inLanguage": "en-US",
      "publisher": {
        "@type": "Organization",
        "name": "FrontOrbit Core Engineering",
        "url": "https://frontorbit.com"
      }
    },
    {
      "@type": "BreadcrumbList",
      "itemListElement": [
        {
          "@type": "ListItem",
          "position": 1,
          "name": "Home",
          "item": "https://frontorbit.com"
        },
        {
          "@type": "ListItem",
          "position": 2,
          "name": "Documentation",
          "item": "https://frontorbit.com/docs"
        },
        {
          "@type": "ListItem",
          "position": 3,
          "name": "Orbit Dine",
          "item": "https://frontorbit.com/docs/dine"
        },
        {
          "@type": "ListItem",
          "position": 4,
          "name": "Item Variants & Modifiers Runbook",
          "item": "https://frontorbit.com/docs/dine/item-variants-portion-sizes-and-modifiers"
        }
      ]
    },
    {
      "@type": "FAQPage",
      "mainEntity": [
        {
          "@type": "Question",
          "name": "How does the stockMultiplier attribute calculate inventory deductions across different portion sizes?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "The recipe depletion engine multiplies the base BOM ingredient quantity by the order count and the variant stockMultiplier scalar (Q_deduct = Q_recipe * Q_order * stockMultiplier), ensuring proportional raw stock deduction across all portion tiers."
          }
        },
        {
          "@type": "Question",
          "name": "What is the operational distinction between mandatory single-select and optional multi-select modifier groups?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Mandatory single-select groups require exactly one choice before an item can be added to the cart (such as Cooking Temperature). Optional multi-select groups permit zero, one, or multiple choices with positive or zero price upcharges."
          }
        },
        {
          "@type": "Question",
          "name": "How do allergy modifiers trigger critical warnings on Kitchen Display System (KDS) stations?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Modifiers with isAllergen: true trigger a high-visibility pulsating red badge on station KDS screens, sound an audible chime alert, and print inverted warning text on kitchen chits."
          }
        },
        {
          "@type": "Question",
          "name": "Can variant presets be customized with bespoke prices and bilingual names?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Yes. 1-click templates pre-populate standard dimensional tiers, but operators retain full control to edit English titles, Urdu Nastaliq nameUrdu, retail prices, and stockMultiplier values before saving."
          }
        }
      ]
    }
  ]
}