How to request a price adjustment after a purchase

You do not need a lawyer tone. You need five facts and the right label. A price adjustment is a request under the retailer's current post-purchase policy, usually for the same SKU at that same store. If you are still unsure whether you want an adjustment or a competitor match, read price adjustment vs. price match first.

This page is the mechanics: what to gather, where to send it, a script you can paste, and what to do when the first agent says no. For definitions and denials in more depth, use the complete guide to retailer price adjustments.

Confirm the policy before you write

Open the retailer's own help page the day you ask. Search for "price adjustment," "price protection," or the post-purchase section of returns. If the page is a generic hub, keep searching rather than guessing a window. Holiday banners on that page matter more than a memory of last year.

Starting points for a few retailers we already watch (confirm the live text; these are not quoted rules): Target, Best Buy, Costco, Kohl's, Macy's, Home Depot. Retailers we already watch are listed on retailers we watch.

If you cannot find any post-purchase language, do not invent a 14-day window in the email. Ask whether they offer a same-SKU adjustment on this order type, and attach the receipt.

What to gather (10 minutes)

• Order ID or receipt barcode.
• Item name and SKU / model / retailer item number as printed on the receipt.
• Purchase date; delivery date if it shipped.
• Unit price you paid (before you argue about tax — ask about tax only if the policy mentions it).
• Current same-SKU price, with a link or screenshot that shows the identifier.
• Who sold it: the retailer, or a marketplace seller on their site.

If the seller line is a third party, stop and write that seller, not the retailer's adjustment desk. Wrong company is the most common silent failure.

1. 1. Policy. Current official page. Note any holiday carve-out. Do not reuse a day count from a forum.
2. 2. Proof. Order ID, SKU, paid price, current listing. Same condition (new vs. open-box).
3. 3. Request. Short message, right label, one ask: refund the difference to original tender.

Which channel to use

Start where the order lives. Online order → website help. Store ticket → that store or the chain's store support, with the receipt. If they bounce you, ask for the team name and the ticket ID. Do not open three chats that tell three stories.

Email you can paste

Replace the brackets. Do not paste a novel. Do not paste copyrighted policy text. Do not threaten reviews in the first message.

Subject: Price adjustment request — order [ORDER ID]

Hello,

I purchased [ITEM NAME] (SKU / model [SKU]) on [PURCHASE DATE] for $[PAID] (order [ORDER ID]). The same item is now listed at $[CURRENT] on your site / in your store.

Please refund the difference of $[DIFFERENCE] under your current price-adjustment or price-protection policy. I still have the item and the original receipt. Refund to the original payment method.

Thank you,
[YOUR NAME]
[PHONE, if they ask]

Chat opener you can paste

Lead with the label so the macro does not dump you into competitor match. If the agent still talks about another store's ad, repeat that you do not have a competitor ad.

Hi — requesting a price adjustment, not a competitor price match.

Order [ORDER ID], purchased [DATE].
Item: [NAME], SKU [SKU].
Paid: $[PAID]. Your current price for this same SKU: $[CURRENT].
Difference: $[DIFFERENCE].

Please apply your current post-purchase price-adjustment policy and refund the difference to the original tender. I can paste the order number and a link to the current listing.

In-store, without a speech

Bring the receipt (or the app order). Open the current listing on your phone with the SKU visible. Say: "I bought this on [date] for $[paid]. It is the same SKU, now $[current]. I would like a price adjustment for the difference." If they say they only price-match competitors, say you are not matching a competitor — you are asking about their own current price. If they cannot do it at the desk, ask how online or central adjustments are filed and write that down.

Same SKU, different looking page

The listing you watch must be the identifier on the receipt. A newer colorway, a 2025 model number next to a 2024 SKU, a bundle that includes a stand, or an open-box line with its own item number is not “close enough.” If the receipt shows a store SKU and the website shows a different one, ask the agent to look up your original line — do not paste a prettier similar product.

Size and finish variants are the usual apparel and furniture traps. If the markdown is on a different size than you bought, that is often a different SKU. Confirm before you spend the window arguing.

Gift cards, split tender, and tax

Say how you paid only so they can refund the right place. Gift card plus card often returns to both, in the store’s default order. Do not demand a check unless the policy offers it. Tax on the difference is retailer-specific; if the help page is silent, ask once. Do not hold the whole ticket hostage over tax.

Do not wait for a deeper drop

A $20 drop inside the window is a live request. Waiting for a $40 rumor can push you past the deadline. You can sometimes ask again if the price falls further while you are still inside the same window — only if the current policy allows a second adjustment. Confirm that before you withdraw a pending ticket.

What usually goes wrong in the request itself

• You called it a price match and they ran the competitor checklist.
• You sent a shopping-engine price from another seller, or a different color / bundle SKU.
• You used a gift receipt with the price removed.
• You counted the window from delivery; the policy counts from purchase (or the reverse).
• You asked for tax, shipping, and a restocking-fee reversal in the same sentence as the markdown.
• You submitted on day 13 and followed up on day 20 after the window closed — keep the first ticket.

One item per request is cleaner than a cart of five SKUs. If several lines dropped, list them as a table in one ticket so they share one order ID, but keep each SKU's paid vs. current price obvious.

If they say no

Ask which exclusion they used. A useful no names a rule: window closed, marketplace seller, clearance, event SKU, or not the same identifier. An unhelpful no is "we don't do that" after you used the word match. Send one follow-up:

Thanks for checking.

To confirm: this is a same-SKU request on your own current price, not a competitor ad. Order [ORDER ID], SKU [SKU], purchased [DATE], paid $[PAID], now $[CURRENT].

If this SKU is excluded, please point me to the current policy paragraph that excludes it (clearance, marketplace, event price, or window). If it qualifies, please process the difference of $[DIFFERENCE].

If they point at a live policy paragraph that actually excludes you, stop. If they never looked at the SKU, the follow-up is the correction. Chargebacks and fake "rights" language do not belong here. Owed is not a law firm and this is not legal advice.

Returning and rebuying is a different decision: return window, restocking, whether the lower price will still exist, lost promos. It is not a substitute script for an adjustment. If the store has no adjustment policy, a return is simply a return.

After they say yes

Save the ticket number and the amount. Refunds often post to the original tender in a few days, not instantly. Store credit is not the same as a card refund; if that matters, say so up front only if the policy allows a choice. Check the statement so you do not "lose" a refund that already posted.

Doing this by hand vs. using Owed

The manual path above is the whole job: watch the SKU, respect the window, file in your name. Owed is for people who already shop at US retailers and would rather forward the receipt than calendar every order. Pro is $9.99/month (first 1,000 accounts get month one free). We prepare the claim kit. You send it. We never take custody of the refund. Read pricing if you want the subscription details. The scripts on this page still work if you never sign up.