Features and Improvements - NorthStar 4.7g release

Software release date: TBD
Release: 4.7g

This document summarizes the major new features and improvements in the NorthStar 4.7g release and serves as a quick reference to these new items. For more complete information, please refer to the ticket number shown.*

Issue No.	Summary	Configuration	Operation
Payment Processing
OE-12930	Payment: Heartland MPPG Integration Heartland via MPPG added as a credit card processor option for payment using swipe method Exception: General refund not supported	Path: Sites > Payment > Add Processor Select Magensa Credit card processor Select Heartland as Processor Name	Tap Credit Card Swipe card on payment device
Staff UI Improvements
OE-14325 OE-14329	Guest-Facing: Add setting to configure guest identifier prompt in kiosk mode Setting added to Guest-facing tab allowing site admin to specify the guest identifier prompt in kiosk mode.	Path: Sites > Guest-Facing New setting: Kiosk prompt Site admin can enter and save text to be used	Text appears in Guest Facing mode as configured
Tax Calculation Change
OE-6258	Tax Calculation: Round the total tax at check level, not item level This improves the method used to calculate tax. Previously, tax was calculated per item and rounded at the item level. With this change, all items are summed first, then tax is calculated and rounded as needed.	N/A	New tax calculation formula applies tax to the sum of the items and then rounds the total: Round(Sum(TaxableItemPrice * Quantity + (TaxableItemPrice * Quantity * TaxRate))),2) Before this change, tax was calculated and rounded by item: After the change, tax is calculated after summing the items and then rounded:
Time Clock
OE-7373	Time Clock: Overtime Rules capability added using configurable thresholds and multipliers	Account feature toggle required ** Expand time clock overtime rules Path: Sites > Sites and Groups > Edit Site > Time Clock > General tab When feature toggle is enabled, settings for overtime rules are shown, allowing sites to configure in accordance with local labor rules Hours - maximum working hours to meet before rule is applied Multiplier - multiplier for overtime hours Example: If Daily Overtime is triggered at 8 hours, the additional time is paid per the multiplier; in the example, it would be paid at 1.5x the regular pay The second Daily Overtime segment is triggered at 12 hours and is paid at 2x the regular pay	Per the configured rules, any overtime and doubletime worked is shown on the Time Records report Regular wages, overtimes wages and doubletime wages are also reflected on the report
Web Ordering API
OE-14340	Check Finalization: If check has items not yet sent to kitchen, provide capability to send items and finalize check in one action When an order is placed and paid for in advance (e.g., online order, advance order, counter service), this improvement revises the workflow to allow the order items to be sent to the kitchen and the check to be finalized in one action. In this workflow, when the check has no balance due and the check has unsent order items, the Finalize button changes to Send and Finalize. When tapped, the order items are sent to the kitchen and the check is finalized. OE-14359 - Change button text to "Send and Finalize" for paid check with unsent items - OE-14357 - Add support to finalize to send unsent order items to kitchen	N/A	Order items in advance (items are not yet sent to kitchen as indicated by red bar) Apply payment (there is no balance due remaining) To send order items to kitchen and finalize check, tap Send and Finalize
OE-14219	Web Ordering API: Add setting allowing online orders to be placed regardless of item availability in POS A new setting has been added to allow menu items to be ordered online when the menu items have been marked as not available in the POS.	Path: Sites > Integrations > Web Ordering API New setting: Allow orders to be placed regardless of item availability	Item is marked as not available via Menu Manager in the POS The Ordering menu will show the item as not available to be ordered (item is disabled) Despite the item being unavailable, it can be ordered through web ordering. Check Search shows an online order with the unavailable menu item ordered:
Uncategorized
OE-14231	Payment: Prevent duplicate payment by locking check during payment process after iPad has been restarted When payment has been started, the check is locked to prevent duplicate payment. This improvement expands that functionality, In the event that the iPad is restarted for any reason (such as device timeout). duplicate payment is prevented by masking the payment screen.	N/A	Order items, tap Payment and pay with credit card Allow device to time out Log in and return to same location (table) Tap Payment Mask will prevent duplicate payment
OE-13515	House cashout: Show checks from web API order that have not been cashed out prior to performing house cashout In the Job workflow, sites have the option to allow house cashouts to be completed with pending cashouts remaining. When this option is not active, all checks must be cashed out prior to performing an entire house cashout. In this improvement, checks created through online ordering that have not been cashed out will now show the check number when a house cashout is attempted, allowing the site to cash out the online check, then perform the house cashout OE-14084 - APP - Display the Check Number from the Server Response in CashoutEntireHouseResult	Path: Users > Jobs > Workflow Setting: Allow entire house cashout with pending cashout remaining When setting is not active, all checks must be cashed out prior to performing a house cashout.	Pre-conditions: Specified job setting is not active A check created via web API order has not been cashed out When user attempts to perform a house cashout, the check number will indicate any checks that have not been cashed out User can locate check, finalize it (taking ownership of the check) and then perform a user cashout House cashout can then be performed
OE-13860	Payment: Control tip prompt on PAX external device Issue: Previously, a tip could be added on the POS AND also added on the PAX device, which would prompt for a tip, resulting in double tipping. Improvement: This improvement allows the site to specify if the PAX device can prompt for a tip. This is defined by area to allow the restaurant greater control over this functionality. For example, the restaurant may want the PAX device to prompt for tip in a guest-facing area (e.g., kiosk) or a bar area but not in the dining area where the server inputs payment information in the PAX device.	The site must be set to allow tipping and one or more areas must be configured to prompt for a tip on the PAX device. SITE SETTING Path: Site > Payment Setting: Tipping enabled = Yes AREA SETTING Path: Site > Areas > select area > General Setting: Prompt for tip on external device Default: Selected	Create and send order, tap Payment Tap NFC icon on Payment screen PAX device will prompt for tip Depending on the PAX device setup, the device will either prompt with suggested gratuities that the user can tap (first screenshot below) or ask the user to enter a tip amount (2nd screenshot below) Tip added on both the POS device and the PAX device: the tip entered on the PAX device is added to the transaction Tip is added on POS device only (not on PAX device): the POS tip is added to the transaction If either Tipping enabled = No and/or Prompt tip on external device is not selected, the PAX device will only prompt for payment and will not prompt for tip Alternate workflows: Add tip: If user does not add tip when first prompted on PAX device, tap Add New Tip on the payment screen, then tap NFC icon again to add the tip Adjust tip: If user wants to adjust the tip that was entered, tap the icon to prompt the Adjust Tip window, then tap NFC icon again to revise the tip
OE-13563	Check Audit Log report: Add Location and Device columns; audit combo, credit card and web ordering API transactions Enhancements to the Check Audit Log report include adding columns to capture Location and Device information and track transactional data for combo menu items, credit card sales and refunds and web ordering API transactions	N/A	Path: Reports > Check Audit Log Columns added: Device - The device the order was taken on Location - The location name Track additional information: Combo added to check Combo first Combo last Gift cards Gift card sale Refund of gift card sale Web ordering information Check created Check submitted Order sent to kitchen
OE-12880	Kitchen Chit Order Type: After an order is moved to a new table, the kitchen chit will display the default order type of the location the items are sent from (the new location, not the original location) The kitchen chit will display the default Order Type of the location the items are sent from. Example: Order is started at a Takeout order type location. Check is moved to a Dine-in order type location with unsent items. When items are sent to the kitchen, the kitchen chit will show "Dine-In" as the order type.		Example: Order started at Takeout location Move to Dine-In location Menu item sent to kitchen Result: Kitchen chit shows "DineIn"