Menu

Blog — Vedron

The number of units sitting in your warehouse is not the same as what you can promise a customer right now. Some of it is already reserved for an open order. Some of your "available" stock for a dropship SKU is not in your warehouse at all. Using the raw on-hand number overstates what you can sell.

The formula

In Vedron, available-to-sell is calculated as:

available = max(0,
  sum(on_hand across included locations)
  + dropship_pool
  - active_reservations
)

Four moving parts. Each needs to be right for the final number to be right.

On-hand across included locations

On-hand stock across your own locations, except warehouses you have flagged as excluded from fulfilment. A damaged-goods location should not inflate what is sellable. A photo-studio sample stash should not either. A quarantine location for products pending QC should not either.

Vedron treats location-level stock as the source of truth and aggregates upward. If you move 10 units from your main warehouse to your secondary warehouse, the aggregate stays the same but each location's number changes.

Dropship pool

Dropship stock is not physically in your warehouse but is legitimately available through a supplier. It is tracked as its own pool, representing what the supplier can ship within their stated lead time.

Why a separate pool, not just added to on-hand? Because the risk profile is different. Owned stock is 100% yours. Dropship stock depends on the supplier's system; if their system is wrong or they go out of stock between syncs, your "available" number is wrong until the next sync. Keeping dropship separate means you can decide per channel whether to expose it (fast-moving marketplace: yes; high-value custom orders: maybe not).

Reservations

Reservations are stock allocated to an order that has not yet shipped. The moment a customer completes checkout, the units for their order move from "available" to "reserved". When the order ships, the reserved units reduce on-hand by that quantity. When the order is cancelled, the reservation releases back to available.

Without reservations, two customers who order the same product within seconds of each other both see "available" until the shipment confirms, and one of them gets an unpleasant surprise. With reservations, the second customer sees an accurate reduced count.

The zero floor

If reservations somehow exceed on-hand plus dropship — a race condition during a flash sale, say — the calculation does not go negative. It stops at zero. The channels see "out of stock" and new orders are not accepted until stock replenishes or a reservation releases.

Showing a negative available number is a common bug in inventory systems that sum naively. Vedron does not do that. The user-facing number is always a count of units you can realistically promise.

What runs today

The available-stock calculation combines on-hand stock across all included locations, adds dropship stock from its own pool, subtracts active reservations, and floors the result at zero. One number. Every channel — storefront, Amazon, eBay, Allegro, every connected marketplace — reads from it.

The same inventory transaction model supports multi-location transfers and bundle disassembly: moving stock between locations, or breaking a bundle back into its components, is recorded the same way as every other movement. Transfers in flight show as "in transit" and do not count toward either location's sellable availability until they land.

Worked example: a bike with options

Say you sell a touring bike. Specifications:

Available-to-sell = max(0, (8 + 2) + 15 - 3) = 22 units.

The 1 damaged unit does not inflate the number. The 3 reserved units are correctly subtracted. The 15 dropship units are included because they are legitimately available if a customer orders them.

If the dropship supplier reports zero at the next sync, the number drops to 7 immediately. If a reservation is cancelled, it goes back up. Every channel reads the current number without needing to recalculate anything itself.

Frequently asked questions

What counts as a "location excluded from production"?

A location you have flagged that way. Typically a damaged-goods location, a quarantine area, a photo-studio sample stash — somewhere stock physically exists but is not meant to count toward sellable availability.

How is dropship stock different from a location I own?

It is a separate pool because it reflects supplier-side availability rather than inventory you physically control. If the supplier goes out of stock, dropship availability drops to zero even though you have not lost any stock yourself.

Can available stock ever show as negative?

No. The calculation is floored at zero. Even if reservations exceed on-hand plus dropship, the number shown is zero rather than a negative. This avoids the negative-available display problems that confuse both operators and customers.

How does the calculation handle bundle products?

A bundle's availability is derived from its component availability. If a bundle needs 1x frame and 2x wheel, and you have 10 frames and 15 wheels, the bundle shows as 7 available (limited by wheels: 15/2 = 7). The bundle itself is not stocked; the components are.

What about products with lead time from the supplier?

Lead-time stock is handled as a separate concept from available stock. Available-now is on-hand plus confirmed dropship; available-with-lead-time is on-hand plus incoming POs with expected delivery dates. The marketplaces see the former; your purchasing team sees both.

How often does the calculation refresh?

In real time. Any inventory event — a sale, a return, a stock transfer, a dropship supplier update — triggers a recalculation. The marketplaces read the result through the same stock table that the storefront reads.

What happens if a reservation sits unused for a long time?

Reservations are tied to open orders. If an order is cancelled, the reservation releases automatically. If an order sits in a long-pending state (payment not confirmed, say), the reservation holds until the order resolves. Order-expiry policies can be configured to release reservations after a set window.

Does this handle multi-location warehouses correctly?

Yes. Each location keeps its own stock figure. The available-to-sell calculation aggregates across all included locations into one number for channel display, but internal views show the breakdown so a fulfilment decision can route from the right location.

What about stock in transit between locations?

Stock in transit is tracked as a transfer transaction. The source location has decremented, the destination hasn't yet incremented, and the units show as in-transit. They do not count toward sellable availability until they arrive at the destination.

Can I see which specific orders are reserving a given SKU?

Yes. The product record shows the open reservations against it, with the order ID, customer, and reservation quantity. Clicking through goes to the order itself.

Talk to us about your setup

Every seller's mix of marketplaces, currencies and payment methods is a little different. Book a short call and we will walk through yours on your real data. Beta clients get the first two months of custom setup on us, and the standard trial can be extended on request.

All posts

Available to sell — the number your team can actually promise

May 26, 20269 min read
Available to sell — the number your team can actually promise

The number of units sitting in your warehouse is not the same as what you can promise a customer right now. Some of it is already reserved for an open order. Some of your "available" stock for a dropship SKU is not in your warehouse at all. Using the raw on-hand number overstates what you can sell.

The formula

In Vedron, available-to-sell is calculated as:

available = max(0,
  sum(on_hand across included locations)
  + dropship_pool
  - active_reservations
)

Four moving parts. Each needs to be right for the final number to be right.

On-hand across included locations

On-hand stock across your own locations, except warehouses you have flagged as excluded from fulfilment. A damaged-goods location should not inflate what is sellable. A photo-studio sample stash should not either. A quarantine location for products pending QC should not either.

Vedron treats location-level stock as the source of truth and aggregates upward. If you move 10 units from your main warehouse to your secondary warehouse, the aggregate stays the same but each location's number changes.

Dropship pool

Dropship stock is not physically in your warehouse but is legitimately available through a supplier. It is tracked as its own pool, representing what the supplier can ship within their stated lead time.

Why a separate pool, not just added to on-hand? Because the risk profile is different. Owned stock is 100% yours. Dropship stock depends on the supplier's system; if their system is wrong or they go out of stock between syncs, your "available" number is wrong until the next sync. Keeping dropship separate means you can decide per channel whether to expose it (fast-moving marketplace: yes; high-value custom orders: maybe not).

Reservations

Reservations are stock allocated to an order that has not yet shipped. The moment a customer completes checkout, the units for their order move from "available" to "reserved". When the order ships, the reserved units reduce on-hand by that quantity. When the order is cancelled, the reservation releases back to available.

Without reservations, two customers who order the same product within seconds of each other both see "available" until the shipment confirms, and one of them gets an unpleasant surprise. With reservations, the second customer sees an accurate reduced count.

The zero floor

If reservations somehow exceed on-hand plus dropship — a race condition during a flash sale, say — the calculation does not go negative. It stops at zero. The channels see "out of stock" and new orders are not accepted until stock replenishes or a reservation releases.

Showing a negative available number is a common bug in inventory systems that sum naively. Vedron does not do that. The user-facing number is always a count of units you can realistically promise.

What runs today

The available-stock calculation combines on-hand stock across all included locations, adds dropship stock from its own pool, subtracts active reservations, and floors the result at zero. One number. Every channel — storefront, Amazon, eBay, Allegro, every connected marketplace — reads from it.

The same inventory transaction model supports multi-location transfers and bundle disassembly: moving stock between locations, or breaking a bundle back into its components, is recorded the same way as every other movement. Transfers in flight show as "in transit" and do not count toward either location's sellable availability until they land.

Worked example: a bike with options

Say you sell a touring bike. Specifications:

  • Main warehouse: 8 units on-hand.
  • Secondary warehouse: 2 units on-hand.
  • Damaged-goods location: 1 unit (excluded).
  • Dropship supplier: 15 units reported available.
  • Open order reservations: 3 units.

Available-to-sell = max(0, (8 + 2) + 15 - 3) = 22 units.

The 1 damaged unit does not inflate the number. The 3 reserved units are correctly subtracted. The 15 dropship units are included because they are legitimately available if a customer orders them.

If the dropship supplier reports zero at the next sync, the number drops to 7 immediately. If a reservation is cancelled, it goes back up. Every channel reads the current number without needing to recalculate anything itself.

Frequently asked questions

What counts as a "location excluded from production"?

A location you have flagged that way. Typically a damaged-goods location, a quarantine area, a photo-studio sample stash — somewhere stock physically exists but is not meant to count toward sellable availability.

How is dropship stock different from a location I own?

It is a separate pool because it reflects supplier-side availability rather than inventory you physically control. If the supplier goes out of stock, dropship availability drops to zero even though you have not lost any stock yourself.

Can available stock ever show as negative?

No. The calculation is floored at zero. Even if reservations exceed on-hand plus dropship, the number shown is zero rather than a negative. This avoids the negative-available display problems that confuse both operators and customers.

How does the calculation handle bundle products?

A bundle's availability is derived from its component availability. If a bundle needs 1x frame and 2x wheel, and you have 10 frames and 15 wheels, the bundle shows as 7 available (limited by wheels: 15/2 = 7). The bundle itself is not stocked; the components are.

What about products with lead time from the supplier?

Lead-time stock is handled as a separate concept from available stock. Available-now is on-hand plus confirmed dropship; available-with-lead-time is on-hand plus incoming POs with expected delivery dates. The marketplaces see the former; your purchasing team sees both.

How often does the calculation refresh?

In real time. Any inventory event — a sale, a return, a stock transfer, a dropship supplier update — triggers a recalculation. The marketplaces read the result through the same stock table that the storefront reads.

What happens if a reservation sits unused for a long time?

Reservations are tied to open orders. If an order is cancelled, the reservation releases automatically. If an order sits in a long-pending state (payment not confirmed, say), the reservation holds until the order resolves. Order-expiry policies can be configured to release reservations after a set window.

Does this handle multi-location warehouses correctly?

Yes. Each location keeps its own stock figure. The available-to-sell calculation aggregates across all included locations into one number for channel display, but internal views show the breakdown so a fulfilment decision can route from the right location.

What about stock in transit between locations?

Stock in transit is tracked as a transfer transaction. The source location has decremented, the destination hasn't yet incremented, and the units show as in-transit. They do not count toward sellable availability until they arrive at the destination.

Can I see which specific orders are reserving a given SKU?

Yes. The product record shows the open reservations against it, with the order ID, customer, and reservation quantity. Clicking through goes to the order itself.

Talk to us about your setup

Every seller's mix of marketplaces, currencies and payment methods is a little different. Book a short call and we will walk through yours on your real data. Beta clients get the first two months of custom setup on us, and the standard trial can be extended on request.

Did you enjoy this article?