Chapter - 3

Structured Product Labeling and Why Every Pharma Team Needs to Master It

Structured Product Labeling (SPL) is the backbone of how the FDA processes and manages drug information, but it’s often overlooked. This guide breaks it down: what is SPL, why it matters, and how you can stay compliant without complicating workflows.
Updated On:
July 2, 2025
Category:
Compliance
Author:
Hana Trokic

Summary of Chapter

  • Structured Product Labeling is an FDA-required, XML-based format developed by HL7 that standardizes drug labeling content for both human and electronic use, enabling efficient processing, validation, and publication.
  • Accurate and timely SPL submissions are mandatory for pharmaceutical companies in the U.S., with high stakes for compliance, as errors can delay approvals, trigger FDA rejections, and jeopardize patient safety.
  • An SPL file is a structured, FDA-required XML document that uses standardized tags to organize critical drug information.
  • SPL isn’t just for prescription drugs, it's also required for listed OTC products like vitamins and topicals, making it essential for all pharma teams to understand and comply with FDA labeling standards regardless of product type.
  • Before submitting SPL files to the FDA, teams must ensure proper XML formatting, use of the correct validation rules, a valid ESG account, and full compliance with labeling requirements like the PLR format for prescription drugs.
  • To reduce errors and streamline compliance, many pharma teams are adopting automated SPL software that simplifies XML generation, ensures validation, supports version control, and integrates with RIM systems for faster, more reliable labeling updates.
  • As global standards like IDMP and UDI drive the shift to digital-first labeling, investing in SPL now positions pharma teams to accelerate market access, ensure compliance, and support seamless integration across healthcare systems.


What Is Structured Product Labeling (SPL)?

Structured Product Labeling (SPL) is an XML-based document markup standard developed by Health Level Seven (HL7), a non-profit organization that develops standards for the exchange, integration, sharing, and retrieval of electronic health information. 

SPLs are required by the FDA for submitting labeling information for human prescription drugs, over-the-counter (OTC) products, biologics, and more.

The SPL XML format structures drug label content in a machine-readable way, ensuring that every section, such as dosage, warnings, and administration instructions, is tagged and organized for both human and electronic use. 

The FDA uses SPL to process, validate, and publish labeling information on public databases like DailyMed.


Why SPL Matters: Compliance, Accuracy, and Speed

Every pharmaceutical company marketing products in the U.S. must meet FDA SPL submission requirements. 

This is not just a technical format. SPL affects everything from drug label requirements and marketing approvals to digital health compatibility. 

Failing to submit accurate, validated SPL can lead to:

  • Delays in product approval
  • FDA rejection or requests for resubmission
  • Fines or warning letters
  • Fines
    • The FDA has authority under the Federal Food, Drug, and Cosmetic Act (FD&C Act) to impose civil monetary penalties. While fines for SPL-specific violations aren’t always publicized, failure to comply with labeling regulations has led to penalties exceeding $100,000 in some enforcement cases.
  • Warning letters
    • Between 2021 and 2024, multiple companies received FDA warning letters for failing to submit accurate or timely SPL files, especially around misbranded drugs and incomplete labeling. These letters often cite violations of 21 CFR Part 201 and result in public notices that can damage brand trust.
  • Risk to patient safety due to inaccurate or outdated information

On the flip side, nailing your SPL submissions ensures:

  • Faster approvals
  • Fewer manual corrections or validation failures
  • Seamless updates to electronic drug labeling systems and platforms


Understanding SPL Data Elements

An SPL file is more than just a digital document. It contains structured metadata and sections that make drug information easy to access and break down. 

Key SPL data elements include:

  • Product and manufacturer identifiers (e.g., NDC code, company name)
  • Labeling version history
  • Indications and usage
  • Dosage and administration
  • Contraindications and warnings
  • Drug interactions
  • Packaging information
  • Marketing status and regulatory info

Each element is tagged in a standardized way, allowing the FDA, and third-party systems, to read and validate the content automatically.

SPL XML File Format

SPLs (Structured Product Labeling) must be in XML format as per strict FDA requirements.

Why XML?

The FDA mandates that SPLs be in HL7-compliant XML format because:

  • XML is machine-readable, enabling automated processing and validation.
  • It supports semantic tagging of drug information (e.g., dosage, ingredients, warnings).
  • It ensures interoperability across different regulatory systems and databases.
    It allows for structured and standardized submission, which is critical for labeling, approvals, and updates.

What Must Be in the XML?

The SPL XML must:

  • Conform to the HL7 SPL schema.
  • Include Logical Observation Identifiers Names and Codes (LOINC) to define label sections.
  • Pass validation using FDA’s SPL schema and stylesheet tools.
  • Be submitted through the Electronic Submissions Gateway (ESG).

If you are just getting started with SPLs, download our simplified example of an SPL (Structured Product Labeling) XML file format. SPL is based on the HL7 Reference Information Model (RIM) and is used by the FDA to exchange information about drug labels.

Please note, this example is just a basic structure to help you understand the format. Seal SPL submissions to the FDA are significantly more detailed and must comply with strict validation rules.



SPL for Over-the-Counter (OTC) Drugs and Nonprescription Products

Many teams wrongly assume SPL is only for prescription products. 

In fact, SPL for over-the-counter drugs is also required if the product is listed with the FDA. This includes vitamins, dietary supplements, and topical agents, among others.

The submission requirements and content structure are similar, although OTC products may have simpler labeling needs. Still, teams must comply with the same standards, which means understanding SPL is essential even outside of Rx products.



FDA SPL Submission Requirements: What You Need to Know

Before submitting your SPL files to the FDA, you need to ensure you are following certain guidelines. Some of them include:

 

  • Proper SPL XML format according to the FDA’s Structured Product Labeling guidance
  • A valid FDA ESG (Electronic Submissions Gateway) account for transmission
  • Use of the correct validation rulesets provided by the FDA for your product category
  • Inclusion of all mandatory data fields and metadata

Additionally, submissions must follow the PLR (Physician Labeling Rule) format for prescription drugs, which changes the sequence and labeling requirements for specific sections.

For a full checklist of submission requirements you need to follow, download our checklist.



Automating SPL Generation: Why Manual Methods No Longer Cut It

Given the complexity of SPL files, and the large risk of human error, many teams are turning to automated SPL generation and SPL compliance software to streamline the process.

Benefits of automating your SPL workflow include:

  • Reduced risk of XML formatting or validation errors
  • Version control across multiple product labels
  • Faster updates when regulations or product details change
  • Integration with Regulatory Information Management (RIM) systems

Some tools even provide built-in validation, FDA gateway submission, and change-tracking, making it easier to manage labeling updates across your global portfolio.



The Role of Structured Product Labeling in the Future of Pharma

The push toward electronic drug labeling and data interoperability across healthcare platforms makes SPL more important than ever. As initiatives like IDMP (Identification of Medicinal Products) and global UDI (Unique Device Identification) standards gain traction, structured, digital-first labeling will become the norm.

Pharma teams that invest in SPL knowledge and infrastructure today will be better positioned to:

  • Launch products faster in multiple markets
  • Avoid compliance pitfalls
  • Support digital health integrations
  • Enable real-time labeling updates across systems

Your Next Step Toward Smarter Labeling

Structured Product Labeling mastery isn’t just a technical requirement, it’s a strategic capability and competitive advantage. 

By understanding the SPL XML format, the FDA SPL submission requirements, and the tools available for automation, your team can stay ahead of compliance risks and regulatory delays.

Whether you're managing updates for a popular drug or submitting a new OTC product, SPL is central to your labeling and go-to-market strategy. And with the rise of automated SPL generation and SPL compliance software, it’s easier than ever to stay compliant, efficient, and competitive.

FAQs

1. What is Structured Product Labeling (SPL) and why is it important for pharma teams?
Structured Product Labeling (SPL) is an XML-based standard created by HL7 to organize drug label information in a machine-readable format. It is essential for pharma teams because it ensures regulatory compliance, improves accuracy, and speeds up FDA approval processes for drug labeling.
2. Which types of products require SPL submission to the FDA?
SPL submissions are required for human prescription drugs, over-the-counter (OTC) products, biologics, and other regulated medical products marketed in the U.S. This includes vitamins, dietary supplements, and topical agents when listed with the FDA.
3. How does the SPL XML format help ensure accuracy and compliance in drug labeling?
SPL’s XML format structures label content with standardized tags for sections like dosage, warnings, and administration instructions. This machine-readable structure enables automatic FDA validation, reduces errors, and ensures consistent and up-to-date labeling.
4. What are the key data elements included in an SPL file?
Key data elements include product and manufacturer identifiers (e.g., NDC codes), labeling version history, indications and usage, dosage and administration, contraindications, warnings, drug interactions, packaging information, and marketing status.
5. Why does the FDA mandate SPL submissions to be in HL7-compliant XML format?
The FDA requires HL7-compliant XML because it enables automated processing, semantic tagging of drug information, interoperability across regulatory systems, and standardized submissions critical for efficient labeling approvals and updates.
6. Can SPL requirements apply to over-the-counter (OTC) drugs and nonprescription products?
Yes. OTC drugs and certain nonprescription products listed with the FDA must also be submitted in SPL format. Although OTC labels may be simpler, they must still comply with the same SPL standards.
7. What are the main FDA SPL submission requirements pharma teams must follow?
Submissions must use the correct SPL XML format, include mandatory metadata, pass FDA validation tools, be transmitted via the Electronic Submissions Gateway (ESG), and for prescription drugs, comply with the Physician Labeling Rule (PLR) format.
8. How can automating SPL generation improve the submission process?
Automation reduces human error, speeds up SPL creation and updates, ensures consistent version control, integrates with regulatory systems, and often includes built-in validation and FDA gateway submission capabilities.
9. What are the risks of manual SPL creation and submission?
Manual SPL creation increases the risk of formatting errors, validation failures, delays in approvals, FDA rejection, fines, and even potential patient safety risks due to inaccurate or outdated labeling information.

Let VerifyAPI Handle The Heavy Lifting
×