Who owns Merries?
Merries is owned by Kao (Japan, TSE: 4452).[1]
This ownership is reported in official statements but has not yet been matched to a regulatory filing.
Key facts
- Current owner
- Kao Corporation reported
- Owned since
- Not recorded
- Previous owner
- None recorded
- Owner HQ
- 🇯🇵 Japan, Tokyo
- Origin
- 🇯🇵 Japan
- Founded
- 1983
- Category
- Personal care & beauty › Tissue & paper hygiene › Diapers & baby wipes
- Parent ticker
- TSE: 4452
- Last verified
- · 1 sources
About Merries
Merries is Kao's nappy brand and one of the largest in Japan, with a reputation for softness and absorbency that made it a significant grey-market export to China before Kao established local distribution. Chinese buyers travelling to Japan cleared shelves in quantities that led some retailers to impose purchase limits.
Ownership timeline of Merries
Where Merries sits in Kao
Controlling ownership as of . Brands grouped under the entity that owns them; large groups are collapsed.
Open the full Kao ownership tree →
Other brands owned by Kao in personal care & beauty
Latest news about Merries
No tagged news items yet. Headlines are added nightly from public feeds; only titles and links are stored.
Headlines link to the original publisher. Brandtree does not reproduce article text.
Frequently asked questions
Who is the parent company of Merries?
The parent company of Merries is Kao, a publicly listed company headquartered in Japan.
Is Merries Japanese?
Yes. Merries originated in Japan in 1983 and its owner, Kao, is also headquartered in Japan.
Is Merries still owned by Kao?
Yes. As of 6 September 2026, Merries is still owned by Kao. The ownership record was last checked against primary sources on that date.
Sources (1) & corrections
Last verified . Every ownership fact above is backed by one of these primary documents. Numbers in brackets in the text refer to this list.
- [1] Kao Corporation Integrated Report 2025 — Kao Corporation, Annual report, published 31 March 2026; retrieved 6 September 2026.
Report a correction Opens a pre-filled GitHub issue. See our corrections policy.