The rejection arrives as a code, not an explanation. ACE refused the filing, the goods are still where they were, and the broker's screen shows a number. The first mistake is treating the code as a verdict on the shipment. It is a diagnosis of the filing: one line, one field, one code that ACE would not accept.
Since September 27, 2025, ACE auto-rejects manifest filings under CBP-190 when the cargo description, shipper, or consignee data is insufficient. The message is blunt because the rule is blunt: a vague description does not clear. General merchandise is not a description. ACE wants to know what the goods are, and it rejects the filing until the description says so.
The rejection protects the importer more than it punishes them. A filing ACE accepts becomes an entry, and an entry with a wrong code becomes a liquidation problem months later. The rejection catches the error while it is still cheap, before the goods move and before the duty is assessed.
Error codes 548, 549, and 550 cover the manifest data failures: insufficient cargo description, missing shipper data, and missing consignee data. Each code points at a specific field, and the fix is in that field, not in the shipment.
HTS errors are the other common rejection, and they are fixed with a Post-Summary Correction, not a new entry. The code was wrong; the goods were fine. A binding ruling settles the classification before you import, which is cheaper than correcting it after the entry is filed.
ISF failures are the expensive cousin. The Importer Security Filing, the 10+2 data elements, must be filed 24 hours before loading, and a late or wrong ISF is a penalty, not a rejection. The rejection is the cheap problem. The ISF is the one that costs money.
A rejection means the filing was not accepted, so nothing was entered. A hold means the entry was accepted and CBP wants to examine the goods, so the filing was fine and the shipment is the question. A discrepancy means the entry and the goods do not match, which is a different filing and a different fix.
Confusing the three is how importers resubmit a filing that was never the problem and get the same result twice. Reading the ruling, or the rejection, before you act is the discipline: the document tells you what is wrong, and the fix follows the document.
Read the code against the entry line it points at. Fix that line: the description, the code, the consignee. Resubmit, and check the acceptance before the goods move.
If the same code comes back, the fix was wrong, not the system. Call the broker and read the filing together, because a second identical rejection is a data problem, not a system problem. The entry summary fields are where most of these errors live, and the form rewards the importer who reads it line by line.
Confirm the current filing requirements with a licensed customs broker before changing a process, because ACE validations change and the code list moves with them.
ACE would not accept the filing, usually because of a bad code, a missing data element, or a cargo description CBP cannot use. The goods are unaffected; the filing is the problem.
They cover manifest data failures under CBP-190: insufficient cargo description, missing shipper data, and missing consignee data. Each code points at a specific field, and the fix is in that field.
A rejection means the filing was not accepted, so nothing was entered. A hold means the entry was accepted and CBP wants to examine the goods. A discrepancy means the entry and the goods do not match. Each one has a different fix.
The Importer Security Filing, the 10+2 data elements, must be filed 24 hours before loading. A late or wrong ISF is a penalty, while a rejection is just a filing that needs correcting before the goods move.