Replies: 6 comments 1 reply
-
The OpenAPI documentation states that the price value for the inventory data when being submitted is a |
Beta Was this translation helpful? Give feedback.
-
As you can see in the payload above we correctly transfer the price as a JSON float value i.e. |
Beta Was this translation helpful? Give feedback.
-
@cajudosu I think I understand. I will raise this with our international teams. |
Beta Was this translation helpful? Give feedback.
-
Thanks a lot 😃 |
Beta Was this translation helpful? Give feedback.
-
@cajudosu we will be disabling the Issues board, so we are converting this to a discussion topic. We are still tracking this as an active ticket in our system. |
Beta Was this translation helpful? Give feedback.
-
@etsyachristensen Any update on this? |
Beta Was this translation helpful? Give feedback.
-
Is there an existing issue for this?
Describe the bug
If you have a product, that has the switch for "Domestic & global pricing" activated, the product has two variations for which you track the quantities seperately and you perform a quantitey update via updateListingInventory, the decimal seperator for the main country changes from comma (",", which is the correct seperator here in Germany) to point ("."). As a result, a price like 39,95 becomes 39.95. If you oversee this and save the product the price becomes 3995,00 (100 times as much!)
Steps to reproduce
Expected behavior
After the stock update via updateListingInventory the price still has a comma (",") as decimal separator.
Additional context
No response
Beta Was this translation helpful? Give feedback.
All reactions