Jordan Deal Links Customs Action to Forced-Labor Section 301
Jordan signed a U.S. trade deal after USTR proposed a 12.5 percent Section 301 tariff in its forced-labor investigation. Annex I leaves the rate open, while treatment of U.S. Section 307 entity determinations may provide early implementation evidence.
Primary lensTariff authority
Sub-topicForced-labor action
Evidence base9 records used
Use caseAuthority exposure review
Jordan's July 21 trade deal gives it a new argument in the forced-labor investigation, where USTR proposed a 12.5 percent Section 301 tariff.
The first useful evidence may come after entry into force, when Jordan must decide how its customs service will act on U.S. Section 307 entity determinations. That obligation is narrower than the comprehensive forced-labor import ban due within five years. It can still produce border decisions long before the broader regime is finished.
Annex I leaves the tariff outcome open. The agreement adds Jordan to the set of economies with a reciprocal-trade commitment and states that the United States intends to consider implementation efforts. It names no Section 301 rate.
The June notice proposed a 10 percent additional duty for the economies it identified as having an existing prohibition, a commitment in an Agreement on Reciprocal Trade, or a partial regime that blocks some forced-labor goods. It proposed 12.5 percent for the remaining economies. Jordan was absent from the named 10 percent group. Its agreement arrived more than six weeks later.
Article 2.9 of the White House July 21, 2026 U.S.-Jordan reciprocal trade agreement now commits Jordan to establish a comprehensive prohibition. The new commitment supports an argument for treatment comparable to the economies in USTR's proposed 10 percent group. USTR still has to determine the action, subject to any specific presidential direction, issue the operative notice, and supply customs instructions.
The June rates are scenarios until then. USTR described them as proposed actions and invited comment on whether a commitment, an enacted ban, or a partial regime should justify different rates. Jordan's signature changes the facts available for that inquiry without disposing of the agency's adverse finding.
Traverse previously examined the pre-signature rate pathway in Trade Act Section 301 India rate-tier Analysis. Jordan presents a later stage: a signed commitment with an undefined customs mechanism and no operative implementation record yet.
The signature did not activate the deal
Article 6.6 sets the entry-into-force rule. No agreement term becomes operative until 60 days after both governments exchange written notifications that their internal procedures are complete. The USTR July 21, 2026 signing announcement confirms the signature and describes the deal, but it reports no exchange of those notifications.
Annex I uses a separate date for its scheduled product treatment. Paragraph 3 applies on the later of August 1, 2026 or the agreement's entry into force. That rule cannot substitute for the notification exchange or establish the start date for Article 2.9.
Companies therefore need an official entry-into-force notice. Adding 60 days to July 21 would assume that both governments completed and notified their internal procedures on the signing date. The public record reviewed for this analysis does not establish that fact.
Timing will shape the proceeding. Jordan could adopt domestic measures before entry into force, and Annex I refers to steps it has taken or is taking. Entry into force marks when the agreement requires performance; earlier voluntary action could still inform USTR.
Annex I leaves the Section 301 rate open
Paragraph 2 of the White House July 21, 2026 U.S.-Jordan Annex I provides preferential tariff treatment for qualifying Jordanian goods in future U.S. tariff actions, to the extent permitted by domestic law. It excludes actions under Title VII of the Tariff Act, Section 232 of the Trade Expansion Act, and Section 201 of the Trade Act. The paragraph supplies no numerical preference or general exemption.
Paragraph 4 deals more precisely with the current problem. Its first sentence says paragraph 3's scheduled treatment must be applied consistently with Section 301. Its second sentence states that, in the forced-labor investigations, the United States intends to take all available information related to Jordan's implementation efforts into account when deciding what action, if any, to take.
That language gives implementation evidence a place in the U.S. decision. It stops short of requiring a 10 percent rate, an exclusion, or a reduction after a named milestone. Article 6.4 also preserves each party's authority to impose additional tariffs under domestic law.
U.S.-Jordan FTA origin rules control eligibility for paragraph 3's scheduled treatment. Paragraph 2's future-action commitment and any Section 301 measure must be read with the origin rules specified for the relevant action. Importers should not assume that FTA qualification resolves Section 301 exposure.
The signed deal supports Jordan's commitment-tier argument. Published customs measures could later show how that commitment operates at the border.
Article 2.9 separates the broad ban from entity recognition
Article 2.9 contains two operative forced-labor commitments. Jordan must establish, within five years after entry into force, a prohibition on goods mined, produced, or manufactured wholly or partly with forced or compulsory labor. The clock begins at entry into force.
A separate sentence requires Jordan to recognize U.S. government determinations concerning entities under Section 307 of the Tariff Act and presumptively prohibit imports of goods from those companies. This sentence carries no express five-year delay. Like the rest of the agreement, it remains inoperative before entry into force.
The difference creates an early administrative opportunity. A comprehensive regime would ordinarily need a legal definition, an enforcement authority, evidentiary and importer procedures, remediation rules, and public reporting. Entity recognition is more focused. Jordan can identify the U.S. determinations it accepts and tell customs officers what to do with goods connected to a covered company.
That process would reach only part of the problem USTR identified. A company-based rule may miss unlisted producers, a small forced-labor input elsewhere in a supply chain, or goods outside a named action. It can nevertheless show whether the first agreement commitment has reached the border.
Jordan's best near-term submission would separate work completed from work still underway. It could identify the legal authority, published list, covered products, responsible agency, and early customs outcomes. The five-year deadline would remain the measure for the wider prohibition.
The entity clause still needs an operating rule
Article 2.9 leaves the covered U.S. instruments undefined. The CBP Forced Labor Frequently Asked Questions explains that a Withhold Release Order rests on information that reasonably, but not conclusively, indicates covered merchandise was produced with forced labor. A Finding reflects CBP's determination that the merchandise was produced with forced labor. Both arise under Section 307, but their evidentiary postures differ.
The agreement refers to determinations on entities and goods from those companies. It does not specify whether Jordan will recognize every company-specific WRO and Finding, how it will treat a product or regional action, or whether existing and future determinations receive the same treatment. It refers to Section 307 rather than the separate UFLPA Entity List framework.
The word presumptively requires procedure as well. Jordan needs to say whether an importer can rebut the connection between a shipment and a named company, what evidence is sufficient, which official decides, and how a later U.S. modification enters the Jordanian system. Traders cannot plan around an unpublished practice.
CBP already maintains Jordan-specific enforcement on the U.S. side. The CBP June 23, 2026 WROs on Needle Craft and Casual Wear direct U.S. ports to detain covered garments made by those Jordanian factories. They are not examples of Article 2.9 implementation, which concerns Jordan's treatment of imports. Their existence shows why a Jordanian rule must define which U.S. actions count and what goods the resulting presumption covers.
A useful customs circular would name the enforcement authority, publish the covered determinations, explain updates and modifications, and state the product and affiliate scope. It would also set the rebuttal process and the disposition of detained goods. Each item would give traders an operating rule and USTR a reviewable fact.
Jordanian importers can begin screening suppliers against active company-specific U.S. actions and ask how modifications will be reflected. Jordanian exporters should keep FTA origin records separate from any Section 301 origin analysis. U.S. buyers should model 10 and 12.5 percent as scenarios and avoid booking either as the applicable rate.
Procurement teams should match the legal name and production site in a U.S. determination against vendor masters, invoices, and manufacturer declarations. A trade name or distributor match is only a lead. The Jordanian rule will need to explain how affiliates, renamed companies, and goods routed through an unrelated exporter are treated.
Compliance teams should preserve dated copies of any Jordanian entity list and the U.S. action it incorporates. A later modification may change a supplier's treatment without answering how Jordan handles goods already ordered or detained. Purchase terms, supplier certifications, and customs-broker instructions should identify which version governed the transaction and who bears the cost of a failed rebuttal.
USTR's eight indicators frame the evidence checklist
USTR's investigation report lists eight features associated with an effective forced-labor import prohibition: a definition grounded in international law, a designated enforcement authority, a public entity list, a rebuttable presumption, clear evidentiary standards, a remediation requirement, an accessible allegations mechanism, and public disclosure.
The report presents these as effectiveness indicators drawn from independent research. Article 2.9 does not incorporate them as terms of the agreement. Jordan would strengthen its implementation case by addressing them because they reveal what USTR examined when it assessed other economies.
The report also looks for outcomes. USTR reviewed denied entries, enforcement statistics, investigations of goods covered by U.S. actions, and the amount of public information available. It treated legal authority without visible use as weak evidence of effective enforcement.
Jordan's submission can mature in three steps. An official circular establishes authority and procedure. A maintained public list shows continued administration. Detentions, exclusions, releases, and successful rebuttals show how the rule operates. Publication dates and case counts would allow USTR and traders to distinguish an active measure from a paper commitment.
This sequence is an analytical inference from USTR's June methodology. Annex I names no mandatory checklist. The United States has stated only that it intends to consider all available information about implementation efforts.
The entry-into-force notification will establish when Article 2.9 becomes operative. Jordan's implementing measure will identify the Section 307 determinations covered, the start date, and the responsible authority. Customs data will reveal actual border treatment. USTR's operative Section 301 action will set the U.S. duty, coverage, exclusions, and effective date.
Jordan still has to build the comprehensive prohibition within five years after entry into force and supply the institutions needed to enforce it. Until USTR publishes its operative notice, companies should treat both proposed rates as scenarios and watch Jordan's entity rule and first customs decisions for evidence of border action.
Free account
Keep reading with a free account.
Today's analysis is open to everyone. A free account opens the full archive and full tool output. No card required.