December 2024

For the campaign with Overall discount type, we hid the discount of the following calculation rule from the product page:

• Total order price

Apart from that, when an order is eligible for more than one overall discount campaign, the system will automatically select a voucher which offers the highest discount.

Note: this logic doesn't work with discount campaign which customers must manually apply the voucher in a shopping cart. In such cases, if a customer manually applies a voucher, the order will only reflect the discount from that specific voucher. The system will not apply any other discounts unless the customer removes the manually entered voucher from the cart and adjusting products in the cart to retrigger the calculation.

Learn more about our campaign feature How to set up a campaign

We created a new endpoint to post create an order log.

• api/v2/order/{id}/logs (POST)

We created new endpoints of API v2 for product editions as follows:

• /api/v2/products/{id}/editions (get) - This endpoint retrieves a list of editions.
• /api/v2/products/{id}/editions/{editionId} (get) - This endpoint retrieves details of a specific edition.
• /api/v2/products/{id}/editions (post) - This endpoint creates a new edition.
• /api/v2/products/{id}/editions/{editionId} (put) - This endpoint updates only particular fields of an edition.
• /api/v2/products/{id}/editions/{editionId} (patch) - This endpoint updates every fields of an edition.
• /api/v2/products/{id}/editions (delete) - This endpoint deletes the edition(s).

To check the api endpoint, please visit this url your shop/api-swagger

We created a new endpoint to manage campaign provider for API v2 as follows:

• /api/v2/campaignproviders (get) - This endpoint retrieves a list of all campaign providers.
• /api/v2/campaignproviders/{id} (get) - This endpoint retrieves details of a specific campaign provider.
• /api/v2/campaignproviders (post) - This endpoint creates a new campaign provider.
• /api/v2/campaignproviders/{id} (put) - This endpoint updates all fields of a specific campaign provider.
• /api/v2/campaignproviders/{id} (patch) - This endpoint update some fields of a specific campaign provider.
• /api/v2/campaignproviders (delete) - This endpoint deletes campaign provider(s). A provider cannot be deleted if it has any associated campaigns.

To check the api endpoint, please visit this url your shop/api-swagger

We implemented a new campaign which offers a discount to customers who make a purchase equal or more of the specified amount. This campaign works with both Discount and Overall discount. The discount will be calculated based on total order price, therefore, users must select Total order price in calculation based on, then enter the amount of Minimum purchase. Learn more about our campaign feature How to set up a campaign

We created new endpoints in API v2 for Master editions as follows:

• /api/v2/mastereditions (get) - This endpoint retrieves a list of master editions.
• /api/v2/mastereditions/{id} (get) - This endpoint retrieves details of specific master editions.
• /api/v2/mastereditions (post) - This endpoint creates a new master edition.
• /api/v2/mastereditions/{id} (put) - This endpoint updates every field of catalog product by specifying master edition ID.
• /api/v2/mastereditions/{id} (put) - This endpoint updates only particular fields of catalog product.

To check the api endpoint, please visit this url your shop/api-swagger

We added a new query 'title' to get variant details endpoint (/api/v2/products/{id}/variants).

We implemented a new feature 'HideHreflangDefault' to hide the x-default hreflang attribute value. The default status is to show the attribute. To use this function, you need to contact the account manager or project manager to activate this feature for you.

We updated the order item endpoint (get) to output more data including amount of each item and edition details.

We resolved an issue on a campaign calendar that shows the incorrect period of a campaign.

We resolved an issue that the configurator version was not copied to a copy product and fall back to select the default version (version 4.4) automatically.

We resolved the issue when syncing the edition dimension but the price wasn't synced accordingly.

After we received a report that some page cannot be deleted, we investigated further and found out that the page was connected to other locations in the system. Therefore, to be clear for the users, we updated the error warning text to indicate that it was connected with other locations in the system.

We received a report that customers cannot proceed to an orderflow again after they created an order once. The issue occurred in shops where the 'Cancel order after' period, which specifies how long an order remains in a pre-created status before being automatically canceled, was set to be longer than the 'Reset products in shopping cart' period.

Therefore, we resolved the issue to work as it used to by creating a new order Id if an order is expired but customers want to proceed to an orderflow.

We added a new setting in the dynamic form for VAT number field. If Vat number field was set as a required field, users can select further to make it required for any specific groups of country. There are 3 settings:

• Every country
• Only company country
• Except company country

After we migrated the configuration rules, we are going to remove the data from the old location.

We updated Azure function to .NET 9.