From Spreadsheets to Scheduling in 90 Days

How New Zealand Discrete Manufacturers Are Replacing Excel Chaos With Cloud ERP

If you run a make-to-order or assemble-to-order manufacturing business in New Zealand, you already know the pressure. Every job is different, every customer has a specification, and the margin you quoted at the start depends entirely on how well you track cost, materials, and time as work moves through the floor.

You might manage most of that on spreadsheets. A tab for the production schedule. Another for open work orders. A separate file for job costing that someone updates manually at the end of each week, if there is time.

The system holds together until it does not. A job goes over cost because material usage was not tracked against the BOM. The schedule falls apart when a work centre is overloaded and nobody spotted it until jobs were already late. Month-end close takes two weeks because operations and finance are working from different data. 

The good news: NZ discrete manufacturers are making this transition faster than most expect. With Oracle NetSuite, a focused implementation covering production scheduling, job costing, and financials is achievable in 90 days. This post walks through what that looks like, what to expect, and the questions worth asking before you start.

Quick answer: Can a NZ discrete manufacturer go live on NetSuite in 90 days?

Yes. For discrete manufacturers moving from spreadsheets or entry-level software, a focused NetSuite implementation covering work orders, job costing, inventory, and financials is achievable in 90 days. The timeline depends on BOM complexity, the number of work centres, integration requirements, and how quickly your team can complete configuration sign-off. Project Salsa typically scopes 60–90-day implementations for SME manufacturers replacing manual processes.

Why Spreadsheets Fail Discrete Manufacturers Specifically

Spreadsheets are not inherently bad. They are flexible, familiar, and free. But discrete manufacturing generates a level of transactional complexity (jobs, components, operations, work centres, cost variances) that spreadsheets cannot manage reliably at scale.

Here is where discrete manufacturers typically hit the ceiling:

• Job costing is always an estimate: When BOMs, labour times, and material issues live in separate spreadsheets, the true cost of a job is only known after the fact, if at all. For MTO manufacturers quoting custom work, this means pricing risk and margin leakage on every order.
  

• The production schedule does not reflect reality: A static spreadsheet schedule cannot account for work centre capacity, queued jobs, or real-time material availability. When something changes on the floor (and it always does) the schedule requires manual intervention to stay current.
  

• MRP is done manually and is always out of date: Calculating what components, you need, when, across multiple open work orders requires someone to reconcile demand against stock and open purchase orders by hand. By the time the calculation is done, something has changed.
  

• WIP is invisible between updates: Without a system tracking material issues and labour bookings against each work order in real time, your WIP balance is a guess. This creates problems for job profitability reporting and for the Financial Controller trying to close the month accurately.
  

• There is no component-level audit trail: Who issued that material to the job? Was the correct revision of the BOM used? When was the routing last updated? Spreadsheets cannot answer these questions reliably, which creates problems when chasing a cost variance or responding to a quality non-conformance.
  

• Scaling creates exponential complexity: A 10-person workshop can manage on Excel. A 40-person operation running 50 concurrent work orders across multiple work centres cannot.
  

What NetSuite Brings to Discrete Manufacturing

Oracle NetSuite is a cloud-based ERP platform with a manufacturing module built around the core disciplines of discrete manufacturing: work orders, BOMs, routing, work centres, job costing, MRP, and financial integration. For NZ manufacturers, it replaces the patchwork of spreadsheets, accounting software, and manual processes with a single connected system.

Work Orders Tied to Customer Jobs

In discrete manufacturing, every production run traces back to a customer order or a replenishment trigger. NetSuite links sales orders directly to work orders, so production always knows what is being built, to what specification, and by when. For MTO and ATO manufacturers, changes to a customer order flow through automatically which means no manual re-entry, no version confusion between the sales team and the floor.

Multi-level BOMs and Routing

NetSuite manages single-level and multi-level bills of materials alongside the routing. The routing defines the ordered sequence of operations a job travels through, each assigned to a work centre with defined labour and machine rates. This gives you accurate material requirements at the point of planning, and cost accumulation at the operation level as work progresses. When a BOM or routing changes, the system holds the revision history.

Work Centre Scheduling and Capacity Visibility

NetSuite's WIP and Routings module gives production planners a drag-and-drop Gantt-style scheduler to sequence work orders across work centres, with visibility into queue and setup times at each operation step. Planners can identify bottlenecks and under-utilised resources before they cause delays on the floor.

This is based on infinite capacity scheduling. The system sequences work orders and surfaces conflicts but does not automatically constrain a schedule based on hard capacity limits. For manufacturers who need finite capacity scheduling, where the system enforces hard constraints and plans around them automatically, that capability is available in NetSuite's Advanced Manufacturing module.

For most NZ discrete manufacturers moving off spreadsheets, infinite capacity scheduling with a visual Gantt planner is a significant step forward from manual scheduling. Finite scheduling is available as a natural next step as operational maturity grows.

Job Costing and WIP in Real Time

This is where NetSuite delivers some of its clearest value for NZ discrete manufacturers. Rather than estimating job costs at close, NetSuite accumulates actual material issues, labour bookings, and machine time against each work order as production happens. WIP is live. Variance between estimated and actual cost is visible before the job closes, giving the Production Manager and the CFO the same picture at the same time.

For manufacturers quoting custom work, this closed loop between quoted cost and actual cost is the foundation of sustainable margin management.

MRP and Material Planning

NetSuite's MRP engine calculates component requirements across all open work orders and firm demand, compares them against current stock and open purchase orders, and generates shortage alerts and recommended replenishment actions. For Supply and Planning Managers, this replaces a manual weekly reconciliation with a system-driven signal so you know about material gaps before they stop the line.

Lot and serial traceability

Discrete manufacturers with traceability requirements, whether driven by customer contracts, industry standards, or internal quality processes, can track components and finished goods by lot or serial number through every stage of production. For manufacturers with more formal quality requirements, NetSuite's Quality Management SuiteApp extends the platform with structured QA processes including non-conformance workflows, inspection management, and hold management. When a quality issue arises, the full audit trail sits alongside the work order and financial transaction in one system.

Financial integration without the manual consolidation

Because NetSuite covers operations and financials in the same platform, COGS, WIP, and stock valuations update automatically as production moves. The Financial Controller does not need to reconcile a job cost spreadsheet against the accounting system at month-end. The numbers are the same numbers because they come from the same source.

What does NetSuite cost for a NZ discrete manufacturer?

NetSuite licensing is subscription-based, priced in USD per user per month. For NZ manufacturers, total cost of ownership includes the platform licence, manufacturing module tier, implementation services, and ongoing support. Project Salsa provides fixed-scope implementations with transparent pricing -- contact us for a quote specific to your business size and complexity.

The 90-day Implementation Roadmap

A 90-day NetSuite implementation is not a rushed deployment. It is a focused one. It works best when scope is well-defined upfront and the business has clear sponsorship for the project. Here is how a typical discrete manufacturing implementation is structured:

Days 1 to 30: Discovery and Configuration

The first phase covers requirements gathering, system design, and foundational configuration. Your implementation partner will work with your team to map current processes, define your chart of accounts, set up items, BOMs, and routings, configure work centres, and establish your job costing structure. This is the phase that takes the most input from your team. Plan for key people across operations, finance, and planning to be available.

Days 31 to 60: Build, Data Migration and Testing

With core configuration in place, attention turns to data migration and user acceptance testing (UAT). Your item master, customer and supplier lists, opening balances, BOM structures, and routing data are loaded and validated. Your team tests real production scenarios including work order creation, material issues, labour bookings, and job cost reporting to identify gaps before go-live.

Days 61 to 90: Training, Parallel Run and Go-live

The final phase focuses on role-specific training across the production floor, planning, and finance teams, any configuration adjustments from UAT, and a controlled go-live. Many manufacturers run a brief parallel period, keeping existing processes running alongside NetSuite for a short window, before fully cutting over.

What to Look for in a NetSuite Implementation Partner

Choosing the right implementation partner matters as much as choosing the right software. A technically capable partner who does not understand discrete manufacturing will cost you time and money. Here is what to evaluate:

• Discrete manufacturing experience: Ask whether they have implemented NetSuite for businesses with a similar operating model – MTO or ATO and comparable BOM and routing complexity. References from NZ manufacturers are particularly valuable.
  

• Fixed-scope proposals: Implementations that start as time-and-materials engagements frequently overrun. A partner who provides a defined scope, timeline, and price demonstrates confidence in their methodology.
  

• Post-go-live support: The first 30 days after go-live are critical. Confirm what support model is in place once the implementation team hands over.
  

• Local presence: A partner based in New Zealand means faster response times, an understanding of local compliance (GST, IRD reporting, NZ payroll), and the ability to be on-site when it matters.
  

• Ongoing product knowledge: Oracle NetSuite releases two major updates per year. A good partner will help you take advantage of new functionality -- not just keep the lights on.
  

Common Questions from NZ Discrete Manufacturers Considering NetSuite

We are not a large business. Is NetSuite the right fit?

NetSuite suits discrete manufacturers from around 30 to 300 staff, and often beyond. For NZ businesses, the threshold is less about headcount and more about operational complexity. If you are managing custom BOMs and routings, struggling with job costing accuracy, or spending significant time on manual planning and reporting, NetSuite is likely a strong fit.

Every job is different. Can NetSuite handle high-variation make-to-order manufacturing?

Yes. NetSuite supports make-to-order and assemble-to-order manufacturing models. Customer-specific work orders, configurable BOMs, revision-controlled routings, and job-level cost tracking are all supported within the standard platform. For manufacturers where no two jobs are the same, this is core functionality and not a workaround.

Our CFO wants to understand the financial case. What does the ROI look like?

For discrete manufacturers, the financial case typically comes from three areas: reduced job costing errors and the margin leakage that comes with underquoting custom work; faster month-end close as operational and financial data unify; and reduced inventory carrying costs as component stock accuracy improves. Project Salsa can walk through a cost-benefit model specific to your business as part of an initial conversation.

Will our team on the floor actually use it?

Adoption is always a risk with any system change. The most successful implementations pair strong executive sponsorship with role-specific training -- separate sessions for the production floor, the planning team, and finance -- and involve key users in UAT rather than presenting them with a finished system. Operators who have tested the system before go-live adopt it faster and with fewer issues.

What about our other systems such as estimating, CAD, payroll?

NetSuite has a robust API and a broad connector ecosystem. Common integrations for NZ discrete manufacturers include estimating and quoting tools, CAD/PDM systems for BOM import, EDI connections, and NZ payroll platforms. Your implementation partner should map integration requirements in the discovery phase -- not after go-live.

The Real Cost of Staying on Spreadsheets

There is a version of this decision where staying on spreadsheets feels safer. The system is known. It requires no training. It does not go down on a Monday morning.

But the cost of staying is real, it is just distributed across your business in ways that are easy to overlook. It is the margin you left on the table because a job cost was wrong. The material shortage that stopped a work centre because MRP was done manually and missed a gap. The quality escape that was not caught because traceability records were across three different files. The month-end close that takes two weeks instead of two days.

For most NZ discrete manufacturers making the move, the question is not whether to transition to cloud ERP but rather when, and with whom.

Ready to move beyond spreadsheets?

Project Salsa is New Zealand's dedicated Oracle NetSuite implementation partner for discrete manufacturers. Talk to our team about what a 90-day implementation could look like for your operation.

Contact us at projectsalsa.co.nz