Developer forum

Forum » Ecommerce - Standard features » Issue with pricing in different UnitPerMeasure than BaseUnitOfMeasure

Issue with pricing in different UnitPerMeasure than BaseUnitOfMeasure

Peter Leleulya
Peter Leleulya
Reply

Version of DW: 9.15.3

Version of Swift 1.19


Source of data: ODATA4 D365 BC connector
Env: Acceptance

We're currently running into an issue regarding products, units of measures, stock units and pricing. 

Product A

Stock Unit A (where StockLocation A is the default stocklocation)

Units of Product A (where STUKS means Pieces)

Prices of product A (are all per unit of M2)

So the issue is that the prices shown in the frontend are only shown when:

  • Either I remove the Unit from the price (because its not a correct stock unit)
  • Or I change all of the units (in price, product and stock) to the same unit

And also not the correct price is shown, because what our customer wants is that when he orders 1 STUKS of the product, that the price shown in the cart etc. is (1/0.277777777) = 3.6 m^2 * 4,79 = €17.24


How can we achieve this in Swift?
Do we need to customize with a price provider? Preferably not ...
I'm hoping for a checkbox somewhere ;)

 


Replies

 
Hans Kloppenborg
Reply

Some extra info about this issue:

We have also tried to set the base unit of measure on M2, since that is the unit of the prices we get provided, and then set 3.6 (baseunits) for the STUKS (Pieces) unit of measure, with the product still on STUKS for the Units and Stock setting, and the baseunit there then M2. We hoped DW would then see that 1 STUKS was 3.6 baseunit M2 and calculate the right price in the frontend, but we ended up with price 0.00 .

 

 
Nicolai Pedersen Dynamicweb Employee
Nicolai Pedersen
Reply

Dynamicweb cannot use prices from one unit to calculate the price of another unit - eventhough those units are connected.

So solution is either a custom price provider that will handle this scenario or adding the price for each unit to the price matrix.

 
Nicolai Pedersen Dynamicweb Employee
Nicolai Pedersen
Reply

By the way - this is DW related and not Swift related...

 

You must be logged in to post in the forum