FedEx OTD by Sales Channel, FedEx

Metrics type: Cross-Platform Metrics • Category: Shipping & Courier

Per-channel FedEx OTD.

At a glance

FedEx on-time delivery rate split out by the sales channel that originated the order: Shopify, Amazon, Walmart, BigCommerce, eBay, TikTok Shop, B2B/EDI, and so on. Different channels carry different SLAs and ship-by-dates; the aggregate On-Time Delivery Rate hides whether one channel is dragging the headline. Marketplace channels (Amazon Seller-Fulfilled Prime, Walmart 2-Day) carry the strictest commits and the steepest penalties when missed.


What it counts	`COUNT(shipments WHERE actualDeliveryDateTime <= scheduledDeliveryDate AND channel = X) / COUNT(delivered shipments WHERE channel = X)`, computed per channel over the trailing 30 days. The aggregate equals On-Time Delivery Rate.
How “channel” is determined	The shipper extracts the channel attribution from the originating ecommerce platform (Shopify order tag, Amazon Seller Central order ID, BigCommerce order metadata) and stamps it on the FedEx booking via the `customerReferences` array. Vortex IQ reads the reference and groups shipments by channel.
Delivery success criterion	Same as the parent card: FedEx Code 01 (DL) Delivered scan with `actualDeliveryDateTime` populated.
On-time threshold	`actualDeliveryDateTime` ≤ `scheduledDeliveryDate` from the booking. Per-channel commits may differ: Amazon Seller-Fulfilled Prime requires 2-day delivery from order placement (calendar-day clock) regardless of FedEx’s transit-time tables, so a shipment that hits FedEx’s commit but misses Amazon’s promise can fail the channel SLA.
Channel SLA layering	FedEx scores against its own commit; Amazon and Walmart score against their own. The card counts shipments late if either fails. For the most common case (FedEx commit met but channel SLA missed), the marketplace’s seller-performance dashboard is the authoritative scorekeeper for penalties.
Returns / RTO	Excluded across all channels. RTO drivers vary by channel (Amazon return-buy-online behaviour, Shopify abandoned-shipment customer-service actions).
Channel coverage	Most DTC merchants see Shopify, BigCommerce, Amazon (FBM), Walmart, eBay, TikTok Shop, Etsy, Faire, and direct-B2B channels in this card. Channels with <5% volume are pooled into “Other” by default to avoid noise.
Marketplace penalty regimes	Amazon Seller-Fulfilled Prime: Late Shipment Rate >4% over rolling 7-day = listing suspension warning. Walmart 2-Day: Order Defect Rate (which includes late shipment) >2% = ineligible for 2-Day badge. eBay: Late Shipment Rate >5% = “Below Standard” seller status. Each marketplace has its own 30-day or rolling window.
Time window	`30D` (rolling 30 days)
Alert trigger	`any channel <90%` (warn). The aggregate alert lives on the parent card; this card alerts per channel.
Sentiment key	`on_time_delivery_rate`
Roles	owner, operations, marketing

Calculation

Calculated automatically from your FedEx 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 DTC home-and-garden merchant selling on Shopify (own site), Amazon FBM, Walmart Marketplace, eBay, and Faire (B2B). Reading taken at 09:00 ET on 12 Mar 26 for the trailing 30 days.

Sales Channel	Shipments	On-Time	Marketplace SLA	Delta vs aggregate
Shopify (own site)	9,420	95.1%	n/a (merchant promise)	+1.2 ppt
Amazon FBM (Seller-Fulfilled Prime)	3,180	91.2%	96% required	-2.7 ppt
Walmart 2-Day	1,680	88.4%	95% required	-5.5 ppt
eBay	920	94.6%	95% required	+0.7 ppt
Faire B2B	480	97.1%	n/a (NET-30 invoicing)	+3.2 ppt
Other (pooled)	150	92.0%	varies	-1.9 ppt
All channels (aggregate)	15,830	93.9%	n/a	0

The card shows aggregate at 93.9%; per-channel alerts have tripped on Amazon FBM, Walmart, and Other. Five things to notice:

Walmart 2-Day at 88.4% is the most urgent issue. Walmart suspends 2-Day badge eligibility above 5% Order Defect Rate; this account is currently at 11.6% (100% - 88.4%). Loss of 2-Day badge means the listing drops in search rankings and conversion falls 30 to 50%. Investigation: 78% of Walmart misses are far-zone Ground shipments to East Coast customers from the merchant’s California DC. Fix: route Walmart 2-Day orders to FedEx Express (2Day) at higher unit cost, or pre-position inventory in a second East Coast DC.
Amazon FBM at 91.2% is in the warn zone but not yet at suspension. Amazon’s Late Shipment Rate threshold is 4%; this is at 8.8%. The trajectory matters more than the level: if it climbs another point, listings risk Seller-Fulfilled Prime suspension and the merchant loses the Prime badge on those SKUs. Same fix vector as Walmart, the channel SLAs are tighter than FedEx’s own commits.
Shopify at 95.1% is healthy because the merchant sets the promise. On the merchant’s own site, checkout copy says “delivered in 5 to 7 business days”; FedEx Ground hits this comfortably even on far zones. The mistake to avoid is tightening the on-site promise to match marketplaces; the merchant should keep the wider window for own-site orders.
Faire B2B at 97.1% is the highest performer because volumes are bigger and ship from one DC. B2B orders go in pallet quantities, often via FedEx Freight or LTL services with looser commit windows. The number is good but not directly comparable to DTC channels.
The 5.5 ppt Walmart drag would not show on the aggregate alone. Walmart is 11% of volume; the headline 93.9% looks fine. Splitting by channel reveals the problem. This card exists for exactly this reason: marketplace channel performance can degrade silently while the aggregate stays in the green.

Note: this card pairs naturally with the platform-side dashboards (Amazon Seller Central → Account Health → Shipping Performance, Walmart Seller Centre → Performance → Order Defects). The merchant should reconcile this card to the marketplace’s own scorekeeping weekly.

Sibling cards merchants should reference together

Channel-split on-time is the diagnostic layer above the aggregate. Pair it with these to act on what each channel needs.

Card	Why pair it with FedEx OTD by Sales Channel	What the combination tells you
On-Time Delivery Rate	The aggregate this card disaggregates.	The aggregate hides channel-specific problems; this card surfaces them. Always read together.
OTD by Route	Geography split.	Often the channel-on-time problem is a zone problem (e.g. Walmart customers happen to be East Coast for a West Coast merchant). Cross-tab channel × zone identifies the actionable fix.
Shipments by Service	Service-mix split.	A merchant who routes Amazon FBM through Ground (cost-cutting) but Shopify through 2Day will see the channel divergence in this card. Service-mix decisions cause channel-specific on-time.
Avg Shipping Cost	Cost trade-off.	Fixing channel on-time often requires shifting that channel’s volume to faster (more expensive) FedEx services. The cost climb shows up here.
Cross-connector: `shopify.unfulfilled_orders`	Channel attribution upstream.	Shopify backlog is the leading indicator for the Shopify-channel row of this card.
Cross-connector: Amazon Seller Central	Marketplace-side scorekeeping.	Amazon’s own Late Shipment Rate is the authoritative number for FBM/SFP penalties. Reconcile weekly.
Cross-connector: `shopify.refund_rate`	Channel-tagged refund tracking.	Refund-rate by channel often correlates 1:1 with on-time-rate by channel; a ppt slip on this card predicts a 0.3 to 0.7 ppt rise in that channel’s refund rate.

Reconciling against the vendor’s own dashboard

Where to look in FedEx’s own dashboard: FedEx Reporting Online does not natively split by sales channel; FedEx is the carrier, not the marketplace. The card relies on the customerReferences field stamped at booking time to attribute channel. Reconciliation against FedEx’s portal is therefore at the aggregate level, not per-channel; for per-channel scorekeeping, reconcile against the marketplace’s own seller-performance dashboard. Why our number may legitimately differ from the marketplace’s dashboard:

Reason	Direction	Why
SLA clock differs	Either	Amazon counts late-ship from order placement (calendar-day clock, including weekends and holidays); FedEx counts from label-print to delivery (business-day clock per service). The Amazon-defined late may be earlier than the FedEx-defined late.
Order-to-ship lag	Card may show higher	If the WMS takes 24+ hours to print a label after the Amazon order (typical for non-Prime FBM), the FedEx-side commit is computed from the later label-print time. Amazon scores from order placement and may flag the same shipment as late while FedEx scores it on-time.
Channel attribution accuracy	Either	Shipments without a `customerReferences` channel tag fall into “Other”. If the merchant’s WMS or label-print app does not always populate the channel reference, the channel split is incomplete. Verify by comparing total shipments to channel sums.
Marketplace pause/exception periods	Marketplace may show higher	Amazon and Walmart sometimes pause SLA scoring during declared service disruptions (named storms, hub outages); the card does not. During an active disruption, marketplace dashboards may show better numbers than the card.

Cross-connector reconciliation:

Card	Expected relationship	What causes legitimate divergence
Amazon Seller Central → Account Health	Direct comparison for Amazon FBM channel.	Different SLA clock as above.
Walmart Seller Centre → Performance	Direct comparison for Walmart channel.	Walmart counts all post-purchase issues including damage and returns; this card is on-time-only.
`shopify.unfulfilled_orders`	Upstream Shopify channel context.	Backlog drives forward-looking on-time issues; this card is the lagging measurement.
`bigcommerce.bc_unfulfilled_orders`	Same as Shopify for BigCommerce channel.	Same caveat.

Known limitations / merchant FAQs

My WMS doesn’t tag channel on the FedEx booking, can I still use this card? Partial coverage only. Without channel attribution at booking, every shipment falls into “Other”. Configuration to add: in your WMS or label-print app (ShipStation, ShippingEasy, Shippo, EasyPost), enable “include sales channel as customer reference” on the FedEx booking template. Once enabled, new shipments populate the channel; existing data is not retroactively tagged. Amazon’s Account Health says my Late Shipment Rate is 6%, but this card says 91% on-time (9% late). Why the difference? Two reasons. (1) Amazon clocks late from order placement (calendar-day); FedEx clocks late from label-print to delivery (business-day per service). (2) Amazon counts late-shipment for orders that did not ship at all within the promised window (regardless of FedEx); the card counts only orders that did ship via FedEx. The Amazon number is the binding one for SFP penalties; this card is the diagnostic. A Walmart 2-Day shipment delivered on time per FedEx but Walmart says it was late. What happened? Order-to-ship lag. Walmart 2-Day requires 2 calendar days from order placement to delivery. If the merchant’s WMS took 36 hours to print the label, FedEx 2Day starts the clock at 36-hour mark and delivers in time relative to FedEx’s commit, but misses Walmart’s calendar-day clock. Fix is upstream of FedEx: tighten the WMS pick-pack time for Walmart orders (cutoff time discipline, pick-list prioritisation). Should I move marketplace orders to FedEx Express to protect channel SLAs? Often yes. FedEx 2Day has tighter and more reliable transit times than Ground; for Amazon SFP and Walmart 2-Day where SLA penalties are real, the cost premium of 2Day is usually justified by listing-eligibility preservation. Test on the worst-performing channel first; aim to lift that channel by 2 to 4 percentage points before expanding. My TikTok Shop channel has very small volume but bad on-time. Should I worry? Only if you are scaling it. Small-volume channels show high variance from individual late shipments. Watch the trend; if volume grows past 100/period and on-time stays below 90%, treat it like a Walmart problem. Below 100/period, the noise dominates; do not over-interpret. Do channels include B2B EDI orders? Yes if the EDI translator stamps a channel reference on the FedEx booking. Most EDI integrations route through the WMS, which has its own channel tag (e.g. “edi_target”, “edi_homedepot”). The card can split B2B further into specific retail accounts if the WMS tags them; ask your CSM about per-retailer channel breakdown. Why is Faire B2B almost always the highest-performing channel? Three reasons. (1) Volume is shipped in pallet quantities or large parcels with looser commit windows. (2) B2B accounts have NET-30 invoicing and don’t have rigid consumer-facing delivery promises. (3) Faire’s checkout shows wider delivery windows than DTC. The number is a real positive but not directly comparable to DTC channels. The aggregate is fine but Walmart is failing. Can I fix Walmart without changing anything for other channels? Yes, that is the leverage of this card. Specific actions: (1) Route Walmart orders to a closer DC if you have multiple. (2) Force Walmart orders to 2Day or Express instead of Ground, even at higher cost. (3) Tighten WMS pick-pack cutoff to give the FedEx 2Day clock more buffer. Each action targets Walmart only; Shopify and B2B carry on with their existing routing. Do channel SLAs change during Q4? Marketplaces often relax SLAs during declared peak (typically the week of Christmas) but tighten them in the weeks before. Check Amazon’s and Walmart’s seasonal-policy bulletins (October each year) for the exact dates. Plan staffing and inventory positioning around the strict window (typically late November through 20 Dec), not the relaxed week.

Tracked live in Vortex IQ Nerve Centre

FedEx OTD by Sales Channel is one of hundreds of KPI pulses Vortex IQ tracks across FedEx 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.

Get Started

The AI OS

At a glance

Calculation

Worked example

Sibling cards merchants should reference together

Reconciling against the vendor’s own dashboard

Known limitations / merchant FAQs

Tracked live in Vortex IQ Nerve Centre

​At a glance

​Calculation

​Worked example

​Sibling cards merchants should reference together

​Reconciling against the vendor’s own dashboard

​Known limitations / merchant FAQs

​Tracked live in Vortex IQ Nerve Centre

At a glance

Calculation

Worked example

Sibling cards merchants should reference together

Reconciling against the vendor’s own dashboard

Known limitations / merchant FAQs

Tracked live in Vortex IQ Nerve Centre