Reading Competitor Prices Without Getting Fooled: Outliers, Decoy Offers, and Comparable-Offer Filters for Game Sellers

Why the lowest price is a bad signal

Most sellers check competitors by sorting a listing page by price and looking at the top row. That row is the most likely to be an outlier. It may be a seller clearing a small leftover, a listing with a typo in the unit size, or an offer that nobody can actually buy because the stock is gone or the seller is away.

If you match that number, you lose margin and may still not win the sale. Buyers who compare offers look at delivery speed, seller reputation, and stock depth, not only price.

The fix is to decide what counts as a comparable offer before you look at any price. Then you reprice against a range of comparable offers, not a single data point.

This post builds on the guardrails in Price Floors, Undercut Steps, and Review Queues and the margin math in Net-Payout Price Floors. Those posts cover how low you can go. This one covers what to compare against.

The five kinds of misleading competitor offers

Before you filter, learn to recognize the usual distortions.

If you have already worked through unit size and price-per-unit mapping, the second row should be familiar. Unit mismatches are the most common reason a price suggestion looks far too low.

Step 1: Write down your comparable-offer definition

For each product family you sell, write a short definition that a colleague could apply without asking you questions. Keep it in the same place as your naming conventions and attribute vocabulary.

For game currency

A comparable offer should match on:

• Same game and the same server or realm, where that applies
• Same currency type
• Price normalized to one standard unit
• A minimum order that fits normal buyer behavior (not far above or below what you offer)
• Stock deep enough to fill your typical order size
• Delivery method and speed in the same class as yours

For game accounts

A comparable offer should match on the attributes you already normalize before listing: server, region, platform, rank or level band, and any key inventory such as rare skins or characters. The guide on normalizing account attributes covers how to keep those values consistent. If your own listings use clean attributes, comparing them to competitors becomes much easier.

For in-game items

Match on item name, quality or tier, quantity per offer, and any bind or trade restrictions. Items with variable quality are the hardest to compare, so be strict. If you cannot say with confidence that two offers are the same item, leave one out.

Step 2: Use a median band, not the minimum

Once you have filtered to comparable offers, put their prices in order and look at the middle of the range.

Here is a worked example for currency priced per 1M units. These are made-up numbers for illustration:

The raw minimum is 0.80. The comparable set is B through E, with a median of about 3.225 and a range of 3.10 to 3.40.

A sensible target sits inside that band. You might price at the lower-middle of the range, then apply your undercut step only if the result stays above your net-payout floor. If your floor is 3.15 after fees and a refund reserve, matching 3.10 is simply a loss. In that case the right move is to hold at 3.20 or 3.25 and compete on delivery speed or stock depth instead.

Step 3: Treat price suggestions as proposals

When a tool gives you a price suggestion, it is a starting point. Sellerbot is built around reviewing price suggestions across your supported marketplaces before you apply them. That fits this workflow, because you can check the suggestion against your comparable-offer definition instead of trusting it blindly. You can see how that review flow looks on the preview page and read about the broader tool set on the features page.

A quick review checklist for each suggestion:

1. Is the suggested price below your floor? If yes, reject or clamp it to the floor.
2. How far did it move? A large drop from the current price is a red flag. Large moves deserve a second look before approval.
3. Does it sit inside the comparable band? If it is well below the band, an outlier probably triggered it.
4. Is the stock behind the cheapest competitor realistic? One tiny offer should not set your price.
5. Did your own listing change? A different unit size or minimum order changes what a fair comparison looks like.

Approve quickly when a suggestion passes all five. Spend your attention on the ones that fail.

Step 4: Split your listings into tiers

Not every listing deserves the same pricing strategy. A simple tiering approach keeps your review time under control:

• Volume tier: fast-moving listings where you compete close to the median band. Review these most often.
• Premium tier: listings where you win on speed, reliability, or rare attributes. Hold price within the band even if cheaper offers exist.
• Long-tail tier: slow listings with few comparable competitors. Check them on a weekly schedule rather than reacting to every move.

Pair this with the weekly sell-through review. If a listing has not sold and your price is already inside the band, the problem may be the title, the delivery promise, or the stock depth, and not the price.

Step 5: Account for differences between marketplaces

The same product can have a different fair price on each marketplace. Fees, buyer traffic, and the mix of competing sellers vary. Do not assume a median band on one marketplace applies on another.

Instead, keep one comparable-offer definition per product family, and compute the band separately for each marketplace. Then check each result against that marketplace's net-payout floor. The platforms page lists the marketplaces Sellerbot supports: Eldorado, G2G, iGVault, Racoon, and GameBoost.

If you recently added a channel, the staged rollout playbook explains how to pilot pricing there before you move all your stock.

Common mistakes to avoid

• Chasing a single competitor. One seller's behavior is not a market. Look at the band.
• Ignoring stock depth. A cheap offer that can fill only one order is not a threat to your whole inventory.
• Comparing different units. Always normalize to price per standard unit first.
• Letting repricing run past your floor. Floors exist so a bad data point cannot damage your margin.
• Never revisiting your definition. Patches, new seasons, and new server launches change which offers are comparable. After a major update, re-check your rules. The patch day playbook covers how to handle those windows.

A simple weekly routine

1. Pick your top listings by sales volume and your top listings by stock value.
2. For each, list the comparable competitor offers using your definition.
3. Mark outliers and note why you excluded them.
4. Compute the median band and compare it with your current price and your floor.
5. Approve, adjust, or reject each pending price suggestion.
6. Record any definition changes, such as a new minimum stock threshold, so the next review is consistent.

This takes less time than it sounds once your definitions are written down. Most of the work is filtering, and the filters rarely change.

Putting it into practice

If you manage listings on several marketplaces, consistency matters more than precision. A rough but consistent comparable-offer rule beats a clever rule that you apply differently every week. Check the plans page to see which plan fits the number of listings and marketplaces you manage, and browse more seller workflows on the Sellerbot blog.

The goal is not to be the cheapest seller. It is to price where comparable buyers are actually willing to pay, and to keep your margin intact while you do it.