Skip to main content
Card class: Standard • Category: Revenue & Sales

​
At a glance

The number of Amazon orders placed in the period. It is the volume half of every revenue read: paired with Total Revenue it gives you Average Order Value, and it is the denominator behind conversion, defect, and return rates. On its own it is a simple count, but you should rarely read revenue or AOV without checking the order count underneath it first.
What it countsThe number of orders created in the window for the selected marketplace. An order is a single customer purchase, which can contain multiple units and multiple line items. The card counts orders, not units.
Orders vs unitsOne order can contain several units of one ASIN or several different ASINs. If you want unit volume, that is a separate read; this card is order-level.
FBA and FBMBoth fulfilment methods count identically. An order is an order whether Amazon ships it (FBA) or you do (FBM).
CancellationsBuyer cancellations before the order is confirmed are excluded by Amazon’s order feed. Post-confirmation cancellations behave like the API’s order state; a cancelled-after-confirmation order can briefly remain in the count until it refreshes.
Pending ordersNewly placed orders can sit in a pending state before payment clears. Whether a pending order counts can shift the very latest “today” figure slightly until it confirms.
Why it is the denominatorAOV is revenue divided by orders. Conversion, defect, and return rates all use order count as the base. A revenue move is only meaningful once you know whether orders or AOV drove it.
Time windowT/7D/30D vsP (today, last 7 days, last 30 days, each versus the prior identical window)
Alert triggerNone by default. Orders is a volume and context metric; the alerts live on revenue and the rate cards that use orders as a base.
Rolesowner, operations

​
Calculation

Calculated automatically from your Amazon Seller Central data. The card counts orders created in the selected window. See the At a glance summary above and the worked example below.

​
Worked example

A UK pet-supplies seller on amazon.co.uk. Period: trailing 30 days to 14 Mar 26, compared against the prior 30 days.
PeriodOrdersTotal RevenueImplied AOV
Prior 30 days4,100£119,000£29.02
This 30 days4,520£120,000£26.55
Orders (this card)4,520+10.2% vsP
Orders this period   =  4,520
Orders prior period  =  4,100
Change vs prior      =  (4,520 - 4,100) / 4,100  =  +10.2% vsP
Revenue change       =  (120,000 - 119,000) / 119,000  =  +0.8% vsP
Implied AOV change   =  26.55 vs 29.02  =  -8.5% (AOV fell)
Five things to notice:
  1. Orders grew but revenue barely moved. Order count rose 10.2% while revenue rose under 1%. That can only happen if AOV fell, and it did, by about 8.5%. The order count is what reveals the mix shift.
  2. Read orders before reading AOV. AOV is revenue over orders. Without the order count, an 8.5% AOV drop looks like a pricing or basket problem; with it, you can see demand actually grew and the mix moved toward cheaper items.
  3. A promotion or cheaper-ASIN surge is the likely cause. More orders at a lower average usually means a discount drove volume on lower-priced ASINs, or a low-ticket item went viral. Cross-check Top ASINs by Revenue to see which ASINs added the orders.
  4. Today is incomplete. The “today” figure fills through the day as orders confirm and pending orders clear. Use the 7-day or 30-day view for stable reads; the daily number is noisy.
  5. No alert, by design. Orders does not raise alarms itself. It is the denominator that makes the revenue, AOV, and rate alerts interpretable.
There is no alert on this card, but the divergence between strong order growth and flat revenue is exactly the kind of signal that makes the volume count worth reading alongside revenue and AOV.

​
Sibling cards merchants should reference together

Orders is one half of every revenue read. These cards are its natural partners:
CardWhy pair it with Orders
Total RevenueThe value half. Orders times AOV equals revenue; always check which one moved a revenue trend.
Average Order ValueRevenue divided by this card. A revenue change splits cleanly into an orders effect and an AOV effect.
Revenue Over TimeThe trend view. Overlaying order count on the revenue trend shows whether growth is volume-led or price-led.
Sales Volume AnomaliesThe anomaly detector that watches order and sales volume for unexpected spikes or drops.
Order Defect RateUses order count as its denominator. A defect rate is only meaningful next to the order base it sits on.
Return RateAlso order-based. The same caution applies: read the rate against the order volume underneath it.

​
Reconciling against Amazon Seller Central

Where to look in Seller Central: The closest native views are:
Seller Central → Orders → Manage Orders for the order list (filter by date and status), and Reports → Business Reports → Sales and Orders, which shows total order items and ordered-product-sales by date.
Manage Orders gives the order-by-order view; Business Reports gives the aggregated counts by day. Set the same date range and the counts should align closely. Timing and reporting-lag table:
TopicDetail
TimezoneBusiness Reports use the marketplace timezone by default; Vortex IQ uses consistent period boundaries. Orders near midnight on the boundary days can fall on different sides, which averages out over a longer window.
Pending ordersA newly placed order can sit pending until payment clears. Whether it is counted yet differs slightly between views for the very latest orders.
CancellationsA post-confirmation cancellation can briefly remain in the count until the order state refreshes on both sides.
Refresh cadenceAmazon order data updates close to real time. Vortex IQ reads it on each sync, so “today” may differ by the sync interval; yesterday and earlier align.
Why our number may legitimately differ from Seller Central:
ReasonDirectionWhy
Order vs order itemDifferent basisBusiness Reports can show “total order items”; this card counts orders. One order with three line items is one order but three order items. Compare like for like.
Timezone boundarySmall edge effectMarketplace-timezone day boundaries versus the card’s boundaries shuffle a few orders at the edges of the window.
Pending and cancelled statesOurs can differ for newest ordersPending-to-confirmed and confirmed-to-cancelled transitions land at slightly different times on the two views.
Sync intervalOurs can lag for “today”The card reflects the last sync; the latest hour of orders may be slightly behind.
Cross-connector reconciliation against other connectors the same seller may run:
CardExpected relationshipWhat causes legitimate divergence
shopify.ordersIndependent order pools. Amazon orders and Shopify orders are separate populations; summing them gives total cross-channel order volume.A multichannel listing tool that mirrors orders for inventory sync can create matching records on both sides; configure it not to double-count.
ebay.ordersMarketplace peer. Another independent order stream, useful for comparing volume and AOV across marketplaces.Unless you dual-list via a feed app, eBay and Amazon orders never overlap.

​
Known limitations / merchant FAQs

Is this orders or units? Orders. One order can contain several units and several different ASINs. This card counts the orders, not the units inside them. If revenue moves and order count is flat, units per order or AOV changed. Why does today’s order count keep changing? Today is incomplete. Orders confirm through the day as payment clears, pending orders resolve, and the latest hour syncs in. Use the 7-day or 30-day view for stable numbers; the daily figure is naturally noisy. Do cancelled orders count? Buyer cancellations before confirmation are excluded by Amazon’s feed. A cancellation after confirmation can briefly stay in the count until the order state refreshes, then drops out. Over any settled window the count reflects net confirmed orders. Why does my count differ from Business Reports? The most common reason is order versus order item: Business Reports can show total order items, while this card counts orders. A timezone boundary difference and pending-order timing also move a few orders at the edges. Compare order-to-order, same date range, same marketplace. Should I read orders or revenue first? Read them together, but let orders frame the revenue. A revenue move is either an orders move or an AOV move. Checking the order count first tells you which lever pulled the revenue trend before you go looking for a cause.

​
Tracked live in Vortex IQ Nerve Centre

Orders is one of hundreds of KPI pulses Vortex IQ tracks across Amazon Seller Central 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.