Closing the Zushi plant for the Kamakura kitchen centre — building the central-kitchen network (1994)
A plant held as a function, a plant that became an asset
Three distribution centres, all rented, for total investment of something like ¥120m — the answer the president gave in a 1999 lecture contains the core of the decision. Having chosen direct operation throughout and the “number one in the district” trade, there was no way to stop a handmade taste varying from store to store except to strip the preparation out of the kitchens. And yet the money was wanted for stores. A rented central kitchen was the compromise that satisfied both. Separating having a plant from building one is where the lightness of this period lay.
That lightness did not last. Total investment in the Nagahama plant ran to about ¥4.5bn — an order of magnitude away from the rented years. The reason for building it was the increase in stores in western Japan brought by the acquisitions of Reins International and Kappa Create: rather than a capability existing first and then supporting acquisitions, it was largely the acquisitions that set the scale of the capability. And as Ootoya’s president Kubota sought to protect the virtue of cooking inside the restaurant, there are signs on which standardisation does not take. Vertical integration is a device for lowering cost, but it is also a mechanism that forces the question, every time, of what to leave intact in the company you have bought.
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.
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
Colowide’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/7616/manifest.json | Resource index |
| GET | /api/7616/history.json | History overview |
| GET | /api/7616/timeline.json | Chronology |
| GET | /api/decisions.json | All management decisions (index) |
| GET | /api/7616/decisions.json | Management decisions (index) |
| GET | /api/7616/decisions/{slug}.json | One decision (full dossier) |
| GET | /api/7616/executives.json | Executives |
| GET | /api/7616/shareholders.json | Major shareholders |
| GET | /api/7616/financials.json | Financial statements |
| GET | /api/7616/financials-longterm.json | Long-term results |
| GET | /api/7616/segments.json | Business segments |
| GET | /api/7616/regions.json | Sales by region |
| GET | /api/7616/workforce.json | Workforce |