That is why I think this is a really important issue.ĭealing with BrickLink is frustrating beyond belief. If not, we end up with some very unpleasant subtle-but-long-term price skewing effects that happen without users being aware of it. So if Brickstore uses the same API, then it should be easy to either translate these parameters to UI options, or to make a default setting based on the user's location.Īs I said I haven't been following this so I really don't know where this project stands right now and if this is already being addressed, but anyway, In short, I just think it's important that what Brickstore will provide as the priceguide prices match what you would get on Bricklink. I know that the API provides several parameters that should be able to take care of this. See also what I posted here for a longer explanation: People price things at what they think is average, but it's strucutrally slightly below that. So, someone may buy in Euro, it gets converted to USD with the exchange rate of that day for the US priceguide, and then in BrickStock a European user converts it back with today's exchange rate, resulting in skewing.Īnd as for the VAT exclusion, well, it's easy to see how that structurally makes prices appear lower than they really are, contributing to the "race to the bottom".
But for the sold average (last 6 months sales), this is not possible, because the exchange rates of the date of purchase are used.
The latter is no problem for current average prices: you can simply convert them back. We believe this is due to the fact it assumes everyone is in the US. Hi guys, I haven't been following any of these developments to be honest, but was invited by Stellar to share an issue with BrickStock that I've been posting about for some time, and that I consider to be very important as it affects the "lego economy".īrickStock's priceguide prices do not match Bricklink's.
0 kommentar(er)
