Skip to main content
Metrics type: Key MetricsCategory: Ecommerce Platform
Alerts for Oversell Risk (negative on-hand projected).

At a glance

A live list of catalog item variations that are projected to fall below zero on-hand once the orders already in flight are fulfilled. This is the forward-looking sibling to a stockout, it catches the moment you have sold more than you have before the cancellation emails go out. On Square, where one merchant of record takes orders from POS, web, and invoices against a shared on-hand count, oversell happens fast.

Calculation

Calculated automatically from your Square Online data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

Worked example

A US gourmet food merchant on Square. One kitchen-and-store location plus a Square Online storefront for nationwide shipping. The alert list is checked on the morning of 14 Mar 26. Three things to notice:
  1. Healthy stock can still be at risk. The Hot Sauce has 8 units on hand, which looks fine on a simple stock report, but 14 are already committed across web and invoice orders. The projection of -6 means six customers will get a cancellation unless stock is replenished or orders are reprioritised. A current-stock view would have missed this entirely.
  2. The smallest shortfall is often the easiest fix. The Coffee Rub at -3 needs only a few units to clear. Work the list by impact and effort, sometimes clearing the small shortfalls quickly protects the most customers, while the large ones need a purchase order.
  3. Pending demand is multi-channel. The Spice Box shortfall comes partly from a Square Invoice (a corporate gift order) and partly from web. Because Square shares one on-hand count, a single large invoice can tip a web-popular item into oversell. Pair with Revenue by Channel to see where the demand is coming from.

Sibling cards merchants should reference together

Reconciling against Square

Where to look in the Square Dashboard: Square Dashboard, Items & Orders, Inventory management for the current on-hand count, and Items & Orders, Orders filtered to open / unfulfilled to see committed demand. Square does not show a single projected figure, so the projection here is on-hand minus the open order quantity for each variation. To confirm a row, read the on-hand for the SKU and subtract the quantity of that SKU across open orders at the same location. Other Square Dashboard views that look like the same thing but aren’t:
  • Inventory management, on-hand: shows current stock only, not the projection. An item can look fine here and still be at risk.
  • Orders, open / in progress: shows the pending demand side. Cross-reference with on-hand to reproduce the projection.
  • Low stock alerts in Square: Square can flag low stock against a reorder threshold, but that is a static threshold, not a demand-aware projection. This card is forward-looking.
  • Item sales report: historical sales, not committed future demand. Not relevant for the projection.
Why our number may legitimately differ from Square Dashboard: Cross-connector reconciliation: The Square shared-count reality: because Square takes orders from POS, Square Online, and Square Invoices against one on-hand count, oversell is structurally easier than on platforms where channels keep separate buffers. That is the upside of one source of truth and the reason a forward-looking oversell projection earns a hero slot, it turns the shared count from a liability into an early warning.

Known limitations / merchant FAQs

How is oversell risk different from out of stock? Out of stock means an item is at zero right now. Oversell risk means an item is projected to go below zero once the orders already placed are fulfilled. You can have plenty on the shelf today and still be at risk if committed demand exceeds it. This card is the early warning; out of stock is the event. Why is an item at risk when it still has stock on hand? Because the pending orders against it exceed the stock. The projection is on-hand minus committed demand. An item with 8 units and 14 in open orders projects to -6, even though a simple stock report shows a healthy 8. Where does the pending demand come from? All Square channels that draw on the shared on-hand count, Square Online web orders, Square POS holds, and Square Invoices. A single large invoice or a viral web product can tip an item into oversell quickly, which is why the projection combines every open order at the location. What do I do when an item appears here? Two levers: increase supply or reduce committed demand. Either replenish stock (a purchase order or a transfer from another location), or pause online sales for that variation and reprioritise which orders to fulfil. Acting before the cancellations go out protects the customer relationship. Will this card stop the oversell automatically? No. It is a detection and prioritisation layer. The corrective action, restock, pause the listing, or cancel and refund, happens in Square. Once on-hand covers committed demand again, the variation drops off the list. Does a refund or cancellation clear the risk? Yes. Cancelling or refunding an order releases its committed quantity, which raises the projected on-hand. That is one of the levers, but it means a customer did not get what they ordered, so it is the last resort behind restocking. Can I tune which order states count as committed? By default we count orders that are open and not yet fulfilled at the same location. If your fulfilment flow uses custom states, the definition of committed demand can be adjusted in your Vortex IQ workspace so the projection matches how your operation actually draws stock.

Tracked live in Vortex IQ Nerve Centre

Oversell Risk (negative on-hand projected) is one of hundreds of KPI pulses Vortex IQ tracks across Square Online and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. Start for free or book a demo to see this metric running on your own data.