How to implement ERP in a furniture manufacturing company

ERP projects in furniture factories rarely fail because of the software. They stall because the panel lists were never clean, the variant rules live in one designer's head, or the saw and paint shop are asked to record their work without seeing why. This guide starts with one product family on the real floor, so the project stays small and the saw and paint shop actually use it.

Before you start: decide what the system must answer on day one

Write down the questions the owner and the production head ask most often. In most furniture factories the list is short: where is this order, what did this job really cost, how much board did we waste this week, which batch is this shutter from, and do we have the fittings to pack it. Those define the first scope. Everything else can follow.

• Name an owner from the factory, usually the production head, not the accountant or IT alone.
• Choose the first product family: one with steady orders, a willing supervisor at the saw, and enough variants to test the rules.
• Agree what will be switched off when it goes live, such as the printed cutting sheet, the finishing whiteboard or the hardware register.

What data do you need to prepare?

Rates and drying times do not need to be exact on day one. A reasonable figure is enough to start, and the floor's own entries will show the real ones within a few weeks.

The stages of an implementation

1. Configure the factory as it runs

Work centres, shifts, models, variants, panel lists, routings, checks and reason codes are set up in the factory's own terms. Opening stock of board, offcuts and hardware is loaded by lot, and the accounting sync is connected. By the end of this stage a test order should run from the cutting list to dispatch on the screens.

2. Run the first product family on real orders

Saw, bander, boring, finishing, assembly and packing staff for the first family are trained at their stations, one short session each, and record real orders while the rest of the factory carries on as before. Gaps show quickly: a variant rule that produces the wrong panel, a missing reject reason, an edge band code nobody uses. Fix them the same day.

3. Switch the first family over

Orders for that family now run on the system alone, and the old cutting sheet and order tracker stop for it. Planning, stock and cost read what the floor records.

4. Extend family by family

The remaining product families and any job work follow the same pattern. Each goes faster than the last, because the material codes, the routings and the training approach are already proven.

How long does a furniture ERP implementation take?

It depends on the scope, how ready the data is and the system. An enterprise ERP covering finance, retail and several factories is a much larger project than putting production, stock and finishing live for one product family. FleekERP's implementation plan is built to put the first production line live in 18 days. A factory migrating years of history from another ERP, or with panel lists that need rework first, will take longer.

Common ERP implementation mistakes in furniture manufacturing

1. Configuring software before understanding the process

Setting up screens before anyone has walked the floor produces a system that matches a template, not the factory. Follow one order through first: how the cutting list is made today, where offcuts go, how shutters are batched for paint, how fittings reach the carton. Configure to that, run it for a few weeks, then ask for changes.

2. Poor master-data preparation

Panel lists with old sizes, board codes that stores and the saw read differently, hardware lists missing a fastener: each one produces a wrong cut, a wrong issue or an incomplete carton in the first week, and the floor loses faith in the system. Clean the masters for the first family before go-live. The opposite mistake is as common: migrating every past order. Open orders, current stock and active models are usually enough.

3. Ignoring shop-floor users

The saw operator, the bander, the paint supervisor and the packer make most of the records, yet they are often trained last, in an office. Train them at their own station on real orders, and keep their entries to what they need: panels and offcut per sheet, completions, rejects with a reason, the finishing batch. In FleekERP the operators log them on shop floor apps, running on ordinary Android phones. Show supervisors their section's numbers from the first day. If cutting updates now travel as WhatsApp photos, read why WhatsApp ends up running the production floor before training starts.

4. Trying to digitise everything at once

Every product family, every section, job work, dispatch and installation on the same day spreads the team too thin to fix problems as they appear. One family running cleanly from cutting list to packing is worth more than the whole catalogue half configured.

5. Unclear BOM and routing ownership

If nobody owns the panel lists and variant rules, they drift: the designer changes a shelf depth, the BOM still shows the old size, and a batch of panels is cut wrong. Name an owner, usually design for the BOM and the production head for the routing, and agree how a change is released and from which order it applies.

6. No pilot, or a pilot with no end

Going live across the factory without a pilot means every gap appears everywhere at once. A pilot family finds them on a small scale. Set the date the old cutting sheet stops for that family, though: a pilot that runs alongside the old sheets indefinitely becomes a second copy nobody trusts.

7. Measuring software usage instead of operational outcomes

Logins and entry counts show whether people use the system. They do not show whether the factory runs better. Judge the project by less board wasted, fewer repaints and orders leaving on time.

After go-live: what to measure

• Board yield per sheet and per order, reviewed weekly, and whether offcuts are being used.
• Rejects and rework by stage and reason, especially recuts and repaints.
• Delivery against the promised date.
• Orders packed complete the first time, with no fitting sent later.
• The time taken to answer where an order is, and what it cost.

In the first weeks, also check how many sheets and finishing batches were logged at the machine rather than afterwards. If that number is low, the results above will not move.

For how the full flow runs once the factory is live, see FleekERP for furniture and woodwork.