Lawyer's answers
Questions and answers on complex imports and project shipments
Questions on non-standard shipments, equipment, multiple contracts, project deadlines and cascading delays.
When does a project shipment need a separate legal review before import?
Treat the import as a project when it involves equipment sets, several contracts, staged consignments, unusual logistics or hard commissioning deadlines. The more dependencies there are, the more important it is to resolve customs issues before shipment.
Audit triggers include a material project value, technologically linked items, several suppliers or contracts, hard commissioning dates, permits or conformity documents, and installation tied to a fixed project schedule. Use the company's own materiality threshold rather than a generic amount.
A classification dispute over one key component can delay installation of an entire line. The indirect commercial effect may include idle contractors, contractual delay exposure and postponed commissioning, so customs risk should be assessed against the project timetable rather than only the amount of possible duties.
A pre-import legal review can cover classification under the General Rules for Interpretation, price allocation across consignments, conformity and licensing requirements, sanctions and export controls, marking requirements, and a document plan for likely customs questions.
Why should a complex import not be managed like routine high-volume trade?
Project imports link several legal and operational layers. A problem in one declaration can affect installation and commissioning elsewhere in the project, so the consequences can be broader than in a routine recurring import.
The dependency chain can run from classification → duties and taxes → permits → price allocation → release timing → installation → commissioning. A dispute at the first stage may delay later stages, but its duration cannot be predicted as a fixed three-to-six-month period.
The main error is treating a one-off project like a routine recurring import: reusing familiar codes, standard document sets and permit assumptions without testing the actual equipment. Non-standard items require a fresh technical and legal review.
A complex project may justify coordinated work between customs counsel, technical specialists and the client's engineering team. The purpose is to align classification, permits, pricing and the project schedule before the first declaration.
What matters most when importing equipment and sets?
Three points deserve early attention: classification of each item, support for the allocation of the overall price across consignments, and the permit or conformity package before the first declaration.
Classification must follow the EAEU CN and the General Rules for Interpretation as applied to the actual goods. GRI 2(a) can cover incomplete or unassembled goods that have the essential character of the complete article; GRI 3(b) can apply to certain mixtures, composite goods and retail sets. Do not assume that every collection of components is a 'set' or that every separated component is classified as the complete machine.
If a single contract price is allocated across consignments, the allocation should have a defensible commercial basis and reconcile with the contract, invoices and accounting. Depending on the project, support may come from component prices, supplier costing, technical allocation or other contemporaneous evidence. An arbitrary split invites valuation questions.
Complex equipment may require EAEU technical-regulation conformity documents or other permits depending on its code, characteristics and intended use. Examples can include TR CU 010/2011, TR CU 004/2011 and TR CU 020/2011 where their scopes apply. The required documents and lead time must be checked for the actual equipment rather than assumed from a generic list.
Is it risky to split a project shipment across several contracts and consignments?
Yes. Splitting one project across contracts or consignments can create price, logistics and permit questions if the links between them are not documented. Customs should be able to understand why the structure exists and how each shipment fits the project.
Typical issues include unexplained price differences for identical items, different Incoterms terms, several suppliers, gaps between consignments and permit rules that depend on how the goods are presented. These facts do not prove undervaluation or avoidance by themselves, but they require a coherent explanation and evidence.
Link staged consignments through the documents that genuinely exist: a framework agreement or project references, an overall technical specification, a documented price-allocation method and a delivery schedule. Each individual contract should remain accurate on its own terms.
A split shipment is not inherently improper and does not guarantee either a dispute or smooth clearance. The risk depends on whether the commercial structure is genuine, documented and consistent with customs valuation, classification and permit rules.
When should counsel become involved in a complex import: before the first declaration or after a dispute starts?
Ideally, review the structure before the first declaration and, where possible, before the supplier contract is final. At that stage the parties can still adjust documents, pricing mechanics, logistics and permit responsibilities without trying to repair a live customs problem.
Before signing, align the Incoterms rule with the intended logistics, record how price changes and discounts work, require the supplier to provide technical documents needed for classification and conformity, document any staged-delivery structure, and allocate responsibility for late or missing documents.
After signing but before the first declaration, classify the material items, consider advance classification decisions for genuinely uncertain key products, assemble conformity and permit documents, test the declaration data against the contract and prepare for likely customs questions.
If the first declaration has already produced a problem, the work becomes reactive: deal with the current shipment, assess what can still be changed in the existing contract and documentation, and protect later consignments from repeating the same issue. Avoid unsupported claims that reactive work is always three to five times more expensive.
Can non-standard logistics create customs risk?
Yes. Transshipment, a change of carrier or storage in a third country can be entirely normal, but the documents should make the route and commercial reason understandable.
Review whether the agreed Incoterms rule matches the actual allocation of logistics obligations, whether the route has a commercial explanation, whether shipment and transshipment dates form a coherent chronology, and which logistics costs must be included in customs value under the applicable EAEU valuation rules.
Risk points include undocumented transshipment, unexplained storage in a third country, carrier changes that do not reconcile with transport records and transit through jurisdictions affected by sanctions or export controls. None of these facts automatically proves a hidden sale or change of ownership.
Unusual logistics can trigger additional questions when the documents do not explain them, but they do not automatically lead to a customs-value adjustment or use of a fallback valuation method. Document the route, costs and commercial reason for each unusual leg from the outset.
What if the project timetable is already critical and there is no room for a customs dispute?
Use triage: identify what is needed for release now, what could create a secondary dispute, and which explanations must not be improvised. Under project pressure, an accurate response is more valuable than an immediate but unsupported one.
In a time-critical case, first establish the cargo's actual location and procedural status; identify the immediate bottleneck; assess lawful release, security, document or shipment options; and prepare the substantive position in parallel so that an operational workaround does not concede the main dispute.
Trying to solve every issue at once can create inconsistent compromises. Prioritise the point that controls release or the project schedule, then address the remaining legal and evidential issues in a controlled order.
Do not invent an answer simply because the project is urgent. Work within the actual statutory or customs deadline, seek additional time where the procedure allows it, and submit a supported response rather than a rushed statement that later has to be explained.
Can the team prepare a document checklist in advance?
Yes. A project-specific working checklist can keep the team from rebuilding the document set for every consignment.
A project checklist can cover contracts and amendments; invoices, packing lists and price support; bills of lading or CMRs, insurance and transshipment records; payment documents; technical descriptions and drawings; conformity, licensing and marking documents; and internal authorities or calculations needed to explain the transaction. Include only documents relevant to the project and current legal requirements.
Build the checklist once for the project and update it for each consignment. The team can then prepare the required blocks in advance and counsel can review completeness before declaration. This can shorten response work, but no fixed 'hours rather than days' outcome should be promised.
The checklist also preserves project knowledge. If a key employee leaves, the next person can see which documents, decisions and outstanding issues were attached to each shipment.
How should a project be documented when one contract covers shipments from several countries?
One contract covering shipments from several countries can be workable, but each origin and shipment country may raise distinct questions about origin, export controls, sanctions and tariff treatment.
Distinguish country of origin from country of shipment. Origin is determined under the applicable EAEU origin rules, including the rules for preferential and non-preferential origin. Certificates or declarations of origin depend on the relevant trade regime; do not use a generic list such as ST-1, Form A or EUR.1 without checking whether that document and preference are actually available for the goods and date.
The framework contract can describe the overall project, while shipment-specific specifications or amendments identify the relevant supplier, dispatch point, goods and price. Origin documents should reflect the actual origin under the applicable rules, not merely the country from which the goods were sent.
Using one headquarters document set for goods shipped from several countries can create inconsistencies in supplier, origin, pricing or logistics. Those inconsistencies may lead to valuation or origin questions, but do not automatically justify a fallback method. The documents should accurately show how the multi-country structure works.
When should sanctions risk be built into a project-shipment review?
Sanctions and export-control review is particularly important where the project includes controlled technology, restricted parties or sensitive routes. The assessment should follow the actual goods, parties, banks, ownership, route and end use rather than a label such as 'sanctions jurisdiction'.
Project screening can cover product export controls, counterparties and ownership, the payment chain, carriers and transit points, and end use. Use current official lists and rules for each relevant jurisdiction and do not treat a commercial screening database as the legal source.
Sanctions problems can arise even in otherwise ordinary projects—for example through export-controlled equipment, correspondent-bank restrictions or a carrier that will not serve a route. The relevant question is the transaction's legal and operational exposure, not whether a country has been publicly labelled 'sensitive'.
Before signing, screen the goods, counterparty, delivery route, payment and end use for sanctions risks. Include sanctions clauses and allocate the risk of regulatory changes. Prepare alternative lawful payment and logistics arrangements, and recheck counterparties during long projects. Compare the cost of screening with the potential loss from a blocked transaction.