Marketplace shipping performance metrics turn day-to-day fulfillment activity into decisions you can act on. This guide explains how to monitor late dispatches, cancellations, delivery promises, tracking events, and order defects; compare the labels used by different marketplaces; run a weekly KPI review; and trace changes back to specific workflow problems. Because marketplace thresholds and reporting names can change, use this framework alongside each platform’s current seller-performance documentation.
Overview
Marketplace account health is rarely determined by one number. A seller may dispatch orders on time but still create customer-service problems through incomplete tracking, inaccurate handling times, address errors, packaging failures, or unrealistic delivery promises. The purpose of a shipping KPI dashboard is to connect those outcomes to the steps your team controls.
Start with a consistent reporting period and a defined order population. For example, review orders promised or shipped during the previous calendar week, while separately tracking open exceptions that have not yet reached a final outcome. Do not combine all marketplaces, warehouses, and shipping services into one percentage if the underlying conditions differ. A useful dashboard lets you filter by marketplace, SKU or product group, fulfillment location, carrier, service level, and order date.
Keep two types of measures together:
- Marketplace-facing measures: handling-time compliance, late shipment or late dispatch rate, cancellation rate, valid tracking coverage, delivery performance, and order defect indicators.
- Operational measures: order release time, pick-to-pack time, backlog, scan latency, address-hold rate, carrier exception rate, and customer contacts about delivery.
The first group shows what a marketplace or buyer may evaluate. The second helps you find the cause before an account-level result deteriorates. For background on the physical workflow, see Order Fulfillment Process for Small Business and Ecommerce Fulfillment Capacity Planning.
What to track
Core marketplace shipping performance metrics
Definitions vary by platform, so record both the marketplace label and your internal definition. The following measures provide a practical baseline:
- Late dispatch or late shipment rate: late-dispatched orders divided by the orders included in the reporting period. Confirm whether the platform uses the label-creation time, carrier acceptance scan, shipment confirmation, or another event as proof of dispatch.
- Handling-time compliance: the share of orders shipped within the handling time configured for the listing or order. Review whether weekends, holidays, cut-off times, and seller-set handling rules affect the calculation.
- Cancellation rate: seller-cancelled orders divided by relevant orders. Separate cancellations caused by stockouts, pricing errors, address concerns, fraud review, and customer requests; they require different corrective actions.
- Valid tracking coverage: the proportion of shipped orders with a tracking number in an accepted format and, where required, evidence that the carrier received the parcel.
- On-time delivery rate: delivered orders arriving by the marketplace’s promised or calculated date, where that measure is available. Treat this as distinct from dispatch performance: a parcel can leave on time and still arrive late.
- Delivery exception rate: orders with an event such as an address problem, failed attempt, weather disruption, damaged parcel, or carrier delay. Group exceptions by reason instead of treating every exception as a carrier problem.
- Order defect or buyer-protection signals: negative outcomes associated with the order, such as an unresolved complaint, refund, dispute, or item-not-received report. Use the platform’s current definition rather than assuming every customer contact counts as a defect.
- Backlog and aging: unshipped orders by age bucket, such as due today, overdue, and at risk. This is an early-warning measure that often moves before a late shipment rate does.
Platform comparison framework
Marketplaces may use different names for similar concepts and may calculate them using different time windows or order exclusions. Instead of copying a threshold from another seller’s account, maintain a comparison sheet like this:
| Measure | Marketplace A | Marketplace B | Marketplace C | Internal control |
|---|---|---|---|---|
| Handling-time or dispatch measure | Record current label and definition | Record current label and definition | Record current label and definition | Orders released and shipped by cut-off |
| Delivery-performance measure | Record promise and delivery event | Record promise and delivery event | Record promise and delivery event | Delivered by promised date |
| Cancellation measure | Record included orders and exclusions | Record included orders and exclusions | Record included orders and exclusions | Stock, pricing, and fraud causes |
| Tracking requirement | Record accepted scan or status rule | Record accepted scan or status rule | Record accepted scan or status rule | Label-to-first-scan time |
| Review window | Record current period | Record current period | Record current period | Weekly and rolling trend |
Update this sheet whenever a marketplace changes a reporting label, dashboard location, calculation rule, or seller-performance requirement. If the dashboard does not explain a metric clearly, save the relevant help-page link and note the date you checked it.
Use rates and counts together
A percentage without its denominator can mislead. A change from one late order to two late orders may create a large percentage swing in a small weekly sample, while a stable-looking rate can conceal a growing number of affected buyers during a high-volume period. Display the numerator, denominator, rate, and comparison period for every KPI. A simple internal formula is:
Rate = qualifying orders ÷ eligible orders × 100
Use the platform’s own calculation for account decisions, but use your internal formula for diagnosis and consistency.
Cadence and checkpoints
A weekly review is frequent enough to catch recurring breakdowns without turning the dashboard into a real-time distraction. Assign one owner and follow the same sequence each time.
- Refresh the data: export or record current marketplace metrics, open orders, tracking events, cancellations, and carrier exceptions.
- Check data quality: look for duplicate orders, missing shipment dates, orders still inside their promised window, and events that arrived late in the integration.
- Compare periods: review this week against the previous week and a rolling four-week view. Mark unusual volume, promotions, staffing changes, inventory receipts, and carrier-service changes.
- Segment the result: filter by marketplace, fulfillment site, SKU, carrier, destination region, shipping service, and shift or dispatch batch.
- Choose one or two actions: assign an owner, due date, and success measure. Avoid creating a long list of changes that nobody verifies.
A practical weekly KPI review template is:
- Reporting period and marketplaces reviewed
- Total eligible orders and shipped orders
- Late dispatch: count, rate, and top three causes
- Seller cancellations: count, rate, and cause breakdown
- Orders missing valid tracking or first carrier scan
- Delivery exceptions and open parcels by age
- On-time delivery result, if available
- Top affected SKUs, locations, carriers, or order cut-off periods
- Corrective action, owner, deadline, and next check
Run a lighter daily checkpoint during promotions or unusually high demand. Focus on orders due today, unallocated orders, stock discrepancies, label failures, and parcels waiting for a carrier handoff. The Ecommerce Order Processing Checklist can help standardize the handoff from paid order to shipment.
How to interpret changes
Metrics describe symptoms; workflow checks identify causes. Use the pattern of movement to choose the investigation.
Late dispatches rise
Check whether orders entered the queue before the stated cut-off, whether inventory was available at the assigned location, and whether pick-and-pack capacity matched demand. Review backlog by age and compare the first missed orders with staffing, equipment, or integration events. If late orders cluster around one SKU, verify the bin location, replenishment process, and listing-level handling time. If they cluster by shift, inspect handoff timing and batch release rules.
Cancellations rise
Separate preventable cancellations from customer-requested cancellations. For stock-related cancellations, compare marketplace inventory with physical counts and safety stock. For pricing or listing errors, check recent catalog edits and synchronization delays. For address or risk holds, confirm that the team uses a documented decision path rather than cancelling automatically. The guide to address verification and order holds provides a useful model for this control.
Tracking is uploaded but delivery performance worsens
Review the time between label creation, physical handoff, and the first carrier scan. A label alone may not demonstrate that a parcel entered the network. Then compare promised transit time with the service actually purchased, destination region, packaging constraints, and recurring carrier exceptions. Do not solve a transit problem by shortening the handling promise; that can increase late-dispatch exposure if the warehouse cannot meet it.
Delivery exceptions or customer contacts increase
Group cases by exception reason and actionability. Address errors may call for an order hold and customer confirmation; repeated failed attempts may call for clearer delivery instructions; damage reports may point to packaging or product-fit issues. For tracking language and buyer communication, consult Package Tracking Status Meaning. Keep a concise customer update template that states what is known, what is being checked, and when the next update will arrive.
When a metric changes, use a short root-cause record: what changed, when it started, where it is concentrated, likely cause, evidence checked, action taken, and result at the next review. This prevents repeated guesswork and creates an operating history.
When to revisit
Review the dashboard every week and conduct a fuller metric audit monthly or quarterly. A monthly review should confirm that formulas, filters, marketplace labels, handling-time settings, carrier services, and notification workflows still match the way orders are actually processed. A quarterly review should examine trends across marketplaces, fulfillment locations, product groups, and peak periods.
Revisit the framework immediately after a marketplace policy or reporting change, a warehouse move, a new carrier service, an integration migration, a large catalog expansion, or a promotion that materially changes order volume. Also revisit it after a cluster of late dispatches, cancellations, delivery complaints, or missing tracking events—even if the headline account metric has not yet moved.
Before the next busy period, set a baseline and capacity check. Confirm available inventory, cut-off times, staff coverage, label supplies, carrier collection arrangements, and escalation contacts. Use the shipping cost calculator when service changes affect landed shipping costs, and review your cancellation and edit workflow before orders reach fulfillment.
Finish each review with three actions: correct one immediate risk, investigate one recurring pattern, and schedule the next checkpoint. That rhythm turns marketplace shipping performance metrics from a passive scorecard into a practical control system for the order fulfillment process.