- Forums
-
Pricing
- Community Pricing
- Pricegrid
- Spreadsheet
- Browse Suggestions
- Latest Changes
- Unusual Pricelist
- Browse by Item
- Browse by Effect
- Steam Community Market
- Market Pricelist
-
Trading
- Classifieds
- Classified Listings
- Utilities
- Calculator
- Premium Search
- Statistics
Previous suggestion was accepted a month ago, but some of the sales used are now out of date.
Special thanks to depressed bean for all the groundwork done in the previous suggestion!
___________________________________
Item 1
Sale 1.1 | Seller (Near ID 16356880376) | Buyer | Proof (from previous suggestion) | Sold for 200 pure
200
__________
(Ignoring cashout)
I was told by fellow suggesters Icycrevasse and Jarool (thanks!) that the previous sale can still be used despite the cashout.
__________
Sale 1.2 | Seller | Buyer | Untraceable
Not using
___________________________________
Item 2
Dumped to Bot
Not using (it's under STN's buy order anyways)
__________
(Covering Marketplace Sales later)
___________________________________
Item 3
(Ignoring Bot dump)
__________
Sale 3.1 | Seller | Buyer | Sold for 208 pure
208
___________________________________
Item 4
Sale 4.1 | Seller | Buyer | Proof (from previous suggestion) | Bulk for multiple taunts of the same effect
Not using (previous suggestion also didn't use it)
__________
Sale 4.2 | Seller | Buyer | Proof | Sold for a Green Confetti Cat's Pajamas (withdrawn from Marketplace.TF moments before the trade)
Using this suggestion to price the Pajamas
___________________________________
Marketplace.TF Sales
October 26th | $499.99 / $1.84 = ~271.7, rounding to 270
October 28th | $499.99 / $1.83 = ~273.2, rounding to 270
___________________________________
Total sales:
200, 208, 270, 270
Lowest Sell Order @ $499.99 (Marketplace.TF), keys are $1.85 so it also rounds to 270
Highest Buy Order @ 120 (STN)
Going with a 200-270 range!
The previous suggestion was accepted under the premise that the 270 sales are both high outliers. Since there's no new sale at 270, they will remain as high outliers.
The only new sale is the 208 Key sale, so I don't think a new suggestion is necessary at the current time. You should wait until this hits the 3 month threshhold.
The previous suggestion also included sales of 125 and 150, both of which are now 4 months old. I don't really agree that 270 should be considered an outlier now, considering the current valid sales and buy orders.
Since this is being used to price a different hat (essentially being a mini for it), I assumed the resuggestion would be better in this case, as it would better reflect the current price for them, instead of relying on a range based on a 4-month old sale.
This would be more relevant if there was new sales data that vastly changed the value of the item, but that's not the case. Just because a sale is considered outdated now it doesn't mean that you can just make a new suggestion retroactively to exclude it.
I'm not retroactively excluding anything, I'm just making a new suggestion normally. The current accepted price is from a suggestion originally made 3 months ago, which due to being resuggested twice only ended up being accepted last month. I'm not cherrypicking sales here, just using the valid ones from the last 3 months in order to suggest a more accurate price for the hat this is a mini for.
Back when the original suggestion was made, the reasoning made perfect sense: 270 was a clear outlier, and it would be better to exclude them and go with the 150-200. This is not the case anymore, the sales that supported a value lower than 200 are now either outdated or below buy orders. The fact that the 270 sales are no longer outliers, in my opinion, does vastly change the value of the item, and it also affects the hat this is a mini for.
I just don't think we should be using sales from 4 months ago to price a trade that happened today, while excluding more recent sales just because they were seem as outliers a month ago.
Here's where the logic falls apart. Someone makes a price suggestion with two sales. One sale at 150 Keys, which is 2 months and 15 days old, and another sale at 200 Keys that is 4 days old. Naturally, the price suggestion should be 150-200. The suggestion gets accepted. So, should someone make a new price suggestion at 200 Keys flat 15 days later just because the 150 Key sale is now 3 months old? No, that's not the case. This is not how price suggestions work. Once data points have been established at a certain point in time, it's done. Doing things the way you want to do it right now is going to create an influx of pointless suggestions that add no new data from the previous suggestions based off a loose interpretation of the rules.
This is the reason we use the in-date system. All price suggestions are valid to use as prices for other hats as long as the price suggestion has been accepted within the last 3 months, with some exceptions for very fringe cases. This isn't perfect, but it aims to cast as wide of a net as possible to price items as accurately as you can.
For the price suggestion you're trying to make, you will need to use the current price of 150-200. Otherwise, that suggestion is not going to work, just like this suggestion is not going to work.
I'll be closing this.