v1.0.16 (PS 1.7)

Bugfix: when using static pricing without geographical limitations, the service was always proposed regardless of whether it was actually available, which could lead to issues with shop delivery location selection.

Please note that this change means that now the module will systematically trigger a quote request during the checkout process, which was not necessarily the case if you had only setup services with static pricing.

v1.0.15 (PS 1.7)

Fix behaviour of order state change: when the module changes the state of the order to 'shipped' (if the relevant option has been activated in module settings), then an email to the customer is triggered (which is the default behaviour when manually changing the state of the order in backoffice).
Better error management in case of issues with the MFB API.

v1.0.14 (PS 1.7)

Relax API quote request restrictions to allow proper working of MFB carriers when creating an order manually in back-office.

v1.0.13 (PS 1.7)

Bugfix release: parcel references (shipper/recipient/customer) were not sent to the API during the booking process.

v1.0.13 (PS 1.6)

Bugfix release: parcel references (shipper/recipient/customer) were not sent to the API during the booking process.

v1.0.12 (PS 1.7)

The module now takes into account the package initialization strategy defined in configuration (max real weight per parcel, max volumetric weight) when creating a new MFB shipment in back office.

v1.0.12 (PS 1.6)

The module now takes into account the package initialization strategy defined in configuration (max real weight per parcel, max volumetric weight) when creating a new MFB shipment in back office.

v1.0.11 (PS 1.7)

Added advanced mechanisms to simulate the most relevant pack-list when trying to estimate the shipping cost for a given cart.
Three settings have been added :

• maximum real weight per package
• maximum volumetric weight per package (only used if maximum real weight per package is checked and if all articles in a cart have dimensions defined)
• force use of weight/dimensions table

You can use these settings to determine the maximum weight/dimensions per parcel for a given cart. Whenever possible and if these options are set, the module will always try to gather articles in as few packages as possible, respecting the maximum weights defined.

If your articles only have weight defined (no dimensions), only the setting 'maximum real weight' will be taken into account.
If your articles (or some articles) have dimensions defined (in addition to weight), you MUST set both maximum real weight and maximum volumetric weight. Volumetric weight takes into account the dimensions of the package (volumetric weight = lengthwidthheight/5000). The simulated packages' dimensions are calculated by stacking article on top of each other, always stacking on the smallest dimension.

Contact us if you do not understand how all these mechanisms work in details. Proper configuration heavily depends on your catalog and your type of packaging. In some cases, even if you have defined article dimensions in your catalog, you might want to force the use of the weight/dimensions table (if you only use standard packaging sizes and have a fairly homogenous catalog).

v1.0.11 (PS 1.6)

Added advanced mechanisms to simulate the most relevant pack-list when trying to estimate the shipping cost for a given cart.
Three settings have been added :

• maximum real weight per package
• maximum volumetric weight per package (only used if maximum real weight per package is checked and if all articles in a cart have dimensions defined)
• force use of weight/dimensions table

You can use these settings to determine the maximum weight/dimensions per parcel for a given cart. Whenever possible and if these options are set, the module will always try to gather articles in as few packages as possible, respecting the maximum weights defined.

If your articles only have weight defined (no dimensions), only the setting 'maximum real weight' will be taken into account.
If your articles (or some articles) have dimensions defined (in addition to weight), you MUST set both maximum real weight and maximum volumetric weight. Volumetric weight takes into account the dimensions of the package (volumetric weight = lengthwidthheight/5000). The simulated packages' dimensions are calculated by stacking article on top of each other, always stacking on the smallest dimension.

Contact us if you do not understand how all these mechanisms work in details. Proper configuration heavily depends on your catalog and your type of packaging. In some cases, even if you have defined article dimensions in your catalog, you might want to force the use of the weight/dimensions table (if you only use standard packaging sizes and have a fairly homogenous catalog).

v1.0.10 (PS 1.7)

Disable all quote request calls to the API when outside of the order tunnel.
This was already the default behaviour when using Prestashop as guest, but if a user was signed-in Prestashop would automatically trigger a quote request everytime the customer added an item to the cart. This would cause the user experience to be significantly degraded.

PLEASE NOTE: if you were trying to display price estimate before the order confirmation, this change might disrupt this approach. We have always discouraged use of such estimates with dynamic pricing, as it is slow and mostly unreliable, especially as Prestashop considers the absence of valid shipping price to mean that shipping is free.
Also note that only MFB shipping services in dynamic mode are affected. If you have configured an MFB service with static pricing then this service will not be affected by the change made in this release.