Below you will find information regarding what the release included for April, 2021. Release: 8.4.0.0

Reminder invoices can now be sent by email

You can now send reminder invoices via email by pressing "Send reminder 1" or "Send reminder 2". If you instead want to create a PDF for manual distribution, use the old function "Create reminder 1" or "Create reminder 2". The PDF can now be found after creation in the invoice preview. Press the PDF icon to export. 

Order updates

Sometime you cannot deliver orders when you said you could deliver. This can be due to a number of reasons, for example if a receiving purchase order gets delayed, or a prioritized order booked up the balance previously allocated to another order etc. When this happens the system perform a so called order recalculation where the system recalculates the delivery dates on all affected orders and then set a new date for when the orders can be expected to be delivered.

These order updates, where orders can a new delivery date, can now be sent out either to the customer as a order confirmation update, or internally as a summary list of all affected orders which have gotten a new date. You can also select to send out no email at all.

These three settings exist:

• Send to customers per individual order
• Send internally as a summary of all affected orders
• Send no updates

These settings can be set on client level, customer level and order level - in this hierarchical level. If no setting is found on order level, the system will check the customer setting. If there's no customer setting, the system will select the client level setting for the order.

Client level setting is selected when activated the function. For now, the function is activated by Customer Support, however, in the future this will be made available for system role users to set up themselves.

On customer level you select the setting under the menu Logistic settings

On order level, we select the setting when we create the order, either via API or manually when booking orders in Backend.

Chat function moved

The chat icon has at occasions been in the way when performing functions in the system. Therefore we have moved the chat icon to the top right corner in the header. With this change we have also added icons and changed names in the header to highlight the functions users have available here.

To chat with Customer support, click on the chat icon in the header and the chat function will appear in the lower right corner as usual. 

In the header you will also find the manual, previously named "Help". If you press "Manual" you will be sent to the corresponding page in the manual.

You will also find notifications here which Customer Support use to inform users in the application.

Reset table to standard

On new pages in the system you can find a cogwheel where you as a user can add or remove columns in the table, as well as rearrange their order. On this pop up, we have added an option to reset the table to standard.

If you press "Reset", the table will go back to its default settings, as appeared before user specific adjustments were made.

Password validation when creating customer users

When customer users are created in  Extend Commerce Backend, there will now be requirements that the password for these users have a certain complexity. Below demands are required for passwords for users using the  Extend Commerce Webshop.

Each password needs to contain characters from at least three of the following categories:

• Uppercase letters of European languages (A through Ö)
• Lowercase letters of European languages (a through ö)
• Base 10 digits (0 through 9)
• Non-alphanumeric characters (special characters): (~!@#$%^&*_-+=`|\(){}[]:;"'<>,.?/)

Password must be at least 8 characters long

Password must not be same as username

We have added an info-icon when you can see the requirements when creating passwords.

Incoterms are now sent to  Extend Commerce WMS

Incoterms on orders are now communicated from  Extend Commerce Backend to  Extend Commerce WMS. 

Incoterms are standardized terms of transport compiled by International Chamber of Commerce (ICC) which define how costs and responsibility are divided between buyer and seller. When incoterms are sent with orders to the WMS from Backend these then declare who will pay for and who is responsible for the transport. The cost for booking transport will be invoiced by the transportation company either to you as the seller or to your buyer depending on your choice of incoterms.

With this change it is therefore important that the Incoterms on orders in Backend are correct if you are using  Extend Commerce WMS with your  Extend Commerce Backend.

In practice, the change can be viewed in  Extend Commerce WMS when booking transport for orders. Here fields "Shipping payer", "Terms" as well as "Sen. account" and "Rec. account" are of importance here.

Example of the difference as follows:

This information will be sent to the carrier if incoterms EXW is used:

EXW: Payer pays freight with account 123456

This information will be sent to the carrier if incoterms FCA is used:

FCA: We as the sender pay freight with account 654321.

Expiry date can now be scanned when receiving goods

When receiving goods at the warehouse, you can now scan the expiry date. Previously the user had to manually add the date. Now both options are available.

Additional debit can now be added as half of a unit

During picking you can now add additional debit as half of a unit.

OBS message for deleting shipment

When deleting a shipment, we have added a message to clarify that the shipment may also have to be handled in Consignor or other transport service.

Match supplier invoice with purchase orders

We have previously only had the option to match supplier invoice in Fortnox with a purchase order in  Extend Commerce Backend via the field "Our reference" in Fortnox. This is also now possible by using the field "Your reference".

The API now lists balance adjustments

We have added support in the API to list balance adjustments. For blockage of balance, we have added support via webhooks.