China+1 in Practice: Running a Japanese Plant and an India Plant on One ERP

The Situation

Picture a mid-sized precision components maker headquartered in Nagoya. For 15 years it has run a single factory in Aichi, building valve assemblies for automotive Tier 1 buyers. The Japan operation is mature, the consumption tax workflow is settled, and the plant manager knows every work center by name.

Then the board makes the call. Customers want a China+1 supply footprint, and India is the chosen destination. Within 18 months the company opens a second plant outside Pune to assemble a subset of the same valve families for Indian and ASEAN buyers. Suddenly there are two legal companies, two currencies, two tax regimes, and one stubborn question from the COO.

How do we run both plants on one system without doubling our back office?

This is the cross-border scenario more Japanese manufacturers now face. The number of Japanese companies operating in India is roughly 1,500, with manufacturing accounting for about half of them, and the explicit national target is to reach 5,000 Japanese companies in India by 2029. The shift is real, and the system choice behind it decides whether the second plant becomes a growth engine or a compliance nightmare.

The Challenge

The temptation is to bolt a second, locally popular tool onto the India operation and let headquarters reconcile everything in spreadsheets. That path fails fast. Three pain points show up within the first quarter.

First, the bill of materials drifts. The Aichi plant updates a component ratio, the Pune plant keeps building to the old recipe, and the cost variance only surfaces at month end. Second, tax breaks. Japan charges a 10 percent consumption tax on domestic sales, while India runs a multi-slab GST with input tax credit mechanics that have no equivalent in the Japanese chart of accounts. Third, visibility. The COO cannot answer a simple question like how many valve assemblies both plants will ship next week, because the two systems do not speak the same language.

The deeper problem is that two systems create two sources of truth. Inventory figures disagree, lot traceability breaks at the border, and the consolidated view of demand that a China+1 strategy is supposed to deliver never materializes. What the company actually needs is one ERP that lets each company operate independently under its own tax and currency rules, while sharing the manufacturing model that defines the product.

The Implementation

The Nagoya team chose to stand up both companies inside a single ERP, each as its own isolated organization with a dedicated data space. The same application, the same login screen, the same release cadence, but two clearly separated companies whose records never bleed into each other. The Japan company runs yen and consumption tax. The India company runs rupees and GST. Both share the same screens, the same approval patterns, and the same product master shape.

One shared manufacturing model

The foundation is a shared way to describe how a product is built. In the ERP, a bill of materials is a structured recipe that produces a defined base quantity of a finished product from a set of ordered component lines, each carrying its own product, quantity, and unit. A BOM carries an optional external reference field, which the Nagoya engineers use for their drawing number so the Pune team builds to the exact same specification. Because both companies live in the same application, a recipe refined in Japan can be replicated into the India company without rekeying components.

Work then flows through manufacturing orders. A manufacturing order is a production instruction that consumes raw materials from a source location, receives finished goods at a destination location, and carries a demand quantity in the finished product unit. Its lifecycle moves from DRAFT to CONFIRMED to COMPLETED, or to CANCELLED, and the operation field on each write drives the transition. The Aichi planner and the Pune planner use the same order shape, so a visiting COO can read either plant's production board without translation.

Controlled completion and lot traceability

The hard part of multi-plant production is keeping stock honest. When an order completes, the system deducts the raw materials from the source location with a manufacturing-out movement, validates or creates the inventory lot for any lot-managed finished product, and then receives the finished goods at the destination location with a manufacturing-in movement. Crucially, if a finished product is flagged for lot management, the order cannot complete without a lot assigned. The system blocks the completion rather than silently letting untraceable stock enter the warehouse.

For a valve maker selling into automotive, this matters. A recall in India has to trace back to the exact lot, the exact component batch, and the exact work order. Because both plants run the same lot model, with auto-generated lot numbers, expiry dates for first-expiry-first-out picking, and quarantine and blocked statuses, traceability is consistent across the border rather than dependent on which plant built the part.

Moving stock between companies

When subassemblies ship from Aichi to Pune for final assembly, the team uses an inventory transfer order. A transfer order records the intent to move stock from a source location to a destination location, requires the two to differ, and creates no stock movement on creation. The movement only happens when the lifecycle advances, so planners can stage cross-border shipments days ahead without distorting current inventory. Each order carries a responsible user, a delivery method, and an expected delivery date, which is exactly the discipline a multi-country operation needs.

Two tax worlds on one ledger

The India company configures GST with the tax rate structure it needs, while the Japan company keeps its consumption tax setup. The accounting engine computes tax per line using the configured rate, so the same journal-entry logic produces correct GST output in rupees for the India company and correct consumption tax in yen for the Japan company. There is no parallel spreadsheet, no manual conversion at period close, and no second license for a regional tool.

The Outcome

Within two quarters of the Pune plant going live, the company reported measurable improvements in how the two plants operated together. BOM variance between the two companies dropped to near zero, because both now built from the same recipe definition with the drawing reference embedded. Month-end close time fell from roughly 12 working days to under 8, as the finance team no longer reconciled two disconnected stock ledgers by hand.

On the compliance side, the India company filed its first GST returns directly from the ERP's tax-rated lines, and the Japan company continued its consumption tax workflow unchanged. Lot-based recall drills that once took the quality team a full day across paper records now resolved in minutes, because each finished lot links back to its manufacturing order and component lots inside one system. For a company of this size, the avoided cost of a second tool, a second integration project, and a second support contract was estimated in the tens of millions of yen over three years.

The strategic payoff was larger than the savings. The COO finally had the single dashboard the China+1 strategy promised, total demand across both plants, total output, and total inventory, without a single spreadsheet in between.

Lessons from a Dual-Market Move

Three lessons stand out for any Japanese manufacturer weighing the same path.

Treat the product definition as global and the tax definition as local. The BOM, the manufacturing order, and the lot model should be identical across companies so engineers and planners speak one language. The tax rates, currency, and chart of accounts should stay company-specific so each entity stays compliant. A good ERP lets you split exactly along that line.

Insist on enforced traceability, not optional traceability. If lot assignment can be skipped under deadline pressure, it will be, and the first recall will expose the gap. The right system blocks completion when a lot-managed product has no lot, which is the only behavior that holds up under audit.

Move stock on intent, not on hope. Cross-border transfers need staging, approval, and an expected arrival date. An inventory transfer order that records intent separately from the actual stock move is what keeps both plants' inventory figures believable while goods are in transit.

Is This Right for Your Business?

This approach fits manufacturers who are adding a second company, not just a second warehouse. If you are opening an India plant, forming a joint venture, or spinning out a sales entity for a new market, the isolated-companies-on-one-system model is designed for your situation. If your expansion is purely domestic, a simpler single-company setup will do.

It also fits teams that have outgrown stitched-together tools. If your finance team spends the last week of every month reconciling two systems, and your quality team cannot trace a lot across plants, you are already paying the cost of two sources of truth. Consolidating onto one ERP with isolated companies is how you stop paying it.

Frequently Asked Questions

Does running two companies on one ERP mean their data is mixed together?

No. Each company operates as its own isolated organization with a dedicated data space, resolved per request, so the two companies never see each other's transactions. Users get one application to learn, but the records stay cleanly separated for audit and compliance.

Can the same system handle GST and consumption tax at the same time?

Yes. Each company configures its own tax rates and currency. The accounting engine computes tax per line from the configured rate, so one company produces GST-rated journals in rupees while the other produces consumption-tax-rated journals in yen, with no manual conversion.

How does lot traceability work when components move between the two plants?

Each finished product flagged for lot management gets a lot with a number, an optional expiry date, and a status such as active, quarantined, or blocked. When a manufacturing order completes, the system validates the lot before receiving the finished goods, and cross-plant moves happen through transfer orders that record intent before moving stock, so traceability survives the border.

Key Takeaway

A China+1 move only pays off if both plants run on one source of truth. Share the BOM and the work order model across companies, keep tax and currency local, enforce lot traceability at completion, and stage cross-border stock on transfer orders. That is the difference between a second plant that scales and a second plant that drowns you in reconciliation. If you are planning an India expansion, Kikan System gives you isolated companies, GST and consumption tax on one ledger, BOM-driven manufacturing orders, and enforced lot tracking, all in one ERP.

Start Running Both Plants on One System

Kikan System is built for manufacturers expanding across markets. Stand up your Japan company and your India company in one ERP, configure GST and consumption tax per entity, and let your teams share BOMs, work orders, and lot tracking without mixing data. The free plan supports up to 2 users, no credit card required, so you can model both plants before you commit. Get started at /#get-started.