Selling on Marketplaces With Supplier Stock

Selling with supplier stock means listing products on a marketplace without holding them yourself, then having the supplier ship each order as it comes in. It widens a catalogue without tying up capital, and it moves the most fragile part of the operation, the stock number, outside your own four walls. This guide covers how to make supplier data usable, how to price against a cost that moves without warning, how to protect handling time when an extra link joins the chain, and in what order to set it up.

What supplier-stock selling actually looks like

Three models exist in practice, and most sellers end up running two of them at once:

• Pure dropshipping. The goods never reach you; the order goes to the supplier and the parcel leaves from there.
• Hybrid. Best sellers sit in your own warehouse, the long tail stays with the supplier.
• Consignment or reserved stock. The goods are physically with the supplier, but a set quantity is allocated to you.

All three share one problem: the quantity you display is a copy of a number in someone else's warehouse. The staler the copy, the higher your cancellation rate. Here the centre of the business is not marketing but data freshness.

The real risk: promising stock you do not hold

Sellers working with supplier stock tend to get caught in the same loop. The supplier reports a sold-out item at the end of the day, you find out in the morning, and you cancel the orders that arrived in between. The cancellation is not a one-off loss: on nearly every marketplace a seller-caused cancellation is a mark against your performance rating, and repeated marks cost you search placement, campaign eligibility and eventually selling privileges.

There is a second cost. The buyer believes they bought from the channel, so a cancelled order returns as a poor review. The goal is not "never run out" but "never leave an out-of-stock item open for sale".

Sell the same item on several channels and the exposure multiplies: one unit is visible in three places at once. We covered that failure in stock synchronisation and overselling; here the only difference is that the pool is fed by someone else's report rather than your own count.

Three practical ways to shrink the risk:

1. Publish a safety buffer. If the supplier shows 10 units, open 7. The gap is your insurance against delayed data.
2. Use one stock pool. Every channel sees the same number, and a sale on one channel drops the quantity everywhere else.
3. Rate suppliers per product. Dropping items that sell out quickly or get reported late is cheaper than cancelling orders week after week.

Making the supplier feed usable

Suppliers usually hand over data as an XML or CSV feed, and it is rarely in the shape a marketplace wants: category names are their own, variants are squeezed into one row, barcodes are missing, and it is unclear whether the price includes tax. Pushing that file to a channel untouched is the shortest route to rejected listings and wrong prices.

A healthy setup runs like this:

1. Map every row to your own product code; the supplier's code is not your SKU. SKU and barcode matching walks through how that mapping is built.
2. Validate barcodes; a row without one will not list on most channels.
3. Fit category and attribute fields to each channel's own tree.
4. Confirm in writing which tax status the price field carries.
5. Find out when the feed is refreshed and build your own update rhythm around it.

For the mechanics of feeds themselves, XML integration and the Google Merchant feed is a good starting point.

A supplier feed is not a catalogue; it is a news source. The catalogue stays yours, and the feed updates only stock and purchase cost.

Pricing when your cost moves

In this model the purchase price changes without notice. Work with fixed selling prices and one morning you will have handed your margin to the supplier. Price by rule instead of by hand: purchase cost + channel commission + shipping + a returns allowance + target margin. Any listing that falls below that floor should be pulled back to the floor price or taken out of sale.

Note which groups move most often: where the cost changes several times a month, keep the margin wide or keep the item out of campaigns. Floor price rules and loss prevention covers how those limits are set per channel. Two extra lines belong in the calculation here: the supplier's own shipping charge, and the terms under which they accept a return. Leave either out and a product that looks profitable on paper ends the month in the red.

Handling time and shipping

The marketplace clock starts when the order is created on the channel, not when your supplier acknowledges it, and dropshipping adds a link to the chain. Passing the order on, receiving the tracking number and writing it back to the channel all have to happen the same day. Marketplace handling time and late shipments explains how the counter works and what lateness costs.

Settle these four questions in writing before the first order:

• Whose carrier contract is used, and whose name is on the label?
• Who writes the tracking number back to the channel, and within what window?
• Is the return address the supplier's or yours, and which one does the buyer see?
• Who issues the invoice, and does that match the marketplace's rules and your local tax obligations?

Setting it up in the right order

1. Take the feed and watch it only, for a week: how often does it refresh, which fields come back empty?
2. Map the items to your own catalogue codes and drop rows without barcodes.
3. Write the pricing rule and the floor price.
4. Start with a small product group on a single channel and measure cancellations and delays.
5. If the numbers hold, widen the product group and the channel count step by step.
6. Track sell-through speed and raise the safety buffer on fast movers. Low stock alerts and days of cover explains how those thresholds are set.

Step one is the one most often skipped. A week of observation tells you when the supplier really updates and which fields come back empty, and every later decision rests on those two facts.

How Bulutegra handles it

Bulutegra takes a supplier feed as a catalogue source and ties it to a single stock pool: whichever of the more than thirty-eight channels makes the sale, the quantity drops from the same pool and every channel sees the same number. An ownership flag per product and channel separates what Bulutegra manages from what an outside system controls, so warehouse items and supplier items can live in one panel under different rules. The price matrix and floor price rule stop below-cost sales when purchase costs move, and the profitability view shows real contribution per channel with commission, VAT and return risk included. Setup begins in shadow mode: for a week or two the system only reads, comparing what the channels and the feed say, and starts writing only when you hand over each channel.

To see how this would work with your own supplier feed, look through the modules or request a demo and we will go through the feed with you.