In the last week the initial set-up for the new promotions structure has been released. More information about the promotions can be found in the orders hub.

We have started development on partial payments support in Core-commerce. In this release the first step has been released where /orders/orderId/payments call now returns the orderPaymentId which can be used by integration teams to update a payment in the future.

::: warning 💔 DeprecationThe Orders_AddPayment call has been changed. Reference has been made deprecated and pspReference has been added.:::

In the PSP implementation the old delivery address was still used instead of the new Delivery preference implementation. This has now been corrected.

• DMS

  • The much anticipated feature 'DMS AI Powerered translations' now has been released! Using this feature, it is possible to translate values in the DMS using OpenAI or DeepL integration. More information: link

• Design system has been updated with new components

• General bugfixes and improvements

The OMS Orders module has been extended with showing the paymentstatus. Also equal orderlines are now shown grouped.

It is now possible to configure a custom domain to be used on the Core-commerce portal and Hubs.

• The new webhooks functionality is released, for full details see: Webhooks
• New endpoint is added to get all return orders for a customer, see: GetAllReturns

Add shipping costs on shopping cart and orders, for more details: orders

Temporary solution until Orisha Commerce Auth0 will be used

Please view the Auth0 configuration for onboarding configuration.

Integration teams can share the customer e-mailaddresses with Core-commerce team in slow chat to be added.

VAT OMS contract changes

1. CalculatedShoppingCart
   • SubTotalAmount removed (total - payment - shipping)
   • VatRate value => 21 => 0.21m
   • Added VatBreakdownItems collection
2. CalculatedShoppingCartLine
   • Changed TotalFromPrice (decimal) to TotalAmountFrom (decimal?)
   • VatTotalAmount (decimal) (VAT applied to TotalAmount)
   • VatTotalAmountFrom (decimal?) (VAT applied to TotalAmountFrom)
   • VatRate value => 21 => 0.21m
3. Order
   • SubTotalAmount removed (total - payment - shipping)
   • Added VatBreakdownItems collection
4. Orderline
   • Quantity removed (single line orders, was leftover)
   • TotalAmount removed (Price == TotalAmount when there's no quantity)
   • VatRate value => 21 => 0.21m
   • PriceFrom (decimal?)
   • VatPrice (decimal) (VAT applied to Price)
   • VatPriceFrom (decimal?) (VAT applied to PriceFrom)
5. VatBreakdownItem
   • BreakdownType (enum: total, payment & shipping)
   • Amount (decimal) => TotalAmount the breakdown is applied to
   • VatAmount (decimal) => Amount VAT for the breakdown type
   • VatRate (decimal) => VAT rate (f.e. 0.21m)

Example for VAT breakdown:

VAT DMS contract changes

1. Product
   • Price removed (ProductPricing should be used)
   • FromPrice removed (ProductPricing should be used)
   • BasePrice (decimal) added (f.e. Tweakwise feed)
2. ProductPricing
   • PriceInclVat (decimal) => Price (decimal)
   • PriceFromInclVat (decimal) => PriceFrom (decimal?)
   • PriceFromExclVat removed
   • PriceExclVat removed
   • VatRate value => 21 => 0.21m
   • VatPrice (decimal) (VAT applied to price)
   • VatPriceFrom (decimal) (VAT applied to pricefrom)