A Singapore manufacturer running one factory does not need a multi-site ERP. A single inventory pool, one production schedule, one set of cost centres — a single-site system handles this cleanly.
The problem starts at the second site. A second factory in Tuas. A production facility in Johor Bahru. A finishing operation in Batam. A warehouse in Jurong. The moment production or inventory exists in more than one location, the single-site system breaks in specific, predictable ways.
What Breaks at Two Sites
Inventory becomes misleading. A single inventory pool shows 500 units of material X "in stock." But 300 are in Tuas and 200 are in JB. The planner at Site A sees 500 and plans accordingly — then discovers the material is at Site B. The production order cannot start. The delivery date slips.
Multi-site inventory requires location-specific stock records. Each site has its own on-hand balance. Transfers between sites are tracked as a distinct transaction type — with lead time, transport cost, and customs documentation (for cross-border moves).
Production scheduling loses visibility. A single-site scheduler sees all machines and all jobs. A multi-site scheduler needs to see capacity and workload per site, plus the dependencies between sites (Site A produces semi-finished goods that Site B assembles). Without per-site scheduling, jobs get assigned to the wrong site or conflict with capacity that does not exist.
Cost tracking becomes inaccurate. Each site has different cost structures — different labour rates, different overhead rates, different utility costs. A single-site cost model allocates overhead evenly. A multi-site operation needs site-specific cost centres so that job costs reflect where the work was actually done.
Cross-border complexity appears. For Singapore manufacturers with production in JB or Batam, the second site introduces currency conversion (SGD/MYR/IDR), cross-border transfer pricing, import/export documentation, and GST treatment on cross-border movement of goods. None of this exists in a single-site system.
What Multi-Site Actually Requires
A multi-site manufacturing system needs five capabilities that a single-site system does not:
1. Location-specific inventory. Every stock item has a quantity per location. Transfers between locations are a distinct transaction with approval, packing, transport tracking, and goods receipt at the destination. The system must show "in transit" stock that has left one site but not arrived at the other.
2. Per-site production scheduling. Each site has its own machines, operators, and capacity constraints. The scheduler must handle both — jobs that run entirely at one site and jobs that span sites (semi-finished at Site A, assembled at Site B). Cross-site dependencies need explicit modelling.
3. Site-specific cost centres. Labour rates, overhead rates, and utility costs differ by site. Job costing must allocate costs based on where the work was performed, not an average across all sites. Consolidated reporting rolls up site-level costs for management visibility.
4. Inter-company transactions (for cross-border). When Site A in Singapore sends materials to Site B in JB, the transaction is an inter-company sale/purchase, not just an inventory transfer. Transfer pricing, customs documentation, and GST treatment apply.
5. Consolidated reporting with drill-down. Management needs to see total revenue, total WIP, total inventory — but also needs to drill into per-site performance. Which site is more efficient? Where is the margin leaking? Which site has excess inventory?
The Singapore + JB / Batam Pattern
The most common multi-site pattern for Singapore SMB manufacturers is Singapore HQ + a production facility in Johor Bahru or Batam. The economics are straightforward: lower labour cost in JB/Batam, customer-facing operations and high-value work in Singapore.
This pattern introduces specific requirements:
Currency handling. The system must handle SGD for Singapore operations and MYR or IDR for the second site. Purchase orders to local JB suppliers are in MYR. Invoices to Singapore customers are in SGD. Job costs must be expressed in a base currency for comparison.
Cross-border transfer documentation. Material moving from Singapore to JB requires export/import documentation, customs declarations, and potentially duty calculation. The system needs to generate or reference these documents.
Time zone awareness. A small detail that causes real confusion: JB and Singapore are in the same time zone, but Batam is UTC+7 (one hour behind). Production schedules, shift times, and delivery deadlines must be site-local.
GST treatment. Materials exported from Singapore to JB are zero-rated for GST. Finished goods imported from JB to Singapore may attract GST. The system must apply the correct GST treatment based on the direction and nature of the cross-border movement.
Scoping a Multi-Site Build
The scope of a multi-site system depends on how the sites interact:
Independent sites (shared reporting only). Each site runs its own production with its own materials and its own customers. The only shared requirement is consolidated reporting. This is the simplest multi-site scope — essentially two single-site systems with a shared reporting layer.
Dependent sites (material flow between them). One site produces semi-finished goods that another site consumes. This requires inter-site transfer management, cross-site production scheduling, and accurate lead time modelling for the transfer.
Integrated sites (shared customers, shared materials). Both sites serve the same customers, draw from shared material pools, and need coordinated scheduling. This is the most complex — and the most common pattern for Singapore + JB operations.
Start Canyon scopes multi-site systems based on the actual site interaction pattern. A two-site build with independent sites and shared reporting might run S$18,000-S$22,000. A fully integrated Singapore + JB operation with cross-border transfers and consolidated costing runs S$25,000-S$35,000. The discovery phase identifies the exact scope.
The free diagnostic at startcanyon.com/diagnostic captures multi-site complexity as part of the assessment. If you are planning a second site or already running one without system support, the diagnostic will flag the specific gaps.