The message arrives after your money is already tied up

The order went through. The payment cleared. The supplier accepted it. Two days later, at 3:54 in the morning, a message arrives: due to price adjustments on the platform, your item requires an additional charge — in one documented October case, an extra $208 demanded on a motherboard that had just been bought on sale for €192.17, roughly €20 below its usual price of around €210.

Read that ratio again. The discount was €20. The surcharge demanded was more than ten times the discount, and more than the entire original purchase price. When the buyer refused, the reason changed within one exchange: first it was a platform price adjustment, then it was a pricing error discovered after the order was placed. The offer that followed is the tell — the seller would create a separate link to cover the difference. Not an adjustment to the original order. A second, separate payment, alongside it, outside the protection the original order carries.

This is not one bad seller being creative. A 2026 margin-defense guide from TS Scout describes post-checkout price increases as a recurring operational risk, driven by tariff stacking, currency swings, and the end of duty-free low-value shipping. Your job in the first reply is to avoid the one click that makes it cost you twice.

What the platform rules actually say

The most useful sentence in that documented case came from the seller's own side. After the buyer pushed back, the seller admitted, in writing: under platform policies, sellers cannot unilaterally change the price or demand extra payment after an order is placed and paid for. That admission was followed by a "however" — the error was supposedly genuine, shipping at the original price was therefore impossible, and the only solution was to cancel.

Both halves matter. The first half is your leverage: a paid order is a contract at the paid price, and a demand for extra payment after payment is a policy violation, not a negotiation you are obliged to join. The second half is the trapdoor: if shipping truly will not happen, the order will end — and how it ends is recorded very differently depending on who ends it.

The real trick is who cancels the order

If the seller cancels, or the shipping deadline passes with nothing sent, the platform records it as the seller's failure — transaction non-fulfilment, graded by severity, earning points that affect the seller's account and the shop's visibility. If the buyer requests the cancellation, it is recorded as a buyer-side cancellation. The seller clicks approve, the refund is prompt, and nothing is left in their statistics.

That asymmetry is why the conversation so often ends with a helpful offer: "I can assist you with the cancellation process, or you may initiate a cancellation request from your order details. We will approve it immediately." The seller is not being kind. They are asking you to absorb their non-fulfilment into your click, so their record stays clean for the next buyer. Your refund arrives either way. Their penalty only arrives if you do not volunteer.

For a dropshipper the stakes are doubled, because behind your supplier order sits your customer order. While you spend three days negotiating a surcharge, your own delivery promise is burning, and under the U.S. FTC's 30-day rule the duty to ship on time, notify delays, and offer cancellation with a prompt refund belongs to your store — "my supplier held the order hostage" explains the delay to your customer, but it does not transfer the obligation.

The playbook, in order

Step 1: Do not pay the difference, and do not cancel. Reply in the order thread, in writing. One short message does the work: the order was placed and paid at the agreed price; platform policy does not allow a unilateral price change or extra payment after payment; please ship the order as paid, or confirm in this thread that you cannot fulfil it. Every word stays inside the platform's messaging, attached to the order, where a dispute reviewer can read it later. Never move this conversation to WhatsApp or email, and never pay a separate "difference link" — a second payment outside the original order is the hardest money to recover.

Step 2: Archive your evidence while it is fresh. Screenshot the order confirmation showing the item, the exact variant, the price paid, and the shipping terms, plus the seller's surcharge message with its timestamp. If you priced your store from this listing, save the listing as it looked when you ordered. This takes four minutes on day two and is nearly impossible to reconstruct on day twenty, when the listing has been edited and the message thread is buried. Sellers who win these disputes are usually just the ones who kept the receipts in order.

Step 3: Let the clock work for you, not against you. If the seller will not ship, the shipping deadline passing unshipped is their non-fulfilment, recorded against them — that record is part of your leverage, and it evaporates the moment you click cancel yourself. What you should do with the waiting time is protect your own customer: check whether a backup supplier can fulfil inside your promised window, and if not, send your customer the delay notice with a revised date or a full-refund option early, while it is still a choice you are offering rather than an apology you are making.

Step 4: If the order dies, open the dispute from the order, with the thread attached. The seller's own admission, the surcharge demand, and your refusal are all in the order messages. File within the platform's protection window rather than accepting an off-platform refund promise, and state the outcome you want plainly: full refund of the amount paid on the original order. Then log the incident against the supplier — one surcharge demand is a data point, a second one is a sourcing decision, and the log is what turns "this seller felt shaky" into a number you can route around.

Step 5: Set a margin ceiling before the next incident. Decide in advance the most you would ever pay a backup supplier to save an order at the original promise — and that the answer to a post-payment surcharge demand is always no, regardless of size. A $3 "small adjustment" paid once teaches the pattern that your store pays. The sellers who get repeated demands are, disproportionately, the ones who paid the first small one.

A concrete example: the €192 order, two ways

Handled the offered way: the buyer clicks cancel, gets €192 back promptly, and feels the story is over. The seller's record shows a buyer-side cancellation — clean — and the practice continues because it cost them nothing. A dropshipper in that seat also lost three days of their customer's delivery window, with no record anywhere that the supplier failed.

Handled the playbook way: the buyer refuses in the order thread, archives the confirmation and the demand, and waits. The seller either ships at the paid price — which happens more often than the opening message suggests, once the cancellation will clearly be theirs — or lets the deadline pass, takes the non-fulfilment record, and the dispute refunds the original payment with the full thread as evidence. Same refund if it fails. Completely different record.

The takeaway

A post-payment surcharge demand is not a pricing problem; it is a records problem wearing a pricing costume. The price was settled when you paid. Do not pay a separate difference link, do not move the conversation off the order thread, and above all do not click the cancellation that converts the seller's failure into your request. Reply once, in writing, archive everything, protect your own customer in parallel, and let the deadline assign the failure to the party that caused it.

Has a supplier ever asked you for extra money after you paid? Tell me the amount and what you did — the patterns in the comments are usually worth more than any single guide.

— Jinguo, maker of GetDropFlow (https://getdropflow.com)