If your promotional material promotes more than one product, you have a choice. You can submit it separately against each application, or you can submit it once as a grouped submission and let FDA distribute it to every application in the group.

For a portfolio with several related products sharing campaign material, grouping is the single largest efficiency available in ad-promo publishing. It is also where the sharpest failure modes live, because a grouped submission can be accepted by the gateway and still fail to do what you intended.

What a grouped submission actually is

A grouped promotional submission is a single submission in eCTD format that contains promotional materials promoting more than one product, together with the current labeling for each promoted product.

The mechanism is distribution. The contents of the grouped submission are distributed to all member applications in the group. A record is created under each application, using the sequence number provided for that application in the US-Regional file, and a link to the shared location of the contents is added to each record. The reviewer sees one submission linked to multiple applications, rather than several near-identical submissions arriving independently.

One hard constraint governs eligibility: the promoted products must all be of the same application type. NDAs group with NDAs, BLAs with BLAs. If your piece spans types, the materials must be submitted separately — as single-product submissions, or as separate groups batched by application type.

Lead and member applications

Every group has exactly one lead application and any number of non-lead members. The distinction is made in the US-Regional.xml file, not in the folder structure and not on the form.

  • All member applications must appear in the Application Set section of US-Regional.xml
  • The <Application-Containing-Files> attribute identifies the lead: true for the lead, false for every non-lead member
  • The lead application should be listed first in the application section
  • A grouped submission may contain only one lead application

Each member application must also carry its own sequence number. That number must be unique to its application and must not have been submitted previously under that application. This is the constraint most likely to bite a large portfolio, and the penalty is disproportionate: if any application number and sequence number combination in the group has been used before, the entire group is rejected.

The trap: References are not an Application Set

This deserves its own section because it is the failure that does not announce itself.

US-Regional.xml has a References section as well as an Application Set. Putting your member applications in References looks like it should work. It does not create a grouped submission.

  • References only create a link between applications
  • References do not require or include a sequence number
  • References do not distribute the submission to the referenced applications

The submission is accepted. The acknowledgements are clean. And every product other than the lead has no record of the material. If you are auditing an existing promotional programme for coverage gaps, this is the first thing to check, because nothing downstream will have flagged it.

What goes in a grouped 2253

The required contents are the same three components as a single-product 2253 — but with the multiplicity handled explicitly:

Component Heading Grouped-specific rule
Form FDA 2253 1.1 Must indicate it is a multi-product submission; the application on the form must match the lead in US-Regional.xml
Supplemental Application List 1.1 (with the form) Lists the non-lead members — application type and number, product name, and the date and file name of the current PI
Current product labeling 1.14.6 Required for each member of the group; separate PDF per label, or a cross-reference if previously submitted
Promotional material 1.15.2 Only one set of materials; each material is linked to all members of the group

Note where the Supplemental Application List lives. It is filed in the same section as the completed Form FDA 2253 — with the forms, not with the materials and not in a cover letter. And note that it does not replace the Application Set: FDA processes the submission using the US-Regional file, and cannot add applications that are not listed there, even when the Supplemental Application List names them.

Non-2253 grouped submissions differ

For grouped submissions that are not 2253s — advisory comment requests, for example — the mechanics shift to the cover letter:

  • One cover letter under the appropriate cover-letter heading
  • The cover letter lists all member applications, with application type, number and product name
  • If the cover letter lists every member, a separate Supplemental Application List is not necessary
  • The subject line should reference the lead application number and clearly identify the submission as a group

The rule people most want to break

Every promotional material in a grouped submission must promote every product in the group.

The tempting misuse is to treat the group as a shipping container. Three member applications, fifteen materials, five promoting each product — submitted as one group because it is one campaign and one deadline. None of those materials promotes all three products, so this is a batch, not a group, and it is explicitly called out as an error.

If your materials do not all cover all products, you need separate submissions. The grouping construct exists for genuinely shared material — the piece that names several products together — not for administrative convenience across a campaign.

A checklist worth encoding

Every item below is machine-checkable before you transmit:

  • All members are the same application type
  • Exactly one member has Application-Containing-Files = true, and it is listed first
  • Members are in the Application Set, not the References section
  • Every member has a sequence number that is unique and unused for that application
  • The lead application matches the application on the Form 2253
  • The Form 2253 is marked as a multi-product submission
  • A Supplemental Application List exists alongside the form, naming every non-lead member with its current PI details
  • Current labeling is present, or validly cross-referenced, for every member
  • Exactly one set of materials under 1.15.2
  • Every material promotes every product in the group

If any of those checks currently runs in someone’s head rather than in software, that is where your next rejection is coming from.

Before you run your first group

OPDP will review a test submission’s structure and give you feedback before you attempt production. Given that a single reused sequence number rejects an entire group, running your first grouped submission through the test process is cheap insurance. Contact the OPDP eCTD mailbox with the submission types you plan to use and they will help plan the test cases.

Primary sources

DnXT builds eCTD publishing, validation and dossier review software for regulatory operations teams. This article is general information about FDA requirements, not regulatory advice — verify every detail against the current FDA guidance and forms before you rely on it.