A supplier price increase can turn a profitable dropshipping order into a loss between checkout and fulfillment. The customer paid the price displayed by your store, but the supplier now wants more for the same SKU. If the order is automatically pushed to fulfillment without a margin check, the store may absorb the entire difference before anyone notices.
The safest workflow is to treat supplier cost as a value that must be validated at the moment of purchase order creation, not as a permanent product attribute. Small increases can be auto-approved within a defined tolerance. Larger increases should stop fulfillment and create an exception for a human decision.
Why supplier price changes happen after checkout
- The supplier updated its catalog after your last feed sync.
- A promotional wholesale price expired.
- The store mapped the order to a different warehouse or supplier tier.
- Currency conversion changed the landed cost.
- The supplier changed packaging, quantity per pack or minimum order rules.
- An API returns a live cost that differs from the cached product feed.
The first step is to determine whether the change is a real cost increase or a data problem. A silent variant or SKU change can look like a price increase while actually pointing to the wrong product. That risk is covered in Supplier SKU Drift: How to Catch Silent Product Changes Before Customers Do.
Do not compare supplier price alone: compare expected contribution margin
A $3 supplier increase does not have the same impact on every order. For a $19 low-margin item it can erase the profit. For a $180 order it may be within a normal cost buffer. Your decision rule should therefore look at the new contribution margin after product cost, supplier shipping, payment fees, platform fees, taxes that affect your economics and any expected support or return allowance.
| Situation | Recommended automation | Human review? |
|---|---|---|
| Cost change below a small fixed and percentage tolerance | Allow fulfillment if minimum margin still passes | Usually no |
| Cost change removes most profit but order stays positive | Pause and calculate expected contribution | Yes |
| Order becomes negative margin | Stop supplier submission | Yes |
| Supplier cost changes together with SKU, pack size or variant | Block automatically | Yes |
| Alternative approved supplier is cheaper and equivalent | Route through supplier-failover rules | Depends on product controls |
Set two thresholds instead of one
A practical system can use both an absolute cost threshold and a percentage threshold. For example, a merchant might allow a change only when the increase is below both limits and the final contribution margin remains above the store minimum.
This avoids two common failures. A pure percentage rule can approve a large dollar increase on an expensive item. A pure dollar rule can approve a small-looking increase that destroys the margin on a cheap item.
What should happen when the order fails the margin check?
Move it to a fulfillment exception state rather than immediately cancelling or sending it to the supplier. The queue should show the customer order number, SKU, old supplier cost, new supplier cost, shipping difference, current margin, alternative suppliers and the deadline for action.
This fits naturally into the operational model described in Fulfillment Exception Queue: How to Manage Aging Orders, No First Scan, Partial Fulfillment and Supplier SLA Breaches.
When is absorbing the increase reasonable?
Absorbing a supplier increase can be rational when the order remains profitable, the customer acquisition cost has already been spent, cancellation would create support costs, and the product is likely to generate repeat business. It can also be better than delaying an order over a very small difference.
But the decision should be explicit. Repeatedly absorbing price increases without measuring them creates a hidden margin leak. Track the monthly amount of supplier-cost variance by supplier and SKU. If one supplier repeatedly changes price after your feed refresh, the issue is not an individual-order problem anymore; it is a catalog or commercial reliability problem.
When should you look for an alternative supplier?
An alternate supplier can protect the order, but only if the substitute source is already approved. Matching by title or image is not enough. The SKU, variant, specification, package quantity, destination availability and delivery promise must still match.
Supplier switching should also be idempotent: once the replacement purchase order is accepted, the original route must be locked so a retry does not create two supplier orders. See Duplicate Supplier Orders After Webhook Retries for the controls that prevent this failure.
Can you ask the customer to pay the difference?
In most consumer workflows, asking for more money after the customer completed checkout is a poor default and may conflict with the price and contractual terms presented at purchase. Do not build an automation that simply invoices the customer for your supplier’s price change.
If the original item genuinely cannot be supplied and you offer a different product, treat it as a customer-approved change rather than a hidden repricing. The same decision discipline applies when the supplier is out of stock; Supplier Out of Stock After the Customer Paid explains the substitute, backorder, cancel and refund paths.
What data should you log?
- supplier cost shown at catalog sync,
- supplier cost quoted at order submission,
- currency and exchange rate used,
- supplier shipping and handling charge,
- original and recalculated contribution margin,
- person or automation that approved the variance,
- final fulfillment route,
- supplier response or error returned by the API.
Without this history, it is difficult to distinguish a supplier pricing problem from a store repricing problem.
Build the control before you need it
Price variance should be tested with synthetic orders before a live supplier changes pricing. Create scenarios for a tiny increase, a large increase, a currency move, a supplier shipping increase, an alternative source and a complete stock failure. Verify that no blocked order reaches the supplier while it is waiting for review.
Stores that sell bundles should be particularly careful because a cost increase in one component can change the economics of the entire set. The article Bundle Margin Math for Dropshipping shows why unit-level margin checks are not enough for every order.
FAQ: supplier price changes after checkout
Should a dropshipping store update prices in real time?
Real-time or frequent updates reduce exposure, but they do not remove the need for a checkout-to-supplier variance check. There is always a window between the customer’s price calculation and the supplier accepting the purchase order.
Is cancelling every negative-margin order a good rule?
Not automatically. The store should first verify that the new cost is correct, check approved alternative suppliers and consider the customer impact. A repeated pattern of negative-margin exceptions should trigger a supplier or pricing review.
What is the most important technical safeguard?
Do not send the supplier purchase order until the live cost, shipping cost, SKU identity and minimum contribution margin have passed validation. Once the order is released, cancellation may be slower or impossible.
admin
Author of practical guides to dropshipping, ecommerce, automation, and growing an online business.