At a glance
Absolute count of Japan Post consignments delivered after the published estimated delivery date for the service tier, in the trailing 7 days. Domestic Yu-Pack late count is structurally tiny (<1 percent of volume). Most of the count for cross-border-active merchants is EMS-international where customs adds days; the count is the customer-service workload behind the On-Time Delivery Rate percentage.
| What it counts | COUNT(shipments WHERE delivered_at > expected_delivery_date) over 7 days. Consignments still in transit and exceeding aim are not counted here (they fall under Exception Rate). |
| API endpoint | POST /api/v1/tracking/list reads the events stream; GET /api/v1/shipping/items provides the consignment metadata including expected_delivery_date. |
| Service-tier scope | Yu-Pack, Yu-Pack Cool, EMS, Letter Pack Plus, Letter Pack Light. |
| Geographic OTD variance | Domestic late count concentrates in rural prefectures with Mon-Fri delivery (Akita, Yamagata, Iwate). International EMS late count concentrates by destination: UK heaviest post-Brexit, Russia and parts of Africa erratic. |
| Returns / RTO | Outbound only. |
| Climate handling | Typhoon and snow events spike the count for affected weeks; not auto-excluded. |
| Peak-period seasonality | Oseibo (mid-December) and Ochugen (mid-July) lift the count 1.5 to 2x; international EMS in those windows compresses faster than domestic. |
| Time window | 7D (rolling 7 days). |
| Alert trigger | >5% of total weekly shipments. For a 4,500/week merchant alert fires at 225 late shipments. Domestic-only merchants rarely trip; cross-border merchants need destination-aware thresholds. |
| Roles | owner, operations |
Calculation
Calculated automatically from your Japan Post data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
The Akihabara manga/anime collectibles retailer, 4,500 consignments per week. Reading at 09:00 JST on 12 Mar 26 for the trailing 7 days (06 Mar 26 to 12 Mar 26).| Service tier | Shipments (7D) | Late | Late % |
|---|---|---|---|
| Yu-Pack (domestic) | 2,925 | 18 | 0.6% |
| EMS (international) | 1,125 | 168 | 14.9% |
| Letter Pack Plus | 450 | 2 | 0.4% |
| All Japan Post tracked (this card) | 4,500 | 188 | 4.2% |
>5% not yet tripped. Three observations:
- EMS-international owns 89 percent of the late count. 168 of 188 late shipments are EMS, despite EMS being only 25 percent of volume. Of those 168, 78 are EMS-to-UK (Brexit customs lag), 32 are EMS-to-Russia (network unreliability), 28 are EMS-to-Italy/Spain (slower customs in Southern Europe), the rest spread across other destinations.
- Domestic late count of 18 is the structural minimum. 18 out of 2,925 Yu-Pack consignments is 0.6 percent, which is normal Japan Post performance. Most of these are Friday-shipped consignments to rural prefectures with Mon-Fri delivery, missing a Monday aim by one day.
- The customer-service load is concentrated. The merchant’s CS team will see most WISMO tickets come from UK and EU customers; the Japanese customers will not file tickets because the parcels arrive on time. Staff Japanese-English bilingual support for the 25 percent of volume that generates 89 percent of late-related contacts.
Sibling cards merchants should reference together
| Card | Why pair it with Late Shipments | What the combination tells you |
|---|---|---|
| On-Time Delivery Rate | Percentage view of the same population. | Percentage is customer-felt; count is operations workload. |
| Exception Rate | Leading indicator. | Domestic exceptions are rare; spikes signal a real network event. |
| Shipments by Destination | Geographic concentration. | Confirms whether the late count is domestic or international. |
| OTD by Route | Per-prefecture and per-country breakdown. | Identifies which lanes drive the bulk of lates. |
| Avg Transit (days) | Mean transit creep. | Rising transit time predicts late count rising in 1 to 2 weeks. |
Cross-connector: shopify.unfulfilled_orders | Upstream input. | Backlog 2 to 4 days ago shows up as late shipments today. |
Cross-connector: shopify.refund_rate | Downstream consequence. | Late spike at day 0 lifts refunds at day 7 to 14. |
Reconciling against the vendor’s own dashboard
Where to look in Japan Post’s own portal: Japan Post Business → Web Yu-Pri (My Page) → Reports → Shipment Status → Filter: delivered late. Yu-Biz contract customers find the same view in the Yu-Biz portal → Performance → Late Shipments. Why our number may legitimately differ from Japan Post’s report:| Reason | Direction | Why |
|---|---|---|
| Timezone (JST) | Boundary day | Portal in JST (UTC+9); card in UTC. Daily snapshots can shift by a day; weekly rolling averages out. |
| Customs lag for international | Ours higher | EMS consignments held at destination customs are counted late by the card; the portal sometimes pauses the SLA clock during customs. |
| Climate-driven exception spikes | Either | Typhoon/snow-affected lanes excluded from official portal stats are still counted by the card. |
| Peak-period batch processing | Either | Mid-December and mid-July, the portal can take 3 to 7 days to reflect new lates; the card matches the API. |
| In-transit-but-already-late | Ours lower | The card counts only delivered consignments past aim. The portal sometimes flags in-transit-past-aim as “late already”. |
| Card | Expected relationship | Causes of legitimate divergence |
|---|---|---|
shopify.unfulfilled_orders | Upstream input. | Webhook delays, B2B/pre-order flows. |
shopify.refund_rate | Downstream sentiment. | Refunds have many drivers. |