FieldStack Release Notes 6.14

Modified on Wed, 21 Apr, 2021 at 9:26 AM

Improvements

  • Improved duplicate prevention with PAX/TSYS integration.  Occasionally an error would be returned that we interpreted as a decline and a successful charge would actually be in the terminal we didn't know about.   We would charge the customer again and they'd end up with a duplicate charge.  We should now be able to see that charge when attempting to make the subsequent charge and use that initial approval.
  • BOPIS/Curbside completion bar code is now labeled and the text representation below the bar code now has the "*" at the beginning in and the end that are needed if a clerk needed to type the value into the Point of Sale.
  • Ability to specify Ordering Units at the Vendor level.  EA (Each) is the default if nothing is specified.  Other possible values are CS (Case), BX (Box), etc.  This value will be used on EDI Orders.  This is to be used in conjunction with Case Size, In Box Item Quantity and Is Box Type (If you want to order 1 CS and have that be a case of 24, change Ordering Unit to CS, Case Size to 24 and Is Box Type to True).   Printed and Emailed orders will continue to order the actual unit quantity.  If you want a printed or emailed order to utilize this functionality, please contact support and we can setup a customer vendor order template.

  • In the employee edit screen, the Employee Full Name can now be up to 40 characters from previous 20 character limit.
  • The Loyalty button for Buy X type loyalty programs on the point of sale now brings the full details of the customer's active loyalty programs.  Previously there was a summary type box that then allowed access to the full details.
  • When creating a new Buy X type loyalty program  you can now specify if the reward is average value or traditional buy X (free item)

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article