March 2026

We created the API V2 endpoint to manage the location's opening hour as follows:

• /api/v2/locations/{id}/openinghours (GET) — This endpoint retrieves details of a location's opening hours and holidays.
• /api/v2/locations/{id}/openinghours (POST) — This endpoint creates a location's opening hours.
• /api/v2/locations/{id}/openinghours (PATCH) — This endpoint partially updates a location's opening hours.
• /api/v2/locations/{id}/openinghours (DELETE) — This endpoint deletes a location's opening hours.
• api/v2/locations/{id}/openinghours (GET) — This endpoint retrieves details of a location's opening hours.
• /api/v2/locations/{id}/openinghours/holidays (POST) — This endpoint creates a location's holiday.
• /api/v2/locations/{id}/openinghours/holidays (DELETE) — This endpoint deletes a location's holidays.
• /api/v2/locations/{id}/openinghours/holidays/{holidayId} (PUT) — This endpoint updates a location's holiday.
• /api/v2/locations/{id}/openinghours/holidays/{holidayId} (PATCH) — This endpoint partially updates a location's holiday.

To check all available API endpoints, please visit this URL your shop/api-swagger.

Apart from that, we applied company's time zone to location's holiday opening hour. The date will be saved in company's time zone. Without time zone setting, date will be saved with the Netherland time zone. This change will not affect the records that were created before this task delivery.

Additionally, we updated the Holiday opening hours, "Recurring yearly" setting to be editable after saved.

In the Orderflow V2 contact form, we removed the default value “0” from the House Number field.

Additionally, we updated the Country field in a contact form to automatically preselected the country based on their country selection on the live website. Without the pre-selection on a website, system will pre-select a country from the browser's cookie, customer’s IP address and a company’s default country accordingly.

In the Orderflow V2 payment step, the Free payment method option was updated to appear only when the order inclusive shipping method fee was free.

We created the API V2 endpoint for media folders as follows:

• /api/v2/media/folders (GET list) — This endpoint retrieves a list of media folders.
• /api/v2/media/folders (GET details) — This endpoint retrieves details of media folders.
• /api/v2/media/folders (POST) — This endpoint creates a media folder.
• /api/v2/media/folders/{id} (PUT) — This endpoint updates a media folder.
• /api/v2/media/folders/{id} (PATCH) — This endpoint partially updates a media folder.
• /api/v2/media/folders/{id} (DELETE) — This endpoint deletes media folders.

To check all available API endpoints, please visit this URL your shop/api-swagger.

The "Combination price groups" feature enables the ability for front-end to retrieve multiple Combination price records at once. Once a group is set up, the system can retrieve all related combination prices at once using group as an identifier.

This implementation also simplifies the Combination price setup by reducing the number of records and shortening the combination, making it easier to manage and maintain. The example setup is available in our documentation.

The Combination price groups are available to manage via Admin site and Public API V2.Migration of Key and Value

From March 9, 2026, system will migrate existing key and value data from Master edition's meta data to Combination price.

If the data migration is completed for a Master edition, the system will use the key and value from a new field.

If any manual changes are made to the Combination Price field (key, value, or groups) before migration occurs, the system will skip the migration for that Master edition and immediately use the data from the new field.

Important Reminder

For all new Master editions created after March 9, 2026, the Combination key and value must be set up in Combination Price rather than in Meta data.

Please note that if a product is copied before the migration is completed (if you choose to create new Master edition), the system will not perform the migration for the newly created Master edition. Instead, it will immediately use the data from the new field.

To ensure correct configuration prices, please make sure the Combination key and value are properly set up for any new Master editions.

We created the API V2 endpoint to retrieve the organization's data usage: GET /api/v2/usage. Please note that the output data is not real-time and may be delayed up to 10 minutes.

This endpoint replaces GET /api/v2/databaseusages and includes additional data for 3D renders. The endpoint /api/v2/databaseusages is scheduled to be removed by the end of March 2026.

You can now view the overview of all Taxonomy tags associated with a product via Catalog products and Master editions directly from the Product Information section on the product detail page. On hover to the Master edition tags, you can also see the Master editions which this tag belongs to and their editions in this product.

We enhanced the Shop notification settings to allow specifying Products, Pages, Categories, and Languages where the notification should be displayed and hidden.

Please note that each shop must update its front-end logic to support and apply these new settings.

The existing "Included URL(s)" and "Excluded URL(s)" fields will continue to function as before, if the new settings are not used.

Read how each new setting work in Shop notifications.

We created an API V2 endpoint to retrieve the digital products under the digital stocks (GET api/v2/digitalstocks/{id}/digitalproducts).

To check all available API endpoints, please visit this URL your shop/api-swagger.

We updated an API V2 endpoint to retrieve order item (GET /api/v2/orders/{id}/items) to include these following data in the response:

• Combination price
• Combination prices
• Service fee
• Service cost
• Edition VAT rate
• Edition VAT percentage
• Edition SellPrice
• Edition Note

Besides, we added these following data to an API V2 to retrieve order details (GET /api/v2/orders/{id})

• Service cost
• SubTotal
• ShippingCost
• Discount
• ServiceCost

To check all available API endpoints, please visit this URL your shop/api-swagger.

We created a Trigger on shipment line created which can be found in Trigger type > Order. This trigger will run a flow when a new shipment line is created — for example, when customers check out, when admin users manually create shipment on Admin or Public API.
The body of a trigger include:

• OrderId
• ShipmentID
• ShipmentLineID

We created a Trigger on order status changed which can be found in Trigger type > Order. You can also select the specific order statuses that will trigger the flow.
This trigger will run a flow when the order's status changes — for example when customers check out, when admin users modify the status via Admin or Public API.
The body of a trigger include:

• Order ID
• Company URL

We created a new component "MyAddress" for Account functionality V2, allowing customers to easily manage their addresses.

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

If a shop has Shop feature "BillingAddress" disabled, a billing address section won't appear and customer can't set a default billing address.

We fixed the issue that caused incorrect 3D objects to be displayed in the options.

We fixed an issue that the category was not assigned to the copy product cross company and edition prices are not copied.

We resolved an issue that the payment limit rules were triggered due to the dummy email address of guest users.

We updated the Orderflow to check for available payment methods by using Billing address's country instead of Shipping address's country. If a shop has "BillingAddress" feature off, system will use Shipping address's country instead.

Please note that we add a new translation key "cf-PaymentNotFound" which will appear when there is no available payment method.

We updated the Telephone number and Telephone number verification field on Orderflow V2 to have maximum digits of 15.

We updated the PUT and PATCH media folders endpoint (/api/v2/media/folders/{id}) to return error when folder ID in a request is the same as in "ParentId" in a request.

We applied the fallback logic to stock description or the instruction of digital products on Orderflow V2. System will primarily show the instruction based on stock description in order language. If the stock description is an order language is not available, system will show the description in a default language.

We updated Combination prices to improve visibility of updating prices status.

• Last updated show the timestamp of the latest update. It is renamed from "Pushed to price cache".
• Last failed shows the timestamp of the latest failed update. The update job will stop working if it fails, so users must re-update the prices.
• Completed shows the timestamp of the latest successful update.

As previously announced on February 9, 2026, the field "Type" was planned to be removed from the response of the API V2 endpoint: GET /api/v2/quotations/{id}.

This completes the alignment between the API response and the Swagger documentation. The response now only includes the standardized field: "MimeType".

In addition, we identified an inconsistency between the Swagger documentation and the actual API response for this endpoint (GET /api/v2/quotations/{id}). The current API response uses the keys "EditionId" for under Product "Configurations", while the Swagger example displays "Id".

To resolve this discrepancy and ensure a smooth transition, the API response now includes both fields: "EditionId" and "Id" for the configuration details.

Please note that to keep the endpoint clean and consistent, "EditionId" is planned to be removed in the future. We recommend reviewing and updating any integrations or workflows that use this endpoint to rely on "EditionId" by the end of April.

As previously announced on December 24, 2025, the fields "TelephoneNumber" and "Comment" were planned to be removed from the response of the API V2 endpoint: GET /api/v2/shopusers/{id}.
This completes the alignment between the API response and the Swagger documentation. The response now only includes the standardized fields:

• "PhoneNumber"
• "AdminComment"

We removed the Account functionality V2 Beta version from the system.

We upgraded project framework to .NET 9.0.14.