Shipment Held: Evidence to Assemble Before You Respond

Synthetic training examples are clearly labeled. Official instructions and responsible professional decisions remain controlling.

Narration

A shipment hold message can involve several systems and several owners. Treating it as one vague “CPSC problem” invites guessing. Before responding, preserve the exact wording and separate questions about the notice, Product Registry, the broker’s ACE filing, testing evidence, and product identity.

Use a four-step triage map: preserve the request, identify the exact shipment and product, assign each question to the responsible source owner, and answer only from reviewed evidence. Keep the original message, sender, timestamp, deadline, entry or shipment reference, and every attachment. Do not rewrite the request into what you think it means.

Here is a simulated notice: “Provide certificate information for line two.” That sentence does not prove why the shipment is held, which certificate path was used, or what response will resolve the matter. It creates questions. Which product is line two? Who sent the notice? Is the request about certificate data, Registry identifiers, supporting records, or the ACE message?

For the portal or notice record, capture the visible status, sender, time, requested action, and case reference. CPSC’s Import Resources include a shipment tracking tool, while carriers and CBP may maintain separate records. Keep those sources distinct. A status in one system should not be silently represented as the status of another.

For Product Registry and ACE, confirm current facts separately. In the Registry, look for the applicable product record, certification state, Certifier ID, Product ID, and Version ID when Reference PGA is involved. With the broker, confirm what was or was not transmitted in ACE. The Product Registry does not automatically communicate with ACE, so stored data does not prove an ACE filing occurred.

For testing and product identity, match the notice to the exact shipment line, SKU, model, label, invoice, certificate, production facts, report, laboratory, and citations. A report for a similar item or an older version should not be substituted without responsible review. Applicability and sufficiency decisions remain with the importer and qualified professionals.

Build a response register with four states: verified, missing, conflicting, and awaiting owner response. Beside every verified answer, record the source and locator. For each gap, name the owner and next action. In this simulated case, the product model is verified from the invoice and label, the factory name is conflicting, the current Version ID is missing, and the broker owns confirmation of the ACE message.

Start with the free browser-only Request Decoder at CertifyPreflight dot com slash CPSC request decoder. Use sanitized wording and remove personal identifiers, credentials, and tracking details. If the result points to a bounded paid service, review that scope before purchasing. CertifyPreflight does not determine applicability, provide legal advice, promise release or timing, guarantee acceptance, or replace the importer, broker, laboratory, CPSC, or CBP.

Meaningful visual descriptions

Official sources

• CPSC Import Resources
• CPSC eFiling Frequently Asked Questions
• CPSC Product Registry
• CPSC eFiling Document Library

Sources reviewed October 8, 2026.