Lightspeed Retail

Hello summer, goodbye spring! As we welcome the warm summer, we hope you’ll also warm up to the new feature enhancement and bug fixes we’ve developed for you. Here’s to this summer being as endless as your summer sales!

Feature Enhancement

  • Average cost: Here at Lightspeed, we recognize that good data leads to good decisions. We also recognize that at the core of this good data, cost calculations play a vital role and a number of actions, such as merging items, can affect them. With that being said, we’ve made an enhancement that will make our merchants using the Average Cost cost method more confident in their reporting and inventory data than ever before. More specifically, when merging items with stock, your Retail account will now base its calculations of the new average cost on all of the merged items’ inventory lots and units costs.CLD-8782

Bug Fixes

  • Date picker: When using the date picker in any area in your account, the date range clears after you close and reopen it. This issue is now fixed.CLD-14481
  • Custom menu buttons: After completing a work order, custom menu buttons that add sale lines to the register don’t work as expected. This issue is now fixed. CLD-14211
  • Credit account statements: When printing a credit account statement, the header field does not scale to fit its text. This issue is now fixed. CLD-12222
  • Work order dates: When creating a work order from the register, selecting a date from the Date Due field clears the Date In field and prompts an Invalid time or date provided message. This issue is now fixed.CLD-13543

Lightspeed Retail with eCom

Down to the very last day of spring, we’ve made efforts to clear out issues that will make room for the omnichannel initiatives we have in store for you this summer. Here are our new bug fixes!

  • Importing brands in eCom: To ensure consistency between your Retail account and eCom store, you are now promoted to manage brands from your Retail account instead of the eCom import tool (click here for more information). CAM-4271
  • Adjustment payment types: When an eCom order requires an adjustment once pushed to Retail, a new Adjustment payment type is created rather than using the one that already exists. This issue is now fixed. EMID-1219