01IOR/EOR
Importer & Exporter of Record
IOR/EOR establishes responsibility.
- IOR/EOR
Industries We Support
Cross-Border Deployment Support for System Integrators
System integrators can design and deliver an infrastructure project without having a legal or importing presence in every country where their customers operate.
That becomes a problem when the project moves from the bill of materials to the physical deployment.
Servers, networking equipment, storage, racks and other infrastructure may come from several vendors and several countries before arriving at the customer's site.
Someone still has to take responsibility for the cross-border transaction.
The same three services, for System Integrators
For a system integrator, it may be connecting multiple vendors and commercial parties into one defensible customs transaction.
Cross-border execution behind international customer projects
System integrators often sit between the OEM, customer and deployment site.
They may design the solution, procure the hardware and manage installation while having no importing entity in the country where the project will be delivered.
That creates a gap between selling the project and legally landing the equipment.
What We Do
CFL supports system integrators by mapping the transaction before the shipment is released.
That can involve several commercial parties:
OEM→distributor→integrator→end customer→data centre or facility
CFL identifies who performs each cross-border function and coordinates:
02Trade Compliance
Trade Compliance
Trade Compliance establishes the conditions for movement.
- customs documentation
- multi-vendor product information
- customs classification
- valuation
- duties and import VAT
- export and import documentation
03Freight Forwarding
Freight Forwarding
Freight Forwarding executes the movement.
- freight consolidation
- customs clearance
- final delivery
Why It Matters
Multi-vendor projects are particularly exposed to documentation inconsistency.
One supplier may describe equipment by commercial name.
Another may use an internal part number.
A third may provide a classification that applies only to its own export process.
When those goods are consolidated into one deployment, the customs file still needs to make sense as a single transaction.
CFL focuses on that point of convergence.
Common Industry Failures
Common problems include committing delivery terms before confirming who can import, assuming the end customer will absorb customs responsibility, mismatched invoices and technical documents, different vendors using conflicting product descriptions, and shipping components independently without considering how the final import programme should be structured.
The technical design may be complete while the border execution remains undefined.
The gap between procurement and deployment
A typical project can involve:
OEM→distributor→system integrator→end customer→data centre
Commercial ownership, physical delivery and importer responsibility may sit with different companies.
CFL helps establish who performs each cross-border role before cargo moves so the shipment is not left waiting while the parties decide who should appear on the customs declaration.
Multi-vendor project shipments
Integrators frequently consolidate equipment sourced from several manufacturers into one deployment.
That creates practical issues around:
- product descriptions and classification;
- origin and valuation;
- export information;
- consignee and importer roles;
- shipment documentation;
- customs treatment.
CFL coordinates these elements with the freight plan rather than treating each vendor shipment as an isolated movement.
Projects without a local entity
If the integrator or customer cannot act as importer in the destination country, an IOR structure may provide a workable route depending on the jurisdiction and transaction.
The important point is to decide that structure during project planning – not once equipment is already booked for transport.
CFL's role
We support the cross-border execution layer of the project.
The integrator remains responsible for solution design, installation and technical delivery. CFL coordinates the international movement, IOR/EOR requirements, trade compliance, customs and import structure.
How This Looks in Practice
Scenario 2 – System Integrator Delivering a Medical Technology Project
A systems integrator procures specialist medical equipment and associated IT hardware from several manufacturers for installation at a customer site overseas.
The customer will receive the equipment but cannot act as importer.
CFL separates the product groups, establishes what documentation is available, confirms which items require additional manufacturer or regulatory evidence, builds the importer structure and aligns the freight plan with the customs position.
The integrator remains responsible for technical installation.
The regulatory specialist remains responsible for product authorization.
CFL controls the agreed cross-border execution between them.
How a multi-vendor project shipment runs, step by step
01
Product and transaction reviewWhat is moving, between whom, and for what purpose?
Each vendor's invoice, packing list and datasheets are gathered into one bill of materials, and the contract chain is mapped, so every line has a seller, an owner and a destination.
02
Compliance assessmentWhat customs, import and export requirements affect the movement?
Classifications supplied by different vendors are reconciled against the equipment as configured for the project, and any item whose export position rests on a vendor's own licence is flagged before consolidation.
03
Importer/exporter structureWho is legally able and willing to perform those roles?
We confirm whether the integrator, the end customer or neither can act as importer in the destination country, and where neither can, whether an IOR structure fits the transaction.
04
Duty and import-cost planningWhat financial obligations arise at the border?
Duty and import VAT are calculated across the whole consignment, and the party funding them is agreed in the delivery terms before the integrator commits to a price that includes them.
05
Freight executionHow should the cargo physically move around that structure?
Vendor shipments are collected and consolidated by air or road into one movement, so the equipment reaches the border as one declared transaction rather than several partial ones.
06
Customs clearance and deliveryDo the physical shipment and declared transaction match?
Declaration, packing lists and delivered pieces are checked against one another at clearance, and the consignment is delivered to the site or data centre the customer nominates, ready for the integrator's team.
What we need from you
One file for the project, not one per vendor.
- Consolidated bill of materials, with manufacturer part numbers per line
- Commercial invoice and packing list from each vendor
- Any HS or export classification each vendor has already issued
- The contract chain: who sells to whom, and on which incoterm
- End customer name, address and intended end use
- Whether the integrator or the customer has an entity in the destination country
- Collection points and ready dates for each vendor
- Delivery site, dock contact and the window your installation team has booked
Timelines
Corridor feasibility4 business hours
Multi-vendor classification file2–4 business days
Freight quotationSame business day
Dual-use authorisation, where one is needed10–45 days, authority-dependent
Import clearance once landed4–48 hours
Questions system integrators ask
Can the end customer be the importer if it has an entity in the country?
Often, if it is willing to carry the importer's responsibilities and the transaction supports it. CFL then works under that importer structure and coordinates the classification, documentation and freight around it.
Our vendors gave different HS codes for similar equipment. Which one is used?
Neither automatically. A vendor's classification is evidence, not a decision. CFL reviews the equipment as configured for the project and declares one consistent classification across the consignment.
Can you work to a delivery date we have already committed to the customer?
Yes, if the date leaves room for what the transaction needs. Where a licence or an IOR structure cannot be ready in time, the corridor check says so before the date is lost at the border.
Do you install or rack the equipment?
No. CFL's scope ends at the receiving point the customer nominates. Installation, configuration and commissioning stay with the integrator, the OEM or the customer's own team.
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