HOW-TO · Inventory

How to set up low stock alerts for marketplaces

Running out on bol.com, Amazon or your webshop usually starts with one missed reorder signal. ChannelDock’s Stock Level Sync helps sellers turn low-stock thresholds into safer marketplace availability before the shelf is empty.

Monitor
fast-moving SKUs
Buffer
risky last units
Reorder
before channels go red
Marketplace stock watchAlert active
bol.com listing12 left
Amazon offer9 left
Reorder point15 units
Safety buffer3 hidden

Low-stock alerts matter because marketplace demand, purchase lead times and channel sync delays rarely line up neatly. A clear alert rule gives the team time to buy, transfer or hide stock before overselling begins.

Earlier buyingreorder before zero
Safer listingshide risky last units
Fewer stockoutsprotect top sellers
Cleaner prioritiesfocus on fast movers

Before you start: what you need

Prepare thresholds, lead times and channel rules before switching on alerts. The best alert is specific enough to trigger action, not so noisy that the team ignores it.

SKU sales velocity

Know which products sell quickly per channel, including bundles and marketplace-only offers.

Supplier or transfer lead time

Estimate how many days it takes to receive, transfer or replenish each SKU.

Access to stock rules

Make sure you can edit inventory buffers, reservations and stock sync settings in ChannelDock.

Tip: start with your top 50 revenue SKUs. Low-stock alerts are most valuable where one stockout blocks sales, hurts marketplace ranking, or creates urgent purchasing work.

Step-by-step low-stock alert workflow

Use this sequence when one catalogue sells across marketplaces and every channel depends on the same physical inventory.

Identify the SKUs that need alerts

Rank products by sales velocity, margin and marketplace importance. Prioritise SKUs where a stockout creates lost sales, poor marketplace performance or manual customer-service work.

Common mistake: setting alerts for every SKU on day one, including slow movers that only create noise.

Calculate a realistic reorder point

Combine average daily sales, supplier lead time, receiving time and a small safety margin. If a product sells 5 units per day and takes 10 days to replenish, the alert should fire well before 50 units are gone.

Common mistake: using the same threshold for every SKU instead of matching the alert to demand and lead time.

Separate sellable stock from physical stock

Subtract reservations, held orders, returns inspection and non-sellable locations before deciding whether the SKU is truly low. ChannelDock can help keep the synced availability aligned with this operational stock number.

Common mistake: alerting on warehouse stock while marketplaces are still selling units already reserved for open orders.

Set marketplace buffers for risky last units

Use buffers to hide a few units from marketplaces when a SKU is close to the reorder point. This reduces overselling risk while the buying or warehouse team replenishes stock.

Common mistake: exposing the last physical units on every channel at the same time.

Route the alert to the owner

Decide who acts when the alert fires: purchasing, warehouse, store manager or 3PL account owner. Add the action next to the alert so the signal does not become another dashboard number.

Common mistake: sending every alert to a shared inbox nobody owns.

Review alerts after real orders

After one or two replenishment cycles, compare alerts with actual stockouts and false alarms. Raise thresholds for fast movers and lower thresholds for slow-moving products.

Common mistake: treating the first alert setup as permanent even when demand changes by season or campaign.

Connect alerts to channel availability

Use Stock Level Sync so buffers, reservations and low-stock rules influence what marketplaces can sell. Pair it with Stock Alerts when the team needs operational notifications.

Common mistake: receiving the alert but still letting every marketplace sell the same last units.

The low-stock alert loop at a glance

A practical alert workflow connects sales velocity to reorder action and channel availability. The alert is only useful if it changes what the team buys, transfers or publishes to marketplaces.

A low-stock alert is not just a warning. It is a decision point: buy more, move stock, reduce availability or stop selling the risky last units.

Sales velocity
Reorder point
Team alert
Safe sync

Common low-stock alert pitfalls

  • Alerting on total physical stock instead of sellable stock after reservations and buffers.
  • Using one blanket threshold for products with very different lead times.
  • Ignoring bundles where one component runs out before the parent SKU does.
  • Sending alerts to people who cannot create purchase orders or transfer stock.
  • Leaving marketplaces live on the last units after an alert has already fired.

Manual stock checks vs. ChannelDock Stock Level Sync

Manual checks can work for a small catalogue. Once the same SKUs sell through multiple marketplaces, alert rules need to connect with the stock number each channel receives.

Without ChannelDock

  • Someone exports stock and highlights low quantities by hand.
  • Alerts are separate from reservations, buffers and marketplace availability.
  • Teams discover stockouts when listings pause or customers complain.

With ChannelDock

  • Stock Level Sync works from one safer available quantity across channels.
  • Buffers and reservations help hide risky units before marketplaces oversell.
  • Alerts become part of the same workflow as reordering, transfers and stock corrections.

Explore Stock Level Sync →

Low-stock alerts for marketplaces FAQ

Start with fast-moving SKUs, calculate a reorder point from sales velocity and replenishment lead time, subtract reserved or blocked stock, then connect the alert to a clear purchasing or transfer action.

A good threshold covers expected sales during supplier lead time plus a safety margin. Fast movers, seasonal products and imported products usually need higher thresholds than slow local replenishment items.

Use available stock. Physical stock can include reserved orders, returns, quarantine, store stock or units that should not be sold on marketplaces.

They help, but alerts alone are not enough. Pair them with buffers, reservations and real-time stock sync so marketplaces stop selling risky last units.

Review the rules after each replenishment cycle and before peak seasons. Change thresholds when sales velocity, supplier lead time or campaign planning changes.

Yes. Bundle availability depends on the lowest available component. Alert on critical components before the bundle itself appears out of stock.

Related workflows to improve next

Once low-stock alerts are reliable, tighten the stock controls that keep the signal accurate.

Prevent overselling

Protect the last units across channels.

Read the how-to

Sync inventory

Publish safe stock to every sales channel.

Read the how-to

Inventory Reservations

Reserve committed stock before sync runs.

Learn more

Stock Advice

Plan replenishment before stockouts hit.

Learn more

Turn low-stock alerts into safer marketplace availability

Use ChannelDock Stock Level Sync to connect reorder points, buffers and reservations with the stock each marketplace is allowed to sell.