Regions & overseas delivery · Available now
Country Packs & Overseas Delivery
A new market should be a pack, not a project. The main process stays fixed; customs steps, tax structure, certification, document templates, currency and language arrive as a pack that is configured and validated before it goes live.
Prefer Chinese? The Chinese edition of this page carries the full source list and every numeric caveat. 本页中文版
- StructureCore pack + 16 country packs
- A pack carriesCustoms · tax · certification · documents · currency · language
- CoverageSoutheast Asia · Latin America · Middle East · Central Asia · Africa
- DeliveryRemote-first, on-site as needed
- StatusAll packs available in product
1. Why country differences become packs
When market rules are written into the main process, the second market disproves the first.
Vehicle export looks like one business with local variations. It is the reverse: the chain of purchase, shipping, clearance, preparation, storage, sale and aftersales has the same shape in every market, while the rules around it differ completely — how many documents, how tax is layered, which certification scheme, which currency is settled in, which language the store works in.
Building each market as a project produces a fork per country: the same process maintained several times, and every fix landing in one fork only. Building the differences as packs keeps one main process and one set of master data, with market specifics in a versioned, switchable package.
That is the delivery claim behind the product: opening a market is adding and validating a pack, not rewriting the business. It also makes the risk visible — a pack that has not passed validation does not reach production, and a pack can be rolled back.
2. What a pack actually carries
Six dimensions, each with a field set behind it.
| Dimension | What it defines | Where it shows up |
|---|---|---|
| Customs process | Declaration steps, supervision mode, release sequence, agency hand-off | Stage flow and checkpoint validation |
| Tax structure | Which taxes apply, in what order they compound, and what the base is | Per-VIN landed cost and quotation |
| Certification and admission | Which scheme, which document, which point in the process it must be in place | Pre-shipment checks and document completeness |
| Document templates | Layouts, mandatory fields and numbering per market | Issued documents and archive |
| Currency and rates | Settlement currency, conversion point and where exchange differences land | Cost card and margin reporting |
| Language and local practice | Working language of the store, driving side and market conventions | Terminals and store configuration |
Default basis; the actual split follows the customer's organisation and authorisation scheme.
Rates themselves are maintained data, not code. Each pack states which version date was used, so when a quotation turns out wrong it is possible to tell whether the structure or the rate table was stale — two very different fixes.
3. The packs currently in the product
Core pack plus 16 country packs across five regions. Driving side is stated because it decides whether a model needs adaptation before shipment.
| Region | Country pack | Driving side | What usually decides the landed cost |
|---|---|---|---|
| Core | pack_core | Shared by all markets | The common skeleton: process, document framework, currency and cost structure |
| Southeast Asia | Philippines (pack_ph) | Left-hand drive, right-hand traffic | Certification before shipment; excise by price band |
| Southeast Asia | Vietnam (pack_vn) | Left-hand drive, right-hand traffic | Special consumption tax by displacement; assembled versus imported duty gap |
| Southeast Asia | Thailand (pack_th) | Right-hand drive, left-hand traffic | Excise by CO₂ band; incentives tied to local production volume |
| Southeast Asia | Indonesia (pack_id) | Right-hand drive, left-hand traffic | Local-content thresholds; type approval before shipment |
| Southeast Asia | Malaysia (pack_my) | Right-hand drive, left-hand traffic | Import approval and quota; type approval for the model |
| Latin America | Brazil (pack_br) | Left-hand drive, right-hand traffic | Four-layer tax structure driven by the classification code |
| Latin America | Mexico (pack_mx) | Left-hand drive, right-hand traffic | Origin decides the duty rate; separate new-vehicle tax |
| Latin America | Chile (pack_cl) | Left-hand drive, right-hand traffic | Preferential duty requires a valid origin certificate; type approval for registration |
| Latin America | Peru (pack_pe) | Left-hand drive, right-hand traffic | Excise by displacement band; fuel quality as a hidden barrier |
| Middle East | United Arab Emirates (pack_ae) | Left-hand drive, right-hand traffic | Declared value scrutiny; free-zone deferral for re-export |
| Middle East | Saudi Arabia (pack_sa) | Left-hand drive, right-hand traffic | Pre-shipment conformity certificates before declaration |
| Middle East | Türkiye (pack_tr) | Left-hand drive, right-hand traffic | Special consumption tax bands and their minimum specific floor |
| Central Asia | Kazakhstan (pack_kz) | Left-hand drive, right-hand traffic | Union-wide tariff plus recycling fee; local assembly advantage |
| Central Asia | Uzbekistan (pack_uz) | Left-hand drive, right-hand traffic | Recycling fee; origin certificate for preferential rates |
| Africa | South Africa (pack_za) | Right-hand drive, left-hand traffic | Ad valorem duty rising with price; right-hand-drive requirement |
| Africa | Nigeria (pack_ng) | Left-hand drive, right-hand traffic | Classification errors trigger whole-shipment reassessment; pre-shipment conformity |
Structural facts only. Rates, categories and deadlines follow the competent authority's current rules in each market and are not stated as conclusions here.
4. How a market goes live
Five steps, each with something to check before the next one.
- Pick the pack and confirm it matches the business. Assembled vehicles and local assembly can land in different regimes within one country, so the operating model decides which pack and which branches apply.
- Validate the fields before the first quotation. The fields a declaration needs and the fields the system asks for must line up; a missing mandatory field surfaces at the port, not in the office.
- Load the rate tables with a version date. The tables are data. Record the version date and who maintained it, because that is what an outdated quotation is traced back to.
- Dry-run one shipment and one quotation end to end. One real vehicle through the full chain, and one quotation broken into its tax layers, is enough to expose a wrong pack.
- Set permissions and baselines per market. Reporting baselines differ — where clearance is slow, days in stock are naturally higher — and comparing countries on one baseline produces the wrong conclusion.
The same approach applies to opening a second market under an existing pack: no pack, no quotation. It sounds strict until the first quotation built on a remembered rate table arrives at the port.
5. What is own, what is shared, what belongs to your advisers
A pack structures a market. It does not give legal advice.
Fields, checkpoints, document templates and rate tables per market, with a version date and a validation state. A pack that has not passed validation stays out of production.
Per-VIN cost assembled in the order the market's taxes compound, not a single rate over a landed value.
The pack changes the rules; it does not change the master data or the process shape. One VIN file travels across markets.
Classification opinions, admissibility judgements and filing positions belong to your responsible staff and professional advisers. The pack makes their answers executable; it does not produce them.
6. Six red lines
Each one produces a quotation that looks right until the car reaches the port.
- Quoting from a rate table with no version date. When the number turns out wrong, there is no way to tell whether the structure or the table was stale — so the same mistake repeats next quarter.
- Applying one rate to a layered tax. Duty, consumption tax and value-added tax compound; a single rate overstates low-displacement cars and understates high-displacement ones, in opposite directions.
- Treating a pack as legal advice. A pack encodes a market's process; it does not decide admissibility, classification or filing positions.
- Assuming driving side. Right-hand-drive markets need adaptation and verification before shipment, and that is a cost and a lead-time item, not a detail.
- Confusing clearance with registration. A car can clear customs and still be unregistrable for lack of type approval or a tax payment certificate.
- Copying a neighbouring market's pack. Similar geography, different regime: the second market disproves the first, and the correction arrives after delivery.
7. Questions we are asked most
Six, in the order they arrive.
Is the system localised for my country?
It is configured for your country through a pack, not translated into a separate product. If a market is not among the current packs, a new pack is added and validated — that is a configuration exercise with a defined validation, not a new build.
Can we run several markets on one instance?
Yes. One main process and one VIN file, with packs selected per market. Data separation and permissions are configured per market and organisation, so a distributor in one market does not see another's.
Are the tax figures in the pack authoritative?
No. The pack holds structure and maintained rate tables with version dates. Figures must be confirmed against the competent authority's current rules by your responsible staff, and the pack records which version was used at quotation time.
What if our business is assembled vehicles rather than imports?
Then a different branch of the pack applies — duty and incentive treatment usually differ substantially. Confirm the operating model before picking the pack; the wrong branch produces a plausible but wrong landed cost.
Do you deliver remotely or on site?
Remote-first, with on-site support when the process requires it. Country packs are built so the main process does not change, which is what makes remote delivery realistic; partner collaboration is used where local presence matters.
Does the demo contain a real market's rates?
No. The demo shows structure and constructed sample data, not current rates for any market.
Citation
Suanshu Haiyuan. Country Packs & Overseas Delivery. Shanghai Siyang Information Technology Co., Ltd.. https://eficien.com/en/regions.html (source list verified 2026-10-17; English edition 2026-10-29).
This page describes how the system carries these stages and fields. It is not legal, tax or customs advice. Rates, categories, deadlines and document requirements follow the competent authority's current rules and must be confirmed by your responsible staff and professional advisers. The Chinese edition lists the official reference entry points; this edition does not restate them, and deliberately gives no numeric conclusions.
8. Where to start
Tell us the country and city; the useful answer is which pack applies and what has to be validated first.
A market plan is worth little without one real shipment and one real quotation behind it. The productive first conversation is specific: one vehicle, one destination, one quotation broken into its layers — and then the pack either holds or does not.
- Name the target market and the operating model — imported or locally assembled.
- Check whether the market is among the current packs, and which branch of the pack applies.
- Bring one recent quotation and break it into tax layers; the missing layer is usually where the margin went.
- Walk one vehicle through the chain in the demo and find the stage that breaks.
- Confirm with your advisers which documents must be in place before shipment for that market.
Is your target market covered?
Tell us the country and city; we will confirm which pack applies and what has to be validated before the first shipment.
Book a 30-minute walkthrough