Japan's Catch-All Export Control Amendments, Explained: The October 9, 2025 Overhaul and Its Impact on the Use, End-User, and Inform Requirements [2026 Update]

Hello, this is Hamamoto from TIMEWELL. "So what exactly changed with the catch-all amendments?" That has been the single most common question in the export control consultations I have joined over the past year. The overhaul of Japan's complementary export controls that took effect on October 9, 2025 was arguably the largest since the regime was introduced in 2002. Then, on February 14, 2026, a separate amendment to the Export Trade Control Order took effect on the neighboring list-control side. With amendments landing back to back, I also hear a more worrying version of the question: "We are no longer sure which point-in-time rules our internal screening flow is actually based on."

This article lays out the catch-all amendments in chronological order and explains how the three triggers, the use requirement, the end-user requirement, and the inform requirement, changed as a result, working from the legal texts and METI's official materials. If you first want the basics of how list controls and catch-all controls differ, start with the companion piece, List Controls vs. Catch-All Controls: The Key Differences, and this article will click into place much faster.

Before the main story, here is the mapping between common names and formal names, a frequent source of confusion in this field.

Common name	Formal name and status
Catch-all controls	Formally "complementary export controls" (hokanteki yushutsu kisei). A regime that complements list controls1
Objective requirements (sometimes called the "osore requirement")	The collective term for two checks: the use requirement and the end-user requirement1
Osore Ordinance	METI Ordinance No. 249 of 2001. The ministerial ordinance defining "risk" for WMD-related catch-all controls2
Inform requirement	The requirement triggered when the exporter receives a written notice (an inform notice) from the Minister of Economy, Trade and Industry stating that a license application should be filed1

The amendment timeline, 2024 through 2026

First, the sequence of events. This overhaul did not arrive out of nowhere; it was a two-year process.

Date	What happened
April 2024	An interim report by the Subcommittee on Security Export Control of the Industrial Structure Council recommended a review of complementary export controls3
January 31, 2025	Public comment period on the review opened4
April 4, 2025	Cabinet decision4
April 9, 2025	The relevant cabinet orders, ministerial ordinances, public notices, and circulars were promulgated3
October 9, 2025	The complementary export controls review took effect: the specified-items category (defined by HS codes), the extension of the conventional-weapons objective requirements, and the new inform requirement for Group A destinations3
November 14, 2025	The Cabinet Order Partially Amending the Export Trade Control Order (Cabinet Order No. 376 of 2025) was promulgated5
February 14, 2026	That cabinet order took effect, revising list-control items, including the addition of FPGA-equipped devices5

Please pay attention to the last two rows. The amendment effective February 14, 2026 is a revision of items on the list-control side (rows 1 through 15 of Appended Table 1 of the Export Order), centered on additions such as FPGA-equipped devices, not a change to the catch-all regime itself. But when the boundary of list controls moves, so does the entry point of the familiar sequence "not list-controlled, so proceed to the catch-all check." It is not unrelated to catch-all operations, which is why I included it in the timeline. The details are covered in a separate article, The Export Trade Control Order Amendment Effective February 2026.

So here is where things stand as of July 2026. The most recent amendment to the catch-all regime itself is the review that took effect on October 9, 2025, and the main battleground in practice has shifted to translating that amendment into internal screening workflows. If you are unsure whether your compliance setup has kept pace with the past two years of amendments, our free export-control readiness check is a quick way to take stock. It takes about three minutes.

The three changes in the amendment effective October 9, 2025

Now the substance. The October 9, 2025 review comes down to three changes.

The first is the creation of the specified-items category. Row-16 goods and technology, the domain of catch-all controls, were split into (1) specified items and (2) everything else¹. Specified items are those falling under the HS codes listed in Article 14-2 of the Goods and Technologies Ordinance within the following six groups¹.

Specified-item group	Typical territory
Machine tools	Metalworking machinery
Radar, radio navigation equipment, radio remote-control apparatus	Detection, communications, remote operation
Integrated circuits	Semiconductor chips
Aircraft and spacecraft and their components	Airframes, engines, drone components
Navigation instruments	Inertial navigation and related equipment
Inspection equipment	Measurement and inspection devices

Using HS codes, the commodity classification numbers used in trade statistics, to designate the items was the clever part of this amendment. The traditional catch-all net was the famously hard-to-grasp "essentially all of row 16," but for specified items the line is now drawn with HS codes that trade teams already use on customs paperwork, which makes it far easier to check mechanically whether your product is in scope. Think of specified items as dual-use goods where the concern of weapons diversion is especially high.

The second change is the extension of the objective requirements in the conventional-weapons catch-all. Previously, the objective requirements (the use and end-user requirements discussed below) applied in the conventional-weapons stream only to UN arms-embargoed destinations. After the amendment, for specified items only, the objective requirements apply even to general-country destinations. The basis is Article 4, Paragraph 1, Item 3, sub-items (c) and (d) of the Export Order¹⁶.

The third change is the new inform requirement for Group A (former White Country) destinations. Historically, the countries and regions in Appended Table 3 of the Export Order (Group A, 27 countries as of July 2026) were entirely exempt from catch-all controls. After the amendment, the inform requirement applies to Group A, limited to cases where there is a risk of diversion to countries of concern. Legally, this was implemented under Article 48, Paragraph 2 of the Foreign Exchange and Foreign Trade Act (FEFTA), through the newly established Article 1, Paragraph 3 and Article 4, Paragraph 2, Item 3 of the Export Order⁴⁷. I read this as a response to a loophole that has grown in recent years: diversion routed through friendly countries. The objective requirements still do not apply to Group A destinations⁴.

A quick refresher: catch-all controls are formally "complementary export controls"

Before going further, a short review of the foundation. Japan's export controls come in two broad streams. One is list controls: items listed in rows 1 through 15 of Appended Table 1 of the Export Trade Control Order (the Export Order), weapons, high-performance machine tools, and the like, where the regulation attaches to the item itself. The other is catch-all controls, formally complementary export controls, whose job, as the name says, is to complement list controls¹.

What falls in scope? Goods and technology classified under "row 16" of Appended Table 1 of the Export Order and the Appended Table of the Foreign Exchange Order. That covers nearly all goods and technology other than list-controlled items, excluding things like food and lumber. Concretely, it corresponds to items in Chapters 25 through 40, 54 through 59, 63, 68 through 93, and 95 of the Appended Table of the Customs Tariff Act¹. Put crudely, even something as ordinary as a pencil could require a license under the right conditions. The net is wide, hence "catch-all." The structure of Appended Table 1 is covered in How to Read Appended Table 1 of the Export Order.

So when is a license required? METI's framing gives two conditions. First, the case where the exporter comes to know of a "risk" that the goods will be used for the development, manufacture, use, or stockpiling of weapons of mass destruction and similar items, or for the development, manufacture, or use of conventional weapons. These are the objective requirements, which break down into two checks, the use requirement and the end-user requirement. Second, the case where the exporter receives a notice from the Minister of Economy, Trade and Industry stating that a license application should be filed. This is the inform requirement. If either one applies, the export or technology transfer requires a license from the Minister¹. A word on history: the WMD-related catch-all regime was introduced in April 2002, and the conventional-weapons regime followed in November 2008²⁸. From here, let us walk through the three requirements as they stand after the amendment.

The use requirement: checking what the goods will be used for

First, the use requirement. METI's definition is simple: a check "from the perspective of what use the goods will be put to"¹. The goods you are about to export, once they arrive, what will they be used for? Confirming that is the use requirement.

When you hear "the case where the exporter comes to know of a risk," you might imagine it turns on an export manager's hunch or mood. It does not. The legal definition is quite concrete. The Osore Ordinance, which defines the use requirement for the WMD stream, says in its first item: the case where a contract for the export of the goods, or a document, drawing, or electromagnetic record obtained by the exporter, states or records that the goods will be used for the development or similar activities of nuclear weapons and related items, or where the exporter receives a communication to that effect from the importer, the end user, or their agent (the statute calls these parties "the importer, etc.")². In other words, the trigger points are objective clues: contracts, emails, specification sheets, or a communication from your counterparty. That is exactly why these are called objective requirements. The dividing line is not "this feels off somehow." It is whether the information in your hands contains a statement that reads as use for the development of nuclear weapons and related items.

Two terms deserve a footnote here. First, "nuclear weapons and related items," also referred to as "weapons of mass destruction and similar items." Under the statutes and METI's materials, this means nuclear weapons, military chemical agents, military biological agents, devices for dispersing them, and rockets or unmanned aerial vehicles with a range of 300 km or more, including their components⁶. The fact that missiles and drones are on this list often surprises first-time readers. Second, "development and similar activities." This is shorthand for four activities: development, manufacture, use, and stockpiling⁶. Not just building the weapon; merely storing it counts.

What does this look like on the ground? Say a specification sheet arrives from an overseas customer, and the stated end use involves a process related to uranium enrichment. Or in a deal running through a trading house, the counterparty's contact mentions in an email that the end user is a military missile development unit. The moment that information lands in your hands, the license question opens up, even if the goods themselves are nowhere on the control lists. That is how the use requirement bites.

The end-user requirement: checking who will use the goods

Second, the end-user requirement. METI's definition: a check "from the perspective of what kind of end user will use them"¹. Where the use requirement looks at how the goods will be used, the end-user requirement looks at who is doing the using.

The legal definition sits in the second and third items of the Osore Ordinance. It covers the case where a contract, or documents specified by public notice of the Minister of Economy, Trade and Industry, states or records that the end user "will engage in" the development or similar activities of nuclear weapons and related items (item 2), or "has engaged in" them (item 3), or where the exporter receives a communication to that effect from the importer, etc.². The point people miss is that both future conduct and past conduct are covered. An organization that was involved in nuclear development in the past remains a red flag even if the current transaction carries a different label.

The end-user requirement does come with a carve-out, though. Borrowing the statute's own phrasing, a license application is not required "when it is clearly evident, from the use of the goods and the terms and manner of the transaction, that the goods will be used for purposes other than the development or similar activities of nuclear weapons and related items"². Even in a transaction with an end user of concern, if the specific goods and the deal terms make it clearly evident that no weapons development is involved, no license is demanded. The standard for judging what counts as "clearly evident" is set out in what practitioners call the "Clearly Evident" Guideline. Its formal title is the "Guideline for Exporters, etc. to Determine When It Is 'Clearly Evident,'" and it is positioned as an annex to the circular on complementary controls⁹. The October 2025 amendment moved the conventional-weapons catch-all onto the same guideline used for the WMD stream and added illustrative examples to aid judgment⁴. I go through the guideline's checkpoints in a dedicated article, The "Clearly Evident" Guideline, Explained, but if you use this in practice, always check the latest version of the original text as published by METI⁹.

The workhorse tool for end-user checks is the Foreign End User List. METI describes it as a reference resource for exporters, provided to improve the effectiveness of catch-all controls, listing entities located in foreign countries and regions for which concerns about involvement in the development of WMD or conventional weapons have not been dispelled¹. In an end-user check, you confirm not only whether the counterparty will engage (or has engaged) in the development of WMD or conventional weapons, but also whether it appears on this list. Alongside the October 2025 amendment, a conventional-weapons version of the Foreign End User List was also introduced⁴. For the practical mechanics of screening counterparties, see The Basics of End-User Screening.

The inform requirement: a written notice from the Minister

The third condition, the inform requirement, has a completely different character from the first two. With the use and end-user requirements, the exporter does the checking and the exporter does the noticing. The inform requirement fires from the government's side.

The mechanism works like this. When METI judges that certain goods or technology risk being used for the development of WMD or conventional weapons, the Minister of Economy, Trade and Industry notifies the exporter in writing that a license application should be filed. This is the inform notice. Once notified, the exporter cannot export the goods or provide the technology without obtaining a license. And a license is granted only when the concern has been dispelled¹.

Why does this mechanism need to exist? Because the government holds information that individual companies simply cannot see. Your contract file can be spotless, and the government may still know, through diplomatic channels or intelligence, that this particular counterparty is a problem. If the objective requirements are a net that catches what enters the exporter's field of vision, the inform requirement is a net that catches what enters the government's. Layer the two nets and you catch transactions that would slip through either one alone. As institutional design goes, I think it is rather well built. And once you see it this way, it also becomes clear why the October 2025 amendment extended only the government-side net to Group A destinations: rather than imposing the exporter's own "risk" checks on transactions with friendly countries, the design casts the net case by case, only when the government itself has picked up a diversion concern.

One practical note. The rules state explicitly that an inform notice is delivered "in writing"¹. The flip side: if you have received no notice and your own checks conclude that no license application is needed, you may export on your own judgment. But as I will come back to below, you need to keep records of how you reached that conclusion.

The post-amendment matrix: destination and item

With the three requirements on the table, here is the post-amendment application matrix on one page. Destinations fall into three groups: the countries and regions in Appended Table 3 of the Export Order (Group A, the so-called former White Countries, including the US, UK, Germany, France, and South Korea; 27 countries as of July 2026); the UN arms-embargoed countries and regions (Appended Table 3-2: Afghanistan, the Central African Republic, the Democratic Republic of the Congo, Iraq, Lebanon, Libya, North Korea, Somalia, South Sudan, and Sudan, 10 countries and regions); and general countries, meaning everywhere else⁶.

Destination and item	WMD catch-all	Conventional-weapons catch-all
Group A (Appended Table 3; 27 countries as of July 2026)	Inform requirement only, limited to cases with a risk of diversion (new as of October 2025)4	Likewise, inform requirement only4
General countries, specified items (row 16, category (1))	Objective requirements + inform requirement1	Objective requirements + inform requirement (objective requirements added by the October 2025 amendment)16
General countries, non-specified items (row 16, category (2))	Objective requirements + inform requirement1	Inform requirement only6
UN arms-embargoed countries and regions (Appended Table 3-2; 10 countries and regions)	Objective requirements + inform requirement1	Objective requirements + inform requirement6

Honestly, applying this matrix to day-to-day transactions by hand, every day, is grinding work. Destination category, item category (including the HS-code check for specified items), WMD versus conventional weapons, plus regulatory amendments in every jurisdiction you touch. The variables are many, and they keep moving. Our export control AI agent TRAFEED was built precisely for this problem of too many moving variables: it reflects amendments to each country's regulations on the day they take effect and visualizes the risk level of a transaction in five seconds. Its AI-based screening accuracy has been verified at over 95% in a joint study with Okayama University (our own research), it holds Japanese Patent No. 7862062, and it is in use at more than 20 organizations. That said, the final classification decision belongs to your company's export control officer. AI assembles the material for a judgment and gives you back your time. It does not take the responsibility off your shoulders.

What the amendment means for your internal compliance program (CP)

Once you understand the amendment, the next job is folding it into your internal compliance program (CP). In my view, four areas need review.

First, adding the specified-items check to your classification flow. The traditional flow was two steps: list-control classification, and if non-controlled, the catch-all check. After the amendment, one more branch appears at the entrance of the catch-all check: does this item fall under the HS codes for specified items? If it does, the objective requirements of the conventional-weapons catch-all must be checked even for general-country destinations. A CP whose flowchart lacks this branch is still running on the pre-amendment rules.

Second, the treatment of Group A transactions. The objective requirements still do not apply, so there is no need to impose new use and end-user checks on Group A shipments. But because an inform notice can now arrive for Group A destinations too, your notice-receipt flow, who receives it, how shipments are held, and who decides on the license application, needs to be rewritten so that it covers all transactions, Group A included.

Third, replacing the forms. METI has published new versions of the "Catch-All Controls Procedure Flowchart" and the "Objective Requirements Confirmation Sheet" reflecting the rules in force since October 9, 2025³. If your company is still recycling the old sheet, replace it now. While you are at it, add the conventional-weapons version of the Foreign End User List to the references consulted in end-user checks⁴.

Fourth, record retention. If your check concludes that no license application is needed, you may export on your own judgment as long as you have not received an inform notice, but you are expected to retain records of how you reached that conclusion, in line with your internal compliance program¹. If the authorities ask you to explain the decision a few years down the road and there is no paper trail, "we checked properly" will not hold. The new post-amendment checkpoints, specified-item applicability and the results of conventional-weapons objective-requirement checks, should be added to what you retain. License applications go to METI's Security Export Licensing Division¹. And for tracking regulatory changes, the commentary published by CISTEC (the Center for Information on Security Trade Control), the industry body in this space, is a reliable companion¹⁰.

One aside. In the export control consultations I sit in on, the companies that get tripped up by catch-all controls usually do not lack knowledge of the system. What they have is the belief that it does not apply to them: "we don't handle list-controlled items, so we're fine." If you have read this far, you already know the flaw in that reasoning. The catch-all net covers row 16, which is to say nearly every good and technology there is. Companies to which it does not apply are the minority.

Summary: the amendment in five lines

Let me pull the threads together.

• The most recent amendment to catch-all controls (formally complementary export controls) took effect on October 9, 2025, following the January 2025 public comment period and the April 9, 2025 promulgation
• The amendment has three pillars: the new specified-items category (six groups, designated by HS codes), the extension of the conventional-weapons objective requirements to specified items bound for general countries, and the new inform requirement for Group A destinations
• The triggers remain the objective requirements (use requirement plus end-user requirement), which fire on the exporter's own checks, and the inform requirement, which fires on a written notice from the government; meeting either one means a license application is required
• On February 14, 2026, a separate amendment to the Export Trade Control Order (Cabinet Order No. 376 of 2025) took effect; it revises list-control items, but because it moves the entry point of classification, it affects catch-all operations too
• The CP checklist is fourfold: add the specified-items check, build the inform-notice response flow, replace the forms with the new versions, and extend record retention to the new checkpoints

For the fine print of the statutes and the latest public notices and circulars, always go back to the primary sources from METI and e-Gov cited in the footnotes below¹¹. The rules move. This article, too, is nothing more than a snapshot as of July 2026. If you would like to work through which post-amendment requirements your own transactions touch, book a consultation. TRAFEED materials are available from our resource library. The day you can explain these amendments in your own words is the day export control stops being a scary regulation and becomes a tool you know how to use. I would like to help shorten the road to that day.

References

Footnotes

1. Complementary Export Controls (Catch-All Controls) — Ministry of Economy, Trade and Industry — last updated December 23, 2025 (accessed July 2026) ↩ ↩² ↩³ ↩⁴ ↩⁵ ↩⁶ ↩⁷ ↩⁸ ↩⁹ ↩¹⁰ ↩¹¹ ↩¹² ↩¹³ ↩¹⁴ ↩¹⁵ ↩¹⁶ ↩¹⁷ ↩¹⁸ ↩¹⁹ ↩²⁰

2. Ministerial Ordinance Specifying Cases Where Exported Goods Risk Being Used for the Development, etc. of Nuclear Weapons, etc. (METI Ordinance No. 249 of 2001) — e-Gov Statute Search — version reflecting the amendment effective October 9, 2025 ↩ ↩² ↩³ ↩⁴ ↩⁵

3. On the Review of Complementary Export Controls (Effective October 9, 2025) — Ministry of Economy, Trade and Industry — last updated April 15, 2026 (accessed July 15, 2026) ↩ ↩² ↩³ ↩⁴

4. On the Promulgation of Cabinet and Ministerial Orders Concerning the Review of Complementary Export Controls and the Results of the Public Comment Process — CISTEC (Center for Information on Security Trade Control) — May 2, 2025 ↩ ↩² ↩³ ↩⁴ ↩⁵ ↩⁶ ↩⁷ ↩⁸ ↩⁹

5. Cabinet Decision on the Cabinet Order Partially Amending the Export Trade Control Order — METI press release — November 11, 2025 (promulgated November 14, 2025; effective February 14, 2026) ↩ ↩²

6. Export Trade Control Order (Cabinet Order No. 378 of 1949) — e-Gov Statute Search — accessed July 2026 ↩ ↩² ↩³ ↩⁴ ↩⁵ ↩⁶ ↩⁷

7. Foreign Exchange and Foreign Trade Act (Act No. 228 of 1949) — e-Gov Statute Search — accessed July 2026 ↩

8. Ministerial Ordinance Specifying Cases Where Exported Goods Risk Being Used for the Development, Manufacture or Use of Goods Listed in Row 1 of Appended Table 1 of the Export Trade Control Order (Excluding Those Falling Under Nuclear Weapons, etc.) (METI Ordinance No. 57 of 2008) — e-Gov Statute Search — version reflecting the amendment effective October 9, 2025 ↩

9. Guideline for Exporters, etc. to Determine When It Is "Clearly Evident" — Ministry of Economy, Trade and Industry — accessed July 2026 ↩ ↩²

10. CISTEC — Center for Information on Security Trade Control — accessed July 2026 ↩

11. Security Export Control (Top Page) — Ministry of Economy, Trade and Industry — accessed July 2026 ↩