Consolidating Askul, and the governance of parent–subsidiary listing (2015)
The logic of completing logistics, and the manners of control
The core of this decision lay where two questions overlapped: the strategic one of how an e-commerce business that owns no logistics is to secure logistics, and the governance one of how far a parent that has brought a listed subsidiary under its control may reach into its management. Since building a nationwide logistics network from scratch would take far too much time and capital, there was a logic to taking Askul — already a partner in LOHACO — into consolidation. If Yahoo, holding customer acquisition and payments, embraced Askul, holding logistics and merchandise procurement, the two together should have been able to stand against Amazon-style retailing as one.
But the logic of completing logistics was a separate matter from the manners of control. When the conflict over LOHACO’s losses and the demand to hand it over reached the strongest form of intervention — the shareholders’ meeting voting down the reappointment of Askul’s president — what the market saw was the peril of parent–subsidiary listing, in which the parent’s will is put ahead of minority shareholders’ interests. How far may a controlling shareholder move the management of a subsidiary? The Askul affair became an occasion for Japan’s capital market to confront that question. Yahoo kept control of Askul, but the rightness of control and the logic of a logistics strategy never, in the end, settled into the same answer.
Revenue and net margin, FY2010–FY2020
Revenue in ¥ bn (bars) and net margin in % (line), for the years around the decision. Shaded columns are FY2015 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)
- 2019 The ZOZO acquisition, and parent–subsidiary listing (2019)
- 2019 The Z Holdings rename and the merger with LINE (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 |