Observation: data like sale rate or avg daily sold go as low as 0.01 currently

Problem: this is a rounding, and for a lot of items (transmogs) the real value is probably much lower. for instance if we try to find the region quantity of a transmog, it usually goes like this :
DBRegionSoldPerDay / DBRegionSaleRate = 0.01 / 0.01 = 1
this is inaccurate because of rounding problems, transmogs more often goes around 150-200 quantity instead of 1.
this is just one example of the problem that comes when rounding is too extreme. some items really have a low avg daily sold and sale rate. rounding them to 0.01 would be incorrect.

Solution: I propose allowing us to have a more precise value, at least 8 decimals, if not the exact value. If you need it to be non 0, then the smallest value that exist in your database beside 0 would work fine as the min.

thank you

Let's say you're flipping stuff on the AH. You buy stuff at or under 75% DBMarket, and post with a min post value of 80% DBMarket. If that 5% difference is too small you might end up loosing gold, if it's too large you'll miss opportunities.

Some items have a much smaller variation than others. That 5% difference for a Chaos Crystal might be 5 Gold, but 5% for a rare battle pet could be 5,000 Gold. The Chaos Crystal might have a fairly steady price, but the battle pet might vary wildly.

If there were a "DBStdDev" for instance, or a "DBRange" (maybe the average of the max - min from Step 3 of calculating the DBMarket value?) then the purchase price might look something more like DBMarket - 0.2 * DBRange, and the min sell price might look more like DBMarket - 0.1 * DBRange. That would help to mitigate the risk of targeting a % gap between buy and sell that's too large or too small.

It's just a thought. Thanks for all the work, this is my favorite addon.

with this data we could decide if the region quantity is too low for our taste, which could allow us to declare our own pricing based on that

example : "if item x has 1 quantity listed on region, do not trust regionmarket and use 250000g instead"

currently we have access to the region quantity on the api but it is an avg, if it was a sum we could find directly the avg. the other way is not possible due to lack of digits, 0 and 1 being the lowest avg so on eu the exact quantity could be between 0 and 123 in those case, we don't have further details. but the best would be to have the exact region quantity.

There is a LOT of possible variation on current content boe now.
If I'm not mistaken you calculate the market price for each item variation. In a result you have some items with very, very low data.

It creates situations where :
Cruel hope crusher item level 710 = 17.6k region market
Cruel hope crusher item level 710+Heroic = 41.9k region market
Cruel hope crusher item level 715+Leech = 6.4k region market

We can't micro manage each items given the number of item variation, TSM should in my opinion automatize this by providing accurate pricing.

I suggest you group each item variation by item level, like TUJ is doing, to consolidate pricing and avoid having the kind of pricing above. Players are then free to create tertiary stat or socket groups that adds a fixed amount of gold added, just like 25/blue battle pets.

That's how you calculate battle pet market price, I think you should apply this to gear with variation.

Letting us check an option that would make the TSM prices behave on some logical rules, such as, the Mythic Warforged Speed Socket BoE will always cost equal or more than the Warforged Mythic BoE type, that kinds of things. TUJ is often accurate on that type of things, while prices from TSM are strange because it makes avg out of very low quantity (for instance there were a Magic Rooster on EU listed for 18k few months ago, so for TSM the region price is 18k, which is true, but obviously not coherent).

Hope it was clear. I know this might not be the intended purpose of the system but that's just a suggestion :p But for me such option makes sense.