Dropshipping and Supplier Sync: Stock and Price Updates That Don't Break the Store

In dropshipping you sell stock you cannot see. All the risk concentrates in one place: the gap between what the store displays and what actually exists at the supplier. A good sync process is not "update daily" but deciding what happens when the information is missing, stale, or contradictory.

The three values that sync

The third is the most forgotten. A supplier's lead time changes with the season and with their own stock, and it is what you promise at checkout - so it needs refreshing rather than setting once.

What do you do when there is no update?

This is the most important decision in the entire sync. Three options, and only one is safe:

• Keep the last quantity - the most convenient and the most dangerous. A feed that has not arrived for three days turns the store into a seller of imaginary stock.
• Zero everything out - safe, but it switches products off because of a technical fault.
• Flag as stale and restrict - keep selling only items with high reported stock, and switch off the marginal ones.

The third is usually right: it distinguishes an item reporting 200 units two days ago from one reporting 2. The first almost certainly still exists; the second probably does not.

Price sync - the control you must have

Price is the one value whose automatic update can cost money immediately. Two controls prevent most incidents: an allowed change band - any update moving a price by more than a set percentage stops for manual approval; and a margin floor - a product whose price falls below the minimum margin is frozen rather than sold.

The first also catches errors at the supplier's end: a file with a shifted column, or a price recorded in agorot instead of shekels. Without it, one mistake in a supplier file becomes a hundred loss-making sales before anyone notices.

What a working sync looks like

1. Fetch the file or data from the supplier, in whatever form they provide.
2. Validate - does the file look sane: a plausible row count, columns in place.
3. Compare against current state and identify unusual changes.
4. Apply whatever passed the controls.
5. A short report on what did not pass and why.
6. An alert when the sync did not run at all.

Step 2 is the forgotten one and the only thing that prevents disaster: an empty or partial file loaded as is switches off half a store overnight.

It is also worth keeping the file received on each run. When a product turns out to have sold at an odd price or a quantity jumped, the only way to know whether the problem was the supplier's or yours is to look at what actually arrived - and without retention that evidence is overwritten on the next run.

What dropshipping does not solve

It is easy to treat dropshipping as a model without operations, and in practice it relocates operations rather than removing them. What stays with you: customer service about shipments you do not send, handling returns of goods you never saw, and quality control on items you never inspect.

That gap also explains why many dropshipping stores look profitable in a spreadsheet and are not in reality: the true cost is spread across service hours, cancellations and credits - three lines that never appear in an item's cost price.

Handling several suppliers for one product

When more than one supplier carries the same item, you need a rule: who is the source of truth for stock, and who for cost. In most cases the simple rule works - availability is the sum, and cost belongs to whoever will actually fulfil.

What matters is that the decision of who fulfils is made automatically by a clear criterion - availability, lead time, or cost - rather than manually per order. Without a rule, every order becomes a small decision, which is precisely what cancels out the advantage of dropshipping.

What to check with a supplier before you start

• How often they update stock, and in what format.
• Whether the stock they report is committed or indicative.
• What happens when they run out after you have ordered.
• Who contacts the customer in that case - you, always.
• What the real lead time is, including at peak season.
• Whether they ship under your name or theirs.

The last affects customer experience more than it seems: a parcel arriving with another company's branding produces an enquiry almost every time, and sometimes a customer who goes straight to the supplier next time.

What you remain responsible for

The customer bought from you, so everything after payment is yours - even though the goods never passed through your hands. In practice that means three things you must hold yourself: tracking that reaches the customer in your name rather than through the supplier, a record of what shipped and when for every order, and an answer to where a parcel is without waiting for the supplier.

The simple way to have all three is to store the tracking number and the source supplier on your own side per order, and build customer messaging on that data as described in automatic tracking updates to the customer. Without it, every customer question becomes an email to the supplier and a day of waiting.

How to test a supplier before you start

Before connecting an entire catalogue, place five real orders to different addresses and measure: how long until they shipped, what packaging they arrived in, what condition the shipment was in, and what happened when you requested a return on one of them. Five orders cost little and reveal almost everything.

The returns test matters most, because it is the scenario suppliers describe least in a proposal. A supplier who avoids the question of who receives a return and what happens to the money is a supplier who will pass that cost to you when it occurs - and it will, in every store.

Sources

• HFD - fulfilment services
• Israel Post - e-commerce services