Rebuilding into a “strong trading house”: Haruna names the flaws (1987)
Naming the disease is not the same as curing it
The heart of this decision was not that Marubeni carried out some sweeping reorganization, but that its incoming president named his own company’s weaknesses in his own words. The race to be number one in sales, the weakness in domestic trade, the vertical silos that walled off the divisions — each was the underside of the success that had carried Marubeni from a textile trader to a general trading house, an inner weakness hard to see from outside. Haruna named them one by one in plain, unadorned language. To frame the aim as a “rebuilding into a strong trading house” was itself a declaration that it all began with admitting where the company actually stood.
Yet naming a disease and curing it are two different things. The weaknesses Haruna listed were not resolved during his tenure; only after more than a decade — the cleanup of financial engineering, the pruning of subsidiaries, the disposal of bad assets — did they finally connect to the rebuilding of the 2000s. An accurate diagnosis promises no early cure. “Rebuilding into a strong trading house” can be read as a prelude that shows how long that distance was. Looking at today’s Marubeni, which has renewed record profits on high resource prices, how far did this 1987 self-diagnosis of its earnings constitution bear fruit, and what did it carry over? It leaves a question worth re-asking at every turning point.
Revenue and net margin, FY1982–FY1992
Revenue in ¥ bn (bars) and net margin in % (line), for the years around the decision. Shaded columns are FY1987 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 Marubeni
- 1976 Marubeni and the Lockheed scandal — a “voyage without a chart” (1976)
- 1992 Cleaning up after financial engineering: Toriumi’s early restructuring (1992)
- 2002 Rebuilding from the “losers’ camp”: a root-and-branch bad-asset cleanup (2002)
- 2012 Buying the grain major Gavilon — and the Viterra grain exit (2012)
- 2020 A blanket impairment on Chile copper and the first net loss in 18 years (2020)
- 2025 The ¥10 trillion market-cap target: the “GC2027” plan and Omoto’s new regime (2025)
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
Marubeni’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/8002/manifest.json | Resource index |
| GET | /api/8002/history.json | History overview |
| GET | /api/8002/timeline.json | Chronology |
| GET | /api/decisions.json | All management decisions (index) |
| GET | /api/8002/decisions.json | Management decisions (index) |
| GET | /api/8002/decisions/{slug}.json | One decision (full dossier) |
| GET | /api/8002/executives.json | Executives |
| GET | /api/8002/shareholders.json | Major shareholders |
| GET | /api/8002/financials.json | Financial statements |
| GET | /api/8002/financials-longterm.json | Long-term results |
| GET | /api/8002/segments.json | Business segments |
| GET | /api/8002/regions.json | Sales by region |
| GET | /api/8002/workforce.json | Workforce |