There’s a comfortable assumption inside a lot of software companies that tariffs are somebody else’s problem. You sell licenses, subscriptions, downloads. Nothing crosses a border in a container, so nothing gets classified, and nothing gets a duty. It’s a tidy story, and in 2026 it’s leaking in more places than most tech teams realize.
The core of the confusion is that “software” almost never travels as pure software anymore. It ships inside things. It arrives on media. It rides along with hardware you’re bundling, prototyping, or importing for your own operations. The moment a physical good is involved, classification is back on the table, and with it the whole tariff apparatus you thought didn’t apply.
Pure digital delivery is the narrow case
Electronically transmitted software, the download or the cloud subscription with no physical carrier, genuinely sits outside the tariff system in most markets. There’s a long-standing posture in international trade toward not imposing customs duties on electronic transmissions, and that’s the part of the story tech companies remember correctly.
The problem is treating that narrow case as the whole picture. As soon as your software has a body, a disc, a pre-loaded drive, a dongle, a shipped appliance, customs sees a good with an HTS classification and a duty rate. The intellectual property might be the valuable part to you. To CBP, there’s a tangible article moving across the border, and it needs a code.
Where the tariff sneaks back in
The exposure hides in the operational corners of a software business more than in the product itself. You tend to find it in places like these:
- Development hardware, servers, and test devices imported for your own engineering teams.
- Physical products that bundle firmware or embedded software with a device.
- Media and packaging carrying pre-loaded applications.
- Hardware appliances you resell with your software layered on top.
- Sample units and prototypes coming from contract manufacturers abroad.
Each of these gets classified as goods, and depending on origin and material, each can pick up the same trade-remedy and national-security duties that hit any electronics importer. A server built around covered components can carry a duty stack that has nothing to do with the code running on it.
The part that stings is that these imports rarely go through a trade-compliance review, because nobody in a software company thinks of a rack of test servers as a customs event. It gets ordered like office furniture, sits with facilities or IT, and clears without anyone asking what it’s classified as or where it was made. The exposure is real and recurring, and it’s invisible until an audit or a broker’s question surfaces it.
Valuation is where it gets genuinely tricky
Even when you accept there’s a physical good, the harder question is what value the duty applies to. When software and hardware ship together, how much of the transaction value is the tangible good versus the license? Customs valuation rules have a lot to say about this, and getting it wrong in either direction creates risk.
Undervalue the hardware to shrink the duty and you’re exposed on valuation. Lump everything together and you may be paying duty on intellectual property that didn’t need to bear it. The right treatment depends on how the deal is structured, how the invoice is written, and how the goods are described. Keeping your classifications and valuation logic in one place with a duty and tariff management platform is worth more here than it looks, because the software-plus-hardware case is exactly where undocumented judgment calls pile up.
Embedded software and the classification fork
Firmware raises a related question that trips up hardware-adjacent software teams. When software is embedded in a device, the device usually classifies as the device, and the software rides along inside that code. That sounds simple until you’re dealing with a product whose entire function depends on the software layer, where the line between “device with firmware” and “software delivered on hardware” starts to blur.
Getting that fork right matters because it decides which chapter, which rate, and which trade actions attach. You want a defensible rationale on file for why a product classifies the way it does, especially as your hardware footprint grows. Running your product catalog through global trade compliance software early, before volumes scale, keeps you from discovering a systematic misclassification across thousands of units after the fact.
Treat it as a live exposure, not a settled fact
The takeaway for a tech company isn’t that everything you ship is dutiable. It’s that “software is tariff-free” is a rule of thumb that only holds for the narrowest slice of what you actually move across borders. The subscription is clean. The appliance, the dev kit, the bundled hardware, and the pre-loaded media are not, and they follow the same rules as any other import.
You’re better off mapping your physical footprint once and knowing exactly where the duties land than assuming your business model exempts you. The mapping exercise takes a day or two and tends to surface a handful of recurring imports nobody was tracking. Once you’ve named them, they stop being surprises. The companies that get caught tend to be the ones who forgot how much hardware quietly moves in and out of a modern software operation.
