The Z Holdings rename and the merger with LINE (2019)
Why an integration meant to stop competition took two reorganisations
The core of this decision was not an aggressive integration to open a new market, but a defensive reorganisation to stop the mutual exhaustion of two companies competing inside the group and to unwind, all at once, the structural weaknesses it carried. The cash-back war between PayPay and LINE Pay was battering the economics of payments; Yahoo’s growth could not continue without M&A; and the licence with the American Yahoo blocked the path overseas. To treat all of these at once with the single move of merging with a competitor — that was the answer chosen by Z Holdings, which changed its very name and reshaped itself into a holding company.
The defensive reorganisation did not, however, settle in one pass. The design that placed the two companies as equals under a holding company preserved their brands and organisations, and for that very reason slowed the effect of integration; payments tilted over time toward PayPay, and the initiative toward the LINE side. Having bought back the brand rights from the former American Yahoo, one of the original grand justifications — the overseas constraint — faded as well. In the end, melting the two into one required a second-stage merger, LINE Yahoo, in 2023, and an integration meant to stop competition was reassembled once more along the logic of capital. The defensive integration worked as a tourniquet, but generating new growth from there demanded a still longer span of reorganisation.
Revenue and net margin, FY2014–FY2024
Revenue in ¥ bn (bars) and net margin in % (line), for the years around the decision. Shaded columns are FY2019 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 LY Corporation
- 1999 Launching Shopping and Auctions together — the split fortunes of EC (1999)
- 2001 Yahoo! BB: leaning on modem-sales revenue (2001)
- 2012 The turn to “bakusoku” management and the Miyasaka regime (2012)
- 2013 The “e-commerce revolution”: free listings and a new revenue structure (2013)
- 2015 Consolidating Askul, and the governance of parent–subsidiary listing (2015)
- 2019 The ZOZO acquisition, and parent–subsidiary listing (2019)
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
LY Corporation’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/4689/manifest.json | Resource index |
| GET | /api/4689/history.json | History overview |
| GET | /api/4689/timeline.json | Chronology |
| GET | /api/decisions.json | All management decisions (index) |
| GET | /api/4689/decisions.json | Management decisions (index) |
| GET | /api/4689/decisions/{slug}.json | One decision (full dossier) |
| GET | /api/4689/executives.json | Executives |
| GET | /api/4689/shareholders.json | Major shareholders |
| GET | /api/4689/financials.json | Financial statements |
| GET | /api/4689/financials-longterm.json | Long-term results |
| GET | /api/4689/segments.json | Business segments |
| GET | /api/4689/regions.json | Sales by region |
| GET | /api/4689/workforce.json | Workforce |