Why SPL drug listings get rejected, how to read the acknowledgment, the common fixes, and how to resubmit without bouncing again.
Drug registration and listing data are submitted as Structured Product Labeling (SPL) XML files and checked against FDA's automated validation rules. FDA responds with acknowledgments: first a receipt confirming your file arrived, then a validation acknowledgment that either accepts the submission or lists the specific errors that caused the rejection.
| Rejection reason | The fix |
|---|---|
| Labeler code / DUNS mismatch | Align the 9-digit DUNS with the labeler code (first segment of the NDC); ensure the labeler code is assigned first |
| Establishment not registered / inactive | Confirm the establishment registration is active and the DUNS/FEI match before listing |
| Document-tracking errors | Name the file with its document root ID, use a lowercase .xml extension, valid effective time (YYYYMMDD), correct SetID/version |
| Structured-data errors | Correct dosage form, route, active-ingredient UNII & strength (convert to SPL units), package description |
| Marketing-category problem | Supply the required NDA/ANDA number, or use the correct category for a monograph product |
| Labeling ≠ SPL | Make the labeling content and the SPL data match exactly |
Registration and listing are really three SPL submissions in a dependency chain: Establishment Registration, the Labeler Code Form (which assigns the labeler code that forms the first segment of your NDC), and the Product Listing. The listing can only validate once the pieces beneath it are in place.
Until an accepted submission goes through, the product isn't properly listed with a valid NDC — and an unlisted drug is misbranded, which can mean import refusal or marketplace flags. So a rejection isn't just a technical nuisance; it leaves the product in a non-compliant state until it's resolved.
FDA Registration Assistance reads the validation acknowledgment, diagnoses every error (labeler code/DUNS, registration status, document tracking, structured data, marketing category, labeling), corrects the SPL, confirms the underlying registration and labeler code, re-validates the complete file, and resubmits — so it's accepted rather than bouncing again. If the root cause is a lapsed registration, we fix that too.
Contact us at info@fdaregistrationassistance.com or call +1 (928) 275-8333 for a quote. An independent compliance firm serving 1,000+ companies across 135+ countries, with 15+ years of experience.
It means your Structured Product Labeling (SPL) submission didn't pass FDA's automated validation. Drug registration and listing data are submitted as SPL/XML files and checked against FDA's validation rules; when something doesn't conform, FDA returns an acknowledgment with error messages instead of accepting the file. The listing isn't "live" until a clean, accepted submission goes through — so the product isn't properly listed until you fix and resubmit.
Through acknowledgments (ACKs). After you submit, FDA sends a receipt acknowledgment confirming the file arrived, then a validation acknowledgment that either accepts the submission or lists the specific errors. The error messages are the roadmap: each points to the data element or formatting issue that failed. Reading the ACK carefully — rather than guessing — is the first and most important step.
A handful account for most: a labeler-code/DUNS mismatch (the 9-digit DUNS must match the labeler code that forms the first segment of the NDC); the establishment not being registered or its registration inactive; document-tracking errors (the file must be named with its document root ID, use a lowercase .xml extension, and have a valid effective time/SetID/version); structured-data errors (dosage form, route of administration, active-ingredient UNII and strength conversion, package description); marketing-category problems (e.g., an NDA/ANDA number required but missing, or the wrong category for a monograph product); and labeling that doesn't match the SPL.
The labeler code is the first segment of the NDC and identifies the firm; it's assigned via a separate labeler-code SPL submission before you can list products under it. If you list a product before the labeler code is assigned, or the DUNS on the listing doesn't match the DUNS tied to that labeler code, the submission fails validation. Getting the labeler code and DUNS aligned is often the fix.
Yes — this is a common one. Product listing depends on a valid, active drug establishment registration; the listing references the establishment (by DUNS/FEI), and if that establishment isn't registered, is inactive, or the identifiers don't match, the listing can't validate. Confirming the establishment registration is active and correctly identified is a prerequisite, not an afterthought.
These are SPL file-structure/metadata errors, and they're surprisingly common: the file must be named with its document root ID (not a custom name), carry a lowercase .xml extension, contain no stray non-SPL files in the package, and have a valid effective time (YYYYMMDD format) and correct SetID/version numbering. They have nothing to do with your product's substance — but they'll reject the file all the same.
The product data has to be coded to SPL's controlled vocabularies: the correct dosage form and route of administration codes, each active ingredient with its unique ingredient identifier (UNII) and a strength expressed in SPL-acceptable units (strength sometimes has to be converted), inactive ingredients, and an accurate package description. A wrong code or an unconverted strength value will fail validation.
Read the validation acknowledgment and identify every error it lists — not just the first one. Then map each error to its cause (labeler code/DUNS, registration status, document tracking, structured data, marketing category, labeling), fix them all, re-validate the corrected file, confirm the establishment registration and labeler code are in order, and resubmit. Resist the urge to change one thing and resubmit blindly.
Usually because only one error was fixed while others remained, or a fix introduced a new inconsistency (e.g., correcting the SPL but leaving the labeling or registration mismatched). SPL validation checks the whole file, so a listing needs every element right at once. Re-validating the complete corrected file before resubmitting — and confirming the underlying registration/labeler code — is what breaks the loop.
Effectively, yes — until an accepted submission goes through, the product isn't properly listed with a valid NDC. That matters because an unlisted drug is misbranded and can be refused at import or flagged in the marketplace. So a rejection isn't just a technical nuisance; it leaves the product in a non-compliant state until resolved.
No, though they're related. A rejected listing is a submission that failed validation; a lapsed registration is an establishment that missed its annual renewal and became inactive. But they interact: a listing tied to a lapsed/inactive establishment will fail, so fixing a listing sometimes means first fixing the registration. If your registration lapsed, see our renewal/reactivation guidance.
You can — SPL is submitted through FDA tools like CDER Direct or via SPL software — but it's technical: XML structure, controlled vocabularies (dosage form, route, UNII), strength conversions, document tracking, and the labeler-code/registration dependencies all have to be right. Companies without an SPL specialist often cycle through repeat rejections. If it's your first listing or a stubborn rejection, expert help is usually faster overall than trial and error.
Sometimes — a foreign establishment's listing depends on a valid registration that includes a U.S. Agent and the required DUNS identifiers, so a missing or unconfirmed U.S. Agent, or a DUNS mismatch for a foreign site, can surface as a listing failure. Getting the foreign establishment's registration and identifiers clean is part of getting the listing to validate.
It depends on what caused the rejection. A single document-tracking or coding error can be corrected and resubmitted quickly; a listing that failed because the underlying establishment registration is incomplete or lapsed takes longer, because the registration has to be fixed first. The surest path is a complete diagnosis up front so every issue is corrected before resubmission — avoiding a second rejection cycle.
No. An accepted listing means the product is listed with a valid NDC and the submission passed validation — it is not FDA "approval." Approval is a separate, product-level status (an NDA/ANDA, or OTC monograph compliance). Fixing a rejected listing gets you to a valid listing; it doesn't change the product's approval pathway.
We read the validation acknowledgment, diagnose every error (labeler code/DUNS, establishment registration status, document tracking, structured data, marketing category, labeling), correct the SPL, confirm the underlying registration and labeler code are in order, re-validate the complete file, and resubmit — so it's accepted rather than bouncing again. We also fix the underlying registration if that's the root cause. We're an independent compliance firm serving 1,000+ companies across 135+ countries with 15+ years of experience. Contact info@fdaregistrationassistance.com or +1 (928) 275-8333.