7.10.0.0, October 2020
- josefin.kvillert (Unlicensed)
- Robin Brändén
- pontus Carme (Unlicensed)
- johanna.fallstrom (Unlicensed)
Below you will find information regarding what the release included for October, 2020. Release: 7.10.0.0
Hightlights
Extend Commerce Backend
Multi-warehouse: framework & priority
New feature | Order management | Requires support to active: NO |
---|
With this release, we welcome an addition to our regulations to support automatic prioritization of warehouse when supplying orders. Last year, we made it possible for an order to be supplied by several warehouses. Parts of an order can be sent to multiple warehouses to be picked and sent to the customer. This works for both create order manual in Extend Commerce Backend and via API / EDI.
When an order enters Extend Commerce Backend via API / EDI, you previously needed to specify which warehouse would supply which product/order line. With our new priority, you do not need to specify which warehouse will supply which product/order line. You can leave the warehouse field blank.
When creating an order manually in Extend Commerce Backend, you need to specify from which warehouse which product should be picked from.
Framework
The regulations first check the stock coverage and postcode for delivery to determine which warehouse can supply the order. This has not changed. However, if there are several warehouses that can supply the order, and no warehouse is specified, Extend Commerce Backend will now also look at a priority where the specified priority determines which warehouse may primarily supply the product/order line. If we have three warehouses and all warehouses can supply the order, the prioritization will determine which warehouse the system goes through first. If all products are in this warehouse, the entire order will be sent to this warehouse for picking. If there are products that are not connected to this warehouse, the system will go ahead and check if these products are connected to warehouse with priority two, and so on, until all products/order lines are supplied by a warehouse.
The priority is completely optional to use. If the priority is not used, you should, as before, specify which warehouse is to supply which products/order lines. If you do not specify layers and priority is not used, the system will select
If the priority is used, it is recommended that all warehouses have a priority. If the priority is used and a warehouse does not have a specified priority, this warehouse will be prioritized last to supply orders.
Below picture describes the regulations.
Select priority on warehouse
You set the priority of warehouse by going to the Warehouse menu and selecting warehouse.
Here you can see, if you have specified a priority, which priority all layers have.
To set a priority on the warehouse, click on the pen and select desired priority of the warehouse in the dropbox and click on 'Save'.
Please observe:
- Multi-warehouse requires activation. Per default a system has single-warehouse activated: one order can be supplied by one warehouse.
- The priority function works differently depending on if you use multi-warehouse or single-warehouse. Please read more in out manual: Multi-warehouse (select language at the top of the page to translate)
- Multiple warehouses cannot share priority. One priority per warehouse.
Do not hesitate to contact our Support for more guidance or information regarding this feature.
Upload pages get new design and functionality
New feature | Masterdata | Requires support to active: NO |
---|
It is now possible to upload product properties via our new upload function in Extend Commerce Backend. You find these in the Masterdata menu under Uploads (new version).
For upload of product properties the template is static and therefore needs no modification. Simple press "Export template" and add data to the file.
On new upload pages where a template exist for the Excel export, you can now define this directly on the page. You no longer need (for new upload pages) define in Visibility settings how the template should look like. By clicking on "Define template" you can simply decide which columns/fields to include in the template, save and then click on the button "Export template". Thereafter your Excel file will be downloaded and you can fill it in, save it and upload it by clicking "Upload". Here you can select the file from directory or drag and drop.
The file you upload does not have to match what is defined under "Define template", as previously required in Visibility settings. This means that you can create your own template or use an old one that does not necessarily match the template defined in the system. The system can process different excel files with different amounts of columns etc., as long as the columns' names are the same as defined in the system. The system will otherwise not know which field you are referring to in your file.
Mandatory fields are required to be included.
Upload product properties
For this upload you do not need to define a template, simply export directly, add data and upload your file.
Batch / serial number
New feature | Order management | Requires support to active: NO |
---|
On the Order preview page, which you enter when clicking on the order number in the order list, we hve added a new tab "Batch / Serial number". Here it can be viewed if the products which have been picked at the warehouse has a registered batch number, serial number or an expiration date.
Batch / Serial number Order preview
Visibility settings: functions move
Improvement | Masterdata | Requires support to active: NO |
---|
With our new uploads, we have gradually moved the function under Visability settings to the upload pages where you can define per page what your Excel file should contain.
Other functions on this page are now moved to their own pages. This refers to:
Show or hide fields for products on the product page
Enter expected values for the master data status function for products, customers and supplier agreements.
All of these functions are moved to their respective pages in the Basic Data menu.
Products
Under 'Product' you will find the pages Product field and Expected values for products.
Product fields
Under 'Product fields', you specify at system level which fields are to be displayed and hidden on the product page. If you choose to hide a field here, it is hidden from all users. The function should be used in such a way that at system level you decide which fields are to be used and displayed in your particular system. If there are fields that you never use and that should not be filled in, you can therefore choose to hide these here to get a more compressed product page with only relevant fields for you.
Product field affects what the product page looks like:
Expected values for products
Under 'Expected values' you specify which fields and connections are expected when a product is created. If you use the function, the system will change the Master Data status to "Complete" (green) on the product if it meets these requirements. You can then adjust from the product page on the product that is not approved by clicking on "Show basic data status overview". The fields that are expected are also marked as blue when creating the product to make it easier for the user to see which fields are expected to be filled in.
Expected values affects master data status and expected values for products:
If the field is mandatory for the system and is an expected value, the field will appear red when mandatory fields over bid expected fields.
Customer
Under 'Customer' you will find the page Expected values for customers. These work in the same way as products, but are expected values and connections when creating customers. If all expected values are filled in for customers, the master data status will show "Complete" (green). As with products, you can adjust unapproved customers on the customer page.
Suppliers
Under 'Supplier', you will find the page Expected values for supplier agreements under 'Basic data settings'. The master data status function works and be adjusted in the same way as with products and customers, but can be adjusted on the Supplier Agreement page.
See which customers have admin users in the webshop
Improvement | Customer | Requires support to active: NO |
---|
We have added the opportunity to search by customer category on all pages where you can use customer search. This enables you to get a list of customers who have a user in your Extend Commerce Webshop either as a "member" or "store admin". This will make it easier to identify customers who have a admin user in your webshop so that they can be more easily administered.
Customer search
If you want a list including inactive customers, deselect the pre-selected active customer status filter.
Upload customer users
Extend Commerce WMS
Adjustment of the product name
Improvement | Extend Commerce WMS | Requires support to active: NO |
---|
Previously there was a limit to 35 characters in product names communicated to the Extend Commerce WMS system. This limitation has now been removed, and system is now passing the entire product name and the full name is now visible in Extend Commerce WMS.
Adjustment of the user interface for order picking
Improvement | Extend Commerce WMS | Requires support to active: NO |
---|
To increase the picking accuracy we have changed the user interface for picking an order in the system.
We have increased the font size of the number of products to pick.
Consolidate logistical unit when moving to the same position
New feature | Extend Commerce WMS | Requires support to active: NO |
---|
We have implemented an option to merge balance when performing a warehouse transfer. This requires an
Previously Extend Commerce WMS have strictly followed the FIFO principle where each transfer of products have had its own identity. For products not handled by expiry dates or batch number, it is now possible to merge the balances when moving the products from on location to another.
Serial number registration
New feature | Extend Commerce WMS | Requires support to active: NO |
---|
We have implemented a new product handling for serial number registration. Previously we have had that the serial number is registered when receiving the product. When using the new product handling method we will instead register the serial number during the picking process. This will be the new standard for registering serial numbers.
Backend
For registering the serial number during picking, the product is required to have this selected product handling in Extend Commerce Backend:
API / Integrations
New webhooks for when invoices are created or changed
New feature | Webhook | Requires support to active: NO |
---|
You can now set up the webhooks CustomerInvoiceCreated and CustomerInvoiceChanged to message you when invoices have been created or changed.
Ongoing: External order number can be sent as consignee order number
Improvement | Ongoing integration | Requires support to active: NO |
---|
The Ongoing integration now supports that Extend Commerce Backendäs "External order number" can be sent as "Consignee order number" to Ongoing. This requires an activation per integration.
If you want this activated for your Ongoing integration, please contact Customer support and they will assist you.
On this page: |
---|
Other releases: |
Filter by labelThere are no items with the selected labels at this time. |