Most delays and unexpected costs in cross-border IT hardware shipments trace back to the same handful of mistakes. We see them repeated by companies shipping networking, telecom, security, broadcasting, and medical hardware into a new market for the first time, and occasionally by companies that have shipped for years but never revisited their process. None of these mistakes are exotic; they are decisions made early, often before a shipment is even booked, that turn into customs holds, storage fees, or compliance headaches weeks later. As an IOR/EOR and freight-forwarding partner working with IT, telecom, security, broadcasting, and pharma/medical hardware shipments across the Middle East, EU/UK/Scandinavia, Asia, LATAM, and North America, we see the same five mistakes surface again and again. Here they are, along with what actually fixes each one.
Networking, telecom, security, and broadcasting equipment move through customs under different rules than general cargo, and a forwarder used to apparel, furniture, or consumer goods has no built-in reason to know what those rules are.
Furniture, apparel, and most consumer goods clear customs against fairly generic classification and documentation rules. IT and telecom hardware often does not. Devices that transmit or receive radio signals, from Wi-Fi access points to base station equipment, typically require type approval or equipment authorization from the destination country’s telecom regulator before they can legally be marketed or imported. In the United States, that means FCC equipment authorization under Part 2 of the FCC’s rules; in the EU, it means CE marking under the Radio Equipment Directive; in the UAE, the Telecommunications and Digital Government Regulatory Authority maintains its own registration process for networking and telecom gear. Encryption-capable security equipment can trigger a separate layer of import controls in some jurisdictions, and pharma and medical hardware often carries device-registration requirements on top of standard customs entry.
A common failure pattern looks like this: a networking equipment manufacturer books its shipment through the same domestic freight forwarder it uses for office supplies. The forwarder classifies the shipment, books the freight, and treats it like any other pallet of boxes, because nothing in its process flags that the boxes contain radio-emitting devices. The shipment lands, customs asks for a type-approval certificate or import permit that was never on anyone’s radar, and the cargo sits in a bonded area accruing storage charges while someone scrambles to figure out what was missing. The equipment was never the problem; the forwarder simply had no reason to ask the question, because most of its shipments never touch this category at all. This is precisely the gap category specialists exist to close. See our detailed breakdown of UAE-specific IOR requirements and common delays for one market where this shows up constantly.
Type approvals, radio certifications, and import permits can take longer to obtain than the shipping leg itself. Booking freight before confirming these requirements is one of the most reliable ways to end up with a shipment sitting at a border, fully paid for and going nowhere.
Regulatory approval timelines vary widely by country and product category, and they rarely align with a shipping quote. ANATEL homologation for networking equipment entering Brazil, CST licensing and SASO conformity requirements for telecom gear entering Saudi Arabia, and FCC equipment authorization for RF devices entering the United States can each take anywhere from a few weeks to a few months, depending on the product and how complete the technical documentation is. A freight quote, by contrast, is usually built around transit time alone. When a company books freight on that timeline without separately confirming certification status, the two clocks run independently, and the certification clock is almost always the slower one.
We have seen this play out with security camera systems booked for airfreight on a tight installation deadline, where the cargo landed days before the required import permit was even submitted for review. The equipment sat in a bonded warehouse accruing storage fees for weeks while the paperwork caught up retroactively, and in some jurisdictions retroactive approval is not even an option; the regulator requires the certificate to predate the shipment, which meant re-exporting and re-importing once compliant. The fix is procedural, not technical: confirm certification, licensing, and import-permit requirements for the specific product and destination before freight is booked, not after the cargo has left the warehouse.
DDP, DAP, and DDU determine who is legally responsible for customs clearance and duty payment, not just who reimburses whom later. Getting this wrong changes who is on the hook if a shipment is held at the border.
Incoterms are defined and published by the International Chamber of Commerce, the organization that owns and periodically updates the Incoterms rules (most recently in the Incoterms 2020 edition). Under DDP, the seller (directly, or through a partner acting as Importer of Record) is responsible for export, freight, import duties, customs clearance, and final delivery; the buyer receives fully cleared goods. Under DAP, the seller manages export and freight, but the buyer takes on import customs and duty payment once the shipment arrives. DDU is functionally the same as DAP from a responsibility standpoint, though it was formally retired as a named Incoterm in the 2010 revision; it still shows up in older contracts and some regional trade documents out of habit.
These are not interchangeable ways of describing the same deal. On paper, the difference between DDP and DAP looks like a line item about who writes the check for duties. In practice, it determines who is legally named on the customs declaration and who is exposed if the shipment is inspected or held. A seller who quotes DDP without an actual mechanism to clear customs at destination, whether that is their own entity or a contracted IOR, has made a promise they cannot keep. A buyer who accepts DAP without understanding that they now own the clearance process can be blindsided by a duty assessment or a hold they were not expecting.
We go deeper on the practical mechanics of each term, including how the choice affects delivery timelines and dispute exposure, in our DDP vs. DAP vs. DDU comparison. And because the Incoterm you choose directly affects how landed cost is calculated, it is worth reading alongside our companion piece on how import duties and VAT are calculated for IT hardware shipments before you quote a customer on either term.
If neither party in the transaction has a locally registered legal entity at the destination, someone still has to be named as Importer of Record on the customs declaration. Shipping without confirming this in advance is how fully compliant equipment ends up legally undeliverable on arrival.
An Importer of Record is the person or legal entity that takes on formal responsibility for a shipment’s customs clearance, permits, licenses, and duty payment in the destination country. Many countries require the importer to have a local legal presence or a designated local representative; a foreign seller and a foreign buyer, even with a signed contract between them, do not automatically satisfy that requirement. We cover this in detail in our explainer on what an Importer of Record actually does and why it matters.
This gap shows up most often in exactly the deal structure that seems safest on paper: a manufacturer signs with a new distributor in a market where neither company has a subsidiary, ships the equipment DDP assuming the distributor will simply receive it, and only discovers on arrival that the distributor is not registered as an importer either. Nobody is legally allowed to accept the shipment, and it is not a documentation problem that can be fixed by resubmitting paperwork; it is a legal-identity problem, and it stops the shipment cold. Our DDP shipping service exists specifically to remove this gap: when we quote DDP, we are also the named Importer of Record (or Exporter of Record on the outbound side), so the shipment has a legally accountable party at the destination from the moment it is booked, not discovered as a missing piece after it lands. This is the same coverage described in more detail on our EOR/IOR services page, which outlines how the arrangement works across our covered regions.
Every RMA, warranty replacement, or repair-and-return is legally its own export, followed by its own import, even though nothing was sold and the unit is broken. Companies that plan the outbound shipment but never map the return path usually find this out the first time equipment fails in the field.
The returning unit is legally an export, and the replacement or repaired unit coming back is legally an import, so the full customs cycle applies twice for what is operationally one warranty event. In the EU, warranty replacements can sometimes qualify for reduced VAT treatment since they are not an outright commercial sale, but that has to be claimed correctly, not assumed. In the Middle East and Latin America, reverse logistics for IT hardware typically demands the same regional customs expertise as the original inbound shipment, and sometimes more, since return declarations can draw extra scrutiny.
A broadcasting company we have worked with had installed transmission equipment across several sites outside a major market, all cleared cleanly on the way in under a standard DDP arrangement. When a unit failed outside the initial installation window, the company had a repair process for the equipment itself but no equivalent process for the customs side of getting it out for repair and a replacement back in under deadline. What should have been a routine swap turned into weeks of delay while the company built the reverse logistics process from scratch under time pressure. Companies that get ahead of this treat RMA and reverse logistics as part of the original shipping plan, including pre-cleared spare inventory staged in the region rather than shipped fresh from origin when a failure occurs. We cover the operational detail in our guide to RMA and post-sales logistics for IT hardware.
None of these five mistakes require an exotic fix. They require confirming certification requirements before booking freight, choosing Incoterms with a clear understanding of who becomes legally responsible if something goes wrong, naming an Importer of Record before a shipment needs one, and building reverse logistics into the plan from day one. Our EOR/IOR services and DDP shipping arrangements are built around closing exactly these gaps for IT, telecom, security, broadcasting, and pharma/medical hardware shippers. If you want a second look at how your current process handles any of these five, talk to our team before your next shipment.
Not confirming certification, type-approval, or licensing requirements before booking freight. The shipment itself is usually fine; the paperwork proving compliance is what is missing.
Yes. It changes who is responsible for duties, taxes, and customs clearance, and in many markets, who is legally accountable if the shipment is held. It is worth understanding before you quote a customer, not after. See our full DDP vs. DAP vs. DDU comparison for the practical differences.
Often more so. Used and refurbished IT, telecom, and broadcasting hardware can face additional scrutiny, environmental and safety compliance checks, and documentation requirements compared to new equipment in some markets. We cover the specifics in our guide to exporting and importing used and refurbished IT, telecom, and broadcasting equipment.
At minimum: a commercial invoice, packing list, accurate HS code classification, and confirmation of any product-specific certifications, type approvals, or import permits required at the destination. If a named Importer of Record is needed, that should be confirmed before booking too.
At the quoting stage, well before freight is booked. Approval regimes such as ANATEL homologation in Brazil or CST and SASO requirements in Saudi Arabia can take weeks to months, and some jurisdictions require the approval to predate the shipment rather than be obtained retroactively.
Yes. We work with IT, telecom, security, broadcasting, and pharma/medical hardware companies to review current shipping processes and close gaps in certification, Incoterms, IOR coverage, or reverse logistics before the next shipment goes out.
