OPDP has been unusually generous in publishing what goes wrong with promotional eCTD submissions. Between the electronic submissions guidance, the common-errors webinar and the grouped-submissions material, the agency has effectively handed the industry a defect list.

What follows is that list, organised by how the failure actually presents — because the useful distinction is not what the error is called, but whether it stops your submission loudly, quietly, or only weeks later when somebody notices the material was filed against the wrong product.

Errors that reject the submission outright

Reusing an application number and sequence number combination

Every submission needs a sequence number unique to its application and not previously used. This sounds obvious until you are running grouped submissions across a portfolio, where each member application carries its own sequence number and the numbering for each is tracked separately.

The failure mode here is unforgiving: if any application number and sequence number pair in a grouped submission has been submitted before, the entire group is rejected — not just the offending member. One stale number in a five-product group takes down all five.

Wrong or mismatched application numbers

Materials submitted against the wrong product is one of the most frequently cited errors, and it comes in several shapes: an incorrect application number in the cover letter, an application number on the Form 2253 that does not match the one in the submission metadata, or promotional material for one product filed under a different product’s application.

The rule to encode is that the application listed as the lead in the US-Regional file must match the application listed on the Form FDA 2253. Any divergence between the form and the backbone is a defect, even when both values are individually plausible.

Mixing application types

Promoted products in a single grouped submission must all be of the same application type. An NDA and a BLA cannot be grouped together, however closely the products are related commercially. If your promotional piece spans both, the materials must be submitted separately — either as single-product submissions, or as grouped submissions batched by application type.

Errors that succeed technically and fail in substance

These are the dangerous ones. The submission is accepted, the acknowledgements come back clean, and the thing you intended to happen does not happen.

Using application references instead of an application set

This is the subtlest failure in the whole area. To create a grouped submission, all member applications must appear in the Application Set section of the US-Regional.xml file. Putting them in the References section instead does not create a grouped submission.

References merely create a link between applications. They do not carry sequence numbers, and — critically — they do not distribute the submission to the referenced applications. The submission is accepted. It simply never lands anywhere except the lead application. Every other product you believed you had covered is uncovered, and nothing in the acknowledgement tells you so.

Structuring a single-product submission as a grouped one, or vice versa

A related mismatch: the submission contains every file a grouped submission needs, the Form 2253 is marked as a multi-product submission, and the US-Regional file says single product. FDA processes the submission using the data in the US-Regional file only. The agency cannot add applications that are not listed in the US-Regional file, even when a Supplemental Application List is sitting right there in the package naming them.

The mirror image also occurs: a submission that is genuinely grouped gets sent multiple times, once per application, with the application number swapped in the US-Regional file each time. It looks like diligence. It produces duplicate records and defeats the purpose of grouping.

Batched materials in a grouped submission

In a grouped submission, every promotional material must promote every product in the group. The common error is treating the group as a convenient envelope: three member applications, fifteen materials, five promoting each product — and none promoting all three.

That is a batch, not a group. It is a natural thing to want to do, because it matches how commercial teams work in campaign waves, and it is specifically called out as wrong.

Errors of placement

Less dramatic, but they generate correspondence and rework:

  • Labeling in the wrong heading. Current product labeling belongs under 1.14.6. In a grouped submission you need it for each member of the group.
  • Materials outside 1.15.2. Only one set of materials goes under 1.15.2 in a grouped submission; each material is then linked to all members.
  • Cover letters in the wrong place. Non-2253 grouped submissions need one cover letter under the appropriate cover-letter heading, listing every member application with type, number and product name. If the cover letter lists them all, a separate Supplemental Application List is not required.
  • Missing the Supplemental Application List. For a grouped 2253, non-lead members go on a Supplemental Application List filed in the same section as the completed Form 2253 — not with the materials, and not in the cover letter section.

The mechanism most teams do not use

OPDP operates a test submission process specifically so that submitters can validate structure before going anywhere near production. The OPDP project management team reviews the structure and provides feedback, including instructions for corrections.

The process is straightforward: review the presentations on the OPDP eCTD page, then contact the OPDP eCTD mailbox with your questions, the submission types you intend to use, and availability for a short planning meeting. The team helps plan test cases, you submit test files, and you report the result back with the COR ID.

For an organisation about to start promotional submissions — or about to change publishing tooling — this is a free structural review from the people who will be receiving the real thing. Very few of the errors above survive it.

What this implies for tooling

Nearly every defect on this list is machine-checkable before transmission. Sequence number reuse, application-number agreement between form and backbone, application-type consistency across a group, application set versus references, whether every material covers every member, heading placement — none of these require judgement. They require a rule set that runs against the assembled sequence and refuses to let it out of the building.

That is worth saying plainly because the instinct in promotional operations is to solve quality problems with a checklist and a second reviewer. Checklists degrade. The errors above are precisely the class that validation should catch, and the reason they keep appearing in OPDP’s material is that most promotional submissions are still assembled by hand.

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.