A shipyard does not make products, it delivers boats. Every hull is a project lasting several months, sometimes several years: a quote that keeps changing, options chosen by the owner, dozens of subcontractors, equipment ordered a year before launch, and a warranty that keeps running after delivery. Software designed for repetitive manufacturing or trading struggles with this reality.
This guide is for owners and finance directors of boatbuilding and refit yards, as well as marine subcontractors (joinery, lamination, electrical, rigging) with 30 to 250 employees. It covers what an ERP must handle, from the quote to seasonal maintenance, and offers a selection grid by company size. The figures are fictional examples, flagged as illustrative: this guide cites no market statistics.
What makes the marine trade different: series vs. bespoke, long cycles, many subcontractors
Three characteristics make boatbuilding unusual for an ERP.
A continuum between series and bespoke. A builder of sailboats or cruising motor yachts produces catalogue models, yet every unit gets options, an interior finish and electronics chosen by the client. At the other end, a superyacht or commercial vessel yard works on an engineer-to-order (ETO) basis, one hull at a time. Many yards mix both: a series platform with a bespoke fit-out.
Very long cycles. Several quarters pass between signature and delivery. Revenue, margin and cash must therefore be steered over the life of the project, not by the monthly invoice.
A dense subcontracting chain. Lamination, aluminium welding, joinery, painting, electrical work, onboard plumbing, sailmaking, rigging: part of the boat’s value is created off site, or by outside crews working inside the yard. The ERP must treat these parties as project resources, not just suppliers.
Refit: a different business inside the same yard. Repairing and upgrading an existing boat looks more like maintenance: the scope is discovered when the boat is opened up, extra work is frequent, and the vessel ties up a slipway or shed space every day. Seasonality affects both activities: winter layup concentrates refit work, while summer concentrates deliveries and breakdown call-outs.
These traits place boatbuilding close to two sectors already covered on this blog: made-to-measure manufacturing with installation, discussed in our guide to ERP for furniture and fit-out manufacturers, and construction in the strict sense, covered in our guide to progress billing in construction. Here the focus is on what is specific to the boat.
From quote to contract: options, change orders and scope variations
A boat quote is a living document. It often starts as an offer based on a model, evolves with the client’s choices, then keeps growing through change orders throughout the build or refit.
A suitable ERP must be able to:
- version the quote and keep the revision history, with the price and the estimated cost of each version;
- separate the base specification, options and variants, so the client sees what they are paying for and the yard knows what it has to build;
- turn an accepted quote into a project: the job automatically picks up the lines, the budgets by work package and the billing milestones;
- trace every change order as a priced amendment to the contract, with its impact on price, costs, lead times and purchases already placed;
- distinguish extra refit work (found when a compartment is opened, for example) from the original order, with client approval before execution.
Illustrative example: a yard signs a €1,200,000 contract for a 12-metre motor yacht. During the build, the owner asks for additional air conditioning and teak decking. The change order adds €38,000 of sales price and €29,000 of estimated cost, and pushes delivery back by three weeks. Without traceability in the ERP, these additions end up buried in emails and the real margin is only known at delivery. The figures are fictional.
The classic trap is the change order agreed verbally on the quayside. An ERP will not eliminate that habit, but a simple approval workflow (the project manager raises the change order from a phone, the client signs it) reduces the amount of unbilled work.
Bills of materials and per-boat configurator
A boat’s bill of materials (BOM) is never frozen. It starts from a base model, changes with the options chosen, and keeps evolving during construction as detailed drawings are issued and equipment is substituted.
The useful functions:
- Base BOM per model, with variants and options. A configurator produces the hull-specific BOM from the client’s choices (engine, navigation electronics, finishes, berths).
- Evolving BOM per boat, tied to a hull or job number: each unit keeps its own structure, even if it starts from a common model.
- Revision management: a drawing change flows through to the affected purchases and production orders, with an alert on whatever is already ordered or built.
- Routings and standard times per work package (hull, deck, interior, electrical system, propulsion), to compare planned and actual hours.
- Technical file and per-equipment traceability: serial numbers of engines, generators and safety equipment, useful for warranty and maintenance.
For the mechanics of a configurator and its limits, our guide to furniture and fit-out explains principles that also apply to boat options. The differences are the length of the supply chain and the weight of bought-in equipment, which is as much part of the BOM as timber or resin.
Resource and yard scheduling
A shipyard manages scarce, highly visible resources: slipways, sheds, work stations, cranes and crews from different trades. A delay in one work package blocks the next and ties up a space that was meant for another boat.
An ERP or planning module must handle:
- project scheduling, with work packages and their dependencies (the engine cannot go in before the hull is closed, painting waits for sanding to finish);
- berth and space scheduling: slipways, sheds, refit quays, with an occupancy view over several months;
- load by trade: laminators, joiners, electricians, boilermakers, comparing capacity and demand;
- time capture by job and work package, ideally on a phone or tablet in the workshop, to feed actual cost;
- rescheduling when equipment arrives late or a change order lengthens a work package.
Illustrative example: a refit yard has four shed spaces for the winter. Five boats are planned, one of which depends on equipment expected in January. An occupancy plan visible in the ERP lets the yard push that boat back instead of blocking the space for weeks. The data is fictional.
Many yards use an external planning tool alongside the ERP. That is not a problem as long as data exchange with the ERP is under control: without an automatic link, hours worked and actual dates are rekeyed, and the plan drifts away from reality.
Subcontracting and long-lead purchases: engines, electronics, rigging
Heavy equipment has lead times counted in months. An engine, a generator, a mast and its rigging, winches, navigation equipment: their order date is dictated by the boat’s schedule, not the other way round.
An ERP must therefore link purchasing and project:
- purchase requirements generated from the boat’s BOM, with a required date derived from the schedule;
- tracking of long-lead orders: acknowledgement, promised date, delays, and alerts when a delay threatens a milestone;
- goods receipt tied to the project and to a storage location, so that equipment can be found in a shed;
- management of supplier deposits, common on major equipment;
- subcontract tracking: orders to a subcontractor with scope, price, milestones and acceptance of the work, with matching before payment.
On that last point, industrial subcontracting involves specific mechanisms (material supplied to the subcontractor, tracking of work in progress at the third party) described in our guide to industrial subcontracting in SAP, Odoo and Sage X3. A yard that supplies material to a laminator or a cutting subcontractor will recognise these cases.
For crews working on the yard’s site, tracking hours and certifications (work at height, hot work, confined spaces) is more a quality and safety process, which the ERP can support without replacing.
Milestone billing and profitability per boat
Billing a boat rarely follows a “deliver, then invoice” pattern. It is built around contractual milestones: signature, start of fabrication, hull closure, propulsion installation, launch, sea trials, delivery. Each milestone triggers an invoice or a request for a stage payment.
The functions to demand:
- a payment schedule per contract tied to milestones, with planned date, actual date and status;
- progress or milestone billing depending on the contract, with logic to deduct payments already made;
- revenue recognition over time where the applicable accounting standard or company policy provides for it, to be validated with your auditor;
- cost per boat: materials, equipment, internal hours, subcontracting, direct expenses, compared with the original budget;
- variance tracking by work package and cost type, with an alert when a package exceeds its budget;
- provision for risks and warranty, adjusted using observed history.
Illustrative example: on a contract with a €1,200,000 price and a €960,000 budgeted cost, the planned margin is €240,000, or 20%. At the halfway point, the interior package has consumed 70% of its budget while only 50% complete. Tracking by work package flags this while there is still time to act, whereas a margin calculation at delivery would have shown nothing. The figures are fictional.
The accounting logic of progress billing, retention and subcontracting is developed in our guide to progress billing in construction, several mechanisms of which apply to shipbuilding contracts.
After-sales, warranty and seasonal maintenance
Once the boat is delivered, the relationship continues. The yard handles delivery snag lists, warranty claims, breakdown call-outs and, for many, maintenance and winter storage contracts.
The ERP should provide:
- a file per boat (hull number, owner, installed equipment with serial numbers, delivery date, warranty period);
- warranty claim tracking linked to the supplier of the equipment concerned, for recharging or replacement;
- service orders with resource, parts, time spent and billing, modelled on maintenance;
- recurring maintenance and winter storage contracts, with scheduling of interventions before the season;
- a maintenance history that feeds refit quotes in the following years.
Seasonality calls for preparing the workload: the ERP must let you schedule spring interventions before the rush of requests, and smooth workshop activity across construction, refit and maintenance. On the regulatory side, the compliance of recreational craft (CE marking in particular) depends on the type of boat and the applicable framework; this guide does not go into detail, and we invite you to consult the official European Commission texts and your notified body before modelling it in the ERP.
Which type of ERP for which company size
The choice depends on the share of bespoke work, the size and complexity of projects, and the IT resources available.
| Profile | Type of solution | Strengths | Watch points |
|---|---|---|---|
| Small yard or subcontractor (30-60 employees), repetitive activity | Adapted general-purpose SME ERP (sales, simple production, accounting) | Contained cost, fast rollout, many vendors | Change orders and per-boat BOMs often limited; add-ons to plan for |
| Mid-size yard (60-150 employees), mix of series and bespoke | ERP with a project module and make-to-order (ETO) production | Job, milestones, evolving BOM, purchasing tied to the project | Heavier configuration; the integrator’s skills are decisive |
| Superyacht or complex-vessel yard (100-250 employees), long projects | Full project or ETO ERP with advanced planning | Margin tracking by work package, over-time recognition, strong traceability | Higher budget and longer project; demanding change management |
| Highly specialised yard | Marine-specific solution, possibly connected to an accounting system | Trade vocabulary and functions | Vendor longevity, openness of interfaces, accounting coverage to verify |
None of these profiles names a vendor at this stage: names come after mapping your processes. Two mistakes are common. The first is buying a sales-and-distribution ERP and then managing projects in spreadsheets: you lose the margin per boat. The second is aiming for a very comprehensive project ERP for a yard that mostly builds series boats: the configuration goes beyond real usage.
10-point selection checklist
- Versioned quote with base specification, options, variants and revision history.
- Priced change orders linked to the contract, the schedule and purchasing.
- Per-boat BOM, evolving, derived from a model and a configurator.
- Scheduling of slipways, sheds and trades, with a load view over several months.
- Mobile time capture by job and work package, usable in the workshop.
- Project-linked purchasing, with a required date driven by the schedule and tracking of long lead times.
- Tracked subcontracting: order, milestones, acceptance, matching before payment.
- Milestone payment schedule and revenue recognition over time, validated with your accountant.
- Cost per boat compared with budget, with variance alerts by work package.
- Boat file for after-sales: equipment and serial numbers, warranty, maintenance contracts, service orders.
To evaluate each candidate, ask for a demonstration on a real scenario: a boat with options, a change order mid-project, a piece of equipment delivered late and a milestone invoice. A vendor that cannot run this scenario end to end will not cover your trade.
Going further
Get our sector analyses by subscribing to the newsletter. If you are preparing an ERP project in a shipyard or at a marine subcontractor, you can also contact DigitsLane to frame your scope and milestones before approaching vendors.