January 2025

We updated method post, put and patch of product edition of API v2 as follows:

• Add Master edition ID; if master edition ID is not filled in, the master edition will be created along with product edition.
• Add Metadata
• Add ERPmetadata

We created a Voucher endpoint for API v2 as follows:

• /api/v2/campaign/{id}/vouchers (get) - This endpoint retrieves a list of vouchers in a specific campaign.
• /api/v2/campaign//{id}/vouchers/{id} (get) - This endpoint retrieves details of a specific voucher.
• /api/v2/campaign/{id}/vouchers/{id} (put) - This endpoint updates all fields of a specific voucher.
• /api/v2/campaign/{id}/vouchers/{id} (patch) - This endpoint updates particular fields of a specific voucher.
• /api/v2/campaign/{id}/vouchers (delete) - This endpoint deletes the voucher(s).

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

We added a new field for users to manually enter the expected shipment date of the existing shipment. Once the shipment date is manually entered, it cannot be removed and the date generated by the system cannot be restored.

We updated method get, post, put, patch of product edition endpoint to include display edition in shopping cart and orderflow setting (a physical product setting).

We created a new endpoint for campaign products as follows:

• /api/v2/campaigns/{id}/products (GET) - This endpoint retrieves a list of product under specific campaign.
• /api/v2/campaigns/{id}/products (POST) - This endpoint adds products to specific campaign.
• /api/v2/campaigns/{id}/products (PUT) - This endpoint updates a whole group of products under specific campaign.
• /api/v2/campaigns/{id}/products (DELETE) - This endpoint removes specific product Id(s) from specific campaign.

To check the api endpoint, please visit this url your shop/api-swagger

We displayed the edition amount on a confirmation page in orderflow if a product has at least one edition whose amount is more than 1.

We created a Campaign endpoint for API v2 as follows:

• /api/v2/campaign (get) - This endpoint retrieves a list of campaigns.
• /api/v2/campaign/{id} (get) - This endpoint retrieves details of a specific campaign.
• /api/v2/campaign/{id} (put) - This endpoint updates all fields of a specific campaign.
• /api/v2/campaign/{id} (patch) - This endpoint updates particular fields of a specific campaign.
• /api/v2/campaign (delete) - This endpoint deletes the campaign(s).

If a campaign contains at least 1 used voucher, that campaign cannot be deleted.

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

We adjusted get list of product variant endpoint of API v2 to be able to filter with empty title. To retrieve variants that do not have title, you need to request with ?query=

To enable users to set up the meta tags, tab headline, share banner differently from title and description displayed on the live website, we've adjusted the meta title and meta description implementation starting with Page and Blog and System page (shopping cart, wishlist, review and not found).

After the adjustment, the live website will use page title and page description, while meta tags which indicate page information in a web browser's tab headline and a share banner will primarily use meta title and meta description. Read more about the usage of meta title and meta description in meta tags in Standard Key Tags for SEO and Social Media in oneCORE

Apart from that, we remove Shortcode (#COMPANY_NAME# , #META_TITLE# , #META_DESCRIPTION#) function from page title and description and implement it in meta title and meta description instead. For system page like Wishlist, Shopping cart and Not found, we will add meta title and meta description field for users to manage page meta tags.

Previously, to update the cost price and average stock price respectively, the available stock of an edition must not be 0 or that edition must be set to allow over sell. Now, we removed this condition for physical product. After the adjustment, average stock price of physical products will be updated per new cost price, not relying on the stock or allow over sell setting.

We created a new endpoint to manage campaign product combination in API v2 as follows:

1. /api/v2/campaigns/{id}/combinations (GET) - This endpoint retrieves a list of combinations and their details under a specific campaign.

2. /api/v2/campaigns/{id}/combinations (POST) - This endpoint creates a new combination under a specific campaign.

3. /api/v2/campaigns/{id}/combinations/{combinationId} (PUT) - This endpoint updates every fields of a specific combination.

4. /api/v2/campaigns/{id}/combinations/{combinationId} (PATCH) - This endpoint updates only particular fields of a specific combination.

5. /api/v2/campaigns/{id}/combinations/{combinationId} (DELETE) - This endpoint deletes a specific combination.

To check the api endpoint, please visit this url your shop/api-swagger

For sync edition function, we combined the price type sync with edition price. Therefore, when users select to sync edition price, the price type will also be synced.

We updated method post, put and patch of product endpoint of API v2 to include translation of all languages. The details are as follows:

• title
• shortdescription
• description
• metatitle
• metadescription

We updated the server-side render to generate an image only once and reuse it for any following identical requests. Identical configurations are considered based on 4 aspects: configuration details, 3D event, model (version and event) and object state (position).

Recently we shipped a new campaign rule 'Product combination' which allows you to set up products which must be purchased together to be eligible for discount. Previously, users needed to specify the required quantity, and discount was applied only to the specified unit.

Now, we added another option 'Non-specific quantity' for users to not enter the required quantity. With this option, order can contain selected products with any quantity. Discount is applied to every unit. Also, this update includes activating the product combination for Overall discount campaign type.

Read more about how to set it up in How to set up your 'product combination'

We resolved an issue on blog page in admin interface that did not display the assigned products.

We resolved an issue with a sorting by price function on category pages.

We fixed an issue with +/- button to increase and decrease quantity that could not be clicked on a sidebar to add product from stock in create shipment function.

We resolved an issue that full URL of some products were not output in the export file.

We fixed an issue on Product rules feature which did not display specified range on a list page of product rule.

We updated the filtering logic of the GET method for the Product Variants Endpoint (v2). The filter will combine the input Edition Ids to identify and return only the variants that match the specified combination. Additionally, we adjusted the POST method to return the existing variant when a user creates a variant that already exists.

We extended the delay time before generating the 3D render of a product configuration to 5 second to support the configuration with much details.

We rebuilt the wishlist to support dimension and state for a possibility to add multiple items in 1 product with configured location to a wishlist.

We resolved an issue that webp images were broken on Docker.

We raised the maximum upload limit of 3D objects from 30MB to 50MB.

We remove ActiveCampaign from API type option.

We moved the ticket template to generate in oneCORE.

We resolved an issue that product images were broken on Docker.