When ACE rejects an FDA line for bulk tea, preserve the exact response, identify whether it came from CBP or FDA, and correct the named data against controlled source documents before the filer resubmits. Do not treat every delay as a rejection, and do not release the tea because the correction was accepted. A technical reject, a request for documents, manual FDA review, detention and final admissibility are different states with different owners and actions.
First identify which state you actually have
ACE carries the electronic entry and Partner Government Agency message set; ITACS shows FDA entry and line status after data reach FDA. The same shipment can therefore move through several technical and regulatory states. A useful buyer response begins by naming the state rather than saying only “FDA hold.”
| Observed state | What it normally means | Correct next action |
|---|---|---|
| CBP or “bucket one” reject | ACE/CBP did not accept the transaction or a PGA message-set condition failed at the CBP layer | Use the exact CBP error reference; filer corrects the transaction or software mapping |
| FDA or “bucket two” reject | FDA received data that are missing, wrongly formatted or inconsistent enough to prevent further processing | Map the FDA status/reason message to the source field, correct it and resubmit through the filer |
| Accepted, pending review | The entry reached FDA but no final admissibility action has been taken | Monitor the line in ITACS and keep product under control |
| Documents required | An FDA reviewer needs evidence to assess the entry or apparent compliance | Submit the specifically requested records, preferably through ITACS; do not overwrite unrelated data by guess |
| Exam, sample, detention or refusal process | An admissibility or enforcement branch is open, not merely a transmission-format error | Follow the Notice of FDA Action and responsible FDA-office instructions with qualified U.S. advice |
| FDA release | FDA has completed its decision for the identified line | Reconcile CBP, FDA and buyer warehouse status before commercial release |
FDA's ITACS Q&A says “entry number could not be found” means the entry has not reached FDA when the number is correct. “No public status available” means FDA has not yet acted; it is not a reject. The distinction prevents documents or corrections being sent through the wrong channel.
Build one eight-field rejection record
| Control field | Evidence to capture | Stop condition |
|---|---|---|
| Entry and line | Entry number, ACE line, FDA line, transmission timestamp and filer reference | The affected line cannot be identified exactly |
| Response layer | CBP or FDA source, status code, reason code, reason group and full text | Only a paraphrase such as “system error” is available |
| Submission snapshot | Accepted/rejected PG records or readable filer report showing values sent | The proposed fix is based only on the invoice, not the actual transmission |
| Source evidence | Specification, invoice, packing list, bill of lading, facility and party master data | Documents conflict on product, site, party, quantity or route |
| Root cause | Wrong fact, wrong format, conditional rule, stale master data, grouping or software mapping | No one can explain why the field failed |
| Approved correction | Old value, new value, evidence owner, filer approver and affected linked records | The correction changes a legal fact without importer approval |
| Resubmission result | Timestamp, response, accepted transaction identifier and any new message | Silence or a screen refresh is treated as acceptance |
| Final status | ITACS/FDA decision, CBP status, warehouse hold and authorised release record | Operations release stock from a broker email alone |
Use an eight-step correction workflow
1. Freeze the original response
Save the complete machine response and a readable export before anyone retransmits. Record who received it and when. A screenshot that cuts off codes, line numbers or the rejected value is weak evidence. Ask the filer for the exact ACE output, because the buyer cannot diagnose a field that was never shown.
2. Classify the layer and state
Use FDA's current ACE/ITDS page and posted PGA error/status references to separate a CBP reject from an FDA reject, then distinguish both from an accepted entry under review. Route technical questions to the filer or FDA ACE Support and processed-entry status through ITACS or the responsible FDA import office.
3. Map the error to the transmitted field
Locate the PG record, entity role, qualifier or condition named in the response. The March 2026 FDA quick-reference guide groups food data around product, quantity and packaging, entities, arrival and origin. Use the full FDA Supplemental Guide for the exact conditional rule.
4. Reconcile the business fact before its format
Compare what was sent with the supplier document pack. Confirm product, product-code basis, manufacturer, shipper, owner, consignee, country fields, quantity hierarchy and arrival. A valid format can still carry the wrong fact. Align manufacturer evidence with the food-facility registration check without treating FFR, FEI and DUNS as interchangeable.
5. Test whether the line must be split
FDA's current common-error page says entries with multiple products should use different lines wherever a data element differs. Split products with different FDA product codes or manufacturers rather than forcing one line to represent two facts. Reconcile each new line to package counts, net quantities and the container-loading record.
6. Approve one controlled correction
Write the old value, corrected value, evidence and reason. The importer should approve changes to product identity, manufacturer, intended use, FSVP importer or other substantive facts; the filer controls the transmission. If the cause is stale supplier data, open supplier change control rather than patching only today's entry.
7. Resubmit and verify the response
Have the filer retransmit through the authorised system and preserve the returned response. If one error clears and another appears, add it as a new record; do not overwrite the first diagnosis. FDA's quick-reference guide warns that when required information is unavailable at entry time, FDA may reject the filing and the filer must resubmit complete and accurate information.
8. Monitor separately from release
After acceptance, check ITACS for the FDA line state. If documents are requested, submit a reconciled package linked to the correct entry and line through the requested route. Keep the tea in the arrival hold workflow until FDA, CBP and buyer controls are complete. Manage Prior Notice through the shipment filing checklist and FSVP through the importer release checklist; correcting one does not close the others.
Know which requirement controls the correction
- Legal requirement: applicable food-import rules control the facts and duties behind the filing; an electronic acceptance does not waive them.
- Official technical instruction: CBP CATAIR, the FDA Supplemental Guide and FDA error/status references control the data format and system response but are not supplier certifications.
- Voluntary standard: a quality or food-safety standard may improve master-data control but cannot correct or release an ACE entry.
- Trade reference: a broker worksheet, prior entry or software template is a starting point, not proof that today's product, site, parties and route are unchanged.
- Buyer specification: should provide stable product, pack, lot and facility data that can be reconciled to the filing.
- Contract requirement: can allocate data deadlines, correction cooperation, delay costs and change notice; it cannot bind CBP or FDA or guarantee admissibility.
Common buyer mistakes
- Calling every pending line an FDA rejection or hold.
- Editing a plausible field before saving the original response.
- Working from an error paraphrase instead of the returned codes and full text.
- Correcting format while leaving the underlying manufacturer or product fact wrong.
- Reusing a prior shipment's product code, quantity hierarchy or party identifiers.
- Combining products or facilities that require separate FDA lines.
- Sending a large document bundle when the entry has not reached FDA.
- Contacting ITACS technical support for a case-specific admissibility decision.
- Treating accepted transmission as Prior Notice confirmation, FDA release or CBP release.
- Failing to feed recurring errors into supplier, broker and software master-data controls.
Practical conclusion
A reliable file follows exact response - layer and state - transmitted field - source fact - root cause - approved correction - resubmission response - separate release decision. The buyer owns commercial facts, the licensed filer owns transmission, and the U.S. importer and advisers own regulatory decisions. Before booking, review Yunjing Tea's quality controls and send the tea, pack, facility chain, destination and entry-data needs.
Sources checked 27 September 2026: FDA's current ACE/ITDS resource page, including its CBP/FDA reject routing; the Industry Quick Reference Guide to the FDA ACE Supplemental Guide, dated 10 March 2026; FDA's Common Entry Submission Errors page reporting 1 October 2024 to 30 September 2025 data; FDA's current ITACS Questions & Answers; and its Documents Required Status guidance. Recheck the live FDA Supplemental Guide, error/status references, system notices and shipment facts before filing or correcting an entry.
