Dropshipping suppliers are chosen on wholesale price, shipping time and trading terms. All of that is visible upfront, so that is what the decision rests on. The trouble is that your day-to-day workload will be decided by something else: dropshipping supplier data quality, meaning what actually sits in the product feed your supplier passes to shops. Here is what to look for in that feed before you list a single product, and which gaps you can fix later versus the ones that stay with you for good.
A price list tells you nothing about supplier data quality
The criteria that make it into supplier comparisons are always commercial. Purchase price, margin, shipping time, minimum order, whether the end customer sees your supplier’s name. All of them matter and all of them can be checked before you start.
None of them answers the question of how much work will be left on your side once the supplier is connected. And the answer to that has a very real price tag. Products arrive as a feed, usually XML or CSV, and what sits in that file draws the line between a shop that runs itself and a shop where somebody fixes something by hand every single day.
A merchant sizes up a supplier by their range and the sales pitch. We look at it from the other side: we connect suppliers to shops and see the same feeds from the inside, across many clients at once. That is how we know two suppliers with near identical price lists can mean completely different amounts of work.
Three gaps we see most often in supplier feeds
Instead of the general advice to "check data quality", here are three specific gaps that show up in real product feeds.
The first and most damaging is missing stock levels. There are suppliers whose feed carries no availability information at all. The shop gets a catalogue but has no idea what from that catalogue can actually be sold today. Every order turns into a bet on whether the item is still sitting in the warehouse.
The second is descriptions. Sometimes they are thin, sometimes they are not there at all. The feed carries a name, a price and a photo, and the body of the product page is yours to produce. At a few hundred items that is weeks of work. At a few thousand it cannot be done by hand in any reasonable time. To put that in perspective: entering 1,000 products manually runs to roughly 160 hours, and that assumes the data is already complete. Missing descriptions add writing from scratch on top of that.
The third gap hits clothing and footwear above all: size charts. Sizing is often left out of the feed, even though it is what determines whether a customer orders the right size. Without it the customer guesses, and the cost of guessing comes back to you as returns. Nobody sends an item back because it is bad. They send it back because it does not fit.
Worth stating plainly: this describes patterns, not particular companies. The same gaps turn up with suppliers across very different price brackets.
Stock levels: not just whether they exist, but how often they change
Say the stock levels are there. That is only half the answer, because what matters next is how current they are.
A stock level is worth something only when it matches reality. A feed refreshed once a day describes a warehouse as it looked many hours ago. In a shop with slow turnover you may get away with it. In a shop selling popular items it means regularly taking orders for goods that are already gone. A sensible refresh runs every few to a dozen or so minutes, which keeps your shop close to your supplier’s actual warehouse.
The consequences of infrequent updates bite harder than most sellers expect. A cancelled order is not just lost revenue and a refund. It is a customer who will not trust you again, and on marketplaces it is a hit to your seller account, because cancellations that are down to the seller feed into your performance metrics and into how visible your listings are.
So the questions to ask a supplier are how often they refresh the feed, and whether the stock level is an actual unit count or just an in-stock/out-of-stock flag. That difference matters once you sell across several channels and want to split available goods sensibly.
How to see a supplier’s data before you list your first product
A product feed is rarely public. You get access after opening a partner account, often only once your company has been verified, which usually takes up to a day. That is no obstacle, because registration is normally free and commits you to nothing.
So it pays to reverse the usual order. First open the account and download the feed, look at the data, and only then decide whether you are listing this supplier’s products at all. The check itself needs no technical knowledge. If you are pressed for time, you can ask a sales rep for a sample feed before registering. Not every supplier will agree, but asking costs nothing.
Once you have the feed, go through a dozen or so products. Check that each one carries an identifier, a barcode number, a name, a price, a stock level, a description, images and a category assignment. The barcode number is the GTIN, printed on the packaging as an EAN or UPC, and without it selling on marketplaces gets harder. Watch out for fields that are empty or filled with something like "no data".
Check variants separately. If you sell clothing, footwear or cosmetics in several sizes, look at whether sizes and colours are separate entries with their own stock levels, or one combined entry. The latter means you will not know whether the size somebody just ordered is actually available. This is not a theoretical problem: while connecting suppliers we have run into catalogues that arrived with no variants at all and had to be filled in on the integration side.
Ask about one more thing that few people think of at the start: whether the feed structure ever changes, and whether the supplier gives notice when it does.
Finally, do the arithmetic. Take the number of products you want to list and multiply it by the number of fields you would have to fill in by hand. That single calculation tells you more about a supplier than an entire sales call.
What can be fixed, and what cannot
Not every gap disqualifies a supplier. Some of them can be filled on the shop side, and it is worth knowing which.
Missing or thin descriptions can be produced automatically from the product data that is in the feed: attributes, specifications, categories. That solves a second problem along the way, because the description arriving in a feed reaches every shop selling that product in exactly the same form, and your own copy sets your product page apart from the rest.
Descriptions in a foreign language are no obstacle either. Translation can run as part of synchronisation, so products land in your shop already in your language. That opens the door to suppliers abroad. The same mechanism works the other way round when you want to sell across borders: one supplier catalogue then feeds several language versions of your shop.
Prices need no manual work either. Pricing rules apply your markup to the supplier price along with the rounding you choose, and with automatic price updates switched on they recalculate themselves whenever your supplier changes the price list.
There is, however, one gap that nothing will fix. If a supplier does not publish stock levels, there is nothing to build automatic availability synchronisation on. And without that there is no dropshipping in any workable sense, because the whole model rests on the shop knowing what the supplier has. No tool invents information that is absent from the source.
And one thing worth saying honestly: some gaps will stay manual work. Nobody generates size charts out of thin air, because those are specific measurements from a specific manufacturer. If your supplier does not provide them, somebody on your side will be collecting them.
Supplier data does not stay still
Judging supplier data quality before you start is one thing. The other is that the feed will change.
Suppliers rewrite descriptions, add and remove fields, restructure categories. Usually without warning, because from where they sit it is housekeeping in their own catalogue. For a shop built on that catalogue the effect is the opposite: product pages start drifting, and you find out from a customer who received something other than what they ordered.
This is where an integrator earns its keep. When you work with the translation module and a supplier changes a product description, the change is detected and the product is flagged for another look. You do not have to compare a thousand entries by hand to notice that something moved.
Over time a second, less obvious benefit shows up. Descriptions from several suppliers pass through one review panel, where you see them broken down by supplier along with a quality score for each translation. At that point the question of which supplier delivers weaker descriptions stops being a hunch and becomes something you can check. That is a very different basis for a conversation with a supplier than a vague sense that something has slipped lately.
In short: ask about the feed, not just the price list
Before you list a new supplier’s products, do four things: open a partner account and download the product feed, check a dozen or so entries for complete data, satisfy yourself about variants and stock levels, and ask how often the feed is refreshed.
A supplier with an attractive price list and a threadbare feed often works out more expensive than one with a higher purchase price. The difference does not sit in your margin, but in the hours somebody has to put in before the products are fit to sell at all. You will not find that cost in any quote.
If you are weighing up a particular supplier and are not sure what is in their data, see which suppliers we work with or write to us and we will go through the feed and tell you what to expect. For the wider picture of how supplier data, translations and orders fit into a single process, see our piece on online store automation.