Restaurant Management/ Menu Management/Reporting

7/2024

Restaurant Management

Features

• Multi-store Coupon -
  If a coupon was marked Multi Store Coupon, and that coupon had the same name as another Franchisee Group's coupon, any changes made to said coupon would affect both coupons. This issue has been resolved so that now when the coupon values of one subset of menu coupons is updated, the update will only apply to that one subset, not all stores.

Restaurant Management Menu Management

Features

• Single Store Menu Management - RMF Syncing Feature -
  This release introduces significant improvements to the syncing functionality between RM and the POS, aimed at enhancing reliability, performance, and user experience. Key Features and Enhancements:

  • Menu sync solution using RMF file where menu edits are pushed to the stores and imported to the POS

  • Addresses various issues causing sync failures and data discrepancies

Restaurant Management Reporting

Features

• Updated navigation for multiple RM NEW reports -
  Updated existing NEW reports that didn’t have the ability to side scroll via a mouse/touchscreen to improve navigability and align with brand standard of recently built reports.

• Began beta test of embedding grid style Sales by Order Type into POS -
  The goal is to have a single source of truth for reporting and align the UI of our reports between RM and the POS. To this end, we embedded the first of many reports into the POS from RM on 7/8 so that when a user on the POS requests the Sales by Order Type report, it comes from RM instead of the POS. This will enable us to keep our reports consistent between the POS and RM from a data and UI perspective, and reduce report development/maintenance time as we need to build/update 1 report in RM vs 1 for POS and 1 for RM. Next steps are to continue adding more reports to pipeline connecting RM and POS and then expanding to GA.

• Began deprecation of 22 Legacy (vNow) Reports -
  The goal is to begin deprecating already replicated, low usage, or broken legacy vNow reports to transition customers to NEW reports. The next steps are to continue building additional reports to deprecate legacy versions.

• Updated RM JSON for Marketing360 to include Order Number for Survey responses -
  In order to help Marketin360 customers more quickly identify orders based on positive/negative feedback within survey responses, we added the Order Number and OL Ref Number to our data connection.

Bug Fixes

• Showing unpaid breaks in Payroll Details Report -
  Previously, the Payroll Detail report showed an employee’s start and end time and calculating payroll based on time worked. Therefore, if an employee took an unpaid break, it was properly accounted for in the calculation, but wasn’t being shown in the report due to it being an unpaid. Example: Employee 1 started at 8am and worked till 5pm, but took an unpaid break from 12-1pm: The report would show 8am start time, 5pm end time, and 8 hours worked.The solution is now we unpaid breaks, so the report would show Employee A having 3 shifts: 8am-12pm for 4 paid hours, 12-1pm unpaid 1 hour, and 1pm-5pm for 4 paid hours.

6/2024

Restaurant Management Menu Management

Features

• RM Loyalty: Validating New Loyalty Solution -
  We completed a new loyalty UI that improves email template creation experience. Previously, we began rollouting out this solution but it was then abandoned due to staff changes. Now, we have completed full testing of the new UI and are confident is continuing the rollout of the feature.

• RM Menu: Brand Menu API Work -
  Work includes backend architecture and API work necessary to complete a proof-of-concept demonstration.

Bug Fixes

• RM Menu: RMF Import/Export - Allow orphan data in RMF -
  During the RMF data export, the exporter performs a basic data integrity check in certain tables for orphan records and skips them if found. This can result in some records that users expect to be included in the RMF being excluded without anyone knowing. We want to be able to instruct the exporter not to perform the check which should lead to hard failures that can be logged enabling the identification and mitigation of existing store data issues. Now RMF Menu Import/Export allows orphan records. Restaurant Management will block menu syncs and publish changes to POS if orphan records are detected. Data dog is tracking these errors.

• RM Menu: RMF import on POS does not remove a MenuPrfMbrXRef -
  The RMF file import to POS is not removing the record from MenuPrfMbrXRef. The result is the Preference Member would not be removed as a choice from the selected Preference. This issue has been resolved so the Preference Member is now removed from the MenuPrfMbrXRef table and allows a user to modify the list of Preference Members from a specific Preference without issue.

• RM Loyalty: Loyalty Email Job needs to use new FileShare -
  The Loyalty email job running in the Enterprise Scheduler needs to be updated to get the email artifacts (templates and images) from the new Azure File Share. We have updated file sharing within Loyalty Email Templates. The Loyalty Email Templates now use the new file sharing so we should not have issues with emails not including the correct images or missing the images completely. There is a timing event that ensures the images are synced across the servers within 15 minutes. This timing can be tightened, but most loyalty emails are sent 12 -24 hours after the loyalty event occurred.

• RM Coupons: Enhance Updating Multi-Store Coupons for Big Brands -
  There was an issue when trying to Update a single Coupon at one store to a Multi-Store Coupon when selecting additional stores in the Coupons configuration. The error that triggered was due to a SQL Timeout Issue. The way that Multi-Store Coupons are edited at a One-to-Many level needed to be enhanced. We have now enhanced the update of the one-to-many coupon logic. A user can now select a single store coupon, select additional stores and save. The coupon then becomes a multi-store coupon and appears in all stores that were selected. Also, when you view the store tab in Coupon properties the correct stores are checked regardless of which store profile is currently selected.

Restaurant Management Reporting

Features

• New Reporting GA Release -
  Launched with 18 reports and continuing to add additional reports to replace legacy reporting. Quicker, searchable, and more flexible than legacy reports to allow customers to more effectively manage their business. Usage: ~39% of reporting using new reports when available due to legacy scheduled Report Packages and user old habits.
  
  

5/2024

Restaurant Management 

Features

• TECH DEBT: Make File Share available to VMs for Loyalty Images and Templates -
  Determined best approach to make the file share rmcompanyfiles on Storage Account hrrmprodstorage01 available to our prod web servers:
  HUBWeb-L1
  HUBWeb-L2
  HUBWeb-W1
  HUBWeb-W2
  This allow changes to be made to our Loyalty applications to read/write files to this share instead of the hardcode \Honeycomb local folder. Modified all Loyalty file access (image and template) to use the newly created File Share.

• Updates Help link in RM to new URL -
  Update link behind Help to the new URL

Bug Fixes

• RCA for Broadcast Message Not Working -
  This feature was added in RM March last year originally for Hungry Howie’s. Currently this is not working in Production. When creating a temporary broadcast message schedule to show at the local POS, it is not showing the message at the POS level. One component that’s been observed is that it’s not inserting a data sync record to sync down the temporary and original System Message in SysConfig but we’re unsure if that’s the only thing causing this issue. Resolved sync issue and refresh for the temporary System Message to appear.

• RMF Export missing data during menu renaming operation causing the menu to not load in the POS -
  When renaming a Menu in RM and publishing the change, the POS menu would not load in the POS. An error would occur, and you would need to kill the HungerRush program. Resolved the missing information causing the error in the POS. A menu can now be renamed and published successfully.

Restaurant Menu Management

Features

• Menu item deletion functionality during RMF menu updates -
  When a Group, Item, Modifier, or Preference Member was begin deleted not all Menu Tables were being updated with the deletion. All Menu tables except for Menu86 will now update accurately based on the Groups, Items, Modifiers and Preference Members being deleted. An entire menu may also be deleted from within Restaurant Management.

Bug Fixes

• Cannot Edit Menu Sizes if Size Count = 7 -
  When a Store’s Menu has a group with the maximum number of sizes allowed(7), they cannot make any edits to the sizes in the group. Resolved issue by allowing edits when 7 sizes exist.

• Duplicate PLU Number Prompt is Looking at Published Changes Instead of Unpublished Changes -
  Romeo’s Corporate is running into an error when inserting two different MenuPLU Values in their Corporate Store (This is affecting all stores). Root cause was discovered and determined that this error prompts whenever the PLU value shows as Published = 1 in the Publish Change Log table. Resolved bug.

Restaurant Management Reporting

Features

• Launched New Order Details Report -
  Gives the ability to generate >1 day of data in new report, is searchable grid vs static PDF, contains trending view for orders to introduce visuals into new Reporting, and adds Credit Card and Gift Card payment details.

• Add Customer Name to Adjustments vNext Report -
  Added Customer Names to Adjustment report to enhance the ability to find adjustments by customers and track these adjustments.

• vNext Payroll Details Hours Display Format -
  Added additional fields to Payroll Detail report in order to better assist payroll processing by customers.

• Delivery Out The Door Time Grid View and align dropdown UI -
  Launched grid version of Delivery Out the Door Time report.

Bug Fixes

• Move Delivery in vNext menu after Inventory and above Driver Delivery Details -
  Fixed order of report navigation panel to put similar reports together.

• Reporting Vnext - Sales and Royalties - Error with the decimals loaded for the excel and the csv for the report in explorer mode -
  Corrected Sales and Royalties export to only generate $ figures with 2 decimals.

• Reporting VNext > Delivery Driver Details > PDF - Space out columns so that "Total" numbers don't look cramped -
  Text wrapping issue in Driver Delivery Details report.

• vNext Payroll Detail Showing Employee Key, not Employee ID that is in vNow Payroll Detail -
  Replaced Employee Key with Employee Number in Payroll reports.

• vNext Sales by Category Report not Matching vNow, POS, and vNext DPR -
  Sales information was not being fully captured due to changes to their Order Type descriptions.

• Missing PLUs vNext Menu Mix Reports -
  Missing PLUs Menu Mix report has been resolved.

• Weekly OT when Daily OT is active should only consider Regular Hours worked when calculating Weekly OT -
  Fixed OT calculation for employees.

4/2024

Restaurant Menu Management 

Features

• Added RMF file Export and Import to facilitate Single Store Menu Update-
  Historically there have been issues with syncing menu changes from RM to POS for various reasons. We elected to use a function that has been available in the POS for many years called Menu Import/Export. This function allows a Menu to be exported from one store and imported to another, though the process was manual. We elected to solve the menu sync issues by moving to the RMF file model, which would export the menu from RM and import the menu into the POS. Upon Publishing Menu Changes from RM, a Menu Export file is created which includes all menu properties. The menu file is communicated to the POS via RM POS Agent which handles importing the menu file into the POS database. We have added a Status which will show the user when the update is Successful at the store. The users at the store will still need to exit the POS program and reload to see the new menu edits.

Bug Fixes

• Menu Group Button Color defined in RM is not displaying the correct color in POS-
  The Menu Group Button color updated in RM was not presenting the correct color in the POS. Updated RM to send the accurate color code to the POS.

• RM Single Menu Management: Missing Configuration ability to alphabetize the Modifiers within the Menu Preview screen-
  The POS offers a feature to Alphabetize the Modifiers within the Menu Group Configuration. This same feature will need to be added to the Menu Preview page within RM. A client may want their Modifiers in Alphabetical order, it that is the case, when they added a New Modifier, instead of having to reposition buttons to put the New Modifier in Alphabetical Order the user can just add the New Modifier and then select the Alphabetize button to reorder all of the Modifiers. Added the alphabetize option to RM Menu Preview.

• RM Single Menu Management: Missing configuration Modifier Category Warning Message by Group-
  The POS has an additional configuration for Modifier Category Warning Message for Online Purposes. When setting up a Modifier Categories you can enter a Warning Message to prompt the user what they need to select: Please select your cheese choice, Select your dipping sauce, etc. Sometimes Modifiers Categories are used across multiple Menu Groups, but the Warning message needs to be different based on the Group. Example: Using Cheese Modifier Category for Pizza and Sandwiches. Pizza's Cheese Modifier Category may say "Make it extra cheesy" and Sandwiches Cheese Modifier Category might say" Please select a cheese". This configuration needs to be added to RM in Menu Editor by Menu Group. Added the configuration to RM. Select the Group to Edit > select Online Ordering > select Online Options. Then select the Modifier Category and enter the Warning Message desired for Online.

Restaurant Management Reporting

Features

• VNext: Add Item/Size option to the Menu Mix Report based on feedback-
  The goal is to continue adding top used reporting into vNext environment to transition off legacy reporting PDFs.

• Reduced HUB Dashboard Load Times by half-

• vNext: Built a grid view of Sales by Order Type & Channel and added ability to export to Excel and CSV-
  The goal is to continue adding top used reporting into vNext environment to transition off legacy reporting PDFs.

• vNext: Ability to Filter Employees within the Payroll Detail Report-
  The goal is to add functionality on top report to increase usage.

• vNext: Added Sales By Category report grid view, along with the ability to export to Excel/CSV-
  The goal is to continue adding top used reporting into vNext environment to transition off legacy reporting PDFs.

• vNext: Added Per Person Average (PPA) to Sales By Order Type and Channel reports to achieve parity between vNext and vNow reports-
  The goal is to add needed granularity to existing reports to reduce dependency on legacy PDF reports.

• vNext: Moved Delivery within vNext Navigation panel so that Delivery, Driver Delivery Details, and Driver Mileage & Compensation are grouped together-
  The goal is to ensure logical ordering of navigation panel for ease of use.

Bug Fixes

• Export for DPR is failing-
  This is related to Labor Types lining up across across stores that may have different labor types.

• vNext: HH - Payroll Details Report: Grand Total values are missing on RM-
  Added Grand Totals to Payroll Details Report.

• Sales and Sales By are both appearing in v-Next Navigation-
  Removed Sales By from vNext Navigation as both Sales and Sales By were populating

• vNext Payroll - Validate that sales column is being correctly calculated an has the same results as POS reports-
  Fixed Payroll report not matching POS report.

• VNext: Update Driver Delivery Details Report with abbreviated headers for the PDF view to allow more room for the Total column-
  Abbreviated headers within Driver Delivery Details report to prevent totals from wrapping within the grid.

• Vnext: Sales and Royalties - Error with the decimals loaded for the excel and the csv for the report in explorer mode we showed 2 decimals but in excel and csv appears 4-
  Fixed Sales and Royalties Excel/CSV exports to only generate amounts with 2 decimal places instead of 4.

• VNext: Delivery Driver Details > PDF - Space out columns so that "Total" numbers don't look cramped-
  Fixed Sales and Royalties Excel/CSV exports to only generate amounts with 2 decimal places instead of 4.
  
  

3/2024

Restaurant Menu Management 

Bug Fixes

• Resort Modifiers configuration missing from RM-
  Restaurant Management is was a Menu Configuration setting Resort Modifiers. This feature makes the Modifiers resort and remove empty spaces, when a Menu Item excludes Modifiers from being available. This configuration has been added.

• Add "None" as a Kitchen Print Category and Report Group Option for Items and Modifiers-
  Currently there is no way to manually select "None" as an option for Items and Modifiers in Kitchen Print Category and Report Groups. If the user does not want to have a report group or kitchen print category specified anymore, their only option is to delete the item and recreate it. This configuration as been added.

• Missing Menu Configuration: Require Approval for Open Price Items-
  Restaurant Management is missing a Menu configuration that is available within the POS Menu Editor. Require Approval for Open Price Items. This configuration is under the Menu configuration tab. The missing configuration has been added.

• Excluded and Preselected settings not saving correctly or publishing accurately-
  The Exclude & Preselected modifier settings were not saving or publishing correctly. Resolved the bug to ensure the settings were being saved and published correctly. There is one remaining bug related to No Subst/Display PreSelect in Kitchen. Opened another ticket.

  • Menu rename cannot be saved if the previous menu name was not published and you are renaming the menu back to the original name-
    This issue created a bad user experience. If a user renames a menu and then realizes they made a mistake and wants to switch the Menu Name back to the original name, the Save button would not be active. Resolved the bug to allow any update to the Menu Name would activate the Save button.

  • Editing then Deleting a Group Before the Edit is Published Produces a Publish Error-
    Whenever an end user makes an edit to a menu group and then deletes the group before the edit is published, it causes a publishing error that would block any publish action. Eliminated the error that was occurring.

  • Making Group Descriptions on New Menu Group Before it's Published Causes Bad Data When Published-
    Whenever an end user makes a new menu group and creates a group description before publishing the new menu group, duplicate data gets produced in the MenuSuggXRef table causing errors when accessing any of the menu modules when that group is selected. Corrected the action from creating bad data. If a user performs the same actions as described above, the Menu Group can successfully be accessed and edited.

  • The number of groups to display in menu configuration page does not match with the group count in the menu preview page-
    There are three Menu Group configurations that change the number of groups displayed on each page in the POS. The POS configurations is default 10 groups per page, or you can select the option Large Group Buttons (displays 5 groups per page), or Small Group Buttons (displays 16 groups per page). The RM config shows these options in the Number of Menu Groups drop down selection. Restaurant Management Menu Preview now displays the correct preview of Menu Groups based on the Number of Groups configuration in Menu properties.

  • Do not allow Save and Another when 7 Sizes exist-
    When a user is creating multiple sizes for a Menu Group and is using the Save & Add Another button, the UI was not recognizing the user had exceeded the number of allowed sizes which is 7. Disabled Save button when the 8th size is attempting to be created.

  • UI RegEx Validation failing for Online Name while updating Modifier-
    UI Validation is failing for and existing OnlineName such as Pepperoni 60-80 cal. Update UI to handle numbers and dashes in an existing OnlineName.

  • Upon Initial Coupon Creation the Tax Type would appear to default to 'None', but then it would save with the first Tax Type listed in the Tax drop down list-
    Potential incorrect Tax Type would be defined on a coupon. Corrected the UI behavior

  • Item Time Pricing does not maintain the change in the UI if change is not published-
    The user may change various Time Pricing fields, then proceed to another area of the Menu Editor. If the user returns to the Tiem Pricing area to validate their work prior to publishing the edit values were not saved in the UI. Though if the user still Published the changes, they would in fact be published to the POS and would be correct in the UI after publishing. Fixed the bug to ensure the UI maintained the Time Pricing changes in memory before publishing.

  • No Subst / Display PreSelect in Kitchen is published as an Excluded Modifier-
    Problem: When the user selected No Subst/Display in Kitchen the Modifier would be Saved as Excluded and that was how it was sent to the POS Menu. Fixed the bug to ensure the correct setting was saved and updated the POS Menu correctly.

  • Missing "Begin 2nd Tier" option for Preferences-
    Restaurant Management Menu Management was missing the Begin Second Tier option in Preferences. Added this missing option.

  • Rename 'Attributes' tabs-
    Some team members felt Attributes was not understood by our end users. Updated or Attributes tab to Items Summary, Modifiers Summary, etc.

  • Missing Require Multiple Items configurations-
    Require Multiple Items feature was missing 2 configurations which made it impossible to configure this feature in Restaurant Management. Added the Multiple Item Count and whether the Multiple Items requirement needed to validate by size.