The SPL Was Sent, but the Public NDC Field Still Shows the Old Value
Find the first divergence between the prepared SPL, sent version, FDA acknowledgement and observed NDC entry before quoting a public drug-listing correction.
Signals to watch
- A labeler reports that an SPL update was sent while the exact Set ID, document ID, version and acknowledgement remain unavailable
- The public NDC value is compared with an internal spreadsheet or label without proving they describe the same product and package
- Marketing dates, annual certification or a Directory exclusion may explain publication without proving the listing was never submitted
When an updated Structured Product Labeling (SPL) file has been sent but a public National Drug Code (NDC) field still shows the old value, find the first state where the evidence diverges. Compare the prepared document, the version actually sent, the specific FDA acknowledgement and the value observed on the named public surface. Do not jump from “submitted” to “FDA published it incorrectly.”
A human-drug listing services sales lead may see the mismatch in an authorised labeler, manufacturer or regulatory-operations Telegram group while a correction vendor is being selected. Waiting until tomorrow can lose the reconstruction work. The useful response today is a four-state repair record—this article’s workflow, not an FDA-defined submission status model—because a promise made before naming the document and public surface may target marketing dates, certification, an excluded record or the wrong comparison.
Before starting: prove that both sides describe the same record
Capture the public URL or query, product NDC, package NDC if relevant, labeler, field name, visible value and observation time. On the source side, capture the value the company expected and the controlled record that supports it.
Do not compare an internal product row with a package-level directory row unless their identifiers and relationship are clear. Do not compare a current label with an old SPL or a future configuration. The FDA drug registration and listing record chain explains the upstream records; this page begins only after one exact public field and one intended source value have been named.
State 1: reconstruct the SPL version that was prepared
The FDA How to List a Drug instructions distinguish identifiers and version maintenance. When updating a listing, the submitter works from the latest submission, keeps the Set ID, generates a new document ID/root ID, increases the version and supplies the effective time as required by the instructions.
The repair record therefore needs the SPL Set ID, document ID, version number, effective time, product and package NDCs, disputed element, intended replacement and supporting label or source. “We regenerated the XML” does not show which listing lineage it belongs to. XML means Extensible Markup Language, the structured file syntax used for the SPL document.
If the intended value never appears in the reconstructed file, the first divergence is local preparation. The scope is to correct and validate a new listing version, subject to the company’s qualified regulatory review.
State 2: prove which file and route were actually sent
Keep the file hash or controlled copy, transmission time, submission route and operator record. FDA’s drug-listing instructions describe several preparation or submission paths. A screenshot saying “sent” is not enough to prove that the reviewed SPL was the file transmitted under the expected labeler and listing.
Consider this illustrative composite fragment. It is not a real company, product, submission, customer message or commercial result:
new SPL went Friday, ack was okay. NDC still has old package description. need someone to get FDA to fix it
A second fragment says:
we copied last version. new effective date maybe Sept. public screenshot is from yesterday
The thread lacks the NDC, labeler, Set ID, document ID, version, effective time, sent file, route, exact acknowledgement, package relationship, marketing dates, annual certification, public query and participant authority. The first commercial offer should be submission reconstruction, not a promise to make FDA edit the entry.
State 3: read the acknowledgement as written
Record the exact acknowledgement or processing status and tie it to the sent document. Do not rename every transport or validation response “accepted.” An acknowledgement can establish only what that response explicitly says about that file and processing stage.
Check whether the record is eligible to appear on the chosen public surface. The NDC Directory page says a future marketing start date prevents publication until the date is reached. A future marketing end date can keep an entry active until that date. FDA also says the Directory does not contain every listed drug and identifies excluded categories.
Annual maintenance matters as well. The listing instructions explain update and certification duties. A public absence or old-looking field cannot be interpreted without the current version and certification state.
If the acknowledgement identifies a problem, the scope is a new or updated SPL with the error resolved. If the response does not support the team’s “accepted” claim, the scope is first to establish the processing state. Neither route proves when every public surface will change.
State 4: observe the exact public surface again
FDA says the NDC Directory is updated daily. That is a directory-update fact, not a service-level promise for a particular submission or for every label repository. Record the query, URL, field value and check time again after the relevant publication condition is met.
The NDC page also says FDA does not submit or alter registration or listing data. To add, correct or update Directory information, the company submits a new or updated product listing through SPL; accuracy remains the submitting company’s responsibility.
This gives the sales lead three distinct end states:
- The intended value was never in the sent version: prepare and submit a corrected listing.
- The sent version has a documented processing problem or unresolved state: address that specific response before assessing publication.
- The evidence supports publication eligibility but the named public surface still differs: preserve the complete packet and use the FDA contact route appropriate to drug registration and listing, without predicting the agency’s decision or response time.
The official-source ladder helps keep a directory observation, acknowledgement and company statement at their proper evidence levels. A device identifier mismatch follows a different system and should use the GUDID correction article instead.
The repair packet that can support a quote
The packet should contain:
- exact public surface, URL or query, visible field and observation time;
- labeler, product NDC and package NDC where applicable;
- SPL Set ID, document ID, version and effective time;
- controlled copy of the file actually sent, route and time;
- exact acknowledgement or processing evidence tied to that file;
- marketing start/end dates and current certification state;
- controlled source supporting the expected value; and
- authorised source owner, regulatory approver and submitter.
With these items, a listing specialist can identify the first divergence and quote the next controllable action. Without them, “public record repair” is only a symptom label.
Top Prospect can organise matching fragments from groups a user has authorised and enabled, keeping the original message, source, time and review reasons together. Its current production matching-target interface saves configurations but does not automatically generate new candidates. It cannot access a private submission, interpret an acknowledgement not provided by the user, change an FDA record or contact the poster. People at the submitting company and qualified regulatory specialists make those decisions. Once the packet exists, the team can review pricing for the properly bounded service.
Key facts
- The SPL Set ID, document ID, version and effective time identify different parts of a listing update.
- “Sent” and a specific FDA acknowledgement are separate evidence states.
- A future marketing start date can delay NDC publication; Directory exclusions and certification also affect what appears.
- The NDC Directory is updated daily, but FDA does not publish a universal synchronization promise for every surface.
- FDA does not submit or alter a company’s registration or listing data; corrections require a new or updated SPL.
- Directory absence does not by itself prove that a drug is unlisted, unapproved, unlawful or discontinued.
Written by the Top Prospect Research Team and reviewed 24 August 2026 against the three FDA sources listed above. This article supports commercial scoping and is not legal or regulatory advice.
Frequently asked questions
Does sending an SPL mean the NDC Directory must already show the new value?
No. The team must inspect the specific acknowledgement or processing result, marketing dates, certification state and Directory inclusion rules, then observe the exact public entry. FDA does not publish a universal propagation time for every public surface.
Can FDA directly edit the company’s listing data?
FDA states that it does not submit or alter registration or listing data. The submitting company is responsible for accuracy and must use a new or updated SPL to add, correct or update listing information.
Does a missing NDC Directory entry prove that the drug is not listed?
No. FDA says the Directory does not contain all listed drugs and describes exclusions and publication conditions. Missing from that surface also does not prove approval status, legality or discontinuation.
What is the minimum correction packet?
Keep the exact public entry and observation time, labeler and NDC, SPL Set ID, document ID, version and effective time, sent file and route, specific acknowledgement, marketing dates, certification state, disputed field, source value and authorised owner.
Sources and further reading
How a Signal worth attention is found
See how Top Prospect finds and organizes Signals worth checking, keeps the original Telegram context, removes duplicates, and helps you decide what to review first. You decide whether to follow up and what to do next.
