When a dropshipping supplier goes quiet

Your supplier is your operations department

In a dropshipping arrangement the supplier does not just provide stock. They hold it, pick it, pack it, choose the carrier, and determine what the customer's experience of your store actually is. You own the relationship with the customer and control almost none of the events that shape it.

That is a workable arrangement. It becomes an unworkable one the moment something goes wrong, because at that point you need information you do not have, from someone with no direct incentive to give it to you quickly.

So the useful work is nearly all front-loaded. What you agree before the first problem determines how the first problem goes.

The five things to agree in writing

Before volume, before pricing negotiations, get these settled. Each one is a question you will otherwise be asking under pressure.

• Dispatch commitment. Not "we ship fast". A specific cut-off and a specific number of working days, so lateness is definable.
• How you get tracking, and when. Automatically at dispatch, or on request. If it is on request, you have already found your biggest problem.
• Stock signal. How you find out something is unavailable. A feed, a daily file, or an email after the order fails.
• Who you contact for an urgent problem, and what counts as urgent to them.
• Who pays for what. Lost parcels, damage, wrong item sent, return shipping. Settle this while nobody is annoyed.

A supplier who cannot answer these clearly is telling you something. Not necessarily that they are bad, but that you will be the one absorbing the ambiguity.

The information gap, and how to narrow it

The structural problem in dropshipping is that a customer asks you a question you cannot answer without asking somebody else. Every hour of that round trip is an hour the customer waits for their own store to tell them something basic.

Three things narrow it.

Tracking that arrives automatically. This is the single largest improvement available, because it converts most enquiries from a supplier question into a lookup.

A stock signal you receive before the order fails. Selling something that does not exist and finding out afterwards is the worst version of this business, and it is usually a data problem rather than a supplier honesty problem.

An agreed response time for questions. Even a slow one you can plan around beats an unknown one. If your supplier answers within one working day, you can promise the customer two, and keep the promise.

Answering a customer when you do not know

You will regularly be asked where a parcel is and not know. There is a good way to handle this and a bad one, and most stores default to the bad one, which is to say nothing until they have an answer.

Silence reads as indifference. The customer cannot tell the difference between "checking" and "ignoring".

The better pattern is an immediate acknowledgement that commits to a next contact, then a follow-up whether or not you have news. Something like: we have asked our warehouse this morning and we will come back to you by tomorrow afternoon either way.

Two things are load-bearing there. "By tomorrow afternoon" gives the customer a reason to stop worrying. "Either way" means you do not go quiet if the supplier has not replied, which is exactly when stores tend to go quiet. Nothing here reveals that the warehouse is not yours, and nothing here is untrue.

Never make the customer wait for the supplier

The most important operating rule in dropshipping is this: your resolution timeline and your supplier's are separate.

If a parcel is lost, decide what you are doing for the customer based on your own thresholds, not on when the supplier concludes their investigation. Reship or refund at your own trigger point, then pursue the supplier separately on their timescale.

Two reasons this matters. The customer has a relationship with you, not with a warehouse they have never heard of, so a delay caused by an internal process is simply a delay caused by you. And supplier investigations frequently take longer than the point at which the customer relationship stops being recoverable.

Set the thresholds in advance, the same way as for any stuck parcel: a value floor below which you resolve without asking, and a number of days after which you resolve regardless. The reasoning is the same as in stuck shipments, only the leverage is worse.

The customer bought from you. Every day you spend waiting for your supplier is a day they experience as you being slow.

Returns, which nobody plans for

Dropshipping conversations focus almost entirely on getting parcels out. Returns get settled later, usually during the first one, usually badly.

Three questions decide how painful this is, and all three should be answered before you take an order.

Where does the item physically go back to? The supplier, or you? A return address in another country turns a routine return into something a customer will not do, and a refusal to return becomes a refund plus a lost unit.

Who pays the return shipping, and does the answer change if the item was wrong or faulty rather than unwanted? Get this in writing, because it is the point at which suppliers and stores most often discover they assumed different things.

How long does a credit take, and does it require the supplier to receive and inspect first? If it does, and you refund the customer immediately as you should, you are financing the gap. That is fine, but it is worth knowing you are doing it.

The seasonal version of this gets much larger in January, and the general planning for that is in returns season: the January plan.

Keeping a record that survives the relationship

Dropshipping suppliers get changed. When they do, most stores discover that everything they knew about the old one lived in one person's inbox.

Keep a running record of a few things: which orders had problems and what kind, how long the supplier took to respond, what they agreed to cover and whether they did, and any pattern by product or destination.

This has three uses. It makes a renegotiation possible, because you can point at specifics. It makes a comparison possible when you evaluate an alternative. And it means the knowledge survives the person, which matters more than it sounds when a supplier relationship is a year old and the person who built it moves on.

The problems that are actually yours

Not everything that goes wrong is the supplier's fault, and it is worth being honest about the share that is not.

Delivery estimates that were never realistic. If your product page promises a window your supplier has never once met, the complaints are yours.

Product data copied without checking. Wrong dimensions, wrong variant names, outdated images. Returns caused by a description are your returns.

Selling stock you have no live signal for. If your availability data is a weekly file, you will oversell, and that is a decision you made rather than a thing that happened to you.

Fixing these is usually cheaper than fixing a supplier, and they account for a substantial share of what looks like supplier failure.

When to add a second supplier

Single-supplier dropshipping is a single point of failure for the whole business. The usual trigger for adding a second is a bad experience, which is late.

Better triggers: when one supplier covers a majority of your revenue, when a category has no alternative source you have actually tested, or when your peak depends entirely on someone else's peak capacity.

Testing an alternative before you need one is cheap, because you can send it a low volume of real orders and measure the same things you now measure for the incumbent. Finding one in the middle of a crisis is not cheap, and the crisis is when your judgement is worst.

What this looks like in Store Huddle

A room per supplier, with the order attached to each problem raised, so the conversation is about an identified order rather than a described one. Problems become tasks with owners and dates, which is what makes "we will come back to you by tomorrow afternoon" a commitment rather than an intention.

The running record of supplier behaviour lives in the room where the supplier is discussed, so it is readable by whoever takes the relationship over. And because customer-facing decisions such as reship thresholds are written down and visible, the person answering an enquiry on a Saturday knows what they are allowed to do without waiting for anyone.

Common questions