01IOR/EOR
Importer & Exporter of Record
IOR/EOR establishes responsibility.
- confirming importer responsibility
- IOR/EOR where required
Industries We Support
A data-centre delivery can involve several organisations before equipment reaches the loading bay.
The facility operator may provide space and power. A customer may own the hardware. An OEM or integrator may arrange the deployment. A finance company may even retain title.
None of those facts automatically determine who should import the equipment.
For a data-centre deployment, it may be separating physical consignee from legal importer.
The receiving location and the legal importer are not the same thing
Data centres sit at the physical end of many international infrastructure deployments.
That does not mean the facility should automatically become importer.
A data centre may provide rack space, power, security and physical receiving while the equipment remains owned by a customer, cloud provider, financing entity or systems integrator.
Those are separate roles.
CFL supports the cross-border movement of infrastructure entering data-centre environments, including:
We establish the cross-border structure around the transaction and coordinate it through customs and delivery.
That can include:
01IOR/EOR
IOR/EOR establishes responsibility.
02Trade Compliance
Trade Compliance establishes the conditions for movement.
03Freight Forwarding
Freight Forwarding executes the movement.
The physical receiving address answers only one question:
Where should the truck go?
It does not answer:
Who is legally importing the equipment?
This distinction is frequently overlooked.
The facility operator may be perfectly willing to receive a shipment while refusing to take legal, tax or customs responsibility for customer-owned assets.
That position should be known before departure.
Frequent failures include using a data-centre address as though it automatically identifies the importer, booking equipment directly to the facility before customs arrangements are complete, assuming the colocation provider will fund duties or import VAT, and confusing receiving responsibility with importer responsibility.
CFL deals with the cross-border layer before the equipment reaches the loading bay.
This is one of the most important questions in an international infrastructure deployment.
A data-centre operator may be willing to receive the equipment physically while having no intention of becoming the legal importer or accepting customs and tax responsibility for customer-owned assets.
That distinction should be established before shipping instructions are issued.
Infrastructure movements can include:
servers, GPU systems, storage, networking equipment, racks, PDUs, spare components and replacement hardware.
Each shipment needs a clear commercial and customs structure behind it.
CFL connects that structure to the physical movement so customs, freight and delivery are not planned independently.
Advanced computing hardware can require additional review depending on the hardware, origin, destination, end user and intended use.
CFL can coordinate the transaction information and export-control diligence required for the shipment, while specialist legal opinions or licence determinations remain with the appropriate legal or export-control advisers when required. GPU hosting and advanced-computing equipment can create export-control considerations extending beyond a simple customs entry.
After customs clearance, delivery may still need to align with receiving procedures, security requirements, booking windows and nominated delivery points.
CFL coordinates the freight movement through to the agreed receiving location.
We do not position CFL as a provider of power strategy, cooling engineering, facility design, leasing or data-centre operations.
We map who owns the hardware, who sold it, who operates the facility and whether a lessor keeps title – the parties the transaction has to account for before anything is declared.
Servers, GPU systems, switches, PDUs and racks are classified from datasheets, not invoice descriptions, and advanced-computing items are flagged for export-control diligence against destination and end user.
The operator's willingness to receive is confirmed separately from importer responsibility. If the owner has no importing entity and the operator declines the role, we assess an IOR structure, where the jurisdiction and transaction allow it.
Duty and import VAT are estimated and assigned to a named payer before dispatch, so the facility is not left funding taxes on hardware it does not own.
Racks travel built or knocked down, by air or road, crated for the facility's dock and access route, with UPS and battery content prepared under Dangerous Goods rules.
The entry is filed against the reviewed file; delivery is then booked into the facility's receiving window and ends at the nominated receiving point, with signed proof of delivery to the owner.
What separates the party receiving the hardware from the party importing it.
Yes, and many operators do. Receiving equipment is a separate role from importing it. If the owner has no entity that can import, the corridor check tells you whether an IOR structure can take that role.
It can. Ownership, the sale behind the invoice and the value declared all follow the finance structure, so the lessor's role is set out before the importer and the customs value are fixed.
Where the facility allows it. We book to the window it sets and plan the air or road leg backwards from that slot, rather than arriving and waiting at the gate.
They need a review of their own. A free-of-charge replacement still has a customs value, and the faulty part going back is a movement too, so both legs are planned together.
Talk to an Expert
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