stavros-malakoudis_api

[tall hemlock]

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1311988480494272552

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[odd flare]

👋 happy to help

unfortunately we don't support decimal quantity

I think the best thing to do is to do your pricing per the smallest quantity fraction

for example if the smallest fraction you would be selling is 0.5yards, then your price should be based on that (e.g. 0.5 -> 5$)

or if the 0.1 yards is your smallest fraction quantity then 0.1 -> 1$

[ember radish]

Our store is running for over 3 years, having tens of thousands of products. Changing the pricing approach is not really feasible.

If you are only talking about the level 3 data then sure, we could make this work. In the second example you provided, let's say we have 0.1 yards, the quantity on the level 3 data would still be 1, but it's mapped to the "real" quantity of 0.1, right?

Are we obliged to expose this internal quantity mapping on the product description (mentioning the minimum quantity increment)?

[odd flare]

In the second example you provided, let's say we have 0.1 yards, the quantity on the level 3 data would still be 1, but it's mapped to the "real" quantity of 0.1, right?
yes correct, so 2.5 yards become quantity 25

[ember radish]

Alright, got it. Thank you for your help 🫡