Exception Rate, Japan Post

Metrics type: Key Metrics • Category: Exceptions & Claims

At a glance

Share of Japan Post consignments that threw a delivery exception in the trailing 30 days, compared with the prior 30-day period. An exception is any tracking scan that diverts a parcel from the normal accept to delivered path: absence redelivery (fuzai), address incomplete, refused, customs held (EMS), damaged, or lost. This is the leading indicator that predicts a falling on-time rate and a rising claims queue 24 to 72 hours later.


What it counts	`COUNT(shipments WHERE has_exception_scan = true) / COUNT(shipments WHERE accepted = true)` over the rolling 30-day window, expressed as a percentage, with the prior 30 days shown alongside (`vsP`). Each consignment counts once even if it logged several exception scans.
Data source	Japan Post Tracking Service (追跡サービス) status history. The Vortex IQ connector ingests the per-item tracking event list and classifies each Japanese status string (for example 持ち戻り “returned to depot”, ご不在 “addressee absent”, 通関手続中 “in customs clearance”) into a normalised exception taxonomy. Domestic Yu-Pack and international EMS items both feed this card.
What counts as an exception	Absence / fuzai redelivery attempts, address incomplete or unreadable, addressee refused, held at customs (EMS), damaged in transit, lost / untraceable, and detained for prohibited-item check. A successful redelivery after a fuzai notice still scores the consignment as an exception, because it cost a failed first attempt.
Return-leg inclusion	Outbound only. Return-to-sender consignments are tracked separately on Returned to Sender; they are excluded from this denominator to avoid double counting a parcel that already failed outbound.
Time window	`30D vsP` (rolling 30 days against the prior 30 days). The 30-day window smooths the heavy weekday despatch cycle and the absence-redelivery tail, which can run 1 to 3 days behind the first attempt.
Alert trigger	`>3%` exception rate over the window. For a merchant shipping 6,000 parcels a month that is roughly 180 exception consignments, the point at which the redelivery and customer-service load becomes material.
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

A Tokyo-based DTC speciality-foods brand, around 6,200 outbound parcels per month, ships 80 percent domestic Yu-Pack (ゆうパック) and 20 percent EMS to overseas customers (mostly US, Taiwan and Singapore). Reading taken at 09:00 JST on 14 Apr 26 for the trailing 30 days (15 Mar 26 to 14 Apr 26), compared with the prior period (13 Feb 26 to 14 Mar 26).

Exception type	Consignments (30D)	Share of accepted
Absence redelivery (fuzai)	168	2.7%
Address incomplete / unreadable	41	0.66%
Held at customs (EMS)	33	0.53%
Refused by addressee	12	0.19%
Damaged / lost	7	0.11%
All exceptions (this card)	261	4.2%

Accepted consignments in the period: 6,210. The card reads 4.2 percent, up from 3.1 percent in the prior period, so the alert at >3% is tripped and the period-over-period delta is +1.1 points. Five things to notice:

Absence (fuzai) dominates, as it almost always does in Japan. Japanese delivery culture means many households are out during the day, and the carrier leaves an absence notice (不在票) rather than a card-only attempt. 2.7 percent absence is normal-to-high; the lever is not the carrier, it is offering Yu-Pack delivery-time-slot selection and PUDO / convenience-store (コンビニ受取) or locker (はこぽす) pickup at checkout. Promoting time-slot selection typically halves the fuzai rate.
The +1.1 point jump is the story, not the absolute level. A single high reading is noise; a period-over-period rise is signal. Check the despatch calendar against the prior period for an obvious cause (a product launch that shipped to a lot of new, unverified addresses will spike address-incomplete exceptions).
Customs holds are an EMS-only sub-population. 33 customs holds on roughly 1,240 EMS items is a 2.7 percent EMS customs-hold rate. If that climbs, the cause is usually CN23 declaration quality, check EMS CN23 Customs Document Generation Failure Rate; a failed auto-generation forces a manual CN23 that is more error-prone and gets held.
Exception rate leads the delivery cards. Today’s 4.2 percent will show up as a dip on On-Time Delivery Rate and a rise on Late Shipments within 24 to 72 hours. Treat this card as the early-warning dial.
Damaged / lost is small but expensive. 7 consignments is rounding on the rate, but each one is a likely claim. Cross-check Open Claims and Claim Value (open); damaged perishable food is the worst case because the customer experience is poor even when the claim pays out.

Sibling cards merchants should reference together

Exception rate is the leading-indicator dial. Pair it with these to find root cause and downstream impact:

Card	Why pair it with Exception Rate	What the combination tells you
On-Time Delivery Rate	The outcome metric this card predicts.	A rising exception rate today is a falling OTD rate in 24 to 72 hours. If exceptions rise but OTD holds, redeliveries are succeeding fast.
Late Shipments	The absolute late count.	Exceptions that do not resolve same-day become late shipments. The conversion ratio tells you how efficient Japan Post redelivery is for your lanes.
Failed Deliveries	The hard-failure subset.	Exceptions that never resolve (refused, undeliverable) graduate to failed deliveries and then to returned-to-sender or claims.
Returned to Sender	Where unresolved exceptions end up.	Repeated fuzai attempts that exhaust the storage window are returned to sender; a rising RTS count trails a rising exception rate.
Open Claims	The damaged / lost subset that escalates.	Damaged and lost exceptions convert to claims at a high rate; this is the early signal for the claims queue.
First-Attempt Delivery Rate	The inverse view of the fuzai sub-population.	First-attempt rate falling is almost entirely the absence-exception story; use it to size the time-slot and PUDO opportunity.
Claim Value (open)	The yen value behind the damaged / lost exceptions.	Tells you whether the small damaged / lost count is cheap parcels or a few high-value ones.

Reconciling against the source

Where to look in Japan Post’s own tooling: The customer-facing record is the Japan Post Tracking Service (追跡サービス), which shows the per-item status history that this card is built from. Business shippers using the Japan Post web-shipping tools (Yu-Pack Print / ゆうパックプリント and the EMS / international shipping portal) see batch despatch records there, but Japan Post does not publish a single merchant-level exception-rate report the way some Western carriers do. The like-for-like check is therefore to export your consignment list, pull the status history per item through the tracking service or the connector’s ingested events, and count the consignments whose history contains an exception scan. Why our number may legitimately differ from a manual count off the tracking portal:

Reason	Direction	Why
Scan timestamps are carrier-local (JST)	Boundary days off	The Japan Post tracking history records each scan in Japan Standard Time. The card stores in UTC and presents in your workspace timezone. For a 30-day window the boundary-day shift averages out, but a single-day comparison against the portal can be off by one day.
Tracking-event ingestion latency	Ours can lag	Japan Post status updates are not real-time; depot and delivery scans batch through the tracking service with a typical 30-minute to several-hour delay, and rural depots can lag longer. A parcel that just threw a fuzai scan may not appear as an exception in our index for up to a few hours.
Exception classification	Either	We classify each Japanese status string into a normalised taxonomy. A manual count may include or exclude statuses differently (for example, whether “in customs clearance” alone counts as an exception, or only “held at customs”). Agree the definition before comparing.
Redelivery counted once	Ours lower per-scan	A parcel with three fuzai attempts logs three exception scans in the portal but counts as one exception consignment here. If you count scans rather than consignments off the portal, the portal number will be higher.
Outbound only	Ours lower	Return-to-sender legs are excluded from this denominator; the raw tracking export includes them.

Cross-connector reconciliation:

Card	Expected relationship	Causes of legitimate divergence
`shopify.refund_rate`	Downstream impact. Unresolved exceptions drive “where is my order” tickets and refunds.	Refund rate has many non-shipping drivers (sizing, quality); exceptions are one input at a 7 to 14 day lag.
`shopify.unfulfilled_orders`	Upstream input.	Address-incomplete exceptions often trace to bad order data captured at checkout.

Known limitations / merchant FAQs

Why is my absence (fuzai) exception rate so high compared with carriers in other countries? This is structural to Japan, not a Japan Post failing. A large share of Japanese households are out during delivery hours, and the carrier leaves an absence notice (不在票) for redelivery rather than leaving the parcel. The fix is upstream of the carrier: offer Yu-Pack delivery-time-slot selection, convenience-store pickup (コンビニ受取), and locker (はこぽす) delivery at checkout. Merchants who promote time-slot selection routinely cut their fuzai exceptions by 40 to 60 percent. Does a successful redelivery still count as an exception? Yes. The consignment scores as an exception because it cost a failed first attempt, redelivery handling, and (usually) a customer interaction to arrange the second attempt. If you want the pure hard-failure view, read Failed Deliveries; if you want the first-attempt success view, read First-Attempt Delivery Rate. My EMS customs-hold exceptions spiked but domestic is flat. What happened? Customs holds are an EMS-only sub-population and are usually a declaration-quality problem, not a carrier problem. Check EMS CN23 Customs Document Generation Failure Rate; when CN23 auto-generation fails, the manual fallback declaration is more error-prone and gets detained at the destination customs authority. Also check for destination-country rule changes (de minimis thresholds, prohibited-item lists) that can hold a whole corridor at once. Why does the rate look different from a count I made off the tracking portal? Three usual reasons. (1) The portal logs every scan, so a parcel with three fuzai attempts is three lines there but one exception consignment here. (2) Scan timestamps are JST on the portal and the card normalises to your workspace timezone, so boundary days differ. (3) Classification: agree which statuses count as exceptions before comparing, “in customs clearance” is normal transit for EMS and we do not treat it as an exception on its own. How quickly does this card react to a problem? Faster than the delivery cards but not instantly. Japan Post tracking events batch with a typical 30-minute to several-hour latency, and rural depots can lag longer, so allow a few hours before a real spike is fully reflected. Use this as the leading indicator and confirm against On-Time Delivery Rate once the delivery scans land. What is the playbook when the rate crosses 3 percent? In order: (1) break the rate down by exception type, if it is fuzai, the action is checkout (time slots, PUDO), not the carrier; (2) if it is address-incomplete, check recent order-data quality and any address-validation change; (3) if it is customs-held, check EMS CN23 Customs Document Generation Failure Rate and destination-rule changes; (4) if it is damaged / lost, escalate to Open Claims and review packaging for the affected SKUs; (5) check the despatch calendar for an Oshogatsu (New Year) or Obon peak that explains a seasonal rise. Does the New Year (Oshogatsu) peak distort this card? Yes, expect a seasonal rise. Late December through the first week of January is the heaviest Japan Post period (New Year nengajo and gift traffic), and both volume and exception rate climb. Annotate year-on-year comparisons across that window rather than re-baselining the threshold permanently. The same applies to a lesser degree around the mid-August Obon period.

Tracked live in Vortex IQ Nerve Centre

Exception Rate is one of hundreds of KPI pulses Vortex IQ tracks across Japan Post 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 source

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 source

​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 source

Known limitations / merchant FAQs

Tracked live in Vortex IQ Nerve Centre