On this page
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 reaches its functional or scalability limits 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 define the required capabilities. Integrated finance, extensibility, globalization and compliance, and long-term investment help determine system fit. Delivery capability, data migration and acceptance criteria determine project risk.
The sections below explain how company scale and industry affect management requirements, how to organize selection, when an international ERP may be appropriate, how system types differ, and which implementation and control requirements should be verified.
Define Company Scale, Industry and Management Priorities
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).
As revenue, entity count and process complexity increase, management priorities extend from cost and inventory control to multi-organization coordination, process traceability and group governance. The table identifies the primary management requirement for each scale and industry context.
| 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 | Batch and process traceability, 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: as revenue, organizational scale and industry complexity increase, management priorities move from individual functions to cross-functional coordination and group governance. 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 increase materially.
"Compliance" actually has two layers, best kept separate. One is operational and management compliance — internal controls, approvals, permissions, audit trails and data traceability needed to meet audit and regulatory requirements. The other is global tax and accounting compliance — multiple currencies, multiple accounting standards and group consolidation needed to support cross-border operations and consolidated reporting. Both become more important as the business scales, 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.
Establish a Reviewable Selection Process
Once the required capabilities are clear, management needs a common basis for comparison. Selection often drags on because companies jump straight into a loop of "watch demos, compare quotes, listen to pitches" without connecting requirements, products and delivery teams. The following work should form one complete selection record.
Step 1 · Profile: get clear about yourself first. On a single page, write down your industry, current size, three-year goals, your three most important management requirements, and whether you plan to expand globally, pursue an IPO or make acquisitions. This is the basis for every later assessment. Without a clear profile, subsequent comparisons may use the wrong criteria.
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.
Shortlist: focus evaluation resources on suitable candidates. 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 different results. Before signing, confirm who will implement it, how many comparable projects the team has completed and who is accountable for issues. A team with relevant industry experience and defined accountability across blueprint, configuration, testing and go-live may be more important than minor differences in product features. Weight this step no less than choosing the product itself.
TCO comparison: assess long-term investment, not only 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.
Determine Whether the Company Needs an International ERP
Not every company needs an international ERP. The following assessment helps determine whether business complexity, growth objectives and compliance requirements have moved beyond what the current system can support.
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.
Compare the Appropriate Scope of Different ERP Types
Setting brands aside, growing companies commonly evaluate 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). Compare management controls, extensibility, global tax compliance and long-term investment. 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) |
|---|---|---|---|
| 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 |
| 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; one system carries a company from growth stage to scale, reducing the cost of replacing systems midway |
| 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 |
| 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; complex scenarios can be compared on a common five-year total-cost basis |
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.
These considerations become clearer in actual projects (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 that as business complexity and compliance requirements increase, ERP selection should focus on support for organizational and operational growth together with the controls needed for standardized management.
Verify Implementation and Control Requirements Beyond the Demo
A product demonstration mainly shows standard processes. Project success also depends on the delivery team, integrated business and finance data, system controls and data migration. Put the following items in the evaluation record and ask each candidate to explain or demonstrate them.
Delivery quality: software capability must be delivered by 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.
Integrated finance: verify that source documents create accounting records in real time. 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."
Compliance and traceability: verify authorizations, audit records and end-to-end transaction history. 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.
Data migration: define scope, responsibility and acceptance in the contract. 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.
Carry these checks into both the selection record and the contract: who will staff the implementation team, how integrated finance and audit trails will be verified, and who will prepare, convert, reconcile and accept migrated data. The final decision then covers both product and delivery.
In Closing
ERP selection establishes the system foundation for the company’s operating and management requirements over the next three to five years. Define management priorities first, compare candidates using common requirements and cost assumptions, and verify implementation capability, data migration, controls and integration.
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 providing ERP implementation and support for growing companies since 2009. MTC Group has served 760 clients and supports businesses across 50+ countries and regions. SAP Business One is SAP's integrated ERP for small and growing companies, managing finance, sales, procurement, inventory, production and analytics in one system. Use the online TCO estimator to model five-year total cost of ownership, or discuss selection and implementation scope with an MTC consultant.
Source note: cases are drawn from MTC implementation projects and anonymized for client confidentiality. System types are categorized by capability and positioning and, except for SAP Business One, do not refer to specific brands.