From “landlord” to “franchise”: reworking the fee model (2002)
The shift that laid the ecosystem’s revenue base
The heart of this decision was that Rakuten put its hand to the very fee model behind its success while business was at its peak. A flat fee, whose revenue accumulated in proportion to the number of shops, had lowered the barrier to opening a store and pushed Rakuten to an early lead — but it was a structure in which growth would stop once shop numbers plateaued. By switching to usage-based charging linked to sales, Rakuten rebuilt the relationship so that its own revenue rose as its merchants’ sales rose, redirected its sales force from signing new shops toward consulting, and put in place a mechanism for growing together with its merchants.
The change carried risk. For high-selling merchants it was in effect a price increase, and if it drove them away it could halt the growth Rakuten had enjoyed since its founding. When Chairman and President Mikitani said he “was prepared to see it through even if the number of merchants halved,” it was a judgment made with that cost in full view. In the event, no exodus came: gross merchandise sales rose from $430.4M (¥52bn) in 2001 to $598.7M (¥75bn) in 2002, and the cash thickened by the fee revision became the seed capital for Rakuten Super Points, launched that November, and for the 2003 move into travel and securities.
The more successful a mechanism, the more a decision to remake it tends to be put off. Rakuten’s transformation of its fee structure — which it called its “second founding” — is instructive precisely because, by reconnecting its relationship with merchants through a link to their sales, it prepared the revenue base of the later Rakuten Ecosystem at an early stage.
Revenue and net margin, FY1997–FY2007
Revenue in ¥ bn (bars) and net margin in % (line), for the years around the decision. Shaded columns are FY2002 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 Rakuten Group
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
Rakuten Group’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/4755/manifest.json | Resource index |
| GET | /api/4755/history.json | History overview |
| GET | /api/4755/timeline.json | Chronology |
| GET | /api/decisions.json | All management decisions (index) |
| GET | /api/4755/decisions.json | Management decisions (index) |
| GET | /api/4755/decisions/{slug}.json | One decision (full dossier) |
| GET | /api/4755/executives.json | Executives |
| GET | /api/4755/shareholders.json | Major shareholders |
| GET | /api/4755/financials.json | Financial statements |
| GET | /api/4755/financials-longterm.json | Long-term results |
| GET | /api/4755/segments.json | Business segments |
| GET | /api/4755/regions.json | Sales by region |
| GET | /api/4755/workforce.json | Workforce |