Lightspeed eCom Changelogs
Page 17
eCom release notes have moved. Visit the Help Center for our latest updates.
bugfix
For business customers with different shipping and billing addresses, PostNL shipping labels only printed the billing address. This issue has been fixed.
feature
Try our new discount rule to give your customers a discount on the lowest priced product when they buy a set number of products from specific categories! Use this new rule to boost your sales during the holiday season! For more information, check out the Discount Rules topic in our Help Center.
bugfix
The order number was missing from the PostNL shipping labels. This issue has been fixed.
bugfix
When you link a product to a product set, you can remove or re-add its variants, as needed. However, the re-add mechanism didn't always work as expected, so we fixed this issue.
bugfix
PostNL shipping labels did not display the company name if the order's recipient was a company. This issue has been fixed.
bugfix
When importing customer data, the customer type changed to "Private". This issue has been fixed.
bugfix
When importing customer data, the import tool didn't update the "To the attention of" field for the billing and shipping addresses. This issue has been fixed.
bugfix
Printed shipping labels excluded the region or state from an address. This issue has been fixed and shipping labels display all necessary address information.
bugfix
Easypost didn't ship orders to the right address if the customers changed the address during checkout. This is fixed and Easypost now respects changes in address.
bugfix
The brands of products didn't appear neither in the quote creation nor in the final quote that could be sent to the customer. We fixed this now, so your quotes contain more information about your products!
bugfix
Users with the "Cost price" pemission could not edit in bulk the cost prices of products with multiple variants. This issue is fixed now and users can edit cost prices in bulk.
bugfix
When a user didn't have the "Settings" permission, he/she was unable to create a headline because the languages’ dropdown list didn’t show the available options. We have now fixed this issue.