Infor in China vs Kingdee: Manufacturing Localization

The short answer

Manufacturing is a different comparison from the finance-led ones, because the operational depth a plant needs is not the same thing as the compliance depth a China entity needs. Infor's advantage is vertical fit: production, scheduling, costing, and distribution logic that suits complex manufacturing environments. Kingdee's advantage is that Chinese compliance is native rather than a project.

For a China plant the practical question is therefore not 'which is better' but 'where does the boundary sit'. Many operations run operational depth and local compliance in different layers, and the boundary is the decision that determines the running cost.

Why manufacturing is a different case

In a trading company, the ERP is essentially a finance and logistics system, and the compliance requirement is the dominant one. In a plant, the ERP is also the system of record for production: bills of materials, routings, work orders, material issues, and cost roll-ups. Those functions have to fit the actual manufacturing process, and a poor fit is not a compliance problem — it is a daily operational problem that erodes trust in the system.

This is why manufacturing selections often favour vertical strength over compliance convenience. A system that models the plant correctly but needs a localization layer can be made to work. A system with perfect compliance that does not match the shop floor will be worked around, and once the plant stops trusting the system, every downstream control degrades.

What Infor brings to a China factory

Infor's position in the market is vertical and industry-focused rather than generalist, with particular depth in manufacturing and distribution environments. For a plant with complex production, mixed modes, or heavy distribution requirements, that depth shows up in how well the system models the operation without extensive customisation.

For a China plant the relevant advantages are usually three: production and costing models that match the process, sector capability that does not require building industry logic from scratch, and a platform that a group may already run elsewhere. The relevant weakness is the same as every global platform's in China — invoicing, tax, and statutory reporting are not native.

Where the localization gap appears

For a manufacturing entity the gap is wider than for a pure trading company, because more flows touch the tax system and more of them are time-critical.

• Sales invoicing, including reversals, at the volume a plant generates.
• Purchase invoice verification against a large supplier base before payment runs.
• VAT reconciliation across a high transaction count, where manual matching becomes infeasible.
• Statutory statements and the annual settlement, which must reconcile with the tax filings.
• Export refund processing where the plant exports, which links production records to customs and refund documentation.
• Payroll for a larger workforce, with city-specific social insurance rules.

The last two are the ones that make manufacturing harder than trading. A plant that exports has a compliance chain running from production through customs to refund, and a gap anywhere in that chain is expensive to close after the fact. Our guide to export tax rebate in an ERP describes the refund side; the customs documentation side is covered in customs declaration integration.

What Kingdee brings on the shop floor and in finance

Kingdee's positioning spans small business to large enterprise, with manufacturing coverage within its product lines. For a China plant its advantage is not usually that it out-models a vertically specialised platform; it is that the compliance layer is native and the support organisation is local and compliance-focused.

For many China manufacturers that trade-off is the right one, because their production complexity is moderate and their compliance load is high. The judgement to make honestly is where on that spectrum the plant sits: a plant with genuinely complex production will feel the difference in operational fit, while a plant with straightforward production but heavy domestic and export compliance will feel the difference in the finance function.

The flows that decide it

For a manufacturing entity, score both platforms on the operational and compliance flows together rather than in separate evaluations, because the decision is about the boundary between them.

• Does the production model fit the actual process — bills of materials, routings, mixed modes, and rework?
• Does the costing method produce figures the business recognises and can price from?
• Can a sales invoice be issued and reversed from the system at production volume?
• Does ledger VAT reconcile to the invoice pool without manual matching?
• Are statutory statements produced from the books, and does the annual settlement reconcile?
• If the plant exports, does the refund and customs documentation flow connect to production records?
• Who maintains the layer that is not native, and what does that cost per year?

Shop-floor systems and the MES question

Most plants of any size run something on the shop floor that is not the ERP: a manufacturing execution system, a quality system, or a custom data collection layer. The interface between that and the ERP is where data quality is won or lost, and it is a bigger determinant of outcomes than the choice between two ERP vendors.

The practical rule is to define the interface contracts early and to decide which system is the source of truth for each data element. Plants that leave this ambiguous end up reconciling production reporting against inventory by hand, which defeats the purpose of having integrated systems at all.

Scenario: a foreign-owned plant serving group customers

If the plant supplies group entities or group customers, the reporting obligation is heavier and standardisation matters more. In that case the operational depth of a vertically specialised platform, combined with a group-standard reporting model, often outweighs the compliance disadvantage, provided the localization layer is funded and owned.

If the plant is largely self-contained and sells into the domestic market, the balance moves the other way: the compliance capability carries more weight, and a domestic platform with adequate production coverage is frequently the lower-risk choice. Our scenario framing in the SAP vs Kingdee comparison applies here with the compliance weight increased.

Scenario: a China-owned plant serving domestic and export customers

This is the case where the export chain matters most, and where compliance depth compounds: the plant files domestically, exports, and claims refunds, all from the same production records. Domestic platforms generally carry more of this in the product, and the argument for choosing one strengthens with export share. The counter-argument is operational fit, and it only wins if the production process is genuinely complex enough that a generalist model would need heavy customisation.

Cost and continuity

The cost comparison follows the same shape as elsewhere, with one manufacturing-specific addition: the integration between the ERP and the shop-floor systems is itself a maintained asset, and poorly bounded interfaces generate recurring reconciliation work.

• Licence and implementation, comparable across options and rarely the deciding line.
• Localization integration for tax and invoicing, recurring, on any global platform.
• Shop-floor interface maintenance, which scales with how loosely the boundary was defined.
• Internal capacity to own the reconciliation between operational and financial views.
• Partner continuity, which decides whether the configuration can still be changed in year three.

Verdict

If the plant's production is complex and it serves a group with standardised reporting, a vertically strong global platform with a properly funded localization is usually the better fit. If production is moderate and the domestic and export compliance load is heavy, a domestic platform is usually the lower-risk choice. The decision is about where to put the boundary, and the boundary has to have an owner. For the operational and compliance requirements in full, see our ERP checklist for foreign companies in China and, for manufacturing-trading hybrids, manufacturing and trading hybrid ERP.