The price dropped the week after they bought
Someone paid full price on Tuesday. On Friday your sale starts, and their phone tells them so. Whether you refund the difference is a policy you should write now, not one a support agent or a chatbot invents in December.
Write a price-adjustment policy before your first holiday sale. Pick one of three honest options: no adjustments, refund the difference within a set number of days, or offer the difference as store credit. Then define which price counts, who can approve it, how it's paid back, and how to say it the same way on the site, in support macros and in any AI assistant.
Someone paid full price on Tuesday
Here's a composite customer. She bought a wool coat on Tuesday for $240. On Friday your early holiday sale starts, and the coat is $189. She finds out because a shopping app tells her. Her saved items got a price-drop alert, or she just checks back. On Saturday she writes in, polite and slightly annoyed, asking for the $51.
What happens next depends on who opens the email. One agent refunds it because it seems fair. Another says sales are final. A third offers a coupon. The chat assistant on your site says something different from all three, because nobody told it anything.
My argument is short. A refund policy nobody wrote is still a policy. It's just written by whoever answers the email. Write the price-adjustment rule before your first sale of the season, and make every channel say the same thing.
Why it's coming up more this year
People have always noticed sales. What's changed is that they get told now. Google's Universal Cart, launched in the U.S. on October 15, notifies shoppers when a saved item's price drops, and other shopping apps and browser tools do the same thing. A customer who bought last week may well have saved the item first.
The timing makes it worse. Prices move more between late October and early December than at any other point in the year. Sales are announced early, then deepened, then extended. Each change hits the customers who bought just before it.
Customers also ask in more places than they used to. Some write to support. Some ask the chat widget. Some reply to the shipping confirmation, which may land in an inbox nobody reads on Saturdays. Some ask in a marketplace message thread if you sell there too. Every one of those is a door, and each door needs the same answer behind it.
And the questions arrive when your team is busiest and most likely to improvise. That's when the inconsistent answers do the damage. One customer tells another, or posts a screenshot of two different replies.
A refund policy nobody wrote is still a policy. It's just written by whoever answers the email.
Pick one of three honest options
There isn't a right answer. There are three defensible ones.
No adjustments. The price you paid is the price. Simple to run and easy to explain. The cost is goodwill, and in practice some of those customers will return the item and buy it again at the lower price. If your returns are free, you pay for two shipments to arrive at the same refund. If you choose this, decide how you'll handle the return-and-rebuy, because it will happen.
Refund the difference within a set window. Seven or fourteen days is common. It's generous and clear, and it's what many customers expect from larger retailers. The cost is real money during your biggest sales, and some admin work for each request.
Store credit for the difference. A middle path. The customer gets the value, and you keep the money in the business. It works best if store credit is easy to use and clearly shown at checkout. Our note on gift cards after a partial return covers why that balance needs one clear home.
Choose one and write it in two sentences. If you can't, it isn't a policy yet.
Whichever you choose, think about the customer who asks after the window closes. A firm, kind sentence that explains the rule and thanks them for asking does more than a surprise exception that the next customer won't get. Exceptions are fine, but they should be someone's decision, logged with a reason, so you can see later whether the rule needs to change.
Decision guide
Three honest price-adjustment options
| Consideration | What it gives the customer | What it costs you |
|---|---|---|
| No adjustments | A clear, simple answer. | Goodwill, plus return-and-rebuy shipments. |
| Refund within a window | The difference back on their card. | Cash during your biggest sales, plus admin. |
| Store credit | The value, to spend with you. | A balance you must track and honor at checkout. |
Define the details that make it work
The two sentences are the easy part. The details are where support gets stuck.
Which price counts? A sitewide sale price, surely. But what about a coupon code from an email list the customer wasn't on? A bundle price? A lower price from a third-party seller on a marketplace? A flash sale that lasted four hours? Say which ones count.
Who can approve it, and up to what amount? If any agent can refund any difference, write that down. If it needs a lead above a certain amount, write that too. Our refund authority ladder is the longer version of this.
How is it paid back? A partial refund to the original card, store credit, or a gift card. Each lands differently in your books and in your payment processor. Make sure finance knows which one you chose before December, not after.
What about orders already in transit? Usually the same as delivered orders. Just say so.
Does the customer have to ask? Some shops refund the difference automatically for recent buyers when a sale starts. It's a lovely gesture and an operational project of its own, because it means finding every affected order and processing each one. Most small teams should start with on request and revisit automation once they know the volume.
Say it the same way everywhere
Once the rule exists, put it in four places on the same day: the FAQ or returns page, the support macro, the instructions for any AI assistant or chatbot, and the internal note for whoever covers the inbox on weekends.
The assistant matters more than people think. If it was set up last spring, it may be quoting last year's policy or making one up from general knowledge. Test it. Ask it whether you'll refund the difference after a sale, and see what it says.
How the work moves
One rule, four places, one day
- Write it
Two sentences, plus which prices count and who approves.
- Publish it
Returns or FAQ page updated the same day.
- Teach it
Support macro and weekend cover note updated.
- Tell the assistant
Update its instructions, then ask it the question.
Put this into practice
This week, before your first sale goes live, do four things. Choose one of the three options and write it in two sentences. List the price types that count and the ones that don't. Set who can approve and up to what amount. Update the returns page, the macro and the assistant at the same time, then send one test question through each.
After the season, look back at how many requests you got and what they cost. That number, not a guess, should decide next year's rule.
Setting rules like this, and making sure the site, the support desk and the checkout agree on them, is everyday ecommerce work for us. If your holiday sale is close and your price-adjustment answer depends on who's on shift, talk to us.
Related work: Sutton|Place.
We build alongside the people doing the work.
Bring us the problem you’re thinking about.