Serve changelog – Help Centre

3.23.0

Serve now supports allowing in-seat ordering for a session to begin before the previous session ends, improving the customer experience and order management.
Use the system setting NextSessionPreOrderAvailable to configure how many minutes before the end of a session pre-ordering for the next session opens. During this time, customers with existing checks in the current session will still be able to place orders, but no new checks can be opened for that session. Customers who have arrived for the next session will be able to open checks and place their in-seat orders. E.g. if set to 10, in-seat orders for next session are allowed 10 minutes before the current session ends.
Serve now displays a Hold icon on checks containing held items.
Update to version 3.23.0 or above of the Serve app and version 3.23.0 of the back-end application (Serve Service) to use these features.

Serve now supports tipping when paying. To use this feature, select the desired payment methods in the the AllowTipsOnPaymentMethods system setting. To use custom percentage values for tips in Serve, customise the TipValues system setting.
Additionally, Serve now allows the configuration of payment methods to be displayed after a split payment. To select which payment methods display after a split payment has been made, use the ShowPaymentMethodsAfterSplitPayment system setting.
Update to version 3.22.0 or above of the Serve app and version 3.22.1 of the back-end application (Serve Service) to use these features.

Serve now supports adding additional items to an existing check with Comps applied. To use this feature, upgrade the back-end application (Serve Service) to 3.21.1.
We've fixed an issue which meant users would still be able to earn loyalty points when "Earn Units when Redeeming Units" was unchecked for a Balance Type in Loyalty.

Serve now loads correctly if the decimal separator used in the Back Office system setting LowestCashUnit is different to the decimal separator in the server regional settings.

Serve now supports paying with loyalty points, streamlining the payment process for customers. To use this feature, set the AllowLoyaltyPointsPayment system setting to Yes.
Note: Update to version 3.20.0 or above of the Serve app to use this feature.

We've fixed an issue which could cause Vista.Service.UserLogging to fail to register user actions taken in Serve in Vista Cloud environments.

You can now use the same names for buttons in Serve that you've already set up in POS. To use this feature, set the UsePOSProfileButtons system setting to Yes. Note: This is set to No by default.
You can now choose to display the short name instead of the full name of recipe items in Serve. To enable this feature, update the system setting DisplayShortNamesInRecipe to Yes. Note: This value is set to No by default.
You can now customise the hold-time intervals for items, regardless of their item delivery group settings or your default hold time settings. This gives you more flexibility over how long items are held before delivery.
To use this feature, go to the new CustomHoldTimeOptions system setting and enter the values of your desired hold times in minutes, separated by vertical bars. For example, if you want to have hold times of 5, 10, 15, 30, 60, and 90 minutes, enter "5|10|15|30|60|90".
Leave the system setting blank to continue using default hold times.
Speed up service by skipping the Optional modifiers screen in Serve when there are no Required modifiers. To use this feature, set the SkipDisplayOptionalModGroup system setting to Yes. Note: The default value is No.
Update to version 3.19.0 of the Serve App to use this feature.
Serve now supports (VAPI) payment connectors that can store a credit card against a tab in the form of a pre-authorisation.

We now support tax-exclusive discounts and deals outside of the USA. Use the following system setting configurations:
- PriceModeConcessions set to TaxEXCLUSIVE.
- TaxRuleSystem set to any value other than USA.

Tabs are no longer prevented from closing by rounding errors caused by some payment connectors in Serve.

Serve now supports use of the LoyaltyMember service (version 5.1.13.2 or higher) for loyalty transaction data as long as the URL is correctly configured during installation of Serve.