Omnipod’s Two 2026 Class I Recall Events: March vs May

Updated2026-08-06

Evidence map comparing the March and May 2026 Omnipod recall scope, cannula-damage location and quality loop — BIO original evidence map: the March internal-cannula action and May above-skin external-cannula action are separated, then connected to user response, lot traceability and manufacturing correction. Sources [1–8].

In short: The May 2026 action covered specified lots of Omnipod 5, DASH and Eros. Three FDA Class I recall records total 7,015,886 Pods and describe damage to the external soft cannula above the skin, between the Pod and insertion point.[2][3][4][5] The March action covered only certain Omnipod 5 Pods: FDA lists 1,240,115 units and an internal soft-cannula tear or leak within the Pod.[6][7] Either problem could lead to insulin under-delivery, hyperglycemia and potentially diabetic ketoacidosis, but they are not one recall and one action’s injury count should not be used to characterize the other.[1][6]

Separate the two actions first

Insulet’s May 26, 2026 notice explicitly says the May medical device correction was separate from the March 12 action. May covered specified Omnipod 5, Omnipod DASH and Omnipod Eros lots; FDA’s March page identifies only certain Omnipod 5 Pods.[1][6]

Both failures could prevent insulin from reaching the body as intended, but the locations differed. May involved a small tear above the skin between the Pod and insertion point; March involved a tear or leak in the soft cannula inside the Pod.[1][6][7] The shared word “cannula” does not make the two failure modes identical.

The May action: three products and three FDA records

FDA lists three Class I records under the May event: 4,936,056 Omnipod 5 Pods, 1,790,784 DASH Pods and 289,046 Eros Pods, totaling 7,015,886.[3][4][5] The firm initiated the action on May 20 and announced it on May 26; FDA’s database shows a June 30 posting date.[1][3][4][5]

Insulet said about seven million Pods were in scope, about 60% were already consumed or expired, and the affected Pods represented about 8.5% of 2025 global Pod production. At the announcement date, it said it had received 24 reports of serious adverse events associated with high glucose, including hospitalization and DKA, and no reported deaths.[1] These are company-reported figures at that stated cut-off.

The March action: certain Omnipod 5 Pods only

FDA’s March record is Z-1797-2026 under event 98586, covering 1,240,115 units; the firm initiated the action on March 12, 2026.[7] FDA’s separate safety page reports that, as of April 17, Insulet had reported 29 serious injuries and no deaths.[6]

Do not add 24 reports and 29 serious injuries. They refer to different recall events, different cut-off dates and differently described reporting sets. Each can be quoted with its own attribution, but the sources do not support calculating a single “2026 total.”[1][6]

Use the recall to ask quality questions, not to overclaim

FDA’s May records list process design as the cause and describe external soft-cannula damage. That supports questions about material and forming inputs, assembly stress, in-process detection, lot traceability and postmarket trending. The record alone does not prove breach of a specific ISO 13485 clause or loss of certification.[3][4][5]

FDA’s QMSR became effective February 2, 2026 and incorporates ISO 13485:2016 into the 21 CFR Part 820 framework.[8] Finished-device manufacturers are directly regulated under QMSR; obligations relevant to material and component suppliers normally flow down through purchasing and supplier controls. A defensible response preserves evidence for lots, changes, process capability, inspection, complaint trends and CAPA instead of generalizing one recall to a whole material category or quality system.

Sources and reading boundary

Recall classification, quantities and injury reporting can be updated. This article reflects official records visible on August 6, 2026; users should follow current lot-check and clinical instructions rather than use this article alone to decide whether a Pod is affected.

The BIO angle

For medical-device material and manufacturing teams, the useful lesson is not recall sensationalism. It is the traceable chain from failure location to process input, in-process detection, complaint signal and lot-level response. BIO does not claim to supply Insulet or Omnipod and does not attribute either event to a specific material from the public record.

FAQ

Were the March and May 2026 Omnipod actions one recall?

No. Insulet explicitly called the May action separate from March; product scope, damage location and FDA records differ.[1][3][4][5][7]

How many serious injuries were reported across both actions?

The official sources do not support one combined number. Insulet said it had received 24 serious-adverse-event reports for the May action; FDA’s page reports that, as of April 17, Insulet reported 29 serious injuries for the March action. Events, cut-offs and reporting frames differ.[1][6]

Does a Class I recall prove ISO 13485 certification failed?

No. Class I describes the seriousness of potential health consequences. A recall record is not an audit finding on a specific ISO clause or a certification decision.[3][4][5][8]

Omnipod’s two 2026 Class I recall events: keep March and May separate