01IOR/EOR
Importer & Exporter of Record
IOR/EOR establishes responsibility.
- importer and exporter responsibility per region
- IOR/EOR where required
Industries We Support
Cross-Border Infrastructure Deployment for SaaS & Software Providers
A software company can start selling into a new country in a day. Serving customers from inside that country usually takes longer.
Data-residency requirements, regulated customers and performance expectations can push SaaS providers to run infrastructure in-region: in colocation, in a partner facility or on the customer’s own premises.
At that point the product has a physical side: servers, storage, network equipment and appliances that need an exporter, an importer and a customs treatment in a country where the company may have customers but no entity.
CFL Worldwide coordinates that cross-border layer.
The same three services, for SaaS & Software Providers
For a SaaS provider, it may be opening an in-region deployment for a customer in a country where the company has no entity.
02Trade Compliance
Trade Compliance
Trade Compliance establishes the conditions for movement.
- product and transaction review
- customs classification
- encryption and export-control review
- customs value for subscription-bundled hardware
- duties and import VAT
03Freight Forwarding
Freight Forwarding
Freight Forwarding executes the movement.
- international air or road freight
- multi-vendor consolidation
- customs coordination
- delivery to the nominated receiving point
Common Industry Failures
Typical problems include shipping hardware under an invoice that shows only a subscription fee; assuming the customer will act as importer of equipment the provider still owns; treating an encryption exemption as settled for a whole product line; and fixing a region's go-live date before anyone has established who imports the hardware. The contract date does not move the border.
In-region hosting for new markets
A new region is often opened for one anchor customer or one regulatory requirement, on a timeline set by the contract rather than by the supply chain.
CFL structures the export, import and customs position for the hardware behind that region and designs the freight around it, so the region opens when the contract says it will.
Appliances and private deployments delivered to customers
Some software is delivered with hardware: an on-premise appliance, a private-cloud stack or an edge device installed at the customer's site.
The customer receives it, but may not have agreed to be its importer, and the software provider may still own it.
CFL helps establish who carries importer responsibility for each delivery and coordinates the documentation with the freight movement.
When the hardware is part of the subscription
A customer may pay for a service, not for the appliance that delivers it. The invoice then shows a subscription and no price for the equipment crossing the border.
Customs still needs a value for the hardware, and duties and import VAT are assessed on it. CFL establishes the valuation basis before shipment rather than at the border.
Encryption and export controls
Appliances and servers that implement encryption can fall within dual-use controls on information security, depending on what they do, where they are going and who will use them.
CFL reviews the equipment and the transaction before it ships, so any exemption is established for the item rather than assumed for the product line.
CFL's role
CFL does not advise on data protection, software licensing or cloud architecture.
Our role begins where the hardware crosses a jurisdiction: IOR/EOR, trade compliance, customs and VAT/import structuring and specialist international freight forwarding.
How an in-region deployment runs, step by step
01
Product and transaction reviewWhat is moving, between whom, and for what purpose?
We map what is shipping for each region or customer – servers, storage, appliances – and how it is supplied: sold, leased, bundled into a subscription or kept in your ownership.
02
Compliance assessmentWhat customs, import and export requirements affect the movement?
Each item is reviewed for classification, encryption-related export controls and the destination's import requirements, with any licence need identified before a go-live date is committed to the customer.
03
Importer/exporter structureWho is legally able and willing to perform those roles?
We establish who can import in each country – your entity, the customer or an IOR/EOR structure, where the jurisdiction and the transaction allow it – and document it before shipment.
04
Duty and import-cost planningWhat financial obligations arise at the border?
Expected duties and import VAT are calculated on a valuation basis that holds up when the invoice shows a subscription, and funding at clearance is agreed in advance.
05
Freight executionHow should the cargo physically move around that structure?
Hardware moves by air or road on a schedule worked back from the region's opening or the customer's delivery date, consolidated where several vendors ship to one site.
06
Customs clearance and deliveryDo the physical shipment and declared transaction match?
The declaration is filed against the file built at origin, and the equipment is delivered to the nominated receiving point – colocation, partner facility or customer premises.
What we need from you
Most of it already sits with your infrastructure and legal teams.
- Bill of materials per region or customer, with part numbers
- Datasheets for servers and appliances, including encryption functions
- Who owns the equipment during and after the deployment
- The commercial model: sale, lease or subscription
- Country of origin for each item
- Your entities, and whether the customer will act as importer
- Receiving site address, contact and delivery window
- The target go-live date for the region or customer
Timelines
Corridor feasibility4 business hours
Classification file2–4 business days
Dual-use authorisation, where required10–45 days, authority-dependent
Freight quotationSame business day
Import clearance once landed4–48 hours
FAQs
We only sell software. Why would we need an importer of record?
Because the infrastructure behind it is physical. Once you deploy servers in-region or deliver appliances to customers abroad, someone has to import that equipment in each country.
Can our customer act as importer of an appliance we still own?
Sometimes. It depends on the jurisdiction and on the customer's willingness to carry importer responsibility. Where they will not, another importer structure is needed before shipment.
Does data residency change the customs position?
No. Data-residency rules decide where data is held; customs and export rules decide how the hardware holding it crosses the border. Both have to be satisfied.
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