For import teams, that distinction controls the file. July 1 changed the review posture and the negotiating calendar. It did not change the entry instruction, the preference claim, the origin binder, or the liquidation calendar for goods already entered under USMCA.
Operating read
A withdrawal threat is not a broker instruction. Treat July 1 as a review record, keep Article 34.6 as the withdrawal watch, and wait for customs implementation text before changing entry treatment.
Article 34.7 says that if the parties do not confirm a new 16-year term at the six-year joint review, the Commission conducts annual joint reviews for the remainder of the current term. It also leaves room for the parties to confirm an extension later. That is review machinery, not the six-month exit clock.
Article 34.6 is written differently. A party may withdraw by providing written notice to the other parties, and withdrawal takes effect six months after notice. Written notice is therefore the customs-relevant treaty event to watch. Without it, the public July 1 record is leverage inside the review process, not the operative date for preference removal.
That split is useful even before any notice appears. Counsel can treat the July 1 record as a warning signal. Brokers need a different kind of record. A live claim change needs text that tells them which goods, which dates, and which treatment apply. Until then, the live file is the qualifying good, the origin record, and the entry posture.
Legal-procedural posture
The domestic review file is separate from the withdrawal file. 19 U.S.C. 4611 requires consultation before each joint review, a report before the six-year review, later reports before annual reviews if extension is not confirmed, and a briefing after the countries meet. That statute supports a congressional-review watch track. It does not itself tell CBP to deny a preference claim.
Section 4611 explains why congressional reporting and stakeholder consultation should be monitored after July 1. It does not collapse all USMCA actions into a single exit process. Later annual-review reports may show whether the United States is staying inside the review process or preparing a more aggressive posture. They still need to be matched to Article 34.6 notice or implementation text before they become entry-line instructions.
A written withdrawal notice would open the treaty timing file. As an operational matter, importers, brokers, and CBP personnel would still need a domestic implementation record that tells them how to treat covered goods at entry. The agreement text would supply the treaty notice and six-month timing frame. The implementation record would translate that timing into entry treatment, transition rules, and operational instructions.
If issued, a Federal Register notice, proclamation, HTSUS revision, Chapter 99 measure, CBP message, or USTR implementation statement would matter only to the extent it supplies covered goods, dates, tariff treatment, transition rules, verification treatment, or entry instructions. As of the July 1 statement, the confirmed public record is narrower. It identifies non-renewal in current form, continuing engagement, and continued force of the agreement.
Affected files
Start with the origin binder. USMCA Chapter 5 allows an importer to claim preferential tariff treatment based on a certification of origin and requires record support for the claim. That remains the ordinary evidence file while the agreement remains in force.
This is evidence control, not archive cleanup. If a later notice creates a date split, importers will need to know which claims were made before the trigger, which entries remain open, and which certifications support the claim. The origin binder becomes the record that lets a filer explain why a claim was valid when made, even if the policy environment later changes.
Keep an open-entry calendar beside it. Liquidation posture matters because 19 U.S.C. 1504 governs when entries liquidate or are deemed liquidated. Protest posture matters because 19 U.S.C. 1514 makes many customs decisions final unless a timely protest is filed. Post-importation refund posture should be tracked separately because 19 U.S.C. 1520(d) provides a one-year path for qualifying goods when no preference claim was made at importation.
If an Article 34.6 notice appears, filers should sort affected entries by entry date, liquidation posture, reconciliation posture, protest window, and any later preference-claim window. The reason is procedural rather than rhetorical. Entry posture determines which records can still be corrected, contested, refunded, or protected if the government later changes treatment.
That sorting should happen before the first implementation record arrives. A notice file can become crowded quickly, and a late spreadsheet will not show why a claim was made under one legal regime while a later entry falls under another. The clean file keeps entry date, summary status, liquidation status, protest posture, and source documents together.
Build the date split before the file becomes crowded. Track the entry date, any notice date, any effective date, and any implementation date in a tariff or CBP record. Those dates may not do the same legal work. A clean file lets the company explain which rule governed the claim, which entries remain procedurally open, and which records supported the treatment chosen at entry.
Keep the sourcing model separate from live entry instructions. A company can model a possible loss of preference now. It should keep that model separate from live entry instructions. The model should have a current-law line, a written-notice scenario, and an implementation-text scenario. Each line needs a different evidence threshold.
The sourcing model should also separate price exposure from customs authority. A purchasing team may need a landed-cost scenario for goods that lose preference. A broker instruction needs a legal trigger, a date rule, and a tariff treatment rule. The two workstreams can use the same watch file, but they should not use the same approval threshold.
This is not another general note on USMCA uncertainty. The useful read is narrower. The first review record separated review leverage from entry-operable withdrawal. USTR described a non-renewal decision under the joint-review process and still said the agreement remains in force. That sentence keeps the current preference file alive unless a later record supplies a different legal trigger.
In practice, the July 1 statement should not be routed straight to brokers as a treatment change. The file should ask which instrument moved. Article 34.7 moved the annual review docket. Article 34.6 would move the withdrawal clock. CBP or tariff-schedule text would move the entry instruction. Those are related files, but they are not the same file.
The same distinction helps inside the company. A commercial team can model a loss-of-preference scenario now. A customs team should not replace current USMCA claim instructions just because the renewal file is unsettled. The stronger compliance answer is a watch file that identifies the record that would actually let a filer change treatment.
What importers and filers should do
Keep current USMCA claim instructions in place unless the government issues entry-operable implementation text. The July 1 statement is a review event. It is not a customs message that rewrites the treatment of qualifying goods.
Build the watch file around written notice, effective date, HTSUS treatment, Chapter 99 treatment, CBP guidance, open entries, liquidation status, reconciliation status, and origin-document support. That list is not a prediction that each item will appear. It is a control list for separating negotiator statements from entry instructions.
Separate current claim authority from contingency planning. The current claim authority is the origin rule and the certification file. The contingency plan is the notice and implementation watch. The two files should speak to each other, but they should not be merged into one instruction until the government gives an entry-operable rule.
Keep a short decision log with the file. Record who owns the origin binder, who owns the open-entry calendar, who owns broker instructions, and who owns commercial scenarios. If a notice later appears, the company should not have to reconstruct those lanes from email.
Mark entries by timing and posture. Start with entries already liquidated, entries unliquidated, entries under reconciliation, entries that may need correction, and entries that may carry a post-importation preference claim. The same policy statement can have different consequences across those groups because the procedure available to each group is different.
Do not let a scenario memo become a standing broker instruction. The internal memo can say what the company would do if USMCA preference were unavailable. The broker instruction should say what the law and implementation record require today. If those two documents collapse into one message, the company risks changing live treatment before the government has supplied the operative rule.
Keep sourcing work in scenario mode until the file changes. The commercial model can include a no-preference scenario. It should also show the current-law baseline and the records needed to move from scenario to instruction. That makes the model useful without turning an untriggered withdrawal theory into an entry rule.
Legal and government-affairs teams should keep watching the Section 4611 file. A later annual-review report could show whether the United States is using the review process as leverage, preparing a withdrawal posture, or negotiating changes inside the existing agreement. That evidence matters for strategy. It does not replace the Article 34.6 notice requirement.
What to watch next
Watch first for an Article 34.6 written notice. That record would start the six-month withdrawal clock and move the file from review leverage to exit timing. It would also create a need to identify the notice date, the effective date, and the parties covered by the notice.
Watch next for implementation text. If issued, a Federal Register notice, proclamation, HTSUS revision, Chapter 99 measure, CBP message, or USTR implementation statement would matter only to the extent it supplies covered goods, operative dates, tariff treatment, transition rules, verification treatment, or entry instructions.
Keep open-entry treatment on the same page. The key questions would be entry date, liquidation posture, reconciliation posture, protest window, post-importation claim window, and any transition rule. A prospective change affects one set of entries. A transition rule or verification instruction affects another. A gap leaves importers in the ordinary customs procedure file.
Keep annual-review settlement on the watch list as well. Article 34.7 allows the parties to confirm extension later, so a written extension would narrow the withdrawal-risk file without needing an Article 34.6 event. That is why the review docket and the withdrawal docket need to stay separate. One can move without the other.
Origin-document treatment may become the practical question if transition guidance appears. If transition guidance appears, the practical question will be whether existing certificates, blanket certificates, importer claims, and post-importation claims remain usable for entries tied to earlier dates. That question belongs in the origin binder before it belongs in a commercial talking point.
The next official U.S.-Mexico review record also belongs in the file. A bilateral meeting can narrow the review file or make withdrawal pressure more credible. It cannot substitute for Article 34.6 written notice.
For now, model USMCA withdrawal from notice, effective date, and implementation text. Do not model it from rhetoric.
Caveats
The July 1 USTR statement is the operative public record for this analysis. It identifies non-renewal in current form and continued force of the agreement while the parties continue engagement.
Annual review is not collapse. Under Article 34.7, the parties can continue annual joint reviews and can still extend the agreement later by written confirmation. A failed renewal decision on July 1 therefore does not answer the final status of the agreement.
A withdrawal notice would create legal and implementation questions. Those questions matter, but they do not become an entry rule until the government gives filers operative instructions. Until then, the right customs posture is to preserve the origin file, map open entries, and keep the withdrawal watch tied to official records.
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.