Commercial model · Available now

A software product plus implementation service, itemised in six lines

No per-seat licence, no commission on the vehicles you export — agree the business scope first, then itemise six lines per project, so cost stays predictable when volume grows.

Prefer Chinese? The Chinese edition of this page carries the full source list and every numeric caveat. 本页中文版

  • ModelLicence + implementation service
  • QuotationSix itemised lines
  • Product lines16 implemented, start with any one
  • Delivery4–8 weeks single line · 6–12 weeks multi-line
  • PaymentStaged, terms agreed per project

1. Three engagement shapes, extend only when you need to

The amount depends on how many product lines, how many country packs and how you take delivery. Thirty minutes on your chain is enough to size the range. All sixteen product lines are implemented, so you can start with any one and have it quoted line by line.

ShapeWho it fitsWhat it coversDelivery
Single lineOne business chain, proving the link before widening1 product line (vehicle export dealership or used-vehicle export); core capabilities activate with the line; 1 country pack; five clients opened as neededAbout 4–8 weeks · remote delivery and online training · demo account first
Multi-lineExporters and overseas master distributors already running several chains3–5 product lines sharing one VIN master data; several country packs in parallel; group cockpit; open API to your existing systemsAbout 6–12 weeks · remote delivery plus on-site at key milestones · staged payment
GroupGroups with several legal entities, countries and storesProduct lines loaded on demand; multi-entity and multi-country consolidation; permissions and audit set to the group structure; bespoke country pack development and verificationScoped by assessment · delivery model and support tier agreed separately · chain mapping first

Multi-line is what most customers pick. Market counts are quoted per country pack and listed separately on the country packs page; anything outside the standard scope is assessed for effort and deliverables before it enters the contract.

2. How a quotation is split into six lines

We quote as a project: software product plus implementation service. We confirm the process, the usage boundary and the integration needs first, then give you scope, delivery plan and price. The six lines are itemised so nothing has to be argued about afterwards.

  1. Software product — licence and functional scope: which product lines, which modules, and the usage boundary (users, stores, legal entities).
  2. Implementation configuration — turning standard features into your process: process mapping, roles and permissions, document templates, base parameters, training.
  3. Data migration — historical data into the new system: source systems, field cleanup, import batches, verification, and who owns reconciliation.
  4. Custom development — anything beyond the standard features: effort assessment, deliverables, acceptance criteria, change process.
  5. System integration — connecting third-party systems: interface list, interface scope, third-party dependencies and who carries their cost.
  6. Ongoing service — operations and upgrades after go-live: support scope, upgrade policy, service hours, renewal boundary.

Market counts are quoted per country pack and listed separately on the country packs page. The standard product covers mainstream scenarios; customer-specific fields go into extension fields and customer-specific dropdown options into the data dictionary, both maintained by the customer. Requirements beyond the standard scope are assessed separately for effort and deliverables. Finance and insurance requirements (Haiyuan·Finance) are already integrated on the system side; the financial service itself is provided by licensed partners and quoted by them independently.

3. Why we do not take a commission per vehicle

Margins in export are thin to begin with. A per-vehicle or per-revenue share makes your system cost scale with volume and run out of control. A licence plus service keeps the SYSTEM cost predictable while your business grows — you do not pay us again for selling more cars.

The same logic applies to headcount: the licence states a usage boundary rather than billing seat by seat, so hiring a buyer or a documentation clerk does not trigger a new quotation.

4. Payment terms

Payment can be staged by delivery milestone. Group customers and ecosystem partners can agree a different settlement method; the terms sit in the contract, not in a public price list.

Nothing is invoiced before the scope is signed, and the six-line structure in the contract is the same one used in the quotation — so a change request is priced against a line that already exists instead of starting a new negotiation.

5. Look before you buy

All sixteen product lines are implemented. Vehicle export dealership and used-vehicle export open a demo tenant that needs no contact details — walk the demo path first, then talk price.

The demo tenant holds sample vehicles, customers, dealers and documents you can edit freely. If you already run spreadsheets, bring one to the walkthrough: comparing your own fields against the system's is the fastest way to see which of the six lines you actually need.

6. What the licence covers, and what it does not

Writing the boundary down first is cheaper than explaining it later.

ItemIn the standard licenceNotes
Product line licence (per line)IncludedCounted per line; all sixteen product lines are implemented, so any one can go first
Core capabilities (VIN record per vehicle, per-vehicle cost card, multi-currency, permissions and audit)IncludedActivates with the business line, not charged separately
Country pack (per country)Included, count per contractMarket-agnostic main process belongs to the core pack; a new market beyond the agreed scope is quoted separately
Implementation deliveryRemote included, on-site extraOn-site and overseas support by man-day; can be co-delivered with a partner to control cost
Data initialisation and historical migrationAssessed by scopeNumber of source systems, years of history and document volume decide the effort; itemised after the survey
Custom development (beyond standard features)Not includedAssessed by effort; deliverables and acceptance criteria written into the contract; configuring standard features is not customisation
Third-party fees (destination certification, customs broker, external interfaces)Not includedSettled directly by you or the third party; we do not collect on their behalf
Operations support and SLAOptionalTiered by service level and response time; can be bought for the critical period only
Finance and insurance service (Haiyuan·Finance)Not includedSystem integration already activates with the product line; the financial service is quoted independently by licensed partners

For anything not quoted, you get a range at the survey stage rather than at signature, so the effort is visible before you commit.

Quotation basis

Suanshu Haiyuan. Pricing model: software product plus implementation service. Shanghai Siyang Information Technology Co., Ltd.. https://eficien.com/en/pricing.html (English edition 2026-10-30). This page states no amount, percentage or currency figure on purpose: a number quoted out of context becomes a budget that has to be argued down later. The Chinese edition of this page (pricing.html) is the commercial reference; scope, deliverables and payment terms are agreed in the contract.

This page describes how a quotation is composed, not what it will cost. Ranges are confirmed in writing after the scope conversation, and nothing here is an offer or a commitment to a delivery date.

7. Questions we are asked most

The five that come up in almost every first conversation.

Is there a list price?

No. Scope decides the amount: how many product lines, how many country packs, and how you take delivery. Thirty minutes on your chain is enough for us to give the structure and a range, and the site deliberately publishes no list price that would be wrong for most readers.

Can we start with one product line and add more later?

Yes, and that is the usual path. All sixteen product lines share one VIN master data and one per-vehicle cost card, so a line added later is not a second system. The licence is counted per line, which is why starting narrow costs less than a group rollout.

Do you charge per user or per seat?

No per-seat licence. The licence states a usage boundary — users, stores, legal entities — and that boundary is what gets quoted. Adding a buyer or a documentation clerk does not trigger a new quotation.

What is not in the licence?

Custom development beyond the standard features, third-party fees (destination certification, customs brokers, external interfaces), on-site delivery, historical data migration effort and optional SLA support. Each is itemised separately so you can decline it explicitly.

How long does implementation take?

About 4–8 weeks for a single product line and about 6–12 weeks for three to five lines delivered in stages. Group rollouts are scoped after chain mapping, because the number of legal entities and countries moves the effort far more than the number of users.

Can we see the system before paying anything?

Yes. Vehicle export dealership and used-vehicle export each open a demo tenant with no contact details required. Walk it first: the pricing conversation afterwards is concrete instead of hypothetical.

Tell us the chain and we can size the range

Product lines, target markets and how you take delivery are enough: thirty minutes gets you the six-line structure, scope first and price second.

Book a 30-minute walkthrough