At a glance
Fulfilment SLA gauge for eBay orders shipped through ShipBob. Measures the percentage of eBay orders fulfilled within the seller’s promised handling-and-shipping window. The “is my 3PL hitting its delivery promise on the eBay side” card; sustained below 90% triggers TRS / Late-Shipment-Rate concerns.
| What it counts | COUNT(eBay orders shipped on-time by ShipBob) / COUNT(eBay orders fulfilled by ShipBob) × 100. On-time = carrier-acceptance scan within the seller’s promised handling time AND first-delivery-attempt scan within the carrier’s quoted transit window. |
| Listing-format scope | All eBay formats. Auctions and BIN both have stated handling times; Best-Offer-resolved orders use the underlying listing’s handling time. |
| GMV / fees framing | Not applicable, this is an SLA percentage. The downstream economic effect (TRS preservation, defect-rate avoidance) is captured in fee / standards cards. |
| Promoted Listings | Promoted-driven orders are fulfilled identically; Promoted spend has no effect on SLA. |
| Multi-site aggregation | Aggregated across every connected eBay marketplaceId that uses ShipBob fulfilment. Per-site SLA on expansion (UK and US ShipBob warehouses operate independently). |
| Currency | Not applicable, percentage metric. |
| Best-Offer-resolved orders | Counted identically to BIN orders; the handling-time clock starts at order-placement, not at offer-acceptance. |
| Refunds | Not directly relevant. A late shipment causing a buyer-initiated refund still counts as a missed-SLA event in this card. |
| Cancellations | Out-of-stock / can’t-ship cancellations don’t appear in this card (they’re not “fulfilled”); they appear instead in cancellation / defect-rate metrics. |
| Time window | 30D (rolling). Long enough to smooth daily carrier noise, short enough to surface trend changes. |
| Alert trigger | <90% on-time. eBay’s TRS late-shipment-rate cap is 3% (i.e. 97%+ on-time); the card’s amber threshold is more permissive but still surfaces material degradation. |
| Roles | owner, operations |
Calculation
Calculated automatically from your eBay 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 apparel seller using ShipBob’s Pennsylvania (US-East) and Illinois (US-Central) warehouses for ebay.com fulfilment. Period: 02 Apr 26 to 01 May 26 (30D).| Warehouse | Orders fulfilled | On-time | Late | On-time % |
|---|---|---|---|---|
| ShipBob Pennsylvania | 1,420 | 1,358 | 62 | 95.6% |
| ShipBob Illinois | 980 | 868 | 112 | 88.6% (alert tripped) |
| Aggregate | 2,400 | 2,226 | 174 | 92.8% |
- The Illinois warehouse is the drag. Pennsylvania is hitting 95.6% (above the 90% card threshold but below the 97% TRS threshold); Illinois is at 88.6% (well below the card threshold). The aggregate looks acceptable at 92.8% but masks per-warehouse divergence; per-warehouse is the actionable view.
- 88.6% on Illinois is a TRS-killing rate. eBay’s TRS late-shipment-rate cap is 3% (97%+ on-time). At 88.6%, this warehouse is contributing 11.4% late shipments to the seller’s overall late-shipment rate, far above the cap on a 12-month rolling basis. The seller has 1 to 2 cycles before TRS is at risk.
- Carrier handover is usually the cause. ShipBob warehouses pick and pack within their own SLA (typically 100% on-time), but the carrier’s first-mile pickup can be delayed. Illinois (servicing the Midwest) often hands over to UPS Ground or USPS Regional; carrier handover delays of 4 to 12 hours show up as late-shipment in eBay’s tracking-upload window.
- The fix is multi-step. (a) Talk to ShipBob about Illinois carrier handover frequency (more pickups per day = lower delay). (b) Consider switching the Illinois carrier blend toward UPS for time-sensitive orders. (c) Re-route Midwest US eBay orders to the Pennsylvania warehouse if PA can absorb the volume. (d) Increase the seller’s stated handling time on eBay listings from “Same day” to “1 business day”, legally accurate, drops the late-shipment rate by 3 to 5 ppt.
- eBay measures late-shipment from order-placement, not fulfilment-confirmation. ShipBob’s “shipped” event is when the warehouse hands over to the carrier; eBay’s late-shipment clock runs from the buyer’s order timestamp. Sub-day delays in ShipBob’s order-receipt-to-handover pipeline (rare but possible) can also contribute to the rate; check ShipBob’s order-ingestion latency.
Sibling cards merchants should reference together
| Card | Why pair it with Fulfilment SLA (via ShipBob) |
|---|---|
| Late Shipment Rate | The eBay-side metric that this 3PL gauge feeds. Should reconcile within 1 to 2 ppt for ShipBob-fulfilled orders. |
| Open INR Cases | Late shipments are 3 to 5x more likely to generate INR cases. SLA degradation on this card is the leading indicator for INR bursts 7 to 14 days later. |
| Defect Rate | Late shipments and INR auto-resolutions both feed defect rate; they’re the operational input chain. |
| Seller Standards | The cliff outcome. Sustained low SLA threatens TRS via the late-shipment-rate component. |
| Health Score | Composite that weights the on-time-shipping component at 25%. |
| Total Revenue | Economic context for SLA degradation; high-velocity SKUs through a low-SLA warehouse are higher-priority fixes. |
| Amazon FBA Performance | Marketplace peer; FBA’s equivalent fulfilment SLA. Cross-channel comparison helps decide whether to consolidate fulfilment under FBA. |
| ShipBob Operational Metrics | Connector source for the underlying SLA data. |
Reconciling against the vendor’s own dashboard
Where to look in eBay Seller Hub (eBay-side data):Seller Hub → Performance → Service Metrics, tracking-uploaded-on-time and validated-tracking rates.Where to look in ShipBob (3PL-side data):
ShipBob → Reports → Fulfilment Performance, per-warehouse pick / pack / handover times.This card cross-references both: the eBay-side “tracking-on-time” rate and the ShipBob-side “handover-on-time” rate. Divergence between the two surfaces operational gaps. Timing, settlement, and reporting-lag table:
| Topic | Detail |
|---|---|
| Timezone | eBay uses Pacific Time for US accounts; ShipBob warehouses use local time. The card normalises to UTC, sub-day boundary effects average out over 30D. |
| Settlement / payout impact | Late shipments don’t directly affect settlement, but they raise INR / late-shipment defect risk, which can introduce eBay funds-on-hold. |
| Promoted Listings cost reporting lag | Not relevant. |
| API throttling | ShipBob API: per-account rate limits typically allow real-time order push. eBay Sell Fulfillment API: 5,000 calls/day. Card refreshes every 4 hours; handover events push within 1 to 5 minutes. |
| Carrier scan latency | eBay’s late-shipment rate uses the carrier’s first-acceptance scan as the on-time benchmark. Carrier scans can lag the actual handover by 4 to 12 hours; this can paint an on-time handover as late on eBay’s side. ShipBob’s view is the truth on handover; eBay’s view is the truth on what buyers see. |
| Reason | Direction | Why |
|---|---|---|
| Carrier scan lag | Ours higher | ShipBob marks orders shipped at handover; eBay waits for carrier acceptance scan. Sub-day delays look on-time on this card but late on eBay. |
| Order-source scope | Ours subset | This card only covers ShipBob-fulfilled orders; eBay’s late-shipment rate covers ALL orders including any seller-self-fulfilled or other-3PL-fulfilled orders. |
| Tracking-validation | eBay slightly stricter | eBay also requires tracking to resolve to “delivered” within the carrier’s stated transit window. ShipBob’s view ends at handover. |
| Card | Expected relationship | What causes legitimate divergence |
|---|---|---|
shipbob.operational_metrics | Source data. This card aggregates ShipBob’s per-warehouse SLA filtered to eBay-channel orders. Should reconcile within sync-lag tolerance. | If ShipBob’s “channel” tagging mismatches the seller’s mapping, eBay-channel orders may be miscounted. |
amazon.fba_performance | Marketplace peer. Amazon FBA fulfilment SLA equivalent. Comparison helps decide whether to migrate eBay fulfilment to FBA’s multi-channel-fulfilment service. | Independent populations; FBA-fulfilled eBay orders bypass ShipBob entirely. |
Known limitations / merchant FAQs
What’s “on-time” exactly? The card uses a strict definition: (a) the order is picked, packed, and handed over to the carrier within the seller’s promised handling-time window AND (b) the carrier’s first-acceptance scan occurs within that same window. Both must hit. eBay’s own late-shipment-rate uses a similar definition but adds (c) tracking resolves to “delivered” within the carrier’s quoted transit window. Why is the card’s threshold 90% but TRS requires 97%? Because TRS allows up to 3% late-shipment, but a healthy seller should be well above the cap to absorb noise. 90% is the amber threshold (something is degrading); below 97% is the red threshold (TRS is at material risk). Tune the card to 95% if you want earlier warning. My ShipBob warehouse claims 100% on-time but my card shows 92%, why? ShipBob measures handover-to-carrier (which is fully under their control); eBay measures carrier-acceptance-scan (which depends on the carrier’s pickup frequency). The 8 ppt gap is typical and represents carrier handover delay, ShipBob handed over on time, but the carrier didn’t scan-accept until the next pickup window. Can I split this card by warehouse? Yes, on expansion. The default headline is aggregate; the per-warehouse view is the actionable view for ops teams. Does this affect TRS standing? Indirectly. eBay’s TRS late-shipment-rate cap is 3% (97%+ on-time). If this ShipBob-fulfilled card sits at 92%, your overall late-shipment rate (which includes any non-ShipBob fulfilment too) will be close to the same figure unless other channels are perfect. At 92%, TRS is at material risk. Multi-site fulfilment: do UK and US ShipBob warehouses appear together? Aggregated by default; per-marketplace breakdown on expansion. UK ShipBob warehouses ship UK orders; US warehouses ship US orders. They operate independently. Does Best Offer affect the SLA clock? The handling-time clock starts at order-placement (i.e. when the buyer’s payment captures), not at offer-acceptance. So Best-Offer-resolved orders have the same handling-time deadline as BIN orders. What about Promoted Listings? No effect. Promoted-driven orders fulfil identically to organic. My SLA dropped from 96% to 88% in a week, what happened? Three usual causes: (1) carrier issue, regional facility delay (often weather-related); (2) ShipBob-side warehouse incident, sortation, system outage, peak-volume buffer overrun; (3) integration sync issue, ShipBob receiving orders from eBay with delay. Check ShipBob’s status page first; check carrier service alerts second; investigate ingestion latency third. Action playbook when this card alerts (<90%):
- Drill per-warehouse to identify the failing facility.
- Check carrier-handover frequency at that warehouse; ShipBob can sometimes increase pickup frequency on request.
- Audit the seller’s stated handling time on listings; if “Same day” but warehouse can only handle 1-business-day on average, raise the listing-side handling time, legally accurate, drops late-shipment rate.
- Consider re-routing the warehouse’s orders during the incident (ShipBob supports geographic re-routing on a per-order basis).
- If the issue persists, evaluate FBA’s multi-channel-fulfilment service as a backup for high-velocity SKUs.