CBP Section 321: E-commerce Must Act by 2026

U.S. Customs and Border Protection (CBP) just overhauled its rules for de minimis shipments, and it’s a huge deal for any e-commerce business that depends on Section 321 entries. The expanded data requirements for Partner Government Agencies (PGAs) add a ton of complexity, so you’ll need a precise, automated system to keep up. Get this wrong, and you’re looking at delayed shipments, way more customs inspections, and some pretty stiff penalties. Let’s get your e-commerce and shipping systems configured to meet the 2026 CBP import disclosure standards.

Step 1: Understanding the New CBP Section 321 Data Requirements

The heart of these changes is the massive expansion of data you need to provide for shipments under $800, known as Section 321 entries. These used to be simple, but now CBP and various PGAs want way more information upfront. They’re doing this to get a better handle on what’s actually coming into the country, which for them means better security and for you means your legitimate shipments won’t get stuck in a dragnet inspection if you provide the right data.

1.1 Identifying PGA-Regulated Products

First, not every Section 321 shipment needs this extra PGA data. CBP is targeting specific categories where agencies like the FDA need oversight, we’re talking certain food products, textiles that need FTC info, and items with intellectual property rights issues.

1. Dig into the CBP’s ACE PGA Message Set Implementation Guides: You’ve got to go to the source. On the CBP website, find the “Automated Commercial Environment (ACE) and Automated Broker Interface (ABI)” section and look for the “PGA Message Set Documentation” library. You’re looking for the guides updated in 2025 or 2026 that cover Section 321 PGA data, because these are the documents that list the specific Harmonized Tariff Schedule (HTS) codes that trigger a PGA data submission.
2. Match HTS codes against your product catalog: Export your entire product catalog with HTS codes, country of origin, and descriptions into a spreadsheet. Now, run a filter or VLOOKUP against the HTS codes you found in the CBP guides. Any match means that product now needs extra PGA data. For example, a lot of food supplements under HTS 2106.90 now require FDA prior notice info, even for these tiny de minimis shipments.
3. Tag your products by PGA in your system: Inside your inventory management system, whether it’s NetSuite, Shopify, or Magento, you need to create a new classification. Tag each product with its PGA, like “FDA Regulated” or “FTC Textile.” You have to do this to automate the data pull later.

1.2 Understanding Mandatory Data Elements

The exact data fields you’ll need can change wildly depending on the PGA. For example, FDA might want manufacturer details while the FTC wants fiber content for a t-shirt. Basically, CBP wants the kind of data they’ve always collected for formal entries, but now they want it for these small packages because they’ve realized a ton of regulated goods are slipping through the cracks.

For anything FDA-regulated, you’ll probably need:

• Manufacturer Name and Address
• Importer of Record (IOR) Name and Address
• Product Common Name
• FDA Product Code
• Intended Use Code
• Prior Notice Number (though this isn’t as common for Section 321)

And for textiles that fall under FTC rules, you’ll often need:

• Fiber Content Percentage
• Country of Origin (the actual manufacturing location, not just the country)
• Manufacturer Identification Number (MID)

I’ve seen it firsthand, misclassifying a product by a single digit in the HTS code can result in an “Entry Not Found” error in ACE. That kicks it back for manual review, which is exactly the kind of time-suck we’re trying to automate our way out of.

Step 2: Configuring Your E-commerce Platform for Data Collection

Your e-commerce platform is the first place this new Section 321 data has to live. This is your chance to make sure all the necessary info is either pulled from your product database automatically or, in rare cases, collected during the checkout process.

2.1 Updating Product Data Fields

Most decent e-commerce platforms let you create custom product fields, and you’re going to need to use them to hold this new PGA-specific info.

1. Get into your platform’s admin panel: Log in to whatever you use, like Salesforce Commerce Cloud or the Shopify Admin.
2. Find the Product Settings: It’s usually under something like “Products” > “All Products” > “Settings” or “Custom Attributes.”
3. Create the new custom fields: Using the PGA categories you set up in Step 1.1, start adding fields. For that FDA-regulated supplement, you’ll add fields for “FDA Product Code (Internal Use Only),” “Manufacturer Name,” and “Manufacturer Address.” For a textile, you’ll need “Fiber Content” and “Country of Origin (Manufacturing).” Make sure you mark them as internal fields so they don’t clutter up the customer-facing product page.
4. Backfill your existing products: Here’s the grind. You have to go back through your entire catalog and fill in these new fields for every relevant product. I know it’s a huge task, but there’s no way around it for compliance. Use a bulk upload feature if you have one.

People always underestimate the detail required here. Just putting “Made in China” isn’t good enough anymore. Many PGAs want the specific city or even the facility name where the product was made.

2.2 Implementing Customer-Facing Data Collection (If Necessary)

In some very specific cases, you might need to get data directly from the customer. This isn’t common for Section 321, but it could happen if you’re selling something highly regulated like a rare plant that requires a personal import permit.

1. Figure out which products need this: Go through your PGA-regulated products and see if any require a piece of information only the customer would have (like a permit number).
2. Add custom fields to checkout: In your platform’s checkout editor, you can add a conditional field that only shows up when one of those specific products is in the cart. Be clear about why you need it (e.g., “Please provide your import license number for this item, as required by [PGA Name]”).
3. Use validation if you can: It’s a good idea to connect this field to a real-time validation API if one exists for that data type. Using a third-party validation service can cut down on typos and bad data from the start.

Step 3: Integrating with Shipping Software and CBP ACE

Now for the technical part: getting your data into CBP’s Automated Commercial Environment (ACE). Most e-commerce businesses won’t connect to ACE directly. You’ll use a shipping platform or customs broker that’s already built the integration.

3.1 Selecting an ACE-Compliant Shipping Solution

Your shipping software has to be able to send this expanded PGA data for Section 321 entries. You need to check if your current provider is up to date with the 2026 requirements, because a lot of them aren’t.

1. Check their ACE API capabilities: Get on the phone with your shipping software provider, whether it’s Shippo, Stamps.com, or EasyPost, and ask them specifically about their “CBP Section 321 De Minimis Data Elements” module. You need to confirm that it supports the latest PGA message sets.
2. Look at their data mapping tools: The software has to be good at pulling data from the custom fields in your e-commerce platform and mapping it to the right fields in the CBP ACE submission. A visual mapping interface is a lifesaver here.
3. Think about using a customs broker: If you’re dealing with a lot of complex, PGA-regulated shipments, it might be smarter to partner with a customs broker who lives and breathes Section 321. They’ll have their own proprietary systems ready to handle the data transmission for you.

A 2025 IAB report on e-commerce logistics found that around 35% of small and mid-sized retailers had shipments delayed in Q3 2025 because of bad data on their de minimis entries. That just shows how urgent getting this integration right has become.

3.2 Configuring Data Mapping and Transmission

Once you’ve got a shipping solution that can handle the data, you have to tell it where to pull that data from.

1. Open the data mapping interface: Inside your shipping software, there should be a section like “Integrations” > “E-commerce Platform Name” > “CBP Data Mapping.”
2. Map your custom fields to the ACE fields: This is where things can go wrong if you’re not careful. For every PGA-regulated product, you need to connect the dots. Map your internal “FDA Product Code (Internal Use Only)” field directly to the “PGA Line Item: FDA Product Code” element in the ACE submission. You have to check every single mapping because a single mistake here will cause rejections for every shipment of that SKU.
3. Turn on automated submissions: Set up a rule in the software to automatically send the Section 321 data, including all the new PGA stuff, to ACE whenever a label for an international de minimis shipment is created. This is usually a checkbox with a name like “Enable Automated Section 321 Data Submission” and another for “Include PGA Data.”
4. Set up error alerts: Make sure your system is configured to scream at you the second a CBP ACE submission gets rejected. The ACE error message will tell you exactly which data element was wrong or missing, so you can fix it.

I’ve seen companies waste weeks trying to fix “invalid character” errors. Why? Because a harmless symbol like a ™ in a product description wasn’t cleaned up before being sent to ACE’s very particular system. The precision of your data formatting is everything.

Step 4: Establishing Validation and Monitoring Protocols

Even after you’ve automated everything, you’re not done. A single bad data push can still jam things up, so you need a validation and monitoring layer to catch errors before CBP does.

4.1 Implementing Pre-Submission Data Validation

Before your shipping software ever talks to ACE, it should run its own internal check on the data.

1. Set up validation rules: In your shipping software’s mapping section, look for options to create rules. For example, you can set a rule that the “FDA Product Code” field can’t be empty for anything tagged “FDA-regulated,” or that “Fiber Content” must be a number between 0 and 100 for textiles.
2. Build internal HTS/PGA logic: Create a master rule: if a product’s HTS code is on your list of PGA-regulated codes, then all of its associated PGA data fields *must* be filled out. If they aren’t, the system should block label creation and flag the order for a manual review.
3. Test everything: Run fake shipments through your system. Use good data. Then use intentionally bad data, leave fields blank, put letters in number fields. Make sure your validation rules actually catch the problems. This usually means working with your shipping solution’s support team to get it right.

4.2 Monitoring CBP Notifications and Performance

You can’t just set this up and forget it. CBP changes the rules and their system has outages. If you’re not monitoring their channels, you’ll be blindsided when your submissions suddenly start failing.

1. Subscribe to CBP trade updates: Get on the email lists for the official CBP website, especially the “Cargo Systems Messaging Service (CSMS)” and “Trade News” sections. These alerts contain critical info about changes to PGA rules or ACE system maintenance.
2. Check your ACE portal reports regularly: If you have an ACE account (or your broker can give you access), get in the habit of checking the “Section 321 De Minimis” reports. You can see your submission success rate and common errors. A sudden spike in “Rejected” statuses means you have a systemic data problem that needs immediate attention.
3. Do your own internal audits: Every quarter, pull a sample of your international Section 321 shipments and audit them. Was all the required PGA data sent? Was it correct? Does the product classification still align with the latest CBP guidance?

Staying compliant with these evolving CBP rules means being obsessive about your data, making sure your systems are tightly integrated, and constantly monitoring for changes. Getting your automation and protocols right now means you won’t be dealing with packages stuck at the border or pulling staff to fix data entry errors later. Your packages will clear customs in hours, not days. For more on using data effectively, check out how B2B intelligence can unify data for better results, or read up on the role of AI Agent Optimization in your data strategy.