Pricing Revealed
“Was” and “now” price claims are discount statements that compare a current price to a prior reference price shown on the same listing, receipt, or advertisement. The “was” number is not always the price the item actually sold for; it can be a manufacturer suggested retail price (MSRP), a prior store price, or an internal reference price that the retailer chooses. In the U.S., the Federal Trade Commission (FTC) has addressed deceptive pricing practices, including claims that a product was sold at a higher price when it was not, and it has brought enforcement actions under the FTC Act for unfair or deceptive acts.
A measurable detail helps: in many jurisdictions, a “was” price claim must be supported by records showing the product was offered at that price for a defined period, but the exact rules vary by country and even by state or local law. For example, the FTC’s guidance and enforcement focus on whether the reference price is truthful and not misleading; it does not automatically require a specific number of days in every case, so you still need to verify what the “was” figure represents. In the UK, the Consumer Protection from Unfair Trading Regulations 2008 and related pricing rules have been used to challenge misleading “was” claims, and the UK’s CMA has also discussed discount pricing practices in enforcement contexts.
Practical examples show the mechanics. A retailer may list a “Was $49.99, Now $29.99” discount on a product that never sold at $49.99 during the relevant timeframe, or it may use a reference price from a different channel (such as an online MSRP) rather than the store’s own historical price. Another common pattern is a “was” price that reflects a price before a promotion cycle, while the “now” price is the only price the item has actually been offered at for weeks—an issue that matters because shoppers often interpret “was” as a real market price.
One small aside from watching retail listings: around 2024, many e-commerce sites started showing “price history” widgets in some regions, but those widgets still depend on what data the site has access to and how it defines the “was” point. If the widget only tracks prices the site itself displayed, it may miss competitor pricing or off-site promotions.
Main Problems And Pain Points
The biggest misunderstanding is treating “was” as a guaranteed prior selling price. In many listings, “was” is a reference number that can come from MSRP, a prior internal price, or a price from a different store or sales channel, and the shopper has no way to tell which without reading fine print or checking external records. This matters because the consumer’s decision process often relies on perceived savings, and perceived savings can drive purchases even when the “now” price is not the lowest available.
Another pain point is time framing. A “was” price might be true at some point, but not during the period that matters to the shopper’s budget. If the “was” price was used only briefly—say, during a one-day markdown before a relabeling—then the “now” discount can look larger than the real discount relative to what the item usually costs. This can distort price comparisons, especially for consumables or items that people buy repeatedly.
Biological mechanisms are not the main driver here, but consumer psychology still has a measurable effect on behavior. Anchoring is the best-known mechanism: the brain uses the first number it sees as a reference point, and a higher “was” number can make the “now” price feel like a bargain even when the “now” price is close to the item’s typical market price. Loss aversion also plays a role: “save $20” framing can trigger urgency, which increases the chance of skipping verification.
Supporting technologies also shape what you see. Retailers use pricing engines that can change prices multiple times per day based on inventory, demand, and competitor signals, and those systems can generate reference prices that are technically legitimate but practically misleading. Some platforms also cache listing text, so the “was” number may persist even after the underlying price history changes—an issue that, frankly, most people skip because they assume the listing is always current.
Real-world situations show the consequences. A shopper may buy an item because the “was” price suggests a 40% discount, then later find the same item at a similar price elsewhere, or the same retailer runs another promotion that resets the “was” number again. Over time, this can lead to repeated overpayment relative to the item’s true baseline cost, especially for electronics accessories, home goods, and subscription add-ons.
Solutions And Advice
Identify What “Was” Means
Start by locating the definition of the reference price on the listing, receipt, or promotion terms. Look for phrases that indicate whether “was” is MSRP, a prior selling price, or a reference price used for discount calculations. If the listing does not explain the source of the “was” number, treat the claim as unverified and compare using other evidence.
Why this works: different reference prices produce different discount sizes even when the “now” price is unchanged. In practice, you might see “was” tied to a manufacturer list price, which can be set high and rarely charged, while a true “was” selling price should match the retailer’s own historical offers.
What it looks like: a listing that says “Was $49.99” with no timeframe or basis is harder to validate than one that states “Was $49.99 on [date]” or “Was $49.99 for the last 30 days.” A mild frustration point: many sites hide the explanation in footnotes that are easy to miss on mobile.
Tools or methods: use the retailer’s own order history if you have it, and save screenshots of the listing showing the “was” and “now” numbers. If you are comparing across retailers, record the unit price (price per item, per ounce, per count) because “was” claims often apply to bundles differently than single units.
Check Price History Windows
Verify whether the “was” price was actually shown for a meaningful period before the promotion. A practical approach is to compare the “was” number to archived snapshots or price-history services that track the same product page over time, then check whether the “was” price appears repeatedly or only once.
Why this works: a reference price that appears only briefly is more likely to be a marketing anchor than a real selling baseline. A measurable target is to look for at least several weeks of consistent pricing before the “was” reference point; if the “was” price appears for 1–2 days and then disappears, the discount claim often overstates savings.
What it looks like in practice: you might find that the “was” price was used during a different promotion category, such as a seasonal sale, and the product page was later updated with a new “was” number. If the product SKU changed, the “was” price may refer to a different variant.
Tools or methods: use web archive snapshots for the exact URL and SKU, and confirm that the product title and model number match. If you use a price-history widget, check whether it tracks the same region and shipping conditions as the offer you are considering.
Compare With Unit Pricing
Convert both “was” and “now” into unit pricing so you can compare across sizes, pack counts, and bundles. For example, if a “now” price is $29.99 for a 12-pack and the “was” price is $49.99 for a 24-pack, the discount math is not comparable until you normalize.
Why this works: “was” claims often change when the retailer changes pack size, bundle composition, or included accessories. Unit pricing reduces the chance that you are comparing different products under the same marketing label.
What it looks like: you calculate “now per unit” and “was per unit,” then compute the percentage difference based on the normalized values. If the normalized discount is much smaller than the headline discount, the “was” anchor is doing most of the work.
Tools or methods: use a spreadsheet or a calculator app; record the unit basis (count, weight, volume) and include tax and shipping if they are part of the final price you pay.
Look For SKU And Variant Changes
Confirm that the “was” and “now” prices refer to the same SKU, model number, and variant. Retailers sometimes reuse product titles while changing internal codes, colorways, or included components, and the “was” price can refer to a different configuration.
Why this works: a price claim tied to a different variant can be technically true for that variant while misleading you about the exact item you plan to buy. This is especially common for accessories, replacement parts, and items sold in multiple compatibility versions.
What it looks like: the listing may show the same photo and description, but the item code changes in the URL parameters or in the “Specifications” section. If the “was” price is attached to a different code, the discount claim does not apply to your exact selection.
Tools or methods: check the SKU on the product page and on the checkout confirmation screen. If you are buying from a marketplace, verify whether the seller changed between the “was” and “now” periods.
Use Receipts And Records For Disputes
When you buy, save the receipt, order confirmation email, and any promotion terms that show the “was” and “now” numbers. If the claim is misleading, having a timestamped record helps you contact customer support with specific references rather than general complaints.
Why this works: many disputes turn on documentation. A clear record also helps if the retailer later edits the listing text, which can happen after promotions end.
What it looks like: your receipt shows “Was $49.99, Now $29.99,” and the item description matches the SKU you selected. If the retailer later claims the “was” price was an MSRP, you can ask for the basis and the date range used for the reference price.
Tools or methods: store receipts in a dedicated folder and include the URL and screenshot from the day you ordered. A small aside: I’ve seen retailers change the “was” label wording from “Was” to “Regular” without changing the underlying reference, which makes screenshots useful.
Know The Consumer-Protection Angle
Understand the legal standard in your region: many consumer-protection regimes treat misleading price comparisons as deceptive advertising. In the U.S., the FTC Act prohibits unfair or deceptive acts, and the FTC has challenged “was” pricing claims that lack substantiation. In the EU and UK, rules against unfair commercial practices and misleading omissions can apply when the reference price is not presented clearly or is not supported.
Why this works: legal standards shape what you can reasonably demand from the seller. If a retailer cannot substantiate the reference price, the claim can be considered misleading even if the “now” price is real.
What it looks like: you may see a retailer provide documentation of the reference price basis, such as internal pricing records or MSRP sources, when asked. If they refuse to clarify, you can escalate through the platform’s dispute process or consumer-protection channels.
Tools or methods: check your local consumer agency guidance on pricing claims, and keep your request narrow: ask what the “was” price represents and the date range used for the comparison.
Set A Personal Verification Threshold
Decide in advance what level of verification you need before buying. A practical threshold is to require either (1) a clear timeframe for the “was” price, (2) evidence from price history showing the “was” price existed for weeks, or (3) a unit-price comparison that shows the “now” price is genuinely lower than typical market pricing.
Why this works: it reduces decision fatigue and prevents you from relying on a single marketing number. It also helps you avoid the “discount trap,” where the headline percentage is large but the actual savings are small after normalization.
What it looks like: if the listing shows “Was $120, Now $79” but the “was” price appears only once in archived snapshots, you either wait for a better offer or compare with another retailer’s current price.
Tools or methods: keep a short list of trusted comparison sources and record the last seen price for the exact SKU. If you track prices, note shipping and return terms because those can outweigh a small price difference.
Case Examples
Example 1: Bundle With Hidden Basis
A shopper sees “Was $60, Now $36” for a cleaning kit. The product page shows a bundle, but the “was” price is tied to the MSRP of individual components rather than the bundle’s historical selling price, and the bundle composition changes between promotions. After checking the SKU and unit pricing, the shopper finds that the “now” price is only about 10% lower than the typical bundle price seen in archived snapshots over the prior month.
Outcome: the shopper buys only after confirming the bundle composition matches the “now” selection and that the normalized unit price is lower than the previous month’s offers. The “was” claim still functions as marketing, but it does not drive the purchase decision.
Example 2: Price History Shows Short-Lived “Was”
A shopper watches an electronics accessory listed as “Was $49.99, Now $29.99.” Archived snapshots show the “was” price appeared for 2 days after a site redesign, then the listing switched to a different reference price label while the “now” price stayed near $29–$33 for weeks. The shopper compares the current “now” price to competitor listings and checks the exact model number in the checkout confirmation.
Outcome: the shopper treats the headline discount as unverified and waits for a price drop below the typical $29–$33 range. The final purchase happens when the “now” price reaches a lower level that matches the shopper’s verification threshold.
Comparison Table Or Checklist
Use this checklist to decide whether a “was/now” claim is likely to reflect real savings.
| Check | What To Look For | Why It Matters | Decision Signal |
|---|---|---|---|
| Reference Price Source | MSRP vs prior selling price vs internal reference | Different sources change the meaning of “discount” | Clear source = higher trust |
| Time Window | “Was” shown for weeks vs a brief spike | Short-lived “was” inflates perceived savings | Weeks of presence = stronger evidence |
| SKU Match | Same model, variant, and pack count | Variant changes can invalidate comparisons | Exact match = higher trust |
| Unit Pricing | Normalized per unit, not headline totals | Bundles and sizes distort percentages | Normalized discount aligns with headline = better deal |
| Final Price Context | Tax, shipping, and returns included | A low “now” can be offset at checkout | Lower all-in price = stronger value |
Common Mistakes
One mistake is trusting the headline percentage without checking the unit basis. A “50% off” claim can be misleading when the pack size changes, when the bundle includes different components, or when the “was” price is for a different variant.
Another mistake is comparing “was” to competitor prices without confirming that the reference item is identical. If the model number differs by one digit, the product can be a different revision with different specifications, and the discount comparison becomes meaningless.
A third mistake is ignoring the timeframe. If the “was” price existed for 1–2 days and then disappeared, the claim can still be technically defensible in some contexts, but it often fails the shopper’s practical test for real savings.
A fourth mistake is not saving evidence. If you later dispute a claim, the retailer may show a different version of the listing, and you will have no timestamped proof of what you saw.
Finally, people sometimes assume that “was” claims are regulated the same way everywhere. Enforcement and substantiation standards vary by jurisdiction, so you should check local consumer guidance rather than relying on a generic rule.
FAQ
What does “was” price usually mean?
“Was” can mean a prior selling price, an MSRP, or an internal reference price used to calculate a discount. The listing should state the basis, and if it does not, the claim is harder to verify.
Can a “was” price be legal if it was never sold?
In many places, it can be legal if the reference price is clearly disclosed as MSRP or another legitimate benchmark. It becomes risky when the claim implies a prior selling price without substantiation.
How long should the “was” price be shown?
There is no single universal rule across all regions and platforms. Some consumer-protection approaches focus on substantiation and non-misleading presentation, so the safest approach is to check whether the “was” price appears for a meaningful period in price history.
Do “was/now” claims include shipping and tax?
Usually the headline price comparison refers to the item price before tax and shipping, but the exact treatment depends on the retailer and the ad format. Always compare the all-in checkout total for a fair decision.
What should I do if the discount looks fake?
Save the receipt and screenshots, then ask the retailer or marketplace for the reference-price basis and date range. If the response is unsatisfactory, use the platform’s dispute process or your local consumer-protection route.
Author's Insight
“Was” and “now” pricing claims are less about math and more about definitions: what number is being referenced, and what timeframe supports it. When shoppers treat “was” as a guaranteed prior selling price, they often miss that retailers can use MSRP or internal reference prices that inflate the anchor. A practical verification workflow—SKU match, unit pricing, and price-history checks—turns a marketing label into a testable claim. If you want a small tool habit, I recommend keeping a dated spreadsheet row for each SKU you track; I used Google Sheets version history on 2024-11-03 to recover earlier notes after a listing changed.
Key Takeaways
“Was/now” claims can reflect real discounts, but the “was” number may come from MSRP, internal references, or short-lived pricing changes. You get better outcomes by verifying the reference price basis, checking that the SKU and pack size match, and comparing normalized unit pricing and all-in totals. These steps reduce the risk of anchoring on a headline percentage that does not match the item’s true baseline cost. The limit is that not every retailer discloses the reference-price method clearly, so you may need to rely on price history and documentation from your own receipts.
