OPS (Ordered Product Sales) - Amazon Glossary

Ordered Product Sales (OPS) is an Amazon reporting metric that measures the total dollar value of products ordered by customers within a defined time period, calculated at the moment an order is placed - before cancellations, returns, or refunds are processed. It is Amazon's primary top-line revenue signal within Seller Central and the foundational metric in Amazon Business Reports, used to track sales performance, advertising efficiency, and marketplace growth.

Why Does OPS Matter for Amazon Sellers?

OPS is the starting point for virtually every financial and operational analysis an Amazon seller conducts - it is the revenue numerator in ACoS, TACoS, conversion rate, and advertising return on ad spend (ROAS) calculations, and the primary signal Amazon uses to rank sellers within its internal performance benchmarks. Understanding what OPS measures - and critically, what it does not measure - is essential for building accurate P&Ls, advertising models, and growth forecasts. Sellers who treat OPS as equivalent to realized revenue systematically overstate their top line, because OPS captures orders at placement, not cash received. The gap between OPS and actual disbursed revenue - created by returns, cancellations, and Amazon's settlement cycle - can represent 5–25% of reported OPS depending on category, and planning on OPS without adjusting for this gap distorts every downstream metric it feeds.

How Is OPS Calculated?

OPS is a summation metric - Amazon aggregates the ordered value of every unit sold across a defined reporting window:

$$\text{OPS} = \sum_{i=1}^{n} (\text{Units Ordered}_i \times \text{Selling Price}_i)$$

Where each transaction i represents an individual order line at its selling price at the time of order placement. OPS is reported inclusive of any promotional discounts applied at checkout - if a unit sells at $24.99 with a $5 coupon applied, OPS records $19.99 for that unit, not $24.99.

OPS does not include:

• Shipping revenue (reported separately where applicable)

• Gift wrap charges

• Sales tax collected by Amazon

• Reimbursements from Amazon for lost or damaged inventory

OPS does include:

• Units subsequently cancelled by the buyer or seller (until the cancellation is processed)

• Units subsequently returned (until the return is processed and the refund issued)

• Orders placed under promotional pricing, lightning deals, or coupons (at the discounted price)

OPS vs. Net Sales: Understanding the Gap

The difference between OPS and net realized sales is one of the most consequential - and most commonly ignored - distinctions in Amazon financial reporting:

$$\text{Net Sales} = \text{OPS} - \text{Returns} - \text{Cancellations} - \text{Promotional Refunds}$$

$$\text{OPS-to-Net-Sales Gap\%} = \frac{\text{Returns} + \text{Cancellations}}{\text{OPS}} \times 100$$

For most Amazon categories, this gap runs between 3% and 8%. In high-return categories - apparel (15–40%), electronics (10–20%), and footwear (20–35%) - the gap is material enough to require explicit modeling in any revenue forecast. A seller in the apparel category reporting $500,000 in monthly OPS may be realizing only $325,000–$425,000 in net sales after returns. Building a P&L on OPS in high-return categories without a returns adjustment produces a revenue figure that bears little resemblance to cash actually received.

Where OPS Appears in Seller Central

Amazon surfaces OPS across multiple reporting interfaces within Seller Central, each with different granularity and use cases:

Sales Dashboard

The default homepage metric in Seller Central. Displays OPS for today, yesterday, the last 7 days, and the last 30 days as a headline number alongside units ordered. Useful for daily performance monitoring but offers no ASIN-level breakdown.

Business Reports - By ASIN

The most granular OPS view available in Seller Central. Reports OPS at the parent and child ASIN level for custom date ranges, alongside units ordered, sessions, page views, unit session percentage (conversion rate), and Buy Box percentage. This is the primary report used for ASIN-level performance analysis.

Business Reports - By Date

Aggregates OPS across all ASINs for a selected date range. Used for trend analysis, period-over-period comparisons, and identifying revenue seasonality patterns.

Advertising Reports

OPS appears as the revenue denominator in ACoS and ROAS calculations within campaign reporting. Amazon's advertising console uses OPS - specifically attributed sales within the attribution window - as the revenue figure for all advertising efficiency metrics, which is why advertising-reported revenue and Business Reports OPS can diverge when attribution windows overlap period boundaries.

Brand Analytics

For Brand Registry enrolled sellers, Brand Analytics surfaces OPS-adjacent metrics including Repeat Purchase Rate, New-to-Brand Orders, and Market Basket Analysis - all of which use OPS as the underlying transaction base.

In Practice: OPS in Decision-Making

Correct approach: A seller reviews their Business Reports By ASIN report for the trailing 30 days. Their flagship ASIN shows $48,000 in OPS with 1,920 units ordered. They cross-reference with their returns data in the Returns Report and identify a 9% return rate on this ASIN - $4,320 in returns. Their net realized sales are approximately $43,680. They build their monthly contribution margin model on $43,680, not $48,000, and set their TACoS target against net sales rather than OPS. Their advertising budget is calibrated to a revenue base that reflects actual cash generation, not gross order volume.

Common mistake: A seller tracks OPS as their primary KPI and celebrates consistent month-over-month growth. OPS has grown from $80,000 to $120,000 over six months - a 50% increase. What they have not tracked is that their return rate has simultaneously grown from 4% to 14%, driven by a quality issue introduced in their most recent manufacturing run. Net realized sales have grown from $76,800 to $103,200 - a 34% increase, not 50%. Their advertising spend has scaled proportionally to OPS, meaning they are now overspending on advertising relative to the revenue base actually being realized. The quality issue, invisible in the OPS trend, is compounding into both a margin and a account health problem through elevated Order Defect Rate (ODR) signals.

OPS and Advertising Metrics: The Attribution Relationship

OPS is the revenue base for Amazon's core advertising efficiency metrics, but the relationship between OPS reported in Business Reports and OPS attributed in advertising reports requires careful handling:

$$\text{ACoS} = \frac{\text{Ad Spend}}{\text{Attributed OPS}} \times 100$$

$$\text{TACoS} = \frac{\text{Total Ad Spend}}{\text{Total OPS (Organic + Paid)}} \times 100$$

Attributed OPS in advertising reports reflects sales that Amazon's attribution model credits to a specific ad click within the attribution window (typically 7 days for Sponsored Products). This figure differs from Business Reports OPS for three reasons:

• Attribution window overlap: Sales occurring near reporting period boundaries may be attributed to ads in one period but recorded as OPS in another

• Multi-touch attribution: Amazon's model attributes the full order value to the last ad click, which can result in the same OPS unit being attributed to multiple campaign types simultaneously in aggregate reporting

• Organic vs. paid split: Business Reports OPS includes all orders regardless of source; advertising-attributed OPS includes only orders Amazon's model connects to an ad interaction

Sellers who use advertising-attributed OPS as their total revenue figure - rather than Business Reports OPS - will undercount organic sales and produce a TACoS calculation that overstates advertising dependency. The correct TACoS calculation always uses total Business Reports OPS as the denominator.

OPS as a Benchmark: Period-Over-Period and Competitive Context

Beyond its role in internal financial modeling, OPS serves as the primary benchmark metric for several comparative analyses:

Year-over-Year (YoY) OPS Growth

The standard growth metric for evaluating Amazon business momentum. YoY comparison normalizes for seasonality - comparing Q4 2025 OPS to Q4 2024 OPS eliminates the seasonal distortion that makes month-over-month comparisons misleading in categories with significant Q4 concentration.

OPS per ASIN (Catalog Efficiency)

Dividing total OPS by active ASIN count gives a catalog efficiency metric - the average revenue contribution per listed SKU. A declining OPS-per-ASIN trend signals catalog fragmentation, where new ASIN launches are cannibalizing rather than incrementally growing total OPS.

OPS Market Share (Brand Analytics)

For Brand Registry sellers, Amazon's Market Basket Analysis and Search Query Performance reports allow sellers to estimate their OPS share within specific search query clusters - a proxy for category market share that informs competitive positioning and keyword investment decisions.

FBA vs. FBM Context

FBA sellers see OPS recorded at the moment of order placement, with fulfillment handled by Amazon. Because Amazon controls the fulfillment process, cancellation rates on FBA orders are structurally lower than on FBM orders - Amazon's fulfillment reliability reduces the buyer-initiated cancellation rate that would otherwise compress OPS-to-net-sales conversion. However, FBA return rates can be higher in certain categories because Amazon's frictionless returns process lowers the behavioral barrier to returning a product, inflating the OPS-to-net-sales gap relative to fulfillment models with more friction in the returns process.

FBM sellers experience a wider and more variable OPS-to-net-sales gap than FBA sellers, driven by higher cancellation rates (FBM sellers sometimes cancel orders they cannot fulfill on time, which counts against OPS), longer fulfillment windows that increase buyer-initiated cancellations, and returns processes that - while less frictionless than FBA - still generate OPS reversals. FBM sellers should apply a larger returns and cancellations haircut to OPS when modeling net revenue, particularly in categories with high consumer price sensitivity where buyers frequently order from multiple sellers simultaneously and cancel duplicates.

SoldScope Expert Tip: Build an OPS Decomposition Model to Identify True Growth Drivers

Most sellers monitor OPS as a single aggregate number - total revenue for the period. This obscures the actual drivers of OPS movement and makes it impossible to identify whether growth is structural or fragile.

An OPS decomposition splits total OPS into its component drivers:

$$\text{OPS} = \text{Sessions} \times \text{Conversion Rate} \times \text{Average Order Value (AOV)}$$

Each of these three drivers responds to different levers. Sessions are driven by organic rank, PPC impressions, and external traffic. Conversion rate is driven by listing quality, price competitiveness, review count and rating, and Buy Box ownership percentage. AOV is driven by product mix, bundle strategy, and price point.

The non-obvious move: run this decomposition monthly at the ASIN level and track each component in a trend table alongside total OPS. When OPS grows, identify which driver is responsible - if sessions are up but conversion rate is flat, the growth is traffic-driven and potentially fragile if the traffic source (a PPC campaign, a rank improvement) reverses. If conversion rate is improving while sessions are flat, the listing or pricing changes are compounding value in a more durable way. When OPS declines, the decomposition immediately isolates whether the problem is a traffic problem (sessions down - check rank and PPC), a conversion problem (sessions flat, conversion down - check price, reviews, Buy Box), or an AOV problem (units flat, revenue down - check promotional pricing impact). Sellers who run this decomposition never spend more than a few minutes diagnosing an OPS variance; sellers who track only total OPS can spend weeks investigating the wrong variable.

Frequently Asked Questions

What is the difference between Ordered Product Sales and Shipped Revenue on Amazon?

OPS records revenue at the moment an order is placed, regardless of whether the item has shipped or been delivered. Shipped revenue - sometimes referenced in older Amazon reporting terminology - records revenue when the item ships. For FBA sellers, the difference is typically one to two days. For FBM sellers with longer fulfillment windows, the gap can be more significant. Most current Seller Central reporting uses OPS as the standard metric; sellers reviewing older reports or third-party integrations should confirm which definition the data source uses.

Why does my OPS in Business Reports not match the revenue in my advertising console?

Advertising console revenue reflects attributed sales - orders that Amazon's attribution model connects to a specific ad click within the attribution window. Business Reports OPS reflects all orders regardless of source. The two figures will always differ because: organic orders appear in Business Reports OPS but not in advertising-attributed revenue; attribution window timing can shift sales across reporting periods; and Amazon's attribution model may attribute the same order to multiple campaign types in aggregate. Use Business Reports OPS for P&L and growth analysis; use advertising console attributed revenue for campaign-level efficiency measurement.

Does OPS include VAT or sales tax?

No. Amazon collects and remits sales tax on behalf of sellers in US states where it is obligated to do so under marketplace facilitator laws. Sales tax collected is excluded from OPS - it flows through Amazon's tax remittance process and does not represent seller revenue. In EU and UK markets, VAT is similarly excluded from the OPS figure reported in Seller Central, though sellers should confirm the specific treatment in their account's regional reports as VAT handling varies by marketplace.

How often does Amazon update OPS in Seller Central?

The Sales Dashboard updates OPS approximately every hour for recent activity. Business Reports generate OPS data with a lag of up to 72 hours for some date ranges, particularly for recently completed periods where returns and cancellation processing may still be ongoing. Sellers monitoring real-time OPS for same-day decisions should use the Sales Dashboard; sellers building financial models should use Business Reports with a lag allowance for period-end processing.

Can OPS decrease after it has been recorded?

Yes. OPS figures in Business Reports can be revised downward after initial recording when cancellations are processed, returns are completed, or Amazon issues refunds on the seller's behalf. This is why OPS figures for very recent periods - particularly the current day or the last 48 hours - are preliminary and should not be used for financial modeling until the period has fully settled. Historical OPS figures for completed periods are generally stable but can still be revised if Amazon processes a late return or chargeback.

How SoldScope Helps

SoldScope's Rank Tracker connects OPS performance directly to organic rank movement - allowing sellers to validate whether OPS growth is driven by sustainable ranking improvements or transient traffic sources, and to identify the keyword positions driving the sessions that convert to OPS. The Keyword Research and Listing Analyzer tools address the conversion rate and AOV components of the OPS decomposition model, helping sellers identify listing and pricing optimizations that improve OPS without requiring incremental ad spend. For sellers monitoring OPS at the catalog level, SoldScope's Chrome Extension accelerates competitive benchmarking by surfacing ASIN-level sales estimates directly within Amazon search results - providing external context for evaluating whether an OPS trend reflects individual listing performance or broader category movement.