Skip to main content

ezCater Menu Limitations & Menu Update Requests (LB 2.0)

M
Written by Mark Robert Turner
Updated yesterday

Overview

This article explains how to safely update ezCater menus after launch without disrupting future-dated orders. It outlines required visibility and POS configuration rules for new, updated, and removed items, and provides guidance on pricing, coupons, and go-live transitions. It also includes a high-level breakdown of the ezCater order flow and recommended settings to ensure orders are properly ingested and sent to the POS.

EZCater Menu Limitations:

  • No Maximum Item Count (Needs to live in the menu item disclaimer)

  • No Default Items or Modifiers

  • No Multi-Select Modifiers

  • No Nested Modifiers

  • No Multiple Sizes per Item: workaround in the important note

  • No Uplift Pricing

  • No store-specific pricing beyond 10 tiers. There is a maximum of 10 pricing tiers (max per corporate group, not per POS). This means that a restaurant partner can have up to 10 different price modes/ tiers, and every store needs to have at least one assigned.

  • No 86ing from the POS or Lunchbox; items and modifiers must be set as unavailable only via the ezCater dashboard.

  • Images and item descriptions must be manually added in ezCater.

  • Menu updates require an update in 2 places, on POS & ezCater

IMPORTANT NOTE: Please note this is a workaround. Lunchbox Sizes are NOT supported; a modifier group can be added with the base price on the item, and a modifier group with modifiers that have upcharges for larger sizes. Example:

  • Coffee $3.00

  • Choose your coffee size

    • small 0.00

    • medium 0.50

    • large 1.00


ezCater Menu Update Requests

Menu changes submitted to ezCater can take up to five business days to process. To request an update, submit the request via form and schedule the change. Review the guidelines below to avoid issues with future orders that have not yet been sent to the POS.

Menu Updates After the Initial Launch

These instructions help prevent order failures when future-date orders are already in the queue:

  1. Adding new items, modifiers, or optional modifier groups

    • Add the new items and hide them from the POS until the launch date. Set visibility to Dine In and ezCater in Lunchbox during this period.

  2. Adding new required modifier groups or converting an existing group to required

    • Create a new item instead of modifying the existing one. If the original item is changed, any pre-existing future orders will fail to send to the POS.

  3. Removing items, modifiers, or required or optional modifier groups

    • Hide them from the POS and set visibility to Dine In and EZCater only. Keep this configuration until the last outstanding order containing the item has been sent to the POS. If some items are unavailable, contact the guest and issue a new quote with updated selections.

  4. Pricing updates

    • There are two approaches:

      • Option A: Update the existing items. A write-off tender ID must be set up, and ezCater has a five-day SLA for price changes. Decide how price mismatches in Toast will be handled during the transition window.

      • Option B: Create new items with updated prices. Build new items ahead of time, hide them from the POS, and set visibility to Dine In and ezCater until the go-live date.

  5. Coupon updates

    1. Only required if the ezCater menu is shared with the native menu and the discounts rely on category or item validation.

  6. At go-live: Expose the new items to the POS. Hide the old items and set their visibility to Dine In and EZCater only in Lunchbox.

Did this answer your question?