Privacy policy

This policy covers this website. Data held inside a customer's ERP deployment belongs to that customer and is governed by their own agreement with us.

What we collect

Enquiries — the name, email, company, country and message you submit in a form, so we can reply.
Newsletter — your email address, until you unsubscribe.
Technical details of a submission — with any form we also record your IP address, the approximate city and country it maps to, your browser, operating system, screen size and language, the pages you viewed before submitting, and the campaign or link that brought you here. We use it to answer you in the right language and time zone, to judge which enquiries are genuine, and to see which pages bring real interest.
Analytics — aggregate page statistics, if analytics is enabled for this site.

What we do not do

We do not sell or rent your details, and we do not send marketing unrelated to what you asked about.

Retention and removal

Enquiries are kept while the conversation is commercially relevant. Write to [email protected] and we will delete your record and confirm it.

Cookies

The site sets a session cookie required for form security, and a two-year cookie holding a random identifier so we can tell a returning visitor from a new one. Neither carries your name, and clearing your cookies removes them. We cannot read your device's hardware or MAC address — that never leaves your own network, and no website can see it.

Any analytics cookies are listed in the cookie policy and are only set if analytics is enabled.

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.

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.

How long does implementation take?

Implementation is staged by department. The first department typically goes live in four to six weeks, with the rest following every two to three weeks. The timeline depends on how quickly you can provide masters and opening balances, and how much time your team can devote to training.

Do you support our country’s e-invoicing portal?

We build integrations for e-invoicing portals on request, provided the portal offers a REST API or file-based submission. You will need to give us the API credentials, a test environment, and a sample invoice payload. The integration is quoted separately and built after the core ERP is live.

What we collect

What we do not do

Retention and removal

Cookies

Asked about this

See it running on a real plant, with your questions in the room