November 2025

We created a new trigger "Trigger on Quotation shipment changes" which will run the flow when there is a change in quotation shipment. The trigger will send the Quotation ID to the specified power automates. The changes cover these scenarios:

• Configure delivery product
• Modify delivery date
• Modify shipment group

We added "None" option to the Header field in component editor. When "None" is selected, the text will be rendered using a <p> tag in the output.

We created a new Account Functionality V2 component "MyAchievements". This component will display all achievements belonging to customer's account and achievement's information, allowing customer to claim the achievement in their Account Functionality.

The set-up guideline is provided in Account Functionality V2.

We implemented an automatic permanent redirect to the lowercase version of a URL whenever customers access the shop using an uppercase URL. This helps ensure all traffic is centralized to a single, consistent URL format. The redirect does not work with the page URLs required authentication and system page URL and internal system URLs.

We created a new trigger "Trigger on quotation followed up" which will run the flow when there is a change in this quotation data

• Follow up date
• Note
• Success rate

We created a new trigger "Trigger on quotation product changed" which will run the flow when there is a change in quotation product. The changes cover these scenarios:

• Add/remove quotation items
• Update quotation item's detail
• Update discount line

We created an API V2 endpoint for OrderShipments and OrderShipmentLines as follows:

• /api/v2/orders/{id}/shipments (GET list) - This endpoint retrieves a list of order's shipments.
• /api/v2/orders/{id}/shipments/{shipmentId} (GET details) - This endpoint retrieves details of a specific order's shipment.
• /api/v2/orders/{id}/shipments/{shipmentId} (PATCH) - This endpoint partially updates a specific order's shipment.
• /api/v2/orders/{id}/shipments (DELETE) - This endpoint deletes specific shipments.
• /api/v2/orders/{id}/shipments/{shipmentId}/shipmentlines (POST) - This endpoint creates a shipment line under specific order's shipment.
• /api/v2/orders/{id}/shipments/{shipmentId}/shipmentlines/{shipmentlineId} (PATCH) - This endpoint partially updates a specific shipment line.

We created a new trigger "Trigger on Quotation contact changes" which will run the flow when there is an update to the information of customers who have request specific quotations. The trigger will send the Quotation ID to the specified power automates. The changes cover these scenarios:

• Update customer details, such as name, telephone number, etc. This also includes an update on the shop user details of a shop user who requests a quotation or switching shop user.
• Update shop user type and shop user type value.
• Update shop user address.

We added the page layout information to GET product details endpoint of API V2 (/api/v2/products/{id}) and displayed the page layout which that product is using in a "Layout" field on Product details page.

We fixed a bug that users couldn't cancel the action on product's image tag feature, and the page kept loading when saving the image tag.

We fixed the UI bug with the "Impersonate" button (from a shop user impersonate feature) that appeared more than one in Shop user details.

We fixed the issue that an API V2 endpoint to assign, update and partially updates shop user types (/api/v2/shopusers/{id}/shopusertypes) didn't work.

We fixed the issue with API V1 GET product list endpoint (/api/v1/products/list) which returns an error when a product didn't contain any editions.

According to the report that expected shipping date was on weekend, which was non-working days, we updated to store the created date, modified date and expected delivery date based on time zone in company setting. Then, the system will calculate the expected delivery date based on company time zone to prevent an issue regarding time zone differences.
Please configure your company time zone to apply this logic to order shipment.

Besides, this would also solve an issue with Notification Template "Enhanced order status notification" which could display expected delivery date and week.
Apart from this update, we removed these 2 duplicated shortcodes from Notification Template "Enhanced order status notification":

• EXPECTED_FIRST_ORDER_SHIPMENT_DELIVERY_DATE
• EXPECTED_FIRST_ORDER_SHIPMENT_DELIVERY_DATE_WEEK

We fixed the issues with the order export file that displayed downpayment amount at order price and data appeared in wrong column.

Also, we also enabled the ability to export a specific order from the search results when searching by order ID.

We fixed the UI bug in Shipping method feature that the duplicated text showed up when there were more than 5 countries added to shipping method's available countries.

We resolved an issue that the overall discount vouchers didn't automatically switch after returning to shopping cart to update products or product amount.

We changed the key in POST, PUT and PATCH Quotation products endpoint of API V2 (/api/v2/quotations/{id}/products) as following details:

• SaleDocumentLineId to ExternalOrderLineId
• SaleDocumentName to ExternalOrderLineName

We optimized shipping method query for enhanced system performance.

We implemented an image manager and integrated it to Product Manager which will optimize database queries and enhance system performance.

We implemented the 3D configurator version 4.10.0 and update the 3D configurator to work with all available versions including 4.4.0, 4.7.1 and 4.10 (new). Users can still select the configurator version as they wish.

Note: Changing the version is allowed only when there is no file uploaded.

This update is part of removing unused data "ProductId" from order.

We optimized the export functionality across all features to reduce file size.