Crock-Pot is owned by Newell Brands (the United States, NASDAQ: NWL), which acquired the brand on 15 April 2016 for $15.4 billion.[1][2] Crock-Pot was founded in 1971 in the United States and was independent until 2016.
Crock-Pot launched the modern slow cooker in 1971, developed from a bean cooker, and arrived as more women were in paid work and wanted meals that could cook unattended all day. Its name is used generically for slow cookers in North America, and it came to Newell with Jarden.
Controlling ownership as of . Brands grouped under the entity that owns them; large groups are collapsed.
Open the full Newell Brands ownership tree →
Newell Rubbermaid acquired Jarden for about $15.4 billion and renamed itself Newell Brands, roughly doubling in size overnight. Jarden had itself been assembled from dozens of acquisitions, and the combined company spent the following years selling many of them again after the debt proved heavier than the integration was worth.
No tagged news items yet. Deals, regulatory actions and recalls are added from SEC filings, regulators and trade press; only titles and links are stored.
Headlines link to the original publisher. Brandtree does not reproduce article text.
The parent company of Crock-Pot is Newell Brands, a publicly listed company headquartered in the United States.
Yes. Crock-Pot originated in the United States in 1971 and its owner, Newell Brands, is also headquartered in the United States.
Newell Brands completed its acquisition of Crock-Pot on 15 April 2016, after announcing the deal on 14 December 2015. The deal was valued at $15.4 billion (enterprise value).
Crock-Pot was an independent company from its founding in 1971 until Newell Brands acquired it in 2016.
Yes. As of 16 September 2026, Crock-Pot is still owned by Newell Brands. The ownership record was last checked against primary sources on that date.
Last verified . Every ownership fact above is backed by one of these primary documents. Numbers in brackets in the text refer to this list.
Report a correction Opens a pre-filled GitHub issue. See our corrections policy.