Release Notes: November 17
Release Notes: November 17
Online Ordering
What's new?
Revel combo only categories - Revel restaurants that use Revel Weborders can now mark categories and category groups as combo only, so their items can only be ordered as part of a combo. Admins set this in the POS settings page or in Enterprise Configuration.
Food required with purchase at checkout - Items marked food required with purchase now need at least one other item in the same online order that isn't alcohol or tobacco. Marketplace orders follow the marketplace's own rules.
Alcohol and tobacco labels on items - Items now keep their category's alcohol and tobacco labels when the menu syncs and when you save an item. Labels you set on an item yourself are left alone. This is rolling out gradually..
What we've fixed
We've resolved the following issues in this release:
Food required checkbox didn't save - Fixed an issue where ticking food required with purchase in the classic menu item editor didn't save. It now saves as expected.
Tracking IDs couldn't be cleared - Fixed an issue where clearing the Google Tag Manager ID, Meta Pixel ID or Segment key in merchant settings had no effect. Saving an empty field now removes the value.
Unsupported POS methods stayed in Marketplace Management - Fixed an issue where a markup or tax override method that the new POS doesn't support could still show after a POS change. These are now cleared so you can choose a valid one.
Duplicate Revel category names clashed - Fixed an issue where duplicate Revel category names collided in the OpenDining menu. Later duplicates now include the parent menu or group name.
Revel changes didn't appear in Enterprise Configuration - Fixed an issue where cached Revel option lists didn't refresh, so changes made in Revel didn't show. They now refresh after one hour.
NCR Aloha payments could be rejected - Fixed an issue where long decimal payment amounts could be rejected or mismatched. Amounts are now rounded to two decimal places for the standard NCR BSP integration. NCR BSP Stable is unchanged.
Split payments on Xenial Stable - Orders paid partly by gift card and partly by credit card now go to Xenial as separate payments, each with the correct payment type and tip. Single-payment orders are unchanged.
Release Notes: November 10
Release Notes: November 10
Online Ordering
What's new?
Marketplace handoff failure alerts: Access Evo can now alert you when a marketplace order fails to reach your store, with a plain-language reason and a link to act on it. Alerts are off until you turn them on in your Evo feed settings.
Count As for option levels: Enterprise menu managers can now set Count As values for option levels centrally in the EMM submenu editor. This needs the option level Count As feature turned on, and published Count As values take effect straight away, so check them first.
DoorDash refund reason filter: Restaurants can choose to refund guests automatically only when DoorDash or the Dasher caused the cancellation. This is rolling out gradually, is off by default, and requires operator action to turn on.
What we've fixed
We've resolved the following issues in this release:
DoorDash Drive Classic refund amounts: Fixed an issue where refunds could go to the restaurant instead of the guest, or refund a full order when DoorDash's reimbursement was $0.
Duplicate DoorDash refunds: Fixed an issue where a retried DoorDash refund could be processed twice.
Unclear DoorDash refunds: Fixed an issue where unclear refunds were retried repeatedly; they now go to manual review with the reason shown on the order page.
POS refunds of $0 or less: Fixed an issue where POS-initiated refunds of $0 or less could refund the full order for Speedline, Revel and DoorDash orders.
Refund error details: Fixed an issue where some refund error details could not be read on the order details page; they now appear as readable text for any POS.
DoorDash item availability dates: Fixed an issue where item dates used New York time, so single-day items stayed on sale an extra day or started a day early; dates now use each restaurant's local time.
Menu actions after Switch Store: Fixed an issue where using Switch Store could stop Sold Out, Delete, bulk changes, reordering, moving items and image uploads from working on the Menu page.
Release Notes: November 3
Release Notes: November 3
New Features Online Ordering
Refund orders from Access Evo. Access Evo agents can issue full, partial or tip refunds with the same rules as the Refund button in Order History, and each refund is protected against being sent twice. This is available through a gradual rollout.
Create and send coupons from Access Evo. Agents can create amount-off, percentage-off or free-delivery coupons, with options such as minimum order and date range, and can email a single-use apology coupon for an order. Duplicate coupon codes are rejected.
Feed settings and low order alerts. Feed Settings now sit under Profile, where each feed is a switch with a note on when it is sent. A new low order alerts feed tells subscribers when an open store takes far fewer orders than usual over the last few hours.
Unsuccessful orders reported separately. The Access Evo sales report now shows unsuccessful orders on their own, and top items count only successful orders.
Clearer failure details. Each failed order in Access Evo shows whether it was rejected, cancelled or failed for an unknown reason, who was responsible, and why, with failure counts by type and source. The customer_name field has been removed from this output.
Loyalty SMS verification. A new Require SMS Verification setting in Loyalty Settings asks guests to confirm their phone number with a code when they join loyalty. It is currently supported only in the Order Experience Builder, so operators must log in, select Update, then select Publish.
More order details in Access Evo. Orders now include the guest's phone number, submitted and due times, and payment details such as payment type, card brand and last four digits, with personal details redacted where required.
Updates & Fixes Online Ordering
Catering approval renamed to acknowledgement. Order History, order details and the Order Calendar now use Acknowledge, Acknowledged and Needs Acknowledgement, and a new Catering Acknowledged status message appears.
Access Evo ordering toggle. Fixed an issue where turning ordering on or off in Access Evo could be skipped if the store already seemed to be in that state, so it now matches the admin nav bar toggle.
Cross-sell mappings after category renames. Fixed an issue where renaming a category left its cross-sell (v2) manual mappings out of date.
Duplicate categories on base menu publish. Fixed an issue where refreshing a POS ID-based base menu could create duplicate categories for categories without a POS ID.
POS pricing for $0 items. Fixed an issue where NCR BSP items priced at $0.00 by the POS, such as buy-one-get-one promotions, failed with an "add item" error. The POS now keeps its own pricing. This is available through a gradual rollout.
Legacy Menu Review removed. The older Menu Review feature has been removed, including its admin screens and the version 1 API endpoints for menus, menu items and restaurants. Integrators should check that they do not call these endpoints.
