Importer & Exporter of Record (IOR / EOR)

Companies increasingly deploy infrastructure into countries where they do not maintain their own legal entity, customs registration or import capability.

That creates a basic operational problem:

Who will legally stand behind the import or export transaction?

A consignee address is not automatically an importer.

A data centre may be willing to receive equipment without accepting customs responsibility for customer-owned hardware.

A customer may own the equipment but have no legal entity in the destination country.

A system integrator may have sold an international deployment without having import capability in every market included in the project.

In those situations, the shipment needs an appropriate import or export structure before it moves.

What We Do

CFL evaluates whether an IOR or EOR structure can support the proposed transaction.

That review starts with the actual shipment rather than a country coverage map.

We look at factors such as:

• origin and destination;
• seller, purchaser and end user;
• ownership of the equipment;
• proposed consignee;
• product type;
• new, used or refurbished status;
• value;
• customs classification;
• purpose of the movement;
• expected duties and import VAT;
• product-specific import requirements;
• available export information;
• delivery location.

Where the transaction and jurisdiction permit it, CFL or an appropriate importing/exporting structure can perform the required role and coordinate it with customs clearance and freight execution.

The exact legal responsibilities of the importer or exporter depend on the jurisdiction and transaction and are established before shipment.

Why It Matters

The importer is not simply a name appearing on paperwork.

The importing party may carry customs responsibilities concerning the accuracy of the declaration, value, classification, supporting documentation, duties, taxes and compliance with applicable import requirements.

That is why CFL does not treat IOR as a paperwork workaround.

Before accepting or coordinating an importer structure, the underlying transaction has to make sense.

For example, consider a European AI infrastructure company deploying servers into a data centre in another country.

The data centre operator provides rack space and receives the equipment physically.

That does not automatically mean the facility should become importer.

The project must establish:

who owns the equipment→who sells it→who imports it→who funds duties and VAT→who receives it→what happens to the equipment afterwards

Resolving that before shipment is significantly easier than trying to change importer arrangements while the equipment is already at customs.

Common Industry Failures

A large number of IOR problems originate before the provider becomes involved.

Typical examples include booking freight while importer responsibility remains unresolved; assuming the consignee can act as importer because its address appears on the shipping documents; using DDP Incoterms without actually establishing a valid import structure; appointing an IOR before disclosing the real product, end user or transaction; and assuming that because an IOR structure worked for one shipment it will automatically work for another country or product.

There is another common mistake:

confusing a customs broker with an Importer of Record.

A broker may prepare and submit a customs declaration on behalf of an importer. That does not automatically mean the broker becomes the party carrying the importer responsibility.

CFL establishes that distinction before the movement begins.

Scenario 1 – GPU Infrastructure Into a New Market

A cloud infrastructure company purchases GPU servers for deployment into a data centre in a country where it has no importing entity.

The data centre agrees to receive the racks but will not become importer.

IOR/EOR:

CFL establishes whether an appropriate importer structure is available for the transaction.

Trade Compliance:

Product information, available export classification, parties, destination, end use, customs classification and import requirements are reviewed.

Freight Forwarding:

Once the transaction is ready, CFL coordinates international freight, customs and delivery to the nominated receiving point.

The problem is therefore not treated as:

“How do we fly these servers there?”

It is treated as:

“How do we lawfully structure and execute the entire cross-border movement?”