Questions we answer every week

Through your account engineer. Configuration changes — fields, approvals, roles, formats, taxes — are usually same-week. Larger module work is scoped and scheduled.

Yes, including the layout your buyers and auditors already accept. Bring a sample of each printed document to the discovery call.

It depends on the complexity of your processes. After discovery, we provide a written scope with effort estimates. Most projects take between four and twelve weeks, delivered in two-week increments.

We can replicate the data and workflows, but not the spreadsheet itself. The goal is to replace manual entries with automated processes, not to recreate Excel in the system.

No. We map the data to your existing formats. If your invoices or challans are accepted by buyers and auditors, we will not ask you to redesign them.

If the feature is useful to other manufacturers, we may add it to the core product. If it is specific to your business, we can develop it as a customisation, but it will not be scalable for other customers.

Send the contact form, call +44 7488 265083 or email [email protected] with a line about what you manufacture. We reply within one business day with a login and a time for a guided walkthrough.

Everything opens: every module, every report, filters and drill-downs. Forms open so you can see the fields, but writes are refused, so the environment stays clean for the next evaluation.

No. It runs in a browser on a laptop or a phone. We send the login once you ask for access, usually the same day.

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.

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.

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.

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.

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.

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.

The mobile app is part of the same deployment and carries your logo and colours. However, it is distributed through the public app stores under our developer account, so the store listing will show our name as the publisher. Factories download it from your branded portal link.

Yes. We provide training scripts, a sandbox environment and live sessions for your team. Training is included in the support relationship, and we can repeat sessions for new staff at no extra charge.

The API can receive production counters from looms via a small service that polls the PLC and sends the data to the ERP. It is not real-time in the sense of a live dashboard, but the counters are posted to the production shift report within minutes of being read. You will need to provide the PLC’s IP address and the memory addresses of the counters.

You can build it on our API or we can quote for it as a separate project. The feature remains your intellectual property, but it must not break the core product or prevent future updates. We review the code before it goes live.

Yes. The HR & Payroll module supports piece-rate, daily-wage and monthly staff. You define the rates per operation, and the system calculates gross pay from actual output recorded on job cards.

If the bank changes its file format, we will update the integration to parse the new format. You will need to provide the new file format specification and a sample file. The update is treated as a change request and quoted separately.

The standard programme runs on our cloud. If you want an on-premise version, we can quote for it, but it is not included in the wholesale pricing and requires a separate support agreement.

We will tell you in the first call if your process does not fit. If a gap emerges later, we will either build the feature within the existing scope or suggest a manual workaround. There are no hidden costs for small configuration changes.

Yes, the API can return stock levels for any item, batch or store. However, it is not designed for high-frequency polling; if your website needs real-time stock updates, consider caching the data in your own database and refreshing it on a schedule (e.g., every 15 minutes).

You log the issue in the partner portal; we respond within the SLA in the agreement. If it is a bug, we fix it; if it is a training gap, we provide the script for your consultant. The factory never contacts us directly.

Item masters, buyers and suppliers, opening stock and opening balances, plus one person per department who knows the real process. We do the loading and validation.

Yes — role-based sessions for each department, plus a written workflow document and an in-app standard-operating-procedure page your staff can open any time.

No. The schedule is designed so that each step is signed off before the next begins. Skipping steps risks breaking the chain of reconciliations, which would mean starting over.

We stop and reconcile. If a batch is missing, we mark it as such and adjust the opening balance. The trial balance must tie before we proceed.

No. You can start with the modules you need and add others later. However, the schedule assumes you will use the core modules—sales, purchase, inventory, production and finance—from the start.

We correct them on the spot. The purpose of the live entry phase is to train your team and catch errors before they become habits. If a mistake is repeated, we stop and retrain.

Per plant, with a user band included in each plan. You are not penalised for giving a supervisor or a store keeper their own login — which is exactly what makes the data trustworthy.

Yearly billing gives you two months free compared with monthly — the toggle on the pricing table shows the exact figure per plan.

We give demo access to businesses evaluating the system, and when you are serious we load a trial environment with your own masters so you can test with your real items and buyers.

Data migration from an old system, on-site training and custom development are quoted separately, because they depend entirely on what you already have. Hosting, backups, SSL and updates are included.

Yes. A one-time licence with optional annual support is available, and source-code handover or escrow can be arranged for Enterprise and custom builds.

On the hosting you choose: our managed cloud, your own cloud account, or your server inside the plant. Nothing is shared between tenants — every customer gets a separate database.

Roles are defined per department with view, create, edit and delete rights per module, and every request is checked on the server. Hiding a menu is not our security model.

Posted documents are never silently deleted. Cancellation reverses the stock and ledger effect and stays on the record with a reason and the user who did it.

Yes. If you start on our managed cloud and later want to move to your own cloud account or on-premise, we will migrate the data at no extra charge. The reverse is also possible: if you start on-premise and later want to move to the cloud, we will handle the migration. The process typically takes one to two days, depending on the size of your database.

For managed cloud, we handle all updates. We test the update in a staging environment, take a snapshot of your production database, apply the update, and notify you when it is complete. For your cloud account or on-premise, you are responsible for updates, but we supply the update package and the test scripts. We recommend applying updates within 30 days of release to ensure compatibility with the latest security patches.

If you run on our managed cloud or your own cloud account, we monitor the server 24/7 and will alert you if there is an issue. If the server fails, we will restore it from the most recent backup. If the internet goes down, the system will be unavailable until the connection is restored. If you run on-premise, you are responsible for monitoring the server and restoring it from backup if it fails. We will provide guidance, but we cannot guarantee the time it will take.

You can restrict access based on role and branch, but not directly on location or device. If you want to prevent users from logging in from outside the plant, you can configure your network firewall to block external access to the server. If you want to restrict certain roles to specific devices, you can issue API tokens only for those devices. Activity tracking will show you where and on what device each user logged in, so you can spot unauthorised access.