Partnering with Japan Post on mailbox-drop services — and the litigation that followed (2023)
Between the cause and its performance
At the starting point of this partnership was a cause that mattered to the whole delivery industry. Faced with the structural constraint of a driver shortage, the largest parcel carrier and the postal operator — long at odds over the regulation of correspondence — joining hands can be seen as a response to the demands of the times that went beyond the industry’s habit of fighting over freight on price. Cutting off part of a competitive field, the mailbox-drop services, and entrusting it to the other side’s strength carried a meaning beyond mere outsourcing: it was a turn away from doing everything in-house.
What followed, however, shows that even a partnership raised on a cause can find that, at the stage of performance, the earnings circumstances of each individual company take priority. The deterioration in Yamato’s own results made full transfer difficult and pushed the relationship with Japan Post as far as litigation. Two companies that had supposedly climbed over a history of institutional conflict over correspondence regulation now held a conflict on another plane — the performance of a contract. In this configuration one can sense the tension between the ideals of industry realignment and the business circumstances of a single firm. As of this writing the course of the litigation cannot be foreseen, and the future of the partnership remains inside the dispute.
Revenue and net margin, FY2018–FY2026
Revenue in ¥ bn (bars) and net margin in % (line), for the years around the decision. Shaded columns are FY2023 onwards — after it was taken.
Source: securities reports
Read the full dossier in Japanese →
The Japanese edition carries the complete record of this decision — the situation that forced it, the options weighed, what actually followed, and the sources behind every claim.
Other key decisions at Yamato Holdings
- 1919 Founding Yamato: from four trucks in Kyobashi to Japan’s first line-haul truck service (1919)
- 1976 Launching Takkyubin: from third place in line-haul to the household parcel market (1976)
- 1981 Twenty years of resistance to the state’s postal parcel monopoly (1981)
- 2017 The first across-the-board Takkyubin rate rise in 27 years, and a cap on volume (2017)
Yen amounts are converted at the average rate of each figure’s own year — not today’s rate; the revenue chart is shown in yen. Exchange rates & sources — the full ¥/US$ table →
Disclaimer
- This page is provided for general information only and is not investment advice, nor a recommendation to buy or sell any security.
- Figures are compiled independently and include our own estimates, approximations and machine-processed data; we make no warranty as to their accuracy or completeness.
- Sources are primarily each company’s securities reports and other public filings, but errors and omissions may remain.
- Any use of this information is at the reader’s own risk. Past performance does not indicate future results.
- Company names, logos and other marks belong to their respective owners.
Data API
Yamato Holdings’s history, financials, executives and
shareholders are published as static JSON — no key, plain GET.
Full specification →
| Method | Endpoint | Returns |
|---|---|---|
| GET | /api/companies.json | All companies |
| GET | /api/9064/manifest.json | Resource index |
| GET | /api/9064/history.json | History overview |
| GET | /api/9064/timeline.json | Chronology |
| GET | /api/decisions.json | All management decisions (index) |
| GET | /api/9064/decisions.json | Management decisions (index) |
| GET | /api/9064/decisions/{slug}.json | One decision (full dossier) |
| GET | /api/9064/executives.json | Executives |
| GET | /api/9064/shareholders.json | Major shareholders |
| GET | /api/9064/financials.json | Financial statements |
| GET | /api/9064/financials-longterm.json | Long-term results |
| GET | /api/9064/segments.json | Business segments |
| GET | /api/9064/regions.json | Sales by region |
| GET | /api/9064/workforce.json | Workforce |