Meal Program with Olo Integration FAQ

what is the meal program? formally known as relish! our product received a brand new name! the ezcater meal program is a corporate subsidy program that enables employees to place individual meal orders that are delivered together these orders include items that are served on an individual basis, rather than larger catering items that may have a larger serving size what makes a meal program order different from a marketplace order? fast cutoff order cutoff is approximately 90 minutes prior to fulfillment, creating significantly shorter lead times than typical catering lead times recurring & sizing orders are often recurring and scheduled, with a maximum of 30 individually packaged and labeled meals fulfillment individual packaging and labeling creates unique needs, so all fulfillment should continue to be completed through the ezcater partner portal the ezcater partner portal remains the source of truth for reporting and review of ezcater orders as a whole how does this impact the olo rails integration implementation? this will impact any new brand that is integrating through the olo menu api or converting from orders to menu api if there is even one location participating in the meal program for the brand, these steps are required currently, there is no method to uncouple the standard marketplace menu from the meal program menus in ezcater, hence the need for tagging in olo if menu tagging is not complete for the meal program items, there will be no available meal program menu for the location the import process will create a blank meal program menu, as the import pulls what is configured inside of the olo menu admin best practices and considerations meal program orders are also subject to the $0 40 per order fees associated with successfully integrated orders a separate olo menu category will be needed for the meal program specifically, which includes any item that is offered on their meal program menu this may be different from standard marketplace catering items, and may not currently exist in the olo catering channel lead times for meal program categories should be set to 60 minutes in olo to avoid any order failures meal program menu setup and considerations tagging must be completed on the meal program category just as done for marketplace additional tags are necessary to ensure this category flows to the meal program menu and not the marketplace menu considerations the menu sync resource outlines that a brand could technically use the same catering item for both catering marketplace and meal program with special tagging however, this set up will force order failures due to the lead time discrepancy and is not best practice standardization internal brand alignment may be required, as the meal program menu setup may differ with franchisee involvement and prior setup menu tagging requirements required tags quantityunit cateringservesize (must always be "1") taxcategory “relishchannel” = “t” if the rp has individually packaged sides, they should also have key individually packaged relish side and the value t where applicable, foodlabelingtags, itemtypetags, and choicetypetags will still be required and reviewed during a menu consultation utensils are only required if the items are shared between the marketplace and meal program testing at this time, while ezcater can validate and provide menu requirement consults for the menu build, there is no testing environment for the meal program, as this will be independent of the standard pos testing environment for any questions on the process, please reach out to the ezcater integrations team at integrations\@ezcater com