U.S. IEEPA Tariffs – Refunds, ACE Implementation, and Latest Developments

IEEPA tariffs are U.S. import charges imposed under emergency economic powers, and they must be filed against the correct HTSUS classification, country of origin, customs value and tariff instruction. ACE is the CBP system used to submit and process those tariff data, and CBP introduced tariff-filing enhancements effective in October 2026.

Rules as of November 2, 2026.

A merchant asking about U.S. IEEPA tariffs usually wants to know three things: whether a product is affected, how the charge reaches the customs entry, and what needs to change in checkout and fulfillment systems. The answer begins with product classification and origin. A product description alone is not enough to determine an IEEPA tariff result.

De minimis is the value below which an import may qualify for simplified treatment under the applicable import rules. The U.S. de minimis threshold is $800, according to U.S. Customs and Border Protection.

What are U.S. IEEPA tariffs?#

U.S. IEEPA tariffs are import charges imposed under the International Emergency Economic Powers Act, a law that permits the President to impose economic sanctions in response to a national emergency. IEEPA tariffs are not identified by a product name alone. They are administered through customs classification, country-of-origin data and filing instructions.

The International Emergency Economic Powers Act, commonly shortened to IEEPA, is a U.S. law that gives the President authority to regulate certain economic activity after declaring a national emergency. For importers, the operational consequence is that a tariff instruction may attach to goods entering the United States based on facts shown on the customs entry.

Those facts start with the product’s tariff classification. The United States uses the Harmonized Tariff Schedule of the United States, or HTSUS, to classify imports. The U.S. International Trade Commission explains that HTSUS codes classify imported goods, including goods subject to IEEPA tariffs.

The code matters because a tariff instruction can refer to a chapter, heading, subheading, tariff provision, statistical suffix, country treatment or combination of those elements. A store cannot safely infer the result from a catalog category such as “home goods,” “electronics,” “apparel” or “accessories.” Customs classification is more exact than marketplace taxonomy.

Country of origin matters separately from ship-from location. A parcel dispatched from a fulfillment center in one country may contain goods originating in another. The origin used for customs is generally the country where the goods were made or last substantially transformed, not necessarily the country where the seller is located or where the parcel was handed to the carrier. Merchants should keep origin evidence close to the product record, not buried in a supplier email.

IEEPA tariffs may sit alongside ordinary customs duty and other import obligations. That does not mean every product, every origin or every entry has the same treatment. The entry must be evaluated against the instructions applicable to the goods at the time of importation.

For a retailer, that means four product facts need to travel together:

1. A clear commercial description.

2. The HTSUS code or the information needed to determine it.

3. Country of origin.

4. Customs value and supporting transaction records.

A fifth fact is just as important operationally: the date the goods enter the United States. Tariff treatment is applied at entry, so a stale spreadsheet can be more dangerous than no spreadsheet if it causes a team to quote an outdated charge as certain.

Why does IEEPA tariff treatment depend on HTSUS classification?#

HTSUS classification determines how Customs identifies imported goods in the tariff schedule, including goods subject to IEEPA tariff instructions. An accurate description, material breakdown, function, construction and origin record give the broker or filing system the facts needed to select the correct tariff line.

The global Harmonized System starts with a six-digit product classification structure. Countries then extend that structure for their own tariff schedules and reporting needs. In the United States, imports are classified in the HTSUS. The USITC’s HTSUS materials are the primary reference for the U.S. tariff schedule.

A classification workflow should not start with a tariff rate. It should start with the article itself.

For example, a merchant selling a travel bag should record whether the outer surface is textile, leather, plastic sheeting or another material. A merchant selling a kitchen tool should record its principal material, whether it is electrically operated and its actual function. A merchant selling a bundled product should record the components, quantities and intended retail presentation.

Those details are not paperwork for paperwork’s sake. They decide which heading, subheading and national tariff line may apply. If the product record says only “bag,” “tool,” “kit,” “accessory,” “gift” or “parts,” the classification process has to rely on guesswork. That guesswork can produce inconsistent entries across carriers, warehouses and brokers.

The same product can also have a different customs result when origin changes. A listing should therefore not treat origin as fixed unless the sourcing arrangement is fixed. If one supplier makes the item in one country and a replacement supplier makes it in another, the SKU may need a separate origin record, separate landed-cost estimate and separate customs review.

A useful product-data structure includes:

• Merchant SKU.

• Product name used by shoppers.

• Customs description used on the invoice.

• Brand and model where relevant.

• Material composition.

• Product function and intended use.

• Dimensions, weight or capacity where relevant.

• Number of components.

• Country of origin.

• Supplier evidence supporting origin.

• HTSUS classification and classification rationale.

• Effective date and reviewer for the classification record.

Merchants building their own customs workflow can use border.bot’s HS classification tools to turn product descriptions, URLs or product images into a classification starting point. The output should still be checked against the item’s actual specifications, especially where material, construction or use changes the tariff result.

What does ACE do for IEEPA tariff filings?#

ACE is CBP’s Automated Commercial Environment, the system used for import processing and tariff filing. CBP has implemented ACE for filing and processing tariffs, including tariffs related to IEEPA, and CBP announced tariff-filing enhancements effective from October 2026.

ACE is not a consumer checkout tool. It is the customs processing environment behind the import declaration workflow. Depending on the shipping model, a customs broker, express carrier, postal operator, importer or another authorized filing party may transmit data into the CBP process. The merchant still needs to supply accurate commercial data.

For an ecommerce seller, ACE matters because the data passed into a shipment declaration must agree with the product record, commercial invoice, order record and carrier manifest. A mismatch can create delays, requests for clarification, incorrect duty estimates or post-entry problems.

CBP’s ACE updates page states that tariff-filing enhancements took effect in October 2026. The operational lesson is simple: do not treat tariff filing as a static spreadsheet exercise. A merchant’s broker instructions, carrier integration, order-export fields and validation rules need regular review.

The fields most likely to cause trouble are usually not technical customs fields. They are basic commercial fields that a store already holds but does not normalize:

• Product description.

• Unit value.

• Quantity.

• Currency.

• Country of origin.

• HTSUS classification.

• Seller and buyer identity.

• Shipment terms.

• Freight and insurance treatment where relevant.

• Product identifiers that link the invoice line back to the merchant’s catalog.

If a merchant sells through multiple channels, those fields must remain consistent across all of them. A marketplace export, warehouse management system, carrier label platform and broker file should not each use a different product description or origin value for the same SKU.

Which data should a merchant send to its broker or carrier?#

A merchant should send its broker or carrier enough product, value, origin and transaction information to prepare an accurate customs declaration. The minimum useful dataset is not just an order total. It is a line-level record that connects each imported item to a defensible classification and origin statement.

A carrier may ask for data in a format that looks simpler than a formal customs entry. That does not reduce the importance of the source data. A short carrier form can still feed into a filing that creates duty liability, customs records and audit exposure.

The most reliable approach is to maintain a customs data layer in the product catalog rather than assembling customs data manually for each order. A merchant should be able to export the same core fields for every channel and warehouse.

Product description#

The commercial description should identify what the product is, what it is made of and what it does. “Clothing,” “gift,” “sample,” “parts” and “accessory” do not give customs enough information to classify goods reliably.

A better description is specific without becoming marketing copy. For example, “women’s knitted pullover, 100% cotton” is more useful than “premium sweater.” “Stainless steel insulated beverage bottle” is more useful than “hydration accessory.” “Rechargeable cordless electric hair clipper” is more useful than “grooming kit.”

Descriptions should match the physical goods. If an item is sold as a bundle, the invoice should make clear whether it is a set for customs purposes or several separately identified articles. Do not let a marketing bundle name hide the contents.

Value#

The customs declaration needs a value that reflects the commercial transaction. A store should preserve the order record, item prices, discounts and any relevant supporting records. The customs value question is separate from the shopper-facing list price. A discount code, bundle discount or free item can affect how the transaction is documented.

The merchant should not solve a duty or checkout problem by reducing declared values or calling a sale a gift. The invoice needs to reflect the actual transaction and the goods shipped. For practical invoice drafting, see the guide to commercial invoices for international shipments.

Origin#

Country of origin should be determined from the product’s manufacture or substantial transformation, not from a warehouse address. If origin is uncertain, pause before shipping rather than letting a carrier auto-fill the shipping country as the origin.

Origin evidence may include supplier declarations, manufacturing records, bills of materials, production information and origin certifications where relevant. The level of evidence needed depends on the goods and the claim being made, but a merchant should at least be able to explain why the origin field says what it says.

Classification#

HTSUS classification should be stored at the SKU or variant level where product differences matter. Size may not change classification for one product category, but material, construction, gender, intended user, electrical function, fiber content or component mix can change it for another.

Keep a rationale. A code without reasoning becomes hard to maintain when a buyer, broker or internal team asks why it was selected. A classification note should identify the product facts used and any assumptions. It should also record the date of review.

How should merchants think about the $800 de minimis threshold?#

The U.S. $800 de minimis threshold is a value threshold for imports, but it is not a blanket instruction to ignore customs classification, country of origin or tariff rules. Merchants should identify the shipment value, then confirm the entry route and applicable treatment with their carrier, broker or customs adviser.

The U.S. de minimis threshold is $800, effective from January 1, 2023, according to CBP. For ecommerce teams, the common mistake is treating that figure as a landed-cost guarantee.

It is not.

The threshold is one part of the import analysis. A shipment still needs accurate goods data. The merchant must know what is in the parcel, where it originated and how the carrier or broker will present it to CBP. A threshold does not make a vague invoice accurate, and it does not answer whether product-specific restrictions, agency requirements or other customs rules apply.

The $800 figure also creates operational edge cases around order splitting and order consolidation. A store should not create artificial shipments simply to chase a threshold without obtaining customs advice. Customs treatment depends on facts and applicable rules, not only on how a checkout system creates parcel labels.

The same caution applies to promotions. A “buy two, get one free” offer may change the shopper’s payment, but the shipment still contains all the goods. The invoice and product records must describe what was shipped and how the transaction was priced.

This chart shows the only threshold figure merchants should treat as a starting point, not a complete duty calculation.

The takeaway is that a single dollar threshold cannot replace product-level classification and origin controls.

In what order should an ecommerce team assess an IEEPA tariff exposure?#

An ecommerce team should assess IEEPA tariff exposure by confirming the goods, classification, origin, value, entry timing and filing path before quoting an import charge. That order prevents the most common error: starting with a rate and trying to force incomplete product data into the result.

The sequence below is designed for a merchant, developer or operations manager. It does not replace legal advice or a customs broker’s entry review. It does create a repeatable internal process that gives the broker better information.

Step 1: Identify the article as customs sees it#

The correct question is not “What do we call it on the website?” It is “What physical article is being imported?”

A listing title can be useful, but it often contains brand language, search keywords and aesthetic descriptions that do not help classification. A customs-ready record describes the item’s material, construction, components and function.

For apparel, record fiber content, knit or woven construction, garment type and user category where relevant. For electronics, record the electrical function, whether the item is a finished device or part, its principal purpose and whether it contains batteries. For furniture and home goods, record materials, construction and intended use. For cosmetics, food, medical products and children’s goods, record the product identity and any regulated attributes separately from the tariff description.

Step 2: Establish origin before selecting a tariff outcome#

Origin cannot be inferred from the seller’s location, payment processor, marketplace account or outbound warehouse. If a seller uses a third-party logistics provider in the Netherlands to dispatch goods made in Vietnam, the customs origin may still be Vietnam. If components are produced in several countries, the merchant needs evidence for the country that customs treats as the origin.

This is why sourcing changes must be connected to customs data. Procurement teams often update vendor and purchase-order records while ecommerce teams continue using the old origin in product feeds. That disconnect is a real operational risk.

Step 3: Classify the actual SKU or variant#

Do not assign one HTSUS code to an entire collection because the product photos look similar. Variants can differ in materials or function. A coated textile bag and a leather bag may need different review. A non-electric kitchen tool and an electrically powered appliance may not belong under the same classification. A basic garment and a garment with a different fiber composition may require separate analysis.

When a new item is added to the catalog, require customs fields before it becomes eligible for international fulfillment. That is easier than stopping orders after the product starts selling.

Step 4: Review tariff instructions against the facts#

The tariff question is a rules question, not just a code lookup. The review should use the selected HTSUS classification, origin and expected entry date. It should also identify whether the instruction requires additional reporting or treatment on the entry.

Do not tell customers that an IEEPA tariff is “included” unless the business has a process that verifies that statement per destination, product and order. The word “included” means the merchant is taking commercial responsibility for a charge that may change when origin, product mix, shipment structure or entry timing changes.

Step 5: Preserve the evidence#

A merchant should retain the source information used to support classification and origin. This can include supplier specifications, material declarations, invoices, manufacturing statements, product photographs, bills of materials, purchase orders and internal classification notes.

The evidence should be attached to the SKU record or a linked document system. A shared inbox is not a durable customs record.

Worked example: a $799 order shipped to the United States#

A $799 order shipped to a U.S. customer may fall below the $800 U.S. de minimis threshold, but the merchant still needs the product description, origin and HTSUS classification before deciding how the parcel should be declared. The $799 figure answers only the value question, not every customs question.

Assume a merchant sells one insulated stainless-steel beverage bottle for $799. The bottle is manufactured in Country A and shipped from a fulfillment center in Country B to a customer in the United States.

The order record contains:

The order value is $1 below the $800 threshold stated by CBP. That does not allow the merchant to write “gift” on the invoice, omit the country of origin or describe the item merely as “bottle.” It also does not make Country B the origin just because it is the shipping location.

The merchant should provide the filer with a description such as “insulated stainless-steel beverage bottle,” the quantity, the $799 transaction value, Country A as origin if supported by manufacturing evidence and the applicable HTSUS classification once determined.

What does the shipment pay? The available facts do not establish an IEEPA tariff rate, ordinary duty rate, tax amount or carrier fee. The only supported conclusion is that the order value is below the stated $800 de minimis threshold. A responsible merchant should not invent a duty result from that number.

Now change one fact: the supplier moves production to Country C. The website listing, retail price and shipping location remain the same. The customs analysis may still change because origin changed. That is why origin needs to be a first-class product field, not a note on the purchase order.

Who pays an IEEPA tariff in an ecommerce shipment?#

The party responsible for the import declaration and customs charges depends on the shipment’s commercial and carrier arrangement. A merchant should decide before checkout whether it will collect and pay import charges, leave them for the customer or use a marketplace or carrier arrangement that assigns the role differently.

A store can sell delivered-duty-paid in commercial terms, quote estimated import charges at checkout or ship on a basis where the buyer may face charges on arrival. The commercial choice does not change the underlying customs facts. It changes who receives the bill, who has promised what to the buyer and who needs access to the supporting data.

For a merchant using a broker or express carrier, the importer of record and billing arrangement should be documented in the shipping account setup. The merchant should know:

• Who appears as importer of record.

• Who receives duty and tax invoices.

• Whether the carrier advances charges.

• Whether the merchant is billed after delivery.

• Whether the buyer can be charged on delivery.

• How disputes are handled.

• Which party submits entry information.

• What data format the carrier requires.

A store should avoid a checkout promise that says “duties included” when the carrier account is actually set up to bill the recipient. The customer experience, the commercial invoice and the carrier billing instructions must match.

How should checkout and pricing systems handle IEEPA uncertainty?#

Checkout and pricing systems should treat IEEPA tariff exposure as product- and origin-specific import data, not as one universal percentage added to every U.S. order. A checkout estimate should be based on the item, origin, value, shipment method and current tariff treatment available to the merchant’s calculation process.

The first pricing decision is whether the merchant will show import charges separately, include an estimated amount in the total price or leave charges payable by the recipient. The second is whether the merchant has enough reliable data to support that decision.

A pricing rule that adds the same surcharge to every U.S.-bound order may be simple, but it can undercharge some items and overcharge others. It can also produce inconsistent margin reporting. A better design attaches customs attributes to each line item.

At minimum, an international checkout service should receive:

• SKU or variant identifier.

• Quantity.

• Selling price.

• Currency.

• Country of origin.

• HTSUS code or classification request data.

• Destination country.

• Destination postal code where required for tax or carrier logic.

• Shipping method.

• Merchant-paid or buyer-paid charge setting.

• Any discount allocation used to document transaction value.

A calculation service should return more than a single total. It should preserve the components and legal basis used to make the estimate, so the merchant can explain differences between a pre-purchase estimate and a later carrier invoice.

Merchants integrating customs calculations can use border.bot’s landed-cost calculation tools to calculate duty, tax and fee components from line-level product, origin and destination data. The goal is not to replace the customs filer. The goal is to prevent a storefront from making pricing promises based on incomplete information.

A merchant should also set a clear policy for orders that cannot be priced automatically. For example, a new SKU with missing origin data could be blocked from international checkout until the information is complete. That creates a small catalog-management task instead of a large customs, refund and customer-service problem later.

What should fulfillment teams change after the ACE updates?#

Fulfillment teams should review the data flowing from their ecommerce platform to their carrier, broker or shipping software after ACE tariff-filing updates. CBP’s October 2026 tariff-filing enhancements make clean, consistent source data more important because filings depend on structured product and transaction information.

The warehouse cannot fix a classification problem if the fulfillment system receives only a marketing title and a retail price. Warehouse teams need an export that is customs-ready before the label is created.

A good fulfillment rule is: no international label without a complete customs record. That does not mean every packer needs to become a tariff specialist. It means the system should prevent incomplete records from reaching the packing station.

Make customs fields mandatory for international SKUs#

A merchant should require a customs description, origin and tariff classification status before enabling a SKU for U.S. fulfillment. “Classification status” can be more useful than a code field alone because it distinguishes:

• Reviewed and approved.

• Provisional, pending review.

• Not classified.

• Variant-specific review required.

• Supplier-origin evidence missing.

• Restricted or agency review required.

This status prevents a product manager from copying a code from a similar item without documenting whether the item is actually comparable.

Version product customs data#

SKU data changes. Suppliers change materials. A product gets redesigned. Packaging changes from a single article to a retail set. A sourcing team moves production. These changes should trigger a customs review.

Keep a version history showing when the description, classification, origin and supplier changed. If a broker asks why a shipment declared one origin in March and another in July, the business should be able to show the sourcing change rather than appearing inconsistent.

Audit carrier exports#

Test what your carrier actually receives. A store may show “100% cotton knit pullover” in its internal system but transmit only “sweater” through a shipping integration. A warehouse may store origin at the parent-product level while variants inherit an incorrect country. A marketplace connector may truncate descriptions.

Run sample exports for representative products and compare:

1. Product description in the catalog.

2. Product description on the commercial invoice.

3. Declared country of origin.

4. Declared value.

5. Classification data.

6. Quantity and unit measures.

7. Recipient and importer information.

8. Shipping terms and billing setup.

The audit should cover direct website orders, marketplace orders, returns, replacement shipments and orders created manually by support staff. Manual orders are often the least controlled path.

Separate returns from new sales#

A return shipment is not the same transaction as a new sale. A replacement is not the same as a free gift. A repair return is not the same as a retail order. Each needs documentation that explains why the goods are crossing the border and how they relate to the original transaction.

Do not ask warehouse staff to improvise invoice descriptions for returns. Build templates and required fields into the returns workflow. For more detail on replacement paperwork, see the guide to commercial invoices for replacement and warranty items.

What records should an importer keep for IEEPA tariff review?#

An importer should keep records that support what the goods were, where they originated, how they were valued and how they were classified. The practical test is whether someone outside the original team could reconstruct the decision from the order, product file, supplier evidence and filing record.

The record set should link commercial, operational and customs data. A folder containing only invoices is rarely enough. A customs classification without the product specification is hard to defend. An origin declaration without a link to the supplier and manufacturing record is also weak.

A merchant should also identify a clear owner for each part of the record. Product teams own specifications. Procurement owns supplier and manufacturing evidence. Finance owns transaction and pricing evidence. Logistics owns carrier setup. Customs or trade compliance owns classification governance. Without named ownership, customs data usually becomes everyone’s problem after a shipment is delayed.

What are the mistakes that create the biggest IEEPA tariff risk?#

The biggest IEEPA tariff risks usually come from wrong origin, weak classification, incomplete invoices and checkout promises that do not match the actual entry process. These are process problems before they become customs problems, which means merchants can reduce risk by fixing product data and workflow controls.

The first mistake is treating country of origin as the country of dispatch. This often happens when sellers use overseas warehouses or third-party logistics providers. The shipping system knows where the parcel is leaving from, so it auto-fills that field. The actual manufacturing origin may be different.

The second mistake is using broad catalog labels as customs descriptions. A product called “fashion accessory” may be a textile article, leather article, jewelry item, hair accessory or something else. The phrase tells a shopper almost nothing about the customs classification.

The third mistake is copying an HTSUS code from a competitor, marketplace template or old broker invoice without checking product facts. Similar-looking goods can differ by materials, construction, function or set composition. Copying a code also copies someone else’s unverified assumptions.

The fourth mistake is failing to reconnect customs data after a sourcing change. A product can keep the same SKU, photographs and retail listing while moving to a new factory in a different country. The customs record must change when the manufacturing facts change.

The fifth mistake is setting a single U.S. surcharge for an entire catalog. That may feel operationally efficient, but it obscures product-level tariff exposure and makes margin reporting unreliable. A merchant should either calculate at item level or clearly communicate that charges are not included.

The sixth mistake is allowing support teams to create replacement orders without customs controls. A support agent may mark a replacement as free in the ecommerce system, but the parcel still contains a physical article that must be accurately described and valued for customs purposes.

The seventh mistake is assuming the $800 de minimis threshold solves the classification question. It does not. The threshold is a value reference. It is not a product description, origin rule or tariff code.

How can developers build an IEEPA-ready customs data flow?#

Developers can build an IEEPA-ready customs data flow by making classification, origin, valuation and filing attributes part of the product and order schema. The best implementation prevents missing customs information early, then passes structured fields consistently into checkout, fulfillment, carrier and broker integrations.

The system should avoid a single free-text “customs info” field. Free text is hard to validate, hard to version and easy to overwrite. Use separate structured fields.

A practical SKU schema may include:

sku
variant_id
customs_description
country_of_origin
origin_evidence_reference
htsus_code
classification_status
classification_reasoning
classification_reviewed_at
material_composition
product_function
unit_weight
unit_value_reference
restricted_goods_status
agency_review_status

At order level, store:

order_id
destination_country
destination_postal_code
shipment_method
currency
line_item_value
discount_allocation
shipping_charge
insurance_charge
importer_of_record
duty_billing_party
commercial_invoice_reference
carrier_reference
broker_reference
entry_date_reference

The developer goal is traceability. When a charge estimate is generated, the system should log which SKU data, origin, classification and value were used. When a product record changes, the system should preserve the prior version for shipments already created.

For API users, border.bot’s Calculate documentation describes how line-level duty, tax, fee and landed-cost calculations can be requested with legal basis and de minimis information. For product classification, the Classify API documentation explains the product inputs and outputs used to determine destination tariff codes.

A system should also handle uncertainty explicitly. If classification confidence is low, if origin evidence is missing or if a product has a restriction flag, the API response should not be silently converted into a guaranteed checkout price. Route the order or SKU into a review queue.

How should merchants communicate import charges to customers?#

Merchants should communicate import charges in language that matches their actual shipping arrangement. If the merchant pays charges through its carrier or broker setup, it can explain that import charges are included subject to the documented terms. If the buyer may pay on delivery, the checkout and shipping policy should say so clearly before payment.

Avoid broad claims such as “no extra costs” unless the merchant can support them for the products and shipping lanes offered. A customer who receives an unexpected carrier payment request is less concerned with the legal distinction between duty, tax, tariff and clearance fee. They see a broken price promise.

A clear policy should answer:

• Is the merchant or customer responsible for import charges?

• Are any import charges estimated at checkout?

• Can estimates change?

• Who is named as importer of record?

• What happens if the recipient refuses delivery?

• How are return shipments handled?

• Which destinations are excluded from merchant-paid charges?

• What customer information is needed for customs clearance?

If the merchant sells through marketplaces, check the marketplace’s import-charge model separately. Marketplace rules can affect what the buyer sees, who collects money and what data is passed to the carrier. Do not assume the marketplace’s catalog fields are sufficient for the merchant’s customs obligations.

Sources#

• U.S. Customs and Border Protection, “De Minimis Threshold for Imports,” January 1, 2023

• U.S. International Trade Commission, “Harmonized System (HTSUS) Codes,” January 1, 2022

• U.S. Customs and Border Protection, “ACE Portal Updates,” October 1, 2026

• border.bot, United States import information

• border.bot, ACE portal information