TFTIOR provides Exporter of Record support for technology hardware, servers, networking equipment, data centre infrastructure, RMA returns, refurbished IT equipment and cross-border asset movements where the equipment owner cannot complete the export locally.
Moving hardware out of a country can be as complicated as bringing it in. Before a shipment is accepted, we review the export structure against the country of departure, the equipment, ownership, destination, end user and reason for export. The freight itself is usually the easy part. The real question is who is legally able to export the goods.
The structure has to work in the actual country of export, not on a coverage map.
Exporter of Record, usually abbreviated to EOR, is commonly used to describe the locally eligible party responsible for the export side of an international shipment. In practical terms that can involve confirming the export may legally take place, determining the customs classification, supporting export-control classification where applicable, reviewing licensing requirements, checking the destination, consignee, end user and end use, preparing or supporting the export declaration, coordinating documents with the forwarder and customs broker, and retaining evidence of export.
The exact legal structure varies from one country to another. In some jurisdictions the exporter must be established locally. In others, customs representation rules allow different arrangements. Export-control regulations may also assign obligations separately from customs law. The United States frames the underlying act of export in Part 734 of the Export Administration Regulations, while the EU, the UK and national regimes such as the Turkish export regime use their own definitions and filing structures.
For that reason TFTIOR does not treat EOR as a generic company name that can be dropped onto every shipment. Exporter eligibility is confirmed for the transaction before the equipment is collected. This is the same discipline we apply on the inbound side through Importer of Record services and the reason we publish a position on paper IOR arrangements rather than presenting a country list as proof of capability.
Whether a third-party exporter structure is permitted and practical in the country the goods are leaving.
Customs classification and, where relevant, export-control classification. For technology this is often more than an HS code.
Proof of departure and supporting records retained where required for audit and transaction history.
Almost always when goods need to leave a country and no local party is eligible to act as the exporter.
A server, switch, firewall or storage device fails and must return to the manufacturer or repair centre. The RMA number and collection instructions do not complete the export from the country where the equipment physically sits, particularly when the original purchaser no longer has a local entity there.
Advance replacement programmes create a two-way problem. The replacement unit enters first, often through an Importer of Record, while the defective device still has to leave. Values, serial numbers and customs histories differ between the two legs.
Servers, storage, switches, PDUs and appliances get replaced, consolidated, relocated, returned to leasing companies, sent for refurbishment or transferred to another group company. Each of those becomes an export the moment the equipment crosses the border.
Equipment bought for one country is later needed elsewhere. Ownership may not change at all. Even without a commercial sale, the declaration still needs an accurate value, reason for export, description and transaction structure.
Customs may ask about age, condition, value, serial numbers, previous import records, ownership, refurbishment status and environmental restrictions. Our work on refurbished and used IT equipment feeds directly into how these exports are structured.
A global company buys equipment in a country where it has no legal entity, then needs to move it to another project location. The local seller often will not act as exporter because its obligation ended with domestic delivery.
Hardware belongs to a leasing company outside the country. At the end of the lease neither the foreign lessor nor the local end user may have a suitable exporter structure. EOR support can bridge that gap where the jurisdiction permits it.
Equipment that entered for testing, demonstration, repair, exhibitions or evaluation must usually be re-exported against the original import procedure. The original declaration, serial numbers, customs regime and timeline all matter.
Several roles exist in the same transaction. Sometimes they overlap. Often they do not.
A freight forwarder primarily coordinates transportation. Depending on the country and service structure it may also arrange customs brokerage or act through an agent. That does not automatically make it the legal exporter for the shipment, and many forwarders decline the position outright for controlled technology.
In a single movement you can have a goods owner, an exporter, a customs broker or customs representative, a freight forwarder and an end user. For complex technology shipments TFTIOR identifies which party holds which position before dispatch, so the consignment does not reach the export stage with nobody able to complete the customs procedure.
The same distinction applies on the inbound side, which we cover in freight forwarder versus importer of record and IOR versus customs broker.
Arranges international transportation, routing and logistics. May coordinate customs brokerage without becoming the exporter.
Submits declarations or represents another party before customs. Representation is not the same as exporter status.
The party legally recognised or accepted as exporter under the applicable customs framework in the country of departure.
The EOR deals with the country the goods are leaving. The IOR deals with the country they are entering.
| Area | Exporter of Record | Importer of Record |
|---|---|---|
| Jurisdiction | Country of departure | Country of destination |
| Main function | Legal export | Legal import |
| Customs event | Export declaration | Import declaration |
| Key compliance area | Export controls, licensing, departure requirements | Import permits, conformity, duties and taxes |
| Typical technology use | RMA, repair return, redeployment | Deployment, rollout, project delivery |
| Main risk | Goods cannot legally leave | Goods cannot legally enter |
For a simple sale between two established companies, each side may already have its own exporter and importer. The problem appears when one side has no legal presence, no customs capability or no suitable entity to take responsibility for the movement. Technology companies hit this often, because hardware moves independently of normal sales flows. Where the question is about the destination rather than the origin, see the non-resident importer of record model and importer of record liability.
EOR work should begin before the equipment is collected, not after the truck is booked.
Export country, destination, equipment description, manufacturer, model, quantity, condition, serial numbers, value, owner, consignee, end user, reason for export, previous import history and RMA information. A description such as IT equipment is generally not enough to review an export.
We confirm whether a third-party exporter structure is permitted and practical in the country of departure. We do not present a market as operationally available unless the exporter structure can actually be identified for the transaction.
Customs classification and, where relevant, export-control classification. A server, encryption-capable network device, high-performance computing system or specialised telecommunications product may need more than an HS code.
Destination, consignee, end user, end use, sanctions, restricted-party lists, military or governmental involvement and export-control restrictions. Two shipments of the same model can produce different outcomes.
Invoice, packing list, equipment list, serial numbers, proof of value, RMA paperwork, ownership records, previous declarations, temporary import documents and end-user information. For non-sale movements the paperwork should reflect the real transaction.
The outcome may be no licence required, export under a specific exemption or authorisation, a licence application, or a shipment that cannot be supported under the proposed structure. We do not use export licence included as a blanket promise.
The declaration is prepared through the appropriate customs channel. Exporter, customs representative and freight provider work from the same approved shipment information. Changes made after approval create avoidable risk.
After customs release the goods leave the country. Where required, export evidence and supporting records are retained for audit and transaction history.
Where TFTIOR also supports the destination market, the outbound EOR process connects to the inbound Importer of Record process so the movement is reviewed as one compliance chain rather than two unrelated shipments.
Valuable, serialised, sometimes encryption-capable and frequently subject to export-control considerations.
Typical products include rack servers, GPU servers, storage arrays, switches, routers, firewalls, optical networking equipment, PDUs, power equipment, spare parts and network appliances. For these shipments the relevant question is not only what the HS code is.
The review may also need to establish what exactly the product is, what its export-control classification is, where it is going, who will receive it, who the end user is, what it will be used for, whether it is new, used or refurbished, who owns it and why it is being exported.
Our server and data centre equipment IOR work already covers the inbound side of these deployments, alongside cloud and AI infrastructure IOR and the GPU and AI hardware import guide. EOR lets the same lifecycle be supported when the equipment later needs to leave.
Serial numbers tie the export to earlier import records, RMA documentation and asset registers.
Network and security appliances can carry encryption controls that sit outside ordinary customs classification.
GPU and accelerator hardware may trigger additional review depending on destination and end use.
A manufacturer can approve an RMA in minutes. That does not make the equipment legally exportable in minutes.
A typical flow runs from failure identified, to RMA approved, to replacement shipped, to defective unit collected, to export declaration, to the manufacturer or repair centre receiving the returned unit. The outbound leg becomes critical once the replacement unit has already entered the country.
Without a workable reverse-logistics structure, defective equipment starts accumulating locally. This is common in international infrastructure projects where the original team focused heavily on delivery and never designed the return path. It is also one of the more frequent causes behind the situations described in our stuck shipments work.
TFTIOR therefore treats RMA as part of the wider asset lifecycle rather than an isolated courier shipment. Our global server lifecycle case study shows how forward deployment, reverse logistics and redeployment can operate across several countries within one programme.
Inbound replacement and outbound defective unit carry different values, serial numbers and customs histories.
Where the unit originally entered under a specific regime, the export usually has to be connected back to that declaration.
Unreturned defective hardware becomes a stranded asset problem long before anyone treats it as a compliance issue.
A server bought years ago for USD 15,000 no longer has that market value, and customs will not accept an arbitrary nominal figure either.
Used and refurbished equipment needs a defensible valuation methodology. Relevant factors include age, condition, configuration, depreciation, comparable market value, repair status, ownership and the reason for movement. The correct approach depends on the jurisdiction and the transaction.
This is why TFTIOR separates logistics value from customs value. The figure used for an internal transfer, RMA or warranty movement should be reviewed against the actual customs requirements rather than copied automatically from an old purchase invoice. Our guidance on customs valuation risks for technology imports covers the same principle from the inbound side.
Not every export is a sale. RMA returns, warranty replacements, repair shipments, internal transfers, intercompany movements, redeployment, loan equipment, demonstrations and temporary exports all cross borders without a change of ownership. Wording such as goods not for sale, value declared for customs purposes only, describes the transaction, but it does not by itself determine the correct customs value. For high-value hardware, arbitrary figures create problems on both the export and the subsequent import.
The document should describe the real transaction instead of inventing a commercial sale that never happened.
A value that survives the export declaration also has to survive the import declaration at the other end.
Depreciation basis, comparable pricing and repair status are worth documenting before anyone asks for them.
Classification alone does not determine the outcome. Destination, end user and end use can matter just as much.
Some products require analysis under frameworks such as the US Export Administration Regulations administered by BIS, EU dual-use controls, UK strategic export controls administered by the Export Control Joint Unit, and national export-control regulations. In Türkiye, export-regime requirements sit with the Ministry of Trade alongside the customs administration, and controlled-goods movements are assessed within that structure.
A product that can be exported freely to one destination may face additional restrictions elsewhere. For this reason TFTIOR reviews controlled-technology movements transaction by transaction. We do not treat an ECCN, an HS code or a manufacturer data sheet as a complete compliance decision by itself. Where specialist legal or licensing advice is required, that requirement should be identified before the shipment moves.
Related reading: dual-use compliance and US export controls, EAR and BIS exposure in IOR shipments.
ECCN belongs to the US framework. The applicable classification system depends on the origin country.
Restricted-party, sanctions and end-use screening belongs at intake, not at the airport.
Some transactions simply cannot be supported under the proposed structure. Saying so early is cheaper for everyone.
The goods are EXW and the buyer is responsible for export. Commercially true. Legally incomplete.
EXW describes how responsibilities are allocated between buyer and seller. It does not override local customs law. If the buyer is a foreign company with no local establishment, it may not be eligible to act as exporter in the country where the goods sit. The freight forwarder may also be unwilling or unable to take that position.
The result is familiar. The buyer owns the goods. The truck is ready. The forwarder is booked. And there is still nobody able to complete the export declaration. In some cases FCA or another structure is more suitable. In others a third-party EOR is required. The correct solution depends on the country and the transaction, which is why exporter eligibility should be checked before the shipping terms are agreed.
Incoterms allocate cost and risk between parties. Customs law decides who may file.
Exporter eligibility is cheaper to confirm at quotation stage than at the terminal.
EOR is not priced per kilo. It is priced against the compliance work the transaction actually requires.
Factor 01
Country of departure
Local exporter eligibility rules, representation structures and filing channels differ sharply between jurisdictions.
Factor 02
Control status of the equipment
Dual-use, encryption-capable or high-performance computing hardware requires deeper classification work.
Factor 03
Destination and end user
Screening depth varies with the destination country, consignee profile and declared end use.
Factor 04
Transaction type
No-sale, RMA, warranty and intercompany movements need a valuation basis that a sales invoice does not provide.
Factor 05
Customs history
Temporary imports and returned goods require the earlier declaration to be traced and reconciled.
Factor 06
Documentation readiness
Complete equipment lists and serial numbers shorten the file. Incomplete information does not block the project, but it does delay a reliable quotation.
Deploy, operate, replace, return, repair, refurbish, redeploy. The same asset can face four different customs questions in its working life.
Traditional logistics diagrams show supplier to customs to customer. Modern technology infrastructure rarely behaves that way. The same equipment may be imported into one country through an IOR structure, exported several years later through an EOR structure, and then enter a third country as used equipment. Each step produces different questions.
TFTIOR supported a technology hardware programme involving new and refurbished servers across nine countries and 20 consignments. The lifecycle covered international import, local customs compliance, deployment, reverse logistics, exporter-side coordination, used equipment handling and redeployment planning. The programme completed without customs penalties or destination reclassification issues.
The case shows why IOR and EOR should not be treated as unrelated services for technology infrastructure. Where hardware has a multi-year operational life, companies should plan how it will eventually leave the country at the same time they plan how it will enter. Read the full global server lifecycle case study, or see how the same discipline runs across a full deployment in end-to-end global data centre import and deployment.
New and refurbished servers across a single programme rather than a set of isolated shipments.
Forward deployment, reverse logistics and redeployment reviewed as one compliance chain.
Completed without customs penalties or destination reclassification issues. Feasibility is confirmed before a shipment is accepted, and shipments that cannot be supported are declined.
The fastest EOR projects are the ones reviewed before the equipment is collected.
For an initial feasibility review we typically need the country of export, the destination, an equipment description, manufacturer and model, quantity, condition, value, equipment owner, consignee, end user, reason for export, proposed Incoterm, previous import documents where relevant, RMA documentation where applicable and the expected shipment date. For controlled or unusual equipment, additional technical information may be requested.
Incomplete information does not automatically prevent the project, but it does prevent a reliable quotation or a compliance decision. Finding a problem before dispatch is normally much cheaper than solving it after the equipment has reached the airport, port or customs terminal.
Can the proposed party legally perform the export in that country?
Is the customs classification appropriate, and does the equipment have strategic, dual-use or other controlled characteristics?
Do the invoice, packing list, equipment list and supporting documents describe the same shipment?
A country on a provider map is not the same thing as a verified exporter structure.
The useful question is not how many countries a provider covers. It is who the exporter is in this country, whether that entity is legally eligible, who signs or files the customs declaration, who performs restricted-party screening, who reviews export-control classification, what happens if a licence is required, how the equipment is valued when there is no sale, what evidence is retained after export, and whether the same provider can support the destination import.
For complex hardware, the named operating model matters more than the number of flags on a coverage page. The same test applies on the import side, which we set out in the IOR due diligence framework and in real coverage versus logistics coverage.
TFTIOR operates from Istanbul through its own Turkish legal entity, which is where our exporter-side work is most directly held.
Typical Turkish scenarios include RMA returns, warranty movements, hardware repair shipments, locally purchased equipment that needs to leave, temporary import and re-export, technology equipment owned by foreign companies, and asset redeployment out of Turkish data centres. Türkiye has its own customs, exporter registration and product-specific requirements, so the structure should be reviewed before shipment rather than assumed from the import side.
Türkiye's export requirements sit primarily within the Ministry of Trade and customs framework. Depending on the equipment and the transaction, product-safety controls administered through TAREKS and records associated with sector-specific requirements may also become relevant. For re-export, RMA and temporary-import movements, the original import declaration and any product-specific compliance history are reviewed before the outbound file is structured. TFTIOR holds Turkish registrations including MERSIS 0859123223400001 and SSHYB authorisation 84634, and appears directly on Turkish customs declarations rather than through an undisclosed third party.
For the inbound side of the same market, see Importer of Record services in Turkey, the complete Turkey IOR guide, and our H1 2026 refurbished server import case study.
TFTIOR evaluates coverage by country, product category, licensing exposure and local regulatory feasibility. Exporter-side structure is confirmed per country of departure before shipment acceptance, not assumed from a generic country list.
The difficult cases are the ones where the equipment has already been collected, the flight is booked, and somebody discovers at the final stage that no eligible exporter exists.
For RMA, data centre, refurbished IT and controlled technology movements, exporter eligibility should be confirmed before dispatch. TFTIOR reviews the transaction first, confirms whether an EOR structure is workable, and identifies the documentation and compliance requirements before the goods enter the export process.
If you have technology hardware that needs to leave a country and your organisation cannot act as the local exporter, send us the origin, destination, equipment list and reason for export.
