September 2025

We created a new endpoint to retrieve Admin users data as follows:

• /api/v2/adminusers (GET list) - This endpoint retrieves a list of Admin users.
• /api/v2/adminusers/{id} (GET detail) - This endpoint retrieves details of specific Admin user.

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

We created a new endpoint (POST /api/v2/products/{Id}/editions/autosort) that automatically sort product editions order based on your chosen criteria — including name (A-Z, Z-A), most sold, recently added, selling price (low-high, high-low). For more flexibility, you can also define which edition levels to sort and how many depth levels to include, so you only need to request the highest edition level instead of all product editions.

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

We created PATCH product image endpoint in API V2 to edit and replace the product image (/api/v2/products/{id}/productimages/{Id}).

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

Dynamic Contents feature makes it easy to manage content across oneCORE features. Instead of updating the same text in multiple places, you can create it once and link it everywhere. This saves time, keeps content in sync, and supports flexible front-end display through custom integration. Read more how to set up your dynamic contents.

We added "CategoryIds" to GET details product endpoint of API V2 (/api/v2/products/{id}). In addition, we created new API V2 endpoints to manage categories of products. The details are as follows:

• /api/v2/products/{id}/categories (POST) — This endpoint adds categories to a product.
• /api/v2/products/{id}/categories (PUT) — This endpoint updates categories of a product.
• /api/v2/products/{id}/categories (PATCH) — This endpoint partially updates categories of a product and their order (vieworder).
• /api/v2/products/{id}/categories (DELETE) — This endpoint removes categories from a product.

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

The AccountOverview component has been updated with new features: users can now upload a profile image and edit their birthday. Please ensure all translation keys are set up. The guideline is provided in Account Functionality V2.

We resolved an issue that content on Account functionality was displayed in incorrect language after opening some pages.

We fixed the bug in AccountPreference component in Account functionality V2 that didn't display the selected language.

Read more about Account Functionality V2 and component set-up guideline in Account Functionality V2.

We implemented a change log for product images. It records when images are added, replaced, or updated — including edits to titles, descriptions, as well as actions like duplication, activation/deactivation and highlighting.

We removed a logic to check for RedisCache API setting when retrieving price. After the update, without the API setting, system will retrieve combination prices directly from our database but do not fallback to Azure RedisCache.

As part of our recent updates, we have migrated external prices to be stored directly within oneCORE with the aim of enhancing performance. This migration has now been fully completed — all prices are functioning as expected, and the connection to Azure RedisCache has been discontinued.
To further improve system stability and maintainability, the following changes are being implemented:
- Refactoring of the external price logic
- Removal of all migration-related code.
- Removal of API settings related to external prices (see list below).

• ExternalPriceRedisCache
• ExternalPriceFailOver
• BCERPFailOver
• BCERPRedisCache
• BCERPExternalTrigger
• BCERPExternalTriggerFailOver