Why customisation matters
The same engine that runs a towel plant is reshaped for whatever you manufacture, distribute or service — in the language your staff actually speak. Every business has processes it will not abandon because software finds them inconvenient. We do not ask you to fit into a template. Instead, we keep the core — documents, stock ledger, double-entry accounting, approvals, roles, reporting — and reshape everything above it to match how you work.
What can be customised
Customisation covers the parts of the system that touch your staff, your customers, and your auditors. Below are the areas we adjust, with examples of how it works in practice.
Modules and workflows
Add new document types, stages, or routing between departments. For instance:
- If your production line includes a pre-dyeing inspection stage, we add it to the Production & Planning module.
- If your sales team issues proforma invoices before quotations, we adjust the Sales & Order Book workflow.
- If your purchase team requires a three-step approval for capital items, we configure it in Dynamic Approvals.
Forms and fields
Use your terminology, mandatory fields, and validation rules. Custom fields can be added to any module. Examples:
- In Inventory & Stores, add fields for fabric GSM, colour fastness rating, or supplier batch number.
- In HR & Payroll, add fields for piece-rate incentives or shift differentials.
- In Quality Control, adjust the defect capture form to match your internal grading system.
Printed documents
Invoices, challans, gate passes, and reports are printed in the layout your buyers and auditors already accept. We do not redesign your stationery; we map the data to your existing formats. This includes:
- Company logo, address, and tax details in the correct position.
- Local language support for printed documents, including right-to-left scripts.
- Barcode or QR code placement for gate passes or delivery notes.
Approval chains
Configure who signs what, at which value, and in how many steps. Approvals can be set by document type, amount, or department. For example:
- A purchase requisition above £5,000 requires two levels of approval.
- A sales discount above 10% requires manager sign-off.
- A gate pass for finished goods requires both stores and security approval.
Language and locale
The full interface can be translated, including right-to-left scripts like Arabic or Hebrew. Local date, number formats, and tax treatments are also supported. Examples:
- Dates displayed as DD/MM/YYYY or MM/DD/YYYY.
- Numbers formatted with commas or spaces as thousand separators.
- VAT or GST calculations adjusted for local tax rules.
Integrations
Connect to e-invoicing portals, banks, weighbridges, barcode printers, machine counters, and marketplaces. We do not build custom integrations for every third-party tool, but we support standard protocols like REST APIs, CSV imports, and direct database connections where feasible. Examples:
- Automatic posting of bank transactions to Finance & Accounts.
- Weighbridge data feeding into Inventory & Stores for incoming raw materials.
- Barcode scanners updating stock levels in real time.
How a customisation project runs
Customisation is not a one-size-fits-all process. Below is how we structure it, what we need from you, and what happens at each stage.
Discovery
We sit with each department and collect the forms, reports, and spreadsheets you use today. This includes:
- Printed documents: invoices, challans, gate passes, inspection reports.
- Spreadsheets: order books, production logs, payroll sheets.
- Approval workflows: who signs what, and at which stage.
We do not assume we understand your process better than you do. If a spreadsheet has been working for years, we start by replicating it in the system.
Scope
We produce a written document separating configuration (adjustments within existing capabilities) from development (new code required). This document includes:
- A list of custom fields, document types, and workflow changes.
- Effort estimates for each item, broken down by hours or days.
- A fixed price for the project, with no hidden costs for configuration.
Development is only required for capabilities not already in the system. For example, adding a new field to a form is configuration; building a new integration for a niche weighbridge system is development.
Build
Work is delivered in two-week increments. You see progress at the end of each increment and can comment or request changes. This includes:
- Screen recordings of new workflows.
- Test data loaded into a sandbox environment.
- Printed documents generated in your format.
We do not proceed to the next increment until you sign off on the current one. If a change request falls outside the original scope, we provide a revised estimate before proceeding.
Migration
Masters, opening stock, and opening balances are loaded and reconciled. This includes:
- Customer and supplier masters.
- Product catalogues with batch and rack details.
- Opening stock quantities and values.
- Outstanding purchase and sales orders.
We do not migrate data blindly. Every record is reconciled against your existing system or spreadsheets. If a discrepancy is found, we flag it and resolve it with you.
Go live
Departments go live one at a time, with training and a written workflow manual. This includes:
- On-site or remote training sessions for each department.
- A printed or digital manual with step-by-step instructions.
- A support window for the first two weeks after go-live.
We do not leave you to figure it out. If a department struggles with the new workflow, we adjust the training or the system until it works.
What we will not do
Customisation has limits. Below are things we do not offer, and what to do instead.
- Rewrite the entire system for one customer. The core engine — stock ledger, accounting, approvals — remains the same. If your process requires a fundamental change to how the system works, it is likely not a good fit.
- Support every third-party tool. We integrate with standard systems like banks, e-invoicing portals, and weighbridges. If you use a niche tool, we will assess feasibility during discovery.
- Build features that only one customer will use. If a capability is not useful to other manufacturers, we will not add it to the core product. Custom development is possible, but it is not scalable.
- Promise a timeline without seeing your processes. Customisation takes as long as it takes. We provide estimates after discovery, not before.
What you need to bring
Customisation works best when you come prepared. Below is what we need from you to start.
- Your worst spreadsheet. The one that is held together with macros and manual entries. It usually reveals what the system needs to replicate.
- Printed documents. Invoices, challans, gate passes, and reports in the exact format you use today.
- Approval workflows. A list of who signs what, at which value, and in how many steps.
- Department-level access. We need to speak to the people who do the work — not just managers, but the staff who will use the system daily.
- A single point of contact. Someone who can make decisions and keep the project moving.
What happens in week one
By the end of the first week, you will have:
- A list of all the forms, reports, and spreadsheets we collected from your departments.
- A draft scope document separating configuration from development.
- A sandbox environment with your data loaded, so you can see how the system works with your processes.
- A clear timeline for the next two weeks, including what we will deliver and what we need from you.
We do not disappear after the first call. You will hear from us at least twice a week until the project is complete.