NetSuite for Equipment Manufacturers

An equipment manufacturer runs two businesses that share a building.

The first sells machines. Long sales cycles, engineering involvement, a build that runs for months, and a delivery date that carries penalties. The second sells parts and service to everything it has ever delivered. Steady, repeatable and usually more profitable.

Most systems get designed around the first and treat the second as something that happens afterwards. That is backwards relative to where the margin sits.

NetSuite for equipment manufacturers has to hold both

The design question is not which of those two businesses to build for. It is how to hold them in one system without either one distorting the other.

The machine business needs cost to accumulate against an order over months, with engineering changes, long lead items and progress billing. The aftermarket needs a record of what you delivered, fast parts availability and service scheduling.

They share an item master and a customer record and almost nothing else. Recognising that early avoids a lot of arguing about why one team reporting requirements make no sense to the other.

Configured products need a structure that scales

Very few equipment makers sell one fixed specification. There is a base machine and a set of options, and the combination is agreed during the sale.

The naive approach creates a new item for every configuration sold. It works for the first year and then the item master is unmanageable, nobody can find anything, and reporting by product becomes meaningless because every unit is its own product.

The better structure keeps a base product with configuration recorded against the order. That way you can report on the base machine across all its variants, and you still know exactly what each delivered unit contains. Our guide to configure price quote covers the sales side of this.

Cost has to accumulate where you can see it

On a build that runs for months, the question that matters is whether this order is going to make money, asked while there is still time to do something.

That means material, labour, subcontract and engineering time all posting against the order as they occur, compared against the estimate the quote was based on. Not reconciled at the end.

Estimate against actual, visible during the build, is the single most valuable report in this kind of business. It catches the orders that were underquoted while you can still manage the scope, and it teaches the estimating team which assumptions are consistently wrong.

Engineering changes are normal, not exceptional

On a long build, the specification changes. A customer asks for something. A component becomes unavailable. Engineering finds a better way.

Systems designed on the assumption that a bill of materials is settled before production starts handle this badly. What you need is a way to change the specification mid build, record why, understand the cost impact, and know which version applied to the unit that eventually shipped.

That last part matters years later, when a service engineer needs to know what is actually inside the machine in front of them rather than what the original order said.

The installed base is the aftermarket asset

Every unit delivered should exist as a record. Where it is. Who owns it now. How it was configured. What has been done to it since.

Without that, the aftermarket business runs on personal memory and whatever the service team wrote down. Parts get quoted wrong because nobody is sure which variant the customer has. Upgrade campaigns cannot be targeted. Service contracts cannot be priced against real history.

Building the installed base from day one costs very little. Reconstructing it later from despatch records and service notes is expensive and never fully succeeds. Our guide to field service management and ERP goes further into how this gets used.

Parts are a different operation

The parts business behaves like distribution rather than like manufacturing. Many items, mostly low value, unpredictable demand, and a customer who needs it today because a machine is stopped.

That means it needs distribution thinking. Stocking policy per part, honest fill rate measurement, and a pricing approach that recognises what availability is worth to a customer with a machine down.

Running parts on the same planning rules as production material is a common mistake and it produces both excess stock and stockouts at the same time. Our guide to spare parts inventory management covers this in detail.

Report the two businesses separately

If machine revenue and aftermarket revenue are not reported separately, with their own margins, the business cannot see what it is actually good at.

What usually emerges when a business does separate them is that the machine business is thinner than assumed and the aftermarket is carrying more of the result than anyone realised. That changes where you invest, how you price machines, and how seriously you treat service.

What to get live first

The financial core, order to build cost accumulation, the item and configuration structure, and the installed base record. The installed base especially, because it only accumulates going forward.

Field service scheduling, parts planning and advanced analytics can follow. The implementation timeline guide covers how phases usually fall out.

Where to start

TechCloudPro works with industrial and equipment businesses on NetSuite implementation, and with the manufacturing operations that supply them. If you cannot currently report machine margin and aftermarket margin separately, that is the first thing worth fixing.