New: role-based approval matrix and session-replay activity tracking are live. Read more

Who builds this

Engineers who spent the last year on a factory floor

We did not start from a template. We built this system for a working plant, document by document, until the trial balance tied and the store keeper stopped keeping a parallel notebook.

Fugen ERP is built and maintained by a small engineering team that ships to manufacturers. The first deployment was a terry towel plant: yarn store, ten looms, a dyehouse, finishing, stitching, packing and a finance department that had been reconciling everything by hand.

That order of work matters. Most ERP products are written as generic frameworks and then bent towards factories by consultants. This one grew the other way round — from real documents, real batches and real payroll runs — and then had the generic layer extracted from it. It is why the demo has four months of coherent operating data behind it rather than three sample rows.

How we work

A discovery call to understand your process. A written scope with what is configured and what is built. A staged rollout, department by department, with your own masters and opening balances. Then a support relationship where configuration changes happen in the same week you ask for them.

What we will not do

We will not promise a two-day implementation, sell you licences you cannot staff, or leave you with a system only a consultant can operate. If your process genuinely does not fit, we will tell you in the first call.

Related questions

Asked about this

Is this a real product or a demo build?

It is a working ERP that runs a European towel manufacturing plant today. The public demo is the same build, loaded with four months of documents — sales orders, production, quality, payroll, vouchers — so you are judging the real thing, not a slide deck.

Can it be customised for a business that is not a factory?

Yes. The engine underneath — documents, stock ledger, double-entry accounting, approvals, roles, reporting — is industry agnostic. We reshape the modules, forms, documents and reports around your process. Tell us how you work and we will show you the shape it would take.

Which languages are supported?

Any language you need, including right-to-left scripts. The interface is fully translatable and we deliver the language files with your deployment. Documents and reports can print in a different language from the interface if your buyers need that.

How long does implementation take?

A standard manufacturing deployment runs four to eight weeks: masters and opening balances first, then live documents module by module. A customised build depends on scope and is quoted after a discovery call.

Do we have to move all departments at once?

No. Most plants start with stores, purchase and sales, then bring production, quality and payroll in once the floor is comfortable. Approvals are switched on module by module when you are ready.

Next step

See it running on a real plant before you talk to anyone

The demo opens with four months of live documents — orders, batches, inspections, payroll and books that tie. Walk through it yourself, then bring us your process.

Open the live demo Book a walkthrough

No form for the demo. No card. No installation.
Or call +44 7488 265083 · hello@fugenservices.co.uk