Custom ERP for a small manufacturer — build or buy?

· Software, ERP, Manufacturing

Most small manufacturers I meet run their factory on a mix of paper job cards, WhatsApp groups and Excel sheets. It works — until it doesn't. An order goes missing between stitching and embroidery, a customer calls asking for an update nobody can give, or the owner spends every evening chasing numbers.

At that point the question becomes: should we buy ERP software, or build our own?

I built a complete factory system for Corporate Uniforms by B.A.G, a uniform manufacturer in Bhopal. This post is what I learned, written for factory owners rather than developers.

Signs your factory has outgrown spreadsheets

You probably need a proper system if:

  • Nobody can answer "where is this order right now?" without walking the floor
  • The same order details are typed into three different places
  • Deadlines slip and you only find out when the customer complains
  • Stock and materials run out without warning
  • Attendance and staff output live in a register nobody analyses
  • The owner is the only person who knows the full picture

None of these is a software problem first. They're information problems: the right person doesn't have the right fact at the right moment. Software just makes the fix stick.

Option 1: buy ready-made ERP

Ready-made ERP and inventory products are a good fit when:

  • Your process is standard for your industry
  • You're happy to change how you work to match the software
  • You need it running this month
  • The monthly cost per user is acceptable as you grow

The catch for many small factories is that they aren't standard. A uniform maker, for example, deals with every order being a different mix of garments, sizes, fabrics and embroidery. Generic software forces that into fields that don't fit, so people go back to WhatsApp and the software becomes one more place to type things.

Option 2: build a custom ERP

Custom software makes sense when:

  • Your process is your advantage, and you don't want to bend it
  • You keep paying for modules and seats you don't use
  • You need the office and the factory floor to work from the same live data
  • You want to own the system, with no per-user licence fees

The trade-off is a higher cost up front and a few weeks of building. In my price guide, custom software and ERP projects usually fall in the $1,000+ range, depending on the number of modules, and a focused first version takes about 6–12 weeks.

How to decide: a simple test

Write down the five most important steps an order goes through in your factory. Then try a ready-made product's free trial and enter one real order.

  • If it fits with small changes, buy.
  • If you're working around the software at every step, build.

I'll tell you honestly which side you're on after a short call. It's not always custom.

What a small-factory ERP actually needs

You don't need a hundred modules. For Corporate Uniforms, the system grew around one flow, and everything else plugged into it.

The core: order to delivery

  1. Register the order once — client, items, sizes, measurements, deadline.
  2. Production stages — each unit moves through cutting, stitching, embroidery, alterations and quality checks.
  3. Dispatch — packed, labelled and checked.
  4. Delivery — closed with its challan.

Because every unit carries its stage, a dashboard shows how many pieces are at each step and which items are overdue, and by how many days.

Labels and barcodes

This was the piece that made it work. Every garment and batch gets a printed barcode label. On the floor, scanning a label updates its stage in a second — no typing, no guessing which bundle belongs to which order. I wrote more about it in building a factory ERP with label printing.

Around the core

Once orders flowed, the rest could plug in:

  • Leads and tasks for the sales team, fed by the website's quote form
  • Inventory and materials
  • Attendance with roles — admin, office staff, floor workers — each seeing only what they need
  • Reports on daily output, overdue items and staff

Two apps, one system

The office and the floor need different tools. The office gets a web app for orders, leads, reports and settings. The floor gets a Flutter mobile app for scanning, stage updates and attendance. Both use the same backend, so a scan on the floor appears on the office dashboard immediately.

Start small, then grow

The biggest mistake is trying to build everything at once. A better plan:

  1. Phase 1: orders and production stages, with labels. This alone answers "where is my order?"
  2. Phase 2: dispatch, delivery and reports.
  3. Phase 3: leads, inventory, attendance — whatever hurts most next.

Each phase is usable on its own, so you see value in weeks, not months, and you only pay for what proves useful.

The lesson that matters most

Factory software succeeds or fails on the floor. If updating a stage is slower than shouting across the room, nobody will do it. Make the right action the fastest one — for Corporate Uniforms, a single scan — and the data takes care of itself.

So before features, ask: what will the person on the floor have to do, and how many seconds will it take?

Quick answers

How much does a custom ERP cost? For a small manufacturer, usually in the $1,000+ range, depending on modules. You get a fixed written quote after we map your process.

How long does it take? A first version is usually ready in 6–12 weeks, delivered in weekly milestones you can test.

Will it work on phones? Yes. A shared backend can serve a web app for the office and a mobile app for the floor.

Do I own the software? Yes. Source code, database and documentation are yours, and you can host it wherever you like.

See screenshots in the Uniform Factory ERP case study, and what's included on the custom software and ERP development page.

Running a factory or workshop in Bhopal or anywhere in India? Tell me how your work flows and we'll map it together.

← All posts