01IOR/EOR
Importer & Exporter of Record
IOR/EOR establishes responsibility.
- local importer feasibility
- IOR/EOR requirements
Industries We Support
Cross-Border Infrastructure Deployment for Hyperscalers & Cloud Providers
Cloud infrastructure may be delivered digitally, but expanding capacity still depends on physical hardware crossing borders.
New regions, additional availability zones, hardware refreshes and capacity expansions can involve servers, storage, networking, racks, components and spare equipment moving between suppliers, warehouses and data centres in different jurisdictions.
The logistics challenge is only one part of the transaction. Before the equipment moves, somebody needs to establish who exports it, who imports it, how customs and import VAT will be handled and whether the equipment or transaction creates additional trade-compliance requirements.
CFL Worldwide coordinates that cross-border layer.
The same three services, for Hyperscalers & Cloud Providers
For a hyperscaler, it may be maintaining consistency across repeated multi-country hardware programmes.
Multi-country infrastructure deployment without rebuilding the customs process every time
Large cloud operators deploy and refresh hardware repeatedly across different jurisdictions.
The physical equipment may be standardized.
The border treatment is not.
A server platform imported into one country under the cloud provider's own entity may require a completely different structure in the next market.
What We Do
CFL supports international infrastructure movements involving:
- servers;
- storage;
- networking hardware;
- spare and replacement equipment;
- supporting infrastructure components.
For each corridor, CFL assesses the cross-border transaction around the relevant importer, customs and freight requirements.
That can include:
02Trade Compliance
Trade Compliance
Trade Compliance establishes the conditions for movement.
- product and documentation review
- customs classification
- valuation
- expected duties and import VAT
- origin and shipment-document consistency
03Freight Forwarding
Freight Forwarding
Freight Forwarding executes the movement.
- international air or road freight
- warehousing and customs coordination
Why It Matters
Cloud infrastructure programmes rarely consist of a single shipment.
They involve deployment, capacity expansion, refresh, replacement and sometimes relocation.
That means the customs model needs to remain repeatable without becoming rigid.
A previous successful import can create a useful reference.
It does not mean the next country, product configuration or commercial structure should automatically use the same treatment.
CFL maintains that distinction.
The objective is consistency where the facts are consistent, and fresh review where they are not.
Common Industry Failures
Typical failures include copying HS classifications from one market into another without review, assuming a consignee can act as importer because it did so elsewhere, inconsistent documentation between countries, and treating refresh or replacement movements as routine freight despite changes in customs value, ownership or destination.
For large deployment programmes, small inconsistencies multiply quickly.
Where complexity appears
A cloud provider may have an entity in one country but not in the next deployment market. Hardware may also be purchased centrally while being delivered into facilities operated by another company.
That can create questions such as who appears as importer, whether the receiving data centre can act in that role, how imported equipment is valued and how duties or import VAT are dealt with.
These questions should be resolved before freight is released rather than handed to the carrier at the border.
Multi-country deployments
The same server or network platform can require a different import structure from one jurisdiction to another.
CFL helps create a repeatable deployment process around:
transaction structure→export review→IOR/EOR→customs and tax treatment→freight→destination delivery
This is especially useful when the same equipment family is being deployed across multiple countries.
Hardware refresh and relocation
Cloud infrastructure does not remain static.
Servers and networking equipment may later be replaced, redeployed, returned, transferred between facilities or moved into another country.
Those movements can create new customs and export questions even when the equipment was compliant during its original deployment.
CFL treats the movement as a new cross-border transaction rather than assuming the original structure still applies.
CFL's role
CFL does not advise on cloud architecture, cybersecurity, data-centre leases or power strategy.
Our role begins where the infrastructure crosses a jurisdiction: IOR/EOR, trade compliance, customs and VAT/import structuring, warehousing and specialist international freight forwarding.
Frequently Asked Questions
Are the same customs requirements used for every country?
No.
Classification principles may be internationally aligned in many areas, but importer requirements, taxes, product controls and customs procedures remain jurisdiction-specific.
Each corridor must be assessed on its own facts.
Can CFL support multi-country programmes?
Yes, subject to the feasibility of each individual country and transaction.
Multi-country projects benefit from consistent information and coordination, but each destination still needs its own import review.
How do you handle spare parts that have to reach many sites at short notice?
Spares are set up before they are urgent: the parts list is classified, the importer in each country agreed and duty handling fixed, so a replacement ships against an existing file, checked only for what has changed.
Can a rollout date hold if a licence turns out to be required?
Only if the requirement is known early. Dual-use authorisations take 10–45 days depending on the authority, so the need is identified at the corridor check and the shipping date worked backwards from it.
Who pays duty and import VAT when one entity buys the hardware and another uses it?
Whoever imports accounts for them at the border. If that is an IOR structure, the amounts are funded by agreement and recharged. Which entity bears the cost is settled per country before shipment; recovery questions stay with your tax advisers.
Can used or refurbished servers move between regions?
Yes, subject to each destination's rules – some countries restrict or add conditions for used IT equipment. The value has to reflect the hardware's condition, so its status is declared from the start.
How a multi-country rollout runs, step by step
01
Product and transaction reviewWhat is moving, between whom, and for what purpose?
We fix one bill of materials per platform – part numbers, configuration and origin – so the review is reused across regions and only the facts that change are re-examined.
02
Compliance assessmentWhat customs, import and export requirements affect the movement?
Each destination gets its own review of import requirements, product rules and export position, because a heading or licence answer from one market may not hold in the next.
03
Importer/exporter structureWho is legally able and willing to perform those roles?
Where the provider has a suitable local entity, it imports. Where it does not, we assess an IOR/EOR structure there, where the jurisdiction and transaction allow it, and record the decision for later waves.
04
Duty and import-cost planningWhat financial obligations arise at the border?
Duty and import VAT are estimated per country for each wave, so finance knows the cash needed at each border before the capacity plan commits to a delivery date.
05
Freight executionHow should the cargo physically move around that structure?
Servers, storage, networking hardware and spares move by air or road from the vendor or a regional warehouse, consolidated where that suits the entry, on a schedule planned around each region's go-live.
06
Customs clearance and deliveryDo the physical shipment and declared transaction match?
Entries are filed against the reviewed file for that country, and hardware is delivered to each facility's nominated receiving point. Clearance records are kept so the next wave into that country starts from evidence.
What we need from you
For a programme, most of this is gathered once per platform and reused.
- Platform bill of materials with manufacturer part numbers
- Country of origin per component, from the manufacturer
- Classifications already used in other markets, with the entries they were used on
- The importing entity in each country, or confirmation that there is none
- Rollout plan: countries, sites, quantities and target dates
- Receiving data centre, contact and delivery rules per site
- Commercial terms between the buying and the receiving entities
- For refreshes and returns: what is leaving, from where, and in what condition
Timelines
Corridor feasibility, per country4 business hours
Platform classification file2–4 business days
Freight quotation, per waveSame business day
Dual-use authorisation, where required10–45 days, authority-dependent
Import clearance once landed4–48 hours
Talk to an Expert
Request a Corridor Check
Tell us the origin, the destination and what is moving. We come back with the licences you need, the duties you will pay, and how long it takes.
Every enquiry is answered by a trade compliance specialist within four business hours
sales@cflworldwide.com