Free tools Windows power users keep installed
One-click scans. No signup required.
The reliable way to find profitable World of Warcraft crafting opportunities is to combine a correctly scoped Auction House snapshot with price history, available quantity, and a recipe-level cost calculation. Start by separating regional commodity prices from realm or connected-realm item prices, record when each observation was generated, compare commodities by unit price, and treat every displayed crafting margin as a screening result rather than guaranteed profit.
This workflow is aimed at the current Retail Auction House. Undermine Exchange’s documented coverage is for the latest Retail version, not Classic, and no general list of universally profitable materials exists: profitability depends on region, realm, recipe access, supply, demand, and the freshness of the data.
As an Amazon Associate I earn from qualifying purchases.
What you need to measure
A useful price tracker answers four questions for every item or recipe:
Recommended Free Tools
- Where is this market? Is it a regional commodity market or a realm/connected-realm market for a non-commodity item?
- When was the observation made? A timestamp distinguishes a current snapshot from an old listing.
- How much is actually available? A low price with one unit available may not support a meaningful purchase or crafting run.
- Does the recipe still make sense? Reagent cost must be compared with a plausible output price, while allowing for uncertainty, player time, and the possibility that the item does not sell.
Track price and quantity together. A price chart without availability can make a thin, impractical listing look like a market opportunity.
#1 Best Overall
- Great product!
Choose the correct market scope before recording prices
Regional commodities
Commodity materials use regional pricing rather than a single character’s realm market. The documented Undermine Exchange API separates regional commodity data from individual-realm item data. Use the regional view when the item is treated as a commodity in the current Retail Auction House.
Realm and connected-realm items
Non-commodity items can be tied to a realm or connected-realm context. Record the exact realm scope with every observation; otherwise, a price from another market can look like a bargain that your character cannot access.
Retail versus Classic
Undermine Exchange documentation describes the latest Retail version, not Classic. Do not use a Retail endpoint or Retail recipe assumption as evidence for a Classic market. If you play Classic, select a tool and dataset that explicitly document the relevant Classic version before drawing conclusions.
Understand what a price observation actually represents
Do not label every number as a live price. Undermine Exchange distinguishes the Blizzard snapshot time from its own lastUpdated value. An item with delayed data or zero quantity may also carry an older lastSeen value.
For each row in a tracker, preserve all three pieces of timing information when the service provides them:
- Snapshot time: when the underlying Auction House state was captured.
- Service update time: when the tool generated or refreshed its record.
- Last-seen time: when that item was last observed, which can be older than the current service update.
If those times are stale, write “stale observation” in your notes instead of presenting the number as current. The documented hourly commodity history covers roughly the previous 14 days, and daily history is also available. Hourly updates are described as approximately hourly, not guaranteed; gaps or delayed updates are possible.
Compare commodities by unit price, not stack total
Commodity listings should be normalized to a per-unit value. Blizzard explained the interface this way in its Visions of N’Zoth: Auction House Update Preview on January 9, 2020: “When selling commodity items, rather than setting a price for stacks of items, you’ll be able to choose a unit price, allowing buyers the ability to decide how many of an item they wish to purchase.”
Use this calculation whenever a source displays a stack total:
unit price = stack price ÷ number of units in the stack
Then compare the unit price with the quantity available at or near that price. A 10-gold stack of 20 units is 0.5 gold per unit; comparing its 10-gold total with a single-unit listing would produce the wrong result.
When buying for a recipe, calculate the cost of the quantity you actually need. The cheapest units may be consumed first by the Auction House for the requested amount, so the marginal cost can rise after the first few units.
Which data sources fit which job?
These services describe different kinds of data. Their provider descriptions are not independent audits, so record the source and its limitations alongside your calculations.
| Source | Best use | Coverage or inputs described by the provider | Important limitation |
|---|---|---|---|
| Undermine Exchange | Current and historical market observations | Regional commodity data and individual-realm item data for the latest Retail version; current price, quantity, timestamps, and history; documented hourly history of roughly 14 days plus daily history | Refresh cadence is approximate; free and paid endpoint tiers are documented, and an old lastSeen or zero-quantity record is not a live buying opportunity |
| WoW Auction House | Retail Auction House price views and other scans | Provider says its Retail data comes from Blizzard auction data and describes addon or client uploads for other scans | Check whether the specific view is a current listing, a historical observation, or an uploaded scan before comparing it with another source |
| TheWoWDB | Recipe and reagent cost screening | Recipe and reagent inputs described as coming from current game-client data; prices described as coming from Blizzard auction data | Its stated calculation excludes the value of player time and the crafting-orders market, so a positive displayed margin is only an initial estimate |
Compare tools on the fields that affect your decision: Retail or Classic coverage, regional or realm scope, update freshness, hourly or daily history length, quantity fields, whether prices are listings or verified sales, recipe and reagent coverage, and access limits. Do not assume that two tools showing the same item are measuring the same market event.
A repeatable price-tracking workflow
1. Define the item, version, and market
Write down the game version, region, realm or connected realm, item ID or exact item name, and whether the item is a commodity. This prevents a regional material price from being mixed with a realm-bound equipment price.
2. Capture a timestamped snapshot
Save the displayed price, quantity, snapshot time, service update time, and last-seen time. If the source offers an export, retain the raw record so you can audit a later calculation. A screenshot or spreadsheet row is sufficient for a small personal tracker, provided the timestamps remain attached.
3. Normalize the price
Convert stack totals to unit prices, use the same currency notation throughout, and record the number of units available at that price. For a recipe, multiply each reagent’s unit price by the number of units required.
Rank #3
4. Add history instead of trusting one scan
Use the hourly history when you need short-term movement and the daily history when you need a broader baseline. The documented hourly window is about 14 days, so it can reveal whether a low listing is recurring or unusual without pretending to show a permanent market trend.
5. Check quantity and depth
Look beyond the first displayed price. Note how many units are available at the lowest price and how quickly the price changes as the required quantity increases. A recipe that needs 200 units should not be costed at a one-unit bargain if the next 199 units are substantially more expensive.
6. Record the observation in a consistent table
Use one row per item and timestamp. A practical template is:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
| Field | What to enter |
|---|---|
| Date and time | UTC or your chosen timezone, used consistently |
| Game and market scope | Retail or Classic; region; realm or connected realm; commodity or non-commodity |
| Item | Exact item name and, when available, item ID |
| Unit price | Normalized price for one unit |
| Quantity | Units available at the observed price or price band |
| Source timing | Snapshot, service update, and last-seen values |
| Notes | Unusual listing, missing data, price jump, or scope exception |
7. Recheck before buying or crafting
Refresh the item and every major reagent close to the time you commit gold. Replace stale rows rather than averaging them silently into a new result.
Calculate whether a recipe is worth investigating
Reagent cost
For each reagent, multiply the quantity required by the unit price at the quantity you can realistically buy:
reagent cost = Σ(required quantity × effective unit price)
Use an effective price when the first listing does not cover the full recipe. For example, if a recipe needs 100 units and only 20 are available at the displayed minimum, cost the remaining 80 at the next applicable price levels instead of multiplying the minimum by 100.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Output value and displayed margin
Compare the reagent cost with a plausible output listing price from the same market scope and timestamp:
Rank #4
- Used Book in Good Condition
gross margin = expected output price − reagent cost
gross margin percentage = gross margin ÷ reagent cost × 100
This is a screening margin, not a guaranteed return. TheWoWDB says its recipe calculation excludes player time and crafting orders. It also does not establish that a listed output price is a completed sale. Keep those exclusions visible in your worksheet.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Illustrative calculation
The following numbers are only an example of the arithmetic, not a claim about a current market. Suppose a recipe uses four units of Reagent A at 12 gold each and two units of Reagent B at 30 gold each:
- Reagent A: 4 × 12 = 48 gold
- Reagent B: 2 × 30 = 60 gold
- Total reagent cost: 108 gold
- Observed output listing used for the screen: 150 gold
- Displayed gross margin: 42 gold
- Displayed gross margin percentage: 42 ÷ 108 × 100 = 38.9%
Before crafting, verify that the 150-gold observation is fresh, that enough outputs can plausibly sell, and that the 108-gold input cost covers the actual quantity you must purchase. If the output does not sell, the displayed margin never becomes realized income.
How to distinguish a recurring opportunity from a one-off listing
Look for repeated price levels
A single low observation can be caused by a small undercut or a thin listing. Compare several hourly observations and, where useful, daily history. Repeated prices across multiple snapshots provide better evidence of a normal market level than one isolated minimum.
Track quantity alongside the price
Record whether the low price appears with substantial quantity or disappears immediately. A recurring low price with meaningful availability is more actionable than a low price that is present for one unit only.
Separate volatility from trend
Do not call a short sequence of changing listings a long-term trend. Describe what the history supports: for example, “the observed price moved within this range during the available window.” The documented hourly history is roughly 14 days, so it is useful for recent context but cannot prove a permanent seasonal pattern.
Best Value
Liquidity: the missing half of profitability
Price data describes what is listed or observed, not automatically what sold. The available provider descriptions do not justify treating the lowest listing as a completed sale price.
Before calling a material or crafted item profitable, look for a documented sales-volume, sell-through, or completed-sale measure in the tool you choose. If no such measure is available, classify your confidence as low and use conservative assumptions:
- Prefer outputs with a demonstrated reason to be purchased, such as a current consumable or a commonly needed component.
- Do not assume that a large displayed margin means rapid sales.
- Limit the amount of gold tied up in inventory until repeated observations support both price and demand.
- Record how long your own listings remain unsold, but do not present personal results as a market-wide statistic.
Screening materials before you commit to a recipe
Start with the recipe, not the headline price
List every reagent and the exact quantity required. A cheap primary material can be offset by an expensive secondary component, and a high output price can be misleading if the recipe consumes large quantities.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Use the same snapshot for inputs and output
Mixing yesterday’s reagent prices with today’s output listing can manufacture a margin that never existed at one time. Capture the full input basket and output observation together whenever possible.
Stress-test the result
Recalculate using a higher input price, a lower output price, or a smaller sale quantity. A result that remains positive under conservative assumptions deserves more attention than one that depends on the cheapest single listing.
Account for access and production constraints
Theoretical recipe profitability still depends on whether your character knows the recipe, can obtain the required inputs, and can produce enough units. TheWoWDB’s stated method does not value your time or crafting orders, so add those considerations separately rather than treating the displayed number as final income.
Common tracking errors and fixes
| Error | Why it misleads you | Fix |
|---|---|---|
| Calling an old record “live” | A delayed or zero-quantity item may retain an older last-seen time | Check snapshot, update, and last-seen timestamps; label stale observations clearly |
| Mixing regional and realm markets | The same item can have different scopes and accessible supply | Store region and realm scope in every row |
| Comparing stack totals | A larger stack can look more expensive even when its unit price is lower | Convert every commodity listing to a per-unit price |
| Ignoring quantity | A minimum price may cover too few units for your recipe | Cost the full required quantity across the available price levels |
| Using a positive recipe margin as a promise | Listed output may not sell, and the calculation may omit time or orders | Call it a screening margin and check liquidity |
| Assuming the lowest listing is a sale | A listing is an offer, not proof of a completed transaction | Use documented sales or sell-through fields when available |
| Applying Retail data to Classic | Coverage and recipes can differ by game version | Use a source that explicitly supports your version |
| Combining incompatible refresh cadences | One source may be hours older than another | Compare timestamps and refresh the basket before acting |
A practical decision rule
Advance an item from “interesting” to “worth testing” only when all of these conditions are met:
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minute- The game version and market scope are correct.
- Input and output observations are recent and timestamped.
- Commodity prices are normalized per unit.
- The available quantity covers, or realistically approaches, your intended purchase and production size.
- Recent history shows the price is not solely a one-off listing.
- The displayed margin remains acceptable under a less favorable input or output assumption.
- You have evidence of demand or a documented sales-volume measure; if not, you have deliberately limited your risk.
If any condition fails, keep the item in the watchlist rather than labeling it profitable.
What this workflow can and cannot tell you
It can show how listed prices and quantities changed within the history a provider documents, help you compare recipe inputs consistently, and expose whether a supposed bargain has enough supply to matter. It cannot guarantee a sale, establish a market-wide profit rate, or produce a universal list of winning materials without a specified version, region, realm, character recipe access, fresh item-level inputs, and demand evidence.
Undermine Exchange’s documented API is most useful when you need structured current and historical observations. WoW Auction House describes a different acquisition model for some scans, and TheWoWDB is useful for recipe-based screening while explicitly excluding player time and crafting orders. Whichever source you use, preserve the scope and timestamps, separate listings from completed sales, and treat the result as a decision aid rather than a promise.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
