October 2025

We added "Title" field to menu item with a link type — Product, Category, Page. This is to support when you would like to link a menu item to Product or Category or Page, but uses the manually inputted title.

We implemented an interface for the 3D scenes feature which is under a proof of concept for a future standard implementation of the 3D product configurator. With 3D scenes, we can have the configurator separate from 3D products; that is to say, the configurator is the "3D scene", while the objects being configured are "products". This feature helps simplify the product setup and management for multi-product configurator.

The "3D scenes" feature along with "3D textures" feature will be under 3D menu. To access the feature, users are required to have "Product3DObjects" permission. Additionally, we adjusted the behavior of menus by removing a redirect after clicking on a menu from menu features without summary page, e.g. dashboard, management, etc.

We created a new trigger on "Quotation status changes" in a system type. This trigger will run a flow when any quotations change their statuses by sending Quotation Id to the target automations flow.

We removed an endpoint to manage page components on a page from /api/v2/pagepagecomponents and added a new endpoint /api/v2/pages/{id}/pagepagecomponents with the ability to manage content within a page component. Please review any automates flow applying this endpoint to avoid the interruption.

• /api/v2/pages/{id}/pagepagecomponents (GET list) — This endpoint retrieves a list of components on a page.
• api/v2/pages/{id}/pagepagecomponents/{id} (GET details) — This endpoint retrieves details of a specific component on a page.
• api/v2/pages/{id}/pagepagecomponents (POST) — This endpoint adds a component to a page.
• api/v2/pages/{id}/pagepagecomponents (PUT) — This endpoint updates component details and content.
• api/v2/pages/{id}/pagepagecomponents (PATCH) — This endpoint partially updates component details and content.
• api/v2/pages/{id}/pagepagecomponents (DELETE) — This endpoint removes component(s) from a page.

To check the API endpoint, please visit this URL your shop/api-swagger.

We added support for a financial discount line in quotations (a discount that applies to each individual item). The financial discount line allows input in a fixed amount of discount. If a quotation item includes both a percentage and a financial discount, the system will calculate the total discount by applying the percentage discount first, then adding the financial discount on top.

Accordingly, we’ve updated the following API V2 endpoints with these details:

• Add "DiscountAmount" to /api/v2/quotations/{id}/products/{quotationProductId} (PUT/PATCH/POST)
• Update /api/v2/quotations/{id} (GET details) to output Discount line based on the sum of financial and percentage discount

We created a new endpoint to retrieve the quotation's change log (/api/v2/quotations/{id}/logs), supporting a filtering by date ranges and type of change.

In order to support a dynamic implementation of quotations, we added "DynamicData" field to quotation which is designed for storing the extra quotation information based on the custom usages. This field is added to API V2 quotation endpoints. In addition, we added the custom fields to dynamic form, "Product quotation" type, in order for you to add these fields to your request quotation form and customer's answers will be saved to quotation DynamicData.
Each custom fields are designed for different type of input and have different settings as follows:
1. Multi-line text - for a long input

• Label
• Placeholder
• Identifier
• Required

• Label
• Placeholder
• Identifier
• Required

• Label
• Placeholder
• Required
• Identifier
• Options which each includes option and identifier. Note: without identifier specified, option will be used as identifier.

• Label
• Required
• Identifier

We created a new Mail type "Manual" for Notification Template feature. This mail type is an ideal for using with automations flow, enabling the manual trigger via Public API (/api/v2/notificationtemplates/trigger) to send email or SMS. To use Manual Notification Template, users must select the Template which specifies a set of data that can be in the email or SMS content, reflecting as shortcodes when managing content. Manual Notification Template can only manage the subject line and content of email or SMS while the other information — such as Recipient Emails, Copy Contact Email, etc. — is designated via Public API.

Note: users are required DynamicNotificationTemplates permission to be able to choose the template.

We created some new API V2 endpoints ideally to use with Manual Notification Template.

• /api/v2/notificationtemplates/trigger (POST) — This endpoint triggers the notification template to send email or SMS and replace shortcodes with actual data.
• /api/v2/notificationtemplates/{id}/attachments (POST) — This endpoint adds an attachment to specific notification template. Supported file formats include PDF, JPG, PNG, GIF, WebP, ZIP, XML, HTML, XLSX, and DOCX.
• /api/v2/notificationtemplates/attachments (POST) — This endpoint uploads an attachment that is not tied to any specific notification template. It is primarily intended for use with Manual Notification Templates. Supported file formats include PDF, JPG, PNG, GIF, WebP, ZIP, XML, HTML, XLSX, and DOCX.

To check the API endpoint, please visit this URL your shop/api-swagger.

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

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

We resolved an issue that users couldn't edit the content directly in Rich text editor in every features in oneCORE.

We resolved an issue that some Account functionality V1 pages can't be opened on a shop which is not turning on LanguageURL feature.

We removed the /home from homepage's URL on page's meta tags and sitemaps.

We resolved an issue affecting digital orders with multiple shipments, where the order status was incorrectly marked as Finished even though some shipments were still awaiting fulfillment. This issue caused some users not to receive their codes correctly.

We fixed an issue in Menu feature that the link type couldn't be changed to Manual after being created.

We fixed the API V2 POST, PUT and PATCH quotation products endpoint (/api/v2/quotations/{id}/products) that returns an error when request with a key Configuration.

According to the previous release regarding the implementation of billing address in quotations, we updated an API V2 endpoint to turn quotation into order (/api/v2/quotations/{id}/orders) to also save quotation shipping address and billing address to order shipping address and billing address.

We resolved an issue in Menu feature that users couldn't delete a menu item if it had child/sub item.

We upgraded the project framework to .NET 9.0.9.

We upgraded project framework to .NET 9.0.10.

We implemented the billing address for quotation, while the current customer address will be considered as shipping address. In the public API V2, quotations endpoint will include BillingAddressId and ShippingAddressId. Any value sent to the key CustomerAddressId (old key) will be saved as ShippingAddressId; however, we urge you to update all integrations to use ShippingAddressId, as we will be scheduling the complete removal in a future release.

Due to the implementation of quotation shipping address and billing address, we expected all parties to not use quotation "CustomerName", "CustomerEmail", "CustomerTelephone", "CustomerCountry" as these will be removed in the near future.

We optimized some query for more efficient Admin site's performance.

We removed the Headline selection from a component editor. Any in-use components which have a headline assigned to will not be affected; however, if the Headline is unassigned from a component after the release, the Headline selection won't reappear.