Januari 2026

We created the API V2 endpoint to manage the 3D render as follows:

• /api/v2/render3d (POST) - This endpoint adds a queue to 3D render. Users must specify ProductId, EditionConfiguration and Angles in a request. Please note that the 3D render will generate renders for the front-end request before the API request by default.
• /api/v2/render3d/{GUID} (GET list) - This endpoint retrieves a list of 3D renders.
• /api/v2/render3d/{GUID} (GET details) - This endpoint retrieves details of the 3D render.
• /api/v2/render3d/{GUID} (DELETE) - This endpoint deletes the 3D renders.

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

We have added two new fields to the GET Shop User Details endpoint in API V2 (GET /api/v2/shopusers/{id}). The new fields "DefaultShippingAddressId" and "DefaultBillingAddressId" return the default shipping address ID and default billing address ID of a specific shop user.

In addition, we identified an inconsistency between the Swagger documentation and the actual API response for this endpoint (GET /api/v2/shopusers/{id}). The current API response uses the keys TelephoneNumber and Comment, while the Swagger example displays PhoneNumber and AdminComment.

To resolve this discrepancy and ensure a smooth transition, the API response now includes both sets of fields: "TelephoneNumber" and "Comment", as well as "PhoneNumber" and "AdminComment".

Please note that to keep the endpoint clean and consistent, "TelephoneNumber" and "Comment" are planned to be removed in the future. We recommend reviewing and updating any integrations or workflows that use this endpoint to rely on "PhoneNumber" and "AdminComment" by the end of February 2026.

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

We added some more order information to API V2 Orders endpoint (GET).

To check the API endpoint, please visit this URL your shop/api-swagger. The data added includes:

• Discount
• Attachment
• OutstandingAmount
• Transaction
• TotalPrice
• OrderLanguage
• ShippingMethod
• UserComment
• QuotaionId
• VatDeductAmount

We created an API V2 endpoint to retrieve company's Languages, Currencies and Shipping countries (/api/v2/company/localization).

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

We added the "ImageUrl" to API V2 ShopUsers endpoint (GET) which will return the shop user's profile image.

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

We applied "ChangeBillingAddress" permission of Default permissions to Orderflow V2.

• If the permission is enabled, customers can change and modify their billing address in an Orderflow. 
• If the permission is disabled, customers cannot change and modify their billing address in an Orderflow. 

We created a new trigger on "Quotation discount changed" in a system type. This trigger will run a flow when there is a change in the total quotation discount — for example, when vouchers are modified or when product's amount or configuration are changed that affects pricing.

We have implemented a feature "3D objects" that allow you to create 3D object records and upload the 3D model files to them. This feature is recommended for the 3D product implementation where you wish to connect the specific models with a master edition rather than with a product.

To access the "3D objects" feature and manage it on master editions, users are required to have a "Product3DObject" role.

Along with this feature, we have updated the standard list of supported 3D file types. After this release, the .gltf and .bin files can't be uploaded to system. Only the compressed files are allowed: .gltf.xz and .bin.xz. This update applies across all features in oneCORE platform.

We applied the fallback mechanics onto the stock title in Orderflow V2 (for digital products). Firstly, the stock title in order language will be used. If the translation is missing, system will use stock title in company default language, and the first language that has translation respectively.

We resolved an issue that the created and modified timestamp shows the current date and time instead of the actual created and modified date and time.

We applied the calculation logic onto Quotation Products endpoint (/api/v2/quotations/{id}/products). With this implementation, any changes to the product quantity, configuration, or discount that affect pricing will automatically trigger a recalculation of both the product price and the overall quotation price.

We fixed an issue on the Payment Limit Rules edit sidebar where the Required payment methods selection always displayed “All” instead of the actual selected methods.

Please note that this issue doesn't affect your current payment limit rule set-up. However, during the fix, when editing a rule, please ensure that the Required payment methods are set to the intended options before saving any updates.

We fixed the issue on an API V2 endpoint to turn quotation into order (/api/v2/quotations/{ID}/orders) that didn't store the quotation's fixed discount when it turned into order. Apart from that, we integrated the quotation's fixed discount with a checkout flow.

We removed the country flags from a language switcher on Admin site.

We fixed a search function bug on a Review feature.

We have resolved an issue with Image preset that didn't generate the preset type "All".

We resolved an issue that some shops could not proceed to shipment step due to Google map metrics error.

We resolved an issue that orders in pre-created status were not automatically cancelled or deleted after the orders weren't proceeded within the specified duration in company setting.

We resolved an issue with API V2 endpoint to retrieve a list and details of products (/api/v2/products) that it didn't include inactive products in a response and returned error.

We fixed an issue that system didn't open the default Admin start page according to the setting.

We fixed a Search function issue on an order list page that couldn't look up for orders with guest name and email.

We enhanced the system encryption process for security purpose.

We upgraded project framework to .NET 9.0.12.

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

We removed the old job and codes.

Previously, the password reset flow requires customers to open the reset link on the same device and browser where the request was made. To improve convenience, we have updated the flow to support cross-device and cross-browser usage, allowing customers can open the password reset link on different devices and browser.