Release note 11.1
Customize your filters
On the orders page on the backoffice, filters are now customisable by user. Feel free to add or remove any filter, you can also reorganise them. You will find them unchanged the next time you login as long as you use the same browser.
We also took the opportunity to introduce two new features:
You can now filter by postal code in the Order filter
You can make partial searches on the username, email, order number by pressing the enter button
Print order documents from the backoffice
You can now print a new document (that was not printed before) directly from the backoffice.
If a carrier returns an error when generating a shipping label, the error message is displayed so that the customer service can process it.
Once generated, a check-mark is displayed to differentiate it from the non-printed documents. And of course any document can also be re-printed in the Store App.
This feature works out of the box for standard documents (dispatch note and shipment) and can be configured to support custom documents.
Gain autonomy with DIY configuration screens
You now have control of some key configurations of your project: General, Delivery, Orders, Orchestration, Stock locations, Security, BI Suite, and more to come…
To ensure a good traceability, every configuration change is logged and can be retrieved in the history tab.
In order to facilitate migration, every configuration parameter can be exported and imported between environments.
Only available for Headquarters and Retail Director roles
Changing configuration may have big impacts, please test on the qualification environment before applying a change in production
Keep in synch with your support team, to make sure that none of your changes will be overwritten by operations done by the support
Better readability of orchestrations in the logs
We have added the name of the rules, which makes things more readable.
New orchestration filter: limit your sources based on the order price
We have noticed that the order price is a major criteria to determine the maximum number of sources to fulfil an order. In the case of a low-value order, it makes sense to allow only a low number of sources, and vice-versa.
That's why we have worked on the "average source price" filter. You just need to define the minimum value of items you want to carry on average in a parcel to maintain profitability.
Example: If an average source price of € 4 is set, a € 10 order will be fulfilled from a maximum of 2 sources.
Order in Store • Warning when there's not enough stock in store
Theoretical stock doesn't always match the reality. But it's a great starting point! That's why we have added a confirmation step when a store associate tries to make an immediate pick-up purchase of an item that is theoretically not in stock. In this case, the immediate pick-up button is displayed in white, to attract less attention, and when clicked, a pop-up asks for confirmation before adding product to the basket.
And much more…
Improvements
Reserve & Collect funnel:
Feature values in the product page are sorted A → Z. American sizes are sorted by XXS, XS, S, M, L, XL, XXL
Document's lifetime can be defined per document type
Security
Versions of embedded libraries have been upgraded to latest versions
Server softwares have been upgraded to latest versions
Fixes
Store App
Order in Store: The first day of the week wasn’t well displayed. It’s been fixed.
Order in Store: When working with the delivery promise, it was not being sent at order creation. It’s not the case anymore.
Order in Store: Some border case search scenarios presented issues. They have been fixed.
An expired milestone flag was displayed when an order didn’t contain milestone information, now no milestones are displayed.
Backoffice: Orchestration page
The ID that was entered on the screen during creation of a ruleset was not being used, now it is!
Rule name edition caused page to stop working. It's no longer the case.
Deletion of the last rule is no longer allowed, as it made the ruleset non-editable.
Backoffice: Stock location page
When the stock location timezone was different from the timezone of the opening hours' timetable, the opening hours were not displayed correctly. It’s not the case anymore.
Stock History
False movements were being logged by OneStock, which distorted movements' history. It’s not the case anymore.
BI : Standard Analytics
When stats were sent in parallel from the workflow for a same entity (two write stats actions triggered at the same time), sometimes one of the two could be lost. It’s not the case anymore.