Crossing RMB 100 million in revenue but not yet reaching 1 billion is the most critical and most failure-prone stage for a growing company. It is moving from "scrappy growth" to "scaled operations." Orders, product lines, factories, subsidiaries and overseas business pile on one after another, and management complexity rises faster than linearly. Yet many companies still run on startup-era systems: a few spreadsheets, an inventory tool used for years, and operations and finance kept as two separate ledgers. More importantly, this stage sees a sharp rise in demands for governance and compliance. If internal controls, auditability and data traceability fall behind, future risks around an IPO, cross-border operations and regulation are magnified many times over. By the time management notices that "reports are always two weeks behind," "the books never match the warehouse," or "a new business unit and the system can't keep up," the system is already dragging on growth.
When it comes time to replace the ERP, the decision is not a binary choice between "cheap domestic" and "expensive international." There are three real options: a domestic ERP, an international ERP built for large groups, and an international ERP purpose-built for small and growing companies. The cost of choosing wrong is real: either you over-invest in capabilities you never use, or the system hits a ceiling within three to five years and you are forced to start over.
The guiding principle: ERP selection is not about "picking a brand," but about working backward from where the company aims to be in three to five years to determine what level and what type of system you need now. Scale and industry complexity decide the "level"; integrated finance, extensibility, globalization and compliance, and cost decide the "type." And the real costs and risks mostly hide outside the contract price.
The five parts below answer, in turn: what level fits my size (1), how to decide step by step rather than on gut feel (2), whether you have reached the point of needing an international ERP (3), how the three system types actually differ (4), and where the hazards beyond the contract lie (5).
1. Place Yourself First: Size × Industry Sets the Management Priority
Two companies both at "RMB 300 million in revenue" — a standard-parts distributor and a manufacturer with four production lines that exports — have completely different management priorities. Two things decide this: scale (number of users, organizational complexity) and industry (process characteristics and compliance intensity).
Each revenue step shifts the management priority: from "doing one thing well" (getting costs right, managing inventory) to "keeping the whole thing under control" (multi-organization coordination, end-to-end traceability, group governance). The table below is not a feature list; it shows the one thing that most deserves your attention once you land in that cell.
| Revenue band | Trade / Distribution / Export | Discrete manufacturing / Equipment | Process manufacturing / Food | High-tech (electronics / semiconductors / new energy) |
|---|---|---|---|---|
| RMB 100–300M | Inventory and cash turnover, clean receivables/payables | Costs computed accurately, on-time delivery | Batch traceability, recipe cost control | R&D and project cost, fast response |
| RMB 300–600M | Multi-warehouse/multi-org coordination, channel and price control | Sales-production coordination, refined quality and cost | End-to-end traceability and quality compliance | R&D collaboration and fast iteration, export compliance |
| RMB 600M–1B | Multi-format group governance, cross-border and compliance | Multi-plant coordination, group integration | Group-level traceability, regulatory and audit readiness | Global supply chain, multi-org auditability |
How to read it: the higher the revenue and the further right the industry, the more the priority shifts from "doing one thing well" to "keeping the whole thing under control." One caution in particular: RMB 100 million to 1 billion is exactly when a company moves from scrappy growth to scale, and if governance and compliance capabilities fall behind, future risks around an IPO, cross-border operations and audits are magnified many times over.
"Compliance" actually has two layers, best kept separate. One is operational/management compliance — internal controls, approvals, permissions, audit trails and data traceability, which determine whether you can withstand audits and regulators. The other is global tax and accounting compliance — multiple currencies, multiple accounting standards, group consolidation, which determine whether you can go global and consolidate the books. Both become more non-negotiable as you scale, and both are exactly where entry-level and many domestic systems tend to fall short.
A rough dividing line: between RMB 50 million and 100 million with standard processes, an entry-level or domestic integrated system is often enough; once you pass 100 million, or have earlier needs around going global, multiple organizations, strong traceability and compliance, an international ERP is usually the safer starting point.
A better gauge than the revenue figure is the management signals: the business is growing fast, Excel and entry-level systems can no longer keep up, you run multiple warehouses and organizations, you are going global or preparing for an IPO. When these signals appear, it is usually time to upgrade.
2. A Five-Step Process: Turn "Gut Feel" into "Recomputable"
Once the required capabilities are clear, the question is how to choose. Selection often drags on because companies jump straight into a loop of "watch demos, compare quotes, listen to pitches" with no through-line. The five steps below turn selection into executable, reviewable decisions.
Step 1 · Profile: get clear about yourself first. On a single page, write down your industry, current size, three-year goals, your three most critical pain points, and whether you will go global / IPO / acquire. This is the basis for every later judgment. Without a clear profile, every later comparison is comparing the wrong things.
Step 2 · Requirements list: separate "must-have" from "nice-to-have." List requirements in three tiers: must-have (missing it means elimination), bonus (better to have), and skippable (don't pay extra for it). The hard part is honest sorting — a good share of what most companies list as "must-have" is never actually used. The more disciplined the list, the harder it is for add-on features to throw off your judgment.
Step 3 · Shortlist: narrow candidates to three or fewer. Filter with the requirements list and keep only products that meet every "must-have," capped at three. Too many candidates dilute the focus and quality of later evaluation.
Step 4 · Choose an implementation partner: you are buying not just software, but delivery capability. The same product, implemented by different teams, can produce vastly different results. Before signing, confirm: who implements it, how many similar projects the team has completed in your industry, and who is accountable when problems arise. A team with industry experience that sees the project through end to end is often worth more than minor differences in product features. Weight this step no less than choosing the product itself.
Step 5 · TCO comparison: count the five-year total, not the first-year quote. Put shortlisted candidates under the same five-year total cost of ownership (TCO — the full cost of running the system over five years) standard. A low quote often pushes cost downstream (see Part Five). A complete five-year TCO should include at least:
- Software licenses (users × unit price × module factor)
- Implementation (typically a multiple of licenses; the more complex, the higher)
- Annual maintenance (usually around 20% of licenses)
- Deployment (cloud / hybrid / on-premise — the differences are not small)
- Internal operating cost (in-house IT staff, servers and day-to-day operations — the most commonly omitted item)
Working this out in advance beats discovering after signing that the costs keep adding up. If you want a quick range first, use our online TCO estimator to run the numbers by users, modules and deployment type.
3. Self-Assessment: 10 Questions on Whether You Need an International ERP
Not every company needs an international ERP. The 10 questions below are a quick self-test of whether your complexity and growth ambitions have reached the point of needing one. Score 1 point for each "yes," then read the total against the conclusions.
Check the statements that fit your company — 1 point each. Your total and the matching conclusion update automatically below.
Your result
Your needs are mostly domestic, single-entity and standard. An entry-level or domestic integrated ERP will do; focus on value for money and local service, and don’t pay for capabilities you won’t use. (Frankly, when the business is simple enough, a suitable entry-level system is plenty.)
You are at the upgrade tipping point. Evaluate an international ERP built for growing companies first, and anticipate whether the next three years will trigger more “yes” answers — you are likely standing at the “do it once, properly” crossroads.
Complexity, compliance and extensibility demands are already bearing down. An international ERP is the safer choice, and the earlier you deploy, the more you save on a second migration later.
4. Comparing Three System Types Across Four Dimensions
Setting brands aside, put the three options a growing company faces side by side — a domestic ERP, an international ERP built for large groups, and an international ERP purpose-built for small and growing companies (SAP Business One is one such system) — and compare them across four dimensions. There is no absolute better or worse, only fit.
| Dimension | Domestic ERP | Large international ERP (for big groups) | SAP Business One (international ERP for growing companies) |
|---|---|---|---|
| 1. Integrated finance & governance | Strong fit with domestic tax/accounting; but operations and finance often need multiple systems stitched together, with limited deep linkage | Strong integrated finance and the most complete internal controls; heavy for SMEs | A digital backbone for integrated finance: source documents post journal entries automatically, finance through production share one set of data, faster close and real-time reports; complete controls, approvals, permissions and audit trails — solid operational compliance |
| 2. Extensibility & growth | Light and flexible, fast custom development; extensibility strains as scale and complexity rise | The most comprehensive extensibility, built for large groups; growing companies rarely use it fully | Extends continuously on a unified platform as the business grows, with new scenarios and external systems connected on demand — holds firm yet opens up; one system carries a company from growth stage to scale, with no need to start over midway |
| 3. Globalization & tax compliance | Timely updates for domestic tax and localization; limited support for cross-border and multiple standards | The most comprehensive global tax compliance; localization needs considerable configuration | Mature China localization, plus native support for multiple currencies, languages and accounting standards and proven group consolidation; smooth fit for going global and connecting with a foreign parent |
| 4. Cost & investment | Low first-year threshold, quick to start; under complex needs, later customization and maintenance can overtake | Front-loaded investment and implementation timelines are high for SMEs | Priced for growing companies, controllable upfront cost and quicker go-live; in complex scenarios the five-year total works out more economical |
This table is not meant to argue "international ERP is better." It points out a commonly misunderstood fact: an international ERP does not equal "expensive and heavy." International ERPs built for large groups are indeed heavy for SMEs, but a system like SAP Business One is exactly what SAP built for small and growing companies — international-grade integrated finance, governance and extensibility, in a size a growing company can afford, deploy quickly and grow with. For companies in the RMB 100 million to 1 billion band, it is often the best fit of the three.
Seen in real deployments, the four dimensions get clearer (all are growing companies, anonymized):
- Integrated finance: An eco-friendly coatings company serving mainly a regional market used to handle operations manually, with the financial close lagging more than 20 days. After consolidating onto an integrated-finance international ERP, the close moved up to 3 days and the on-time delivery rate rose from 62% to 85%.
- Extensibility & growth: An HVAC home-comfort services company with 40 specialty stores used one system to support revenue growth from RMB 200 million all the way to 1 billion, optimizing SKUs from 12,000 to about 7,000 and doubling inventory turnover — the system never became the bottleneck.
- Compliance & traceability: A frozen-food company with five independently accounted legal entities used an international ERP to achieve integrated finance and reinforce compliance to listing standards, with monthly financial reports generated automatically and the monthly business review brought forward by a week.
The common thread is one line: when complexity and compliance demands truly bear down, "able to scale, able to stay compliant" is the dimension that matters most in selection.
5. A Checklist of Traps: Four Questions Easily Glossed Over in a Demo That Decide Success
Four questions tend to be waved past during selection by a polished demo, yet they decide whether the project succeeds after go-live. Turn them into an evaluation checklist and verify each with your candidates.
Trap 1 · Delivery quality: you buy software, but you depend on the team. The same product yields markedly different results across implementation teams, and the people who sign the deal are often not the people who deliver. Before signing, confirm: who implements it, whether the team is professional and committed, and who owns problems. This is exactly why Part Two lists "choose an implementation partner" as its own step — delivery capability decides outcomes more than minor differences on a feature list.
Trap 2 · Truly integrated finance: is operations actually linked to finance? Many systems call themselves "integrated," but operations and finance are not one set of data. True integrated finance means that the moment a source document is created, it automatically generates the journal entry, sharing one data backbone. The test is direct: enter a transaction on the spot and see whether the journal entry is generated automatically in real time, or has to be batch-imported or manually patched at month-end. The difference decides whether you get a "real-time operating ledger" or "books that are two weeks behind."
Trap 3 · Compliance and traceability: from RMB 100M to 1B, the standards only tighten. The further a company scales, the more regulatory, audit and group-governance demands grow. Verify on the spot whether the system can: control permissions and approvals by tier, keep auditable trails of key operations, drill a single reported figure back to its original source document, and trace batches and serial numbers both ways. This is a hard threshold for listing, cross-border operations and regulated industries — discovering the system can't do it right before an IPO or audit is extremely costly.
Trap 4 · Data migration: the most underestimated workload. Cleanly migrating historical data from the old system to the new one is almost always the most underestimated part of a project. Customers, materials, payables/receivables, inventory and historical documents vary in quality and definition, and the cleansing and mapping effort routinely exceeds expectations. At the selection stage, write the scope, responsibility and acceptance criteria for data migration into the contract, rather than discovering its complexity right before go-live.
Map the four traps back to the five-step process: "delivery quality" is guarded by "choose an implementation partner"; "truly integrated finance" and "compliant and traceable" should be tested live during shortlist evaluation rather than taken on promise; and the scope, responsibility and acceptance for "data migration" go into the contract. The framework closes the loop.
In Closing
From RMB 100 million to 1 billion, ERP selection is ultimately a decision about "preparing for the next three to five years." Getting it right rests on a framework you can recompute yourself, not on who tells the better story: use the size × industry matrix to set required capabilities, walk the five steps, use the 10-question self-test to judge whether you need an international ERP, use the three-way comparison to see the real differences, and use the trap checklist to avoid the hazards beyond the contract.
Keep the method in your own hands, and the selection won't be swayed by sales talk.
MTC (Shanghai MTC Information Technology) is a SAP Business One gold partner, with 17 years focused on ERP implementation for growing companies, serving 8 business scenarios, more than 50 countries and regions, and over 300 enterprises. SAP Business One is SAP's integrated ERP for small and growing companies, managing finance, sales, procurement, inventory, production and analytics on a single data backbone. To apply this framework to your own company, use the online TCO estimator to compute your own five-year total, or talk with an MTC consultant.
Cases in this article come from MTC implementation experience, with data anonymized. "Domestic ERP," "large international ERP" and "international ERP" are categorized by capability and positioning; aside from SAP Business One, they do not refer to any specific brand.