Hello, this is Hamamoto from TIMEWELL. There is one question I hear more than any other from people who are just starting out in export control. "With catch-all controls, when exactly do I need a license?" With list controls, you can look up whether an item falls under the appended tables and get a clear answer. Catch-all controls are different. The trigger is written into the law using the word "risk" (osore, おそれ) — a slippery term if there ever was one. This is where most newcomers stall.
It looks slippery, but the triggers boil down to three terms. The use requirement (yōto yōken, 用途要件), the end-user requirement (juyōsha yōken, 需要者要件), and the inform requirement (infōmu yōken, インフォーム要件). The first two together are called the objective requirements (kyakkan yōken, 客観要件), and if a transaction meets either the objective requirements or the inform requirement, a license application to the Minister of Economy, Trade and Industry is required[^1]. In this article, I want to untangle these three conditions using the actual legal text and METI's official materials.
Before we start, one source of confusion in this field is the gap between common names and formal names. Let me lay out the mapping up front.
| Common name | Formal name and status |
|---|---|
| Catch-all controls | Formally "complementary export controls" (hokanteki yushutsu kisei, 補完的輸出規制). A regime that complements list controls[^1] |
| Objective requirements (sometimes called the "osore requirement") | The collective term for two checks: the use requirement and the end-user requirement[^1] |
| Osore Ordinance | METI Ordinance No. 249 of 2001. The ministerial ordinance defining "risk" for WMD-related catch-all controls[^2] |
| 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 filed[^1] |
A quick refresher: catch-all controls are formally "complementary export controls"
First, 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 our subject today, catch-all controls. Their formal name is complementary export controls, and as the name says, their job is to complement list controls[^1].
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[^1]. Put crudely, even something as ordinary as a pencil could require a license under the right conditions. The net is wide — hence "catch-all."
So what are those conditions? METI's framing gives two. First, even for goods or technology outside the control lists, the case where the exporter comes to know of a "risk" that they 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. 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[^1]. Why does the title of this article say three conditions? Because the objective requirements break down into two separate checks — the use requirement and the end-user requirement. Two plus one makes three. That is the whole arithmetic.
A word on history. The WMD-related catch-all regime was introduced in April 2002, and the conventional-weapons regime followed in November 2008[^2][^3]. The system has been running for more than twenty years, but as we will see below, it went through a major overhaul in October 2025. If you want the bigger picture first, I have covered the relationship between the two streams in List Controls vs. Catch-All Controls and the structure of Appended Table 1 in How to Read Appended Table 1 of the Export Order. And if what you really want to know is whether your own compliance setup can handle these checks, we offer a free export-control readiness check.
Replace siloed classification work with AI.
METI's FY2024 data shows 52% of foreign exchange law violations stem from classification errors. TRAFEED cuts determination time by ~70% and stores structured rationale for every decision.
The use requirement: checking what the goods will be used for
Now for the three conditions, one at a time. First, the use requirement. METI's definition is simple: a check "from the perspective of what use the goods will be put to"[^1]. 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.")[^2]. 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" (kaku heiki tō, 核兵器等). 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[^4]. The fact that missiles and drones are on this list often surprises first-time readers. Second, "development and similar activities" (kaihatsu tō, 開発等). This is shorthand for four activities: development, manufacture, use, and stockpiling[^4]. 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"[^1]. 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.[^2]. 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"[^2]. 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 (akiraka gaidorain, 明らかガイドライン). 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[^7]. In its responses to public comments, METI explained that this guideline is something exporters consult — on the premise that the end-user requirement applies — when determining whether, in the transaction at hand, it is clearly evident that the goods will be used for purposes other than the development of conventional weapons, and noted that the Red Flags under the US Export Administration Regulations (EAR) contain a similar provision[^6]. 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[^6]. I will deliberately not reproduce the specific checklist items here. The original text is the only text that matters, so if you use this in practice, always check the latest version of the guideline as published by METI[^7].
The workhorse tool for end-user checks is the Foreign End User List (gaikoku yūzā risuto, 外国ユーザーリスト). 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[^1]. 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[^6]. 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[^1].
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.
One practical note. The rules state explicitly that an inform notice is delivered "in writing"[^1]. 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 three conditions apply differently for WMD and for conventional weapons
So far, so good — the contents of the three conditions are on the table. But practice has one more layer of complication in store. Catch-all controls run in two streams, one for WMD (introduced in 2002) and one for conventional weapons (introduced in 2008), and which requirements apply depends on both the destination and the item. On top of that, the amendment that took effect on October 9, 2025 redrew this map substantially[^5].
The timeline of the amendment first. In April 2024, an interim report by the Subcommittee on Security Export Control of the Industrial Structure Council recommended a review of complementary export controls. Public comments opened on January 31, 2025; the Cabinet decision came on April 4 of the same year; the relevant cabinet orders, ministerial ordinances, public notices, and circulars were promulgated on April 9; and everything took effect on October 9[^5][^6]. Under this amendment, row-16 items were split into two categories: (1) specified items and (2) everything else[^1]. Specified items are machine tools, radar, radio navigation equipment and radio remote-control apparatus, integrated circuits, aircraft and spacecraft and their components, navigation instruments, and inspection equipment — those falling under the HS codes in Article 14-2 of the Goods and Technologies Ordinance[^1]. Think of them as dual-use items where the concern of weapons diversion is especially high.
Here is the post-amendment matrix. 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[^4].
| 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)[^6] | Likewise, inform requirement only[^6] |
| General countries, specified items (row 16, category (1)) | Objective requirements + inform requirement[^1] | Objective requirements + inform requirement (objective requirements added by the October 2025 amendment)[^1][^4] |
| General countries, non-specified items (row 16, category (2)) | Objective requirements + inform requirement[^1] | Inform requirement only[^4] |
| UN arms-embargoed countries and regions (Appended Table 3-2; 10 countries and regions) | Objective requirements + inform requirement[^1] | Objective requirements + inform requirement[^4] |
Two changes in this table deserve your attention. One is that the inform requirement now reaches Group A destinations for the first time. Previously, Group A countries were entirely exempt from catch-all controls, on the logic that they maintain trustworthy export control systems of their own. 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[^6][^8]. The objective requirements still do not apply to Group A destinations[^6]. I read this as a response to a loophole that has grown in recent years: diversion routed through friendly countries. The other change is that for specified items, the objective requirements of the conventional-weapons catch-all now apply even to general countries. The basis is Article 4, Paragraph 1, Item 3, sub-items (c) and (d) of the Export Order[^1][^4].
Honestly, applying this matrix to day-to-day transactions by hand, every day, is grinding work. Destination category, item category, 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 to actually check in practice
Finally, the part you can use tomorrow morning. To determine whether a license application is needed, use the "Catch-All Controls Procedure Flowchart" and the "Objective Requirements Confirmation Sheet" published by METI. New versions reflecting the rules in force since October 9, 2025 are out, so if your company is still recycling the old sheet, replace it now[^1]. 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[^1]. 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. License applications go to METI's Security Export Licensing Division[^1]. 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[^10].
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.
Let me pull the threads together.
- The formal name of catch-all controls is complementary export controls. Nearly all goods and technology outside the control lists (row 16) fall in scope
- The triggers are 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
- The use requirement asks what the goods will be used for; the end-user requirement asks who will use them. The trigger points are objective clues: documents such as contracts, or communications from the importer and related parties
- The end-user requirement carries a "clearly evident" carve-out, with the judgment standard set out in the "Clearly Evident" Guideline. End-user checks also involve consulting the Foreign End User List
- The amendment effective October 9, 2025 created the specified-items category, extended the conventional-weapons objective requirements to general countries, and introduced the inform requirement for Group A destinations
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[^9]. The rules move. This article, too, is nothing more than a snapshot as of July 2026. If you would like to work through which requirements your own transactions touch, Book a consultation and we will sort it out together. The day you can explain these three conditions 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
[^1]: Complementary Export Controls (Catch-All Controls) — Ministry of Economy, Trade and Industry — last updated December 23, 2025 (accessed July 7, 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 (retrieved July 7, 2026) [^3]: 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 (retrieved July 7, 2026) [^4]: Export Trade Control Order (Cabinet Order No. 378 of 1949) — e-Gov Statute Search — retrieved July 7, 2026 [^5]: On the Review of Complementary Export Controls (Effective October 9, 2025) — Ministry of Economy, Trade and Industry — last updated April 15, 2026 [^6]: 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 [^7]: Guideline for Exporters, etc. to Determine When It Is "Clearly Evident" — Ministry of Economy, Trade and Industry — accessed July 7, 2026 [^8]: Foreign Exchange and Foreign Trade Act (Act No. 228 of 1949) — e-Gov Statute Search — retrieved July 7, 2026 [^9]: Security Export Control (Top Page) — Ministry of Economy, Trade and Industry — accessed July 7, 2026 [^10]: CISTEC — Center for Information on Security Trade Control — accessed July 7, 2026
![Use Requirement, End-User Requirement, Inform Requirement — The Three Triggers of Japan's Catch-All Export Controls, Explained for Beginners [2026 Edition]](/images/columns/catchall-three-requirements-guide/cover.png)