Skip to main content

Olo Orders to Menus API Conversion

If your brand is already live on the Orders API, you can add the Menus API through a conversion — a focused project that connects your existing Olo menu directly to ezCater, so one menu drives both platforms

Who conversions are for

Conversions apply only to brands currently live on the Orders API. All new brands joining ezCater are onboarded through the Menus API from the start, so no conversion is needed.

If you’re not yet on either API, start with the Menu Integration Overview instead.

What you gain

Benefit

What it means for you

Location menu flexibility

Maintain a unique menu per location, with no cap on menu tiers

Easier menu management

Streamlined item and pricing updates, reducing manual intervention by ezCater

Accurate, reliable syncing

Your menu and menu images stay consistent between Olo and ezCater in real time

What the conversion involves

The primary action is menu tagging — adding metadata tags to your existing menu directly in Olo Menu Management, following the Menu Setup Guide. In some cases, minor menu adjustments may be needed, such as restructuring deeply nested modifiers or adding a Meal Program category, but these are situational and will be communicated upfront.

Every brand going through a conversion is paired with a dedicated project manager and software configuration specialist who provide 1:1 support through the entire process, from initial setup through final conversion.

Most brands convert all locations at once rather than running smaller pilots — a single cutover keeps ongoing menu maintenance simpler

The conversion process

  1. Review the documentation. Start with the Menu Setup Guide for metadata tagging guidance, and the recorded walkthroughs on Videos & Walkthroughs if a guided step-by-step is helpful. If any of your locations participate in Meal Program, also review Meal Program Menu Set Up — it’s an additional required step

  2. Apply metadata tags. Tag all menu items in the Olo company menu, then assign all menu categories and items to the Olo demo vendor

  3. Initial menu import. Work with the ezCater team to import the menu into ezCater’s POS testing environment, error free

  4. Menu review. ezCater reviews the menu and produces a menu consult doc with any identified requirements or recommendations

  5. Revisions. Work through the feedback in the menu consult doc to resolve any missing tags or errors

  6. Final approval and rollout. Once all tagging and requirements are approved by a menu configuration specialist, your project manager converts all locations

Tagging requirements

Tagging is the core of the conversion. Every item must include CateringServeSize, TaxCategory, QuantityUnit, and a utensils configuration (free or paid). Where applicable, add FoodLabelingTags, ItemTypeTags, and ChoiceTypeTags — these are reviewed during the menu review step, and any missing or incorrect tags are flagged in the menu consult doc.

For every tag’s accepted values, see the Tag Reference. For the utensils patterns and per-item-type configurations, see Utensils — free utensils are the most common choice, and utensils are required on every food item with the exception of individual drinks.

If even one of your locations participates in Meal Program, Meal Program tagging must be completed as part of the conversion — including RelishChannel = T and the Meal Program–specific rules in Meal Program Menu Set Up. Without it, the import creates a blank Meal Program menu for those locations

Structural considerations

A few menu structures need attention before conversion. Common updates needed are:

  • 86’d items: Temporary deactivation isn’t supported on Marketplace — 86’d items must be removed from the menu, or ezCater’s visibility removed from the item in Olo. See Features or Rails Visibility for more information

  • Quantity modifiers: Selections like “choose exactly 3 sandwiches” are supported using minimum and maximum settings on the option group; selecting multiple quantities of a single option is not. See Features for the configuration guidance.

  • Deeply nested modifiers: One level of nesting is supported; anything past the

    first level causes menu ingestion failures and needs restructuring. See Features.

Getting started

Email [email protected] to confirm your brand’s eligibility and kick off the project. Your project manager and software configuration specialist will take it from there.

Did this answer your question?