Stable

SNAP-R Classification for India-Developed Software

Reis Renneker

Written by Reis Renneker

U.S. companies can request a CCATS for India-developed software. Learn how SNAP-R supports accurate ECCN and EAR analysis.

SNAP-R Classification for India-Developed Software

SNAP-R classification can give a U.S. company greater certainty when software is developed in India or another foreign jurisdiction. Development location does not prevent a company from requesting a commodity classification, particularly when U.S.-origin content, encryption functionality, or dual-use capabilities create questions under U.S. export controls.

Can Foreign-Origin Software Receive a CCATS?

Foreign Development Does Not Bar a Classification Request

A U.S. company may generally submit a commodity classification request through SNAP-R for software developed outside the United States. The resulting classification is commonly associated with a Commodity Classification Automated Tracking System, or CCATS, determination from the Bureau of Industry and Security.

There is no general requirement that the software must be manufactured, coded, compiled, or first released in the United States before a classification request can be submitted. India-developed software may therefore be evaluated through the same electronic process used for U.S.-developed software, provided that the submission contains enough technical and commercial information for a meaningful review.

The development location remains relevant, but it is not the only factor. A foreign-origin software product may incorporate U.S.-origin source code, object code, development tools, libraries, encryption components, or other controlled technology. Depending on the facts, those connections may affect whether the software is subject to the Export Administration Regulations, commonly called the EAR.

A CCATS Addresses Classification, Not Every Compliance Question

A commodity classification request can help determine the appropriate Export Control Classification Number, or ECCN, for a defined software product. In some foreign-origin scenarios, the request may also help clarify how U.S.-origin content affects the product's treatment under U.S. export controls.

However, a CCATS should not be treated as a universal approval for every transaction. It does not replace destination, end-user, end-use, sanctions, or denied party analysis. The determination applies to the product and technical facts presented in the submission. Materially different versions, features, or encryption capabilities may require additional review.

Determine EAR Scope Before Selecting an ECCN

Jurisdiction and Classification Are Separate Decisions

Export compliance teams should distinguish between determining whether software is subject to the EAR and determining its ECCN. These are related questions, but they are not interchangeable.

Foreign-origin software is not automatically outside U.S. export controls. Compliance teams typically examine the amount and type of controlled U.S.-origin content incorporated into the product. They may also need to consider whether foreign-produced software is derived from specified U.S. technology or software, or is produced by a qualifying foreign facility or equipment configuration.

This analysis can be particularly important when development is distributed across multiple offices. For example, an India engineering team might write most of the application while a U.S. office supplies encryption modules, proprietary libraries, technical specifications, or controlled development technology. The final product's origin label alone would not resolve its EAR status.

EAR99 Does Not Mean Outside the EAR

If software is subject to the EAR but is not described by a specific Commerce Control List entry, it may generally be designated EAR99. That designation is different from concluding that the software is not subject to the EAR.

EAR99 software may still require restrictions or authorization based on the destination, parties, or intended end use. Conversely, software classified under an ECCN may sometimes be eligible for export or reexport without a license, depending on the applicable reasons for control, destination, transaction structure, and available authorization.

A sound classification workflow therefore follows a deliberate sequence:

  1. Define the exact software product and version.
  2. Identify its development history and country connections.
  3. Map incorporated U.S.-origin code, technology, and components.
  4. Determine whether the software is subject to the EAR.
  5. Evaluate the relevant Commerce Control List categories.
  6. Document the ECCN or EAR99 conclusion.
  7. Apply transaction-level export controls before release or transfer.

This sequence reduces the risk of treating an ECCN as a substitute for a complete jurisdiction and authorization analysis.

Preparing a Strong SNAP-R Classification Submission

Define the Software's Technical Capabilities

The quality of a SNAP-R classification request depends heavily on the accuracy and completeness of its technical description. Broad labels such as business software, cloud platform, or security application rarely provide enough information. The submission should explain what the software does, who uses it, how it is delivered, and which functions could be relevant to the Commerce Control List.

For India-developed software, the company should identify which legal entity owns the product, which offices participated in development, and whether U.S.-origin code or technology is incorporated. The analysis should distinguish between source code, object code, software as a service, downloadable applications, firmware, application programming interfaces, and supporting technology when those distinctions affect classification.

Address Encryption Directly

Encryption is frequently one of the most important classification issues for modern software. A submission should typically describe:

  • The purpose of the encryption functionality
  • Encryption algorithms and key lengths
  • Whether encryption protects data confidentiality, authentication, digital signatures, or access credentials
  • Whether users can modify or activate cryptographic functions
  • Whether the software includes open-source or third-party encryption libraries
  • Whether encryption is ancillary to the software's primary purpose
  • How the software is distributed, updated, and administered

A classification request that minimizes or omits encryption functionality can produce an unreliable result. Engineering, cybersecurity, product, and trade compliance personnel should generally review the technical narrative together before submission.

Keep the Product Scope Precise

A CCATS determination is most useful when the submitted product scope is specific. The filing should identify the relevant product names, versions, modules, and configurations. If a product family contains materially different security or encryption capabilities, separate treatment may be appropriate.

SNAP-R remains the electronic channel for submitting commodity classification requests. Companies should maintain current account access, assign responsible users, and allow time for internal review before filing. Supporting materials should be consistent with the narrative entered in the system, especially where architecture diagrams, product literature, questionnaires, or encryption details are included.

Using a CCATS in an Export Compliance Program

Convert the Determination Into Operational Controls

Receiving an ECCN classification is not the end of the process. The determination should be integrated into product master data, order management, customer onboarding, screening, licensing, and release procedures. Relevant teams should be able to identify which software version the classification covers and which conditions still require review.

A practical classification record typically includes the product name, version, ECCN or EAR99 designation, EAR jurisdiction conclusion, CCATS reference, classification date, technical assumptions, encryption characteristics, and responsible compliance owner. The record should also identify facts that would trigger reassessment.

Transaction controls remain necessary because export authorization requirements typically depend on more than product classification. Destination, end user, ownership, intended use, delivery method, and access location can all matter. Providing software through a cloud environment may also create export control considerations when foreign users receive access to controlled software or technology.

Reassess After Material Product Changes

Software changes continuously. A classification that was accurate for one release may not remain accurate after new cryptographic features, network surveillance functions, information security capabilities, or controlled technical content are added.

Trade compliance teams should establish change-management triggers with engineering and product leadership. Review may be appropriate when the company:

  • Adds or strengthens encryption
  • Integrates a new U.S.-origin library or software development kit
  • Changes the product's primary function
  • Introduces advanced cybersecurity or monitoring capabilities
  • Moves development responsibilities between countries
  • Changes delivery from local installation to cloud access
  • Releases source code or development technology to new foreign personnel

The company should also retain the factual materials supporting its classification. Consistent records help demonstrate why the business reached its conclusion and whether later versions remain within the original CCATS scope.

Recent Developments
  • No regulatory changes, Federal Register notices, or BIS policy updates to SNAP-R procedures or CCATS classification requests were identified for October or November 2026. The electronic SNAP-R portal remains the mandatory method for submitting commodity classification requests.
  • US companies can continue to file SNAP-R classification requests (CCATS) for software of foreign origin, including items developed in India, to determine whether US-origin content makes the item subject to the EAR. This aligns with existing BIS rules that allow such requests without a US manufacturing requirement.
  • A November 2, 2026 industry article restated that software developers and technology firms should use SNAP-R CCATS filings when ECCN classification is unclear, particularly for encryption or dual-use software, regardless of development location.
  • No relevant practitioner discussions of SNAP-R classification for India-developed software appeared in recent X posts. Earlier 2026 reminders focused only on migrating legacy SNAP-R accounts to the current system to prevent filing delays.
1 2 3

Frequently Asked Questions

Can a U.S. Company Request a CCATS for Software Developed in India?

Yes. A U.S. company may generally submit a SNAP-R commodity classification request for India-developed software. Foreign development does not prevent classification. The submission should clearly explain the product's origin, technical capabilities, U.S.-origin content, encryption functions, and relationship to the requesting company.

Does Development in India Place Software Outside the EAR?

No. Development in India does not automatically place software outside the EAR. A company should evaluate incorporated U.S.-origin content and any other applicable U.S. jurisdictional connections. The analysis is fact-specific and should be completed before relying on the product's foreign origin.

Does a CCATS Authorize Every Export or Reexport?

No. A CCATS generally provides a classification determination for the product described in the request. It does not eliminate the need to evaluate destination restrictions, denied or restricted parties, prohibited end uses, licensing requirements, or the availability and conditions of an authorization.

What Information Is Most Important in a Software Filing?

The submission should provide a precise product description, development history, delivery model, intended users, technical functions, encryption details, and relevant U.S.-origin content. Product names, versions, modules, and configurations should be clearly defined. Engineering documentation and the compliance narrative should describe the same functionality.

How Stable Software Can Help

Connect Trade Compliance With Duty Recovery

Export classification and import duty recovery address different compliance obligations, but both depend on accurate data, documented procedures, and disciplined execution. Stable Software makes DrawbackAI, flat-license duty drawback software that U.S. customs brokers can white-label for importer clients and use to file claims under their own filer codes.

Stable Software charges a flat software license and never takes a percentage of the refund. This model allows customs brokers to maintain control over their client relationships and drawback filing operations without sharing a portion of recovered duties. Organizations evaluating how software can strengthen broader trade compliance and recovery processes can explore the duty drawback platform to determine whether it fits their operating model.

Resources

TypeResource
SourcePrimary source

✉️

Sign up for our newsletter

A monthly post on trade, tariffs, and customs, delivered straight to your inbox.