The RE Engine and the shift to digital, catalogue sales (2017)
From one-off sales to repeat sales
The move from selling a package once to selling a digital title continuously can be read as more than a mere switch of sales channel. Shifting from a business that bets on opening-week units to one that recovers a catalogue over several years was also an attempt — in a game industry where development budgets have swelled into the tens of billions of yen — to win back for management the time needed to keep producing hits. It came together only when the in-house RE Engine technology and the sales design of DLC and price strategy meshed at the same moment.
That said, how far this structure can be sustained remains an open question today. The higher the digital ratio climbs past 70% and the more the company leans on repeat sales, the sharper the recoil could be should the next new title miss the wave of a console generational change. The mi-no-take management that founder Kenzo Tsujimoto preached was a philosophy of restraint over investment and borrowing; that a decision to commit, along that same line, to the technology investment of an in-house engine now underpins today’s twelve straight years of profit growth reflects the company’s next challenge — how to reconcile technology with discipline.
Revenue and net margin, FY2012–FY2022
Revenue in ¥ bn (bars) and net margin in % (line), for the years around the decision. Shaded columns are FY2017 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 Capcom
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
Capcom’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/9697/manifest.json | Resource index |
| GET | /api/9697/history.json | History overview |
| GET | /api/9697/timeline.json | Chronology |
| GET | /api/decisions.json | All management decisions (index) |
| GET | /api/9697/decisions.json | Management decisions (index) |
| GET | /api/9697/decisions/{slug}.json | One decision (full dossier) |
| GET | /api/9697/executives.json | Executives |
| GET | /api/9697/shareholders.json | Major shareholders |
| GET | /api/9697/financials.json | Financial statements |
| GET | /api/9697/financials-longterm.json | Long-term results |
| GET | /api/9697/segments.json | Business segments |
| GET | /api/9697/regions.json | Sales by region |
| GET | /api/9697/workforce.json | Workforce |