Olo Orders <> Olo Menu API Conversion Overview

9 min

what is an olo orders <> olo menu api conversion? eligible brands already live on the olo orders integration can be added to the olo menu api integration as well, allowing them to seamlessly integrate their olo menu to the ezcater marketplace note this applies only to brands currently live on the olo orders integration; all new brands joining ezcater are already onboarded through the menu api what does the conversion involve? the primary action required is menu tagging adding metadata tags to an existing menu directly in the olo menu editor in some cases, minor menu adjustments may be needed, such as restructuring nested modifiers or adding a meal program category, but these are situational and will be clearly communicated upfront compared to the original integration process, conversion is a significantly smaller lift with a much more focused effort brands will work with the ezcater software configuration specialists to finalize and approve the menu tagging for conversion what support is provided? each brand going through a conversion will be paired with a dedicated project manager and software configuration specialist who work together to provide 1 1 support throughout the entire process from initial setup through final conversion key benefits location menu flexibility maintain a unique menu per location, no cap on menu tiers easier menu management streamlined item and pricing updates, reducing manual intervention by ezcater accurate, reliable menu syncing syncing your menu directly between olo and ezcater keeps your menu and menu images consistent in real time considerations menu tagging https //api ezcater io/menu sync will need to be completed in its entirety, including meal program https //api ezcater io/meal program menu set up#meal program menu set up if the restaurant partner is participating in the program at even one location 86ing, deeply nested modifiers, and quantity modifiers are not yet supported on the menu api at this time 86’ing items must be removed from the menu or ezcater’s visibility must be removed from the items in olo to accomplish removing an item from the ezcater marketplace quantity modifiers we can accommodate certain configurations using minimums and maximums, but not when the goal is to be able to select multiple of one option example choose 3 sandwiches grilled cheese club mediterranean veggie italian this should be configured using a minimum of 3 and maximum of 3 on the group in olo if the goal was to have up to 3 sandwich types selected, you would instead configure this as a minimum of 1 and maximum of 3 example of not supported quantity modifiers choose 10 sandwiches grilled cheese + 3 club + 0 mediterranean veggie + 2 italian + 5 nested modifiers we can only support a single level of nesting any nesting past that first level will cause menu ingestion failures example ( \supported\ / \not supported\ ) \sandwich box (item)\ \choose sandwich (modifier group) \ \grilled cheese (modifier option)\ \club (modifier option)\ \mediterranean veggie (modifier option)\ \italian (modifier option)\ \toasted (nested modifier, single choice)\ \cut in half (second nested modifier)\ \\ \cut in half (second nested modifier)\ most brands opt to convert all locations at once, rather than smaller piloting periods for menu maintenance purposes what action items are required to convert? the following steps outline the full conversion process that the ezcater team will work alongside brand technical contacts to complete review documentation — start with the menu api documentation https //api ezcater io/menu sync for metadata tagging guidance, as well as the ezcater metadata tagging video https //ezcater wistia com/medias/8ehlcu9tng for any guided step by step that may be beneficial if any locations participate in the meal program, also review the meal program setup https //api ezcater io/meal program menu set up#meal program menu set up , as this is an additional required step apply metadata tags — tag all menu items in the olo company menu, then assign all menu categories and items to the olo demo vendor initial menu import — work with the ezcater team to import the menu into ezcater's pos testing environment, error free menu review — ezcater will review the menu and produce a menu consult doc with any identified requirements or recommendations revisions — work through any of the feedback from the menu consult doc to resolve any missing tags or errors final approval & rollout — once all tagging and requirements are approved by a menu configuration specialist, the project manager can then convert all locations menu tagging requirements menu tagging is the core of the conversion process the following requirements apply to all menus going through a conversion, and ezcater resources are available to identify both the key and the value for each metadata tag all items must include the following metadata tags cateringservesize taxcategory quantityunit utensils (free or paid) where applicable, tags should be added such as the foodlabelingtags, itemtypetags, and choicetypetags, as these will be reviewed during the menu review portion of the project if a required tag is missing or needs to be updated, this detail will be added to the menu consult document special call out utensils utensils are required on every item, with the exception of beverages, and can be configured as both free (most common!) or as paid options free utensils while hidden on the ezcater menu, they are presented as part of the checkout experience free utensils are modeled as an option/choice, and are tagged as “utensils ” to create free utensils specifically for ezcater, do not use the single use category functionality instead, create a modifier group (typically just called utensils) and attach to each ezcater specific item add in the appropriate choices from the menu sync utensils setup https //api ezcater io/menu sync#free utensils specific metadata chart add metadata tag with the key of choicetypetags and a value of utensils and apply the modifier to all items menu tagging requirements meal program meal program tagging is an additional step required for any brand that has locations that participate in ezcater's meal program (formerly relish), but is not required for brands that do not the following requirements ensure meal program orders flow correctly through the api for reporting and menu maintenance purposes review the meal program setup documentation https //api ezcater io/menu sync#meal program menu set up for full tagging guidance and requirements key considerations orders may fail due to a "relish finalized" status that occurs approximately 90 minutes before the customer's requested event time, which can differ from lead times of other menu categories using ezcater specific menu categories/items in the olo menu admin allows for a custom lead time to be set independently for these orders, helping prevent these failures all meal program orders are still fulfilled through the portal — but olo tagging is required to ensure the existing meal program menu is not overwritten with the menu sync menu setup the meal program menu must be configured within the olo menu company admin , either within its own dedicated olo category or tagged onto existing menu items that are shared between both marketplace and meal program menus option 1 — existing categories meal program tags can be applied to existing menu items, but lead time must be carefully accounted for to prevent syncing issues this set up is highly discouraged due to order failure potential option 2 — dedicated category (highly recommended) a separate meal program category can be created in olo to house these items, keeping them clearly isolated from standard menu items, or to include menu items that would not typically be available for the standard catering menus required tagging lead time configuration must be considered for the ezcater specific meal program category/items to account for the “relish finalized window” which occurs approximately 90 minutes prior to the order event time any item that is not physically included with the main ordered item — meaning it will not arrive inside or with the primary item automatically— must be tagged with individually packaged relish side = t this tag triggers a separate label to be generated for that item from the portal example if a bowl is ordered and mac and cheese is available as an add on at an additional cost, the mac and cheese arrives separately from the bowl and will require this tag to generate its own label choicetypetags should also be applied to any drinks or desserts included as part of a package, as these will similarly generate a separate label utensils are not required for any menu items created or duplicated specifically for the meal program resources menu sync tagging instructions https //api ezcater io/menu sync menu tagging video https //ezcater wistia com/medias/8ehlcu9tng menu sync utensils setup https //api ezcater io/menu sync#free utensils specific metadata menu sync utensils video https //youtu be/vqemuk gwf4 meal program menu set up https //api ezcater io/meal program menu set up#meal program menu set up