If you run an established service operation, you already have systems. An ERP for accounting, maybe an RMA for what goes in and out of the lab, spreadsheets for what neither of them covers. And someone has surely already offered to replace them all.
This page is not that. Nodux handles the work that happens out there: the tech standing in front of the machine, at the customer's location, often with no signal. It is the stretch where almost every large operation still depends on WhatsApp, loose photos and the memory of whoever went.
Where it fits, exactly
The split is simple, and it is worth having it clear before you read on:
- Your ERP handles the money: invoicing, accounting, purchasing.
- Your RMA or lab system handles the equipment that comes into your facilities: serial number, warranty, reverse logistics.
- Nodux handles the on-site work: the work order, the tech, that machine's history, the evidence and what your customer sees.
They are three moments of the same operation, and the same system almost never covers all of them well. The one that tries to cover everything ends up mediocre at all three, and you have already lived that.
What an accountable operation needs
When you answer to a manufacturer, a retail chain or an auditor, it is not enough that the work was done well. You have to be able to prove it.
- History per machine. Every machine builds up everything that was done to it, by whom and when. Not per customer or per month: per machine, which is how a warranty gets argued.
- Evidence signed on site. Whoever receives the work signs the report on the tech's phone, before the tech leaves. No paper traveling around, no signature chased down later.
- SLA measured, not promised. The clock runs on its own and warns you before it expires. Compliance shows by tech, by customer and by period.
- Log with author and time. Every change to the ticket is signed by whoever made it, and so are the edits. For the day someone asks about a detail from eight months ago.
- Works with no signal. The tech opens the work order, updates it and attaches the photos offline: it waits in a queue and uploads on its own when the connection returns, without duplicating anything. The evidence does not depend on the coverage inside a warehouse.
Your brand, not ours
The portal where your customer follows their equipment carries your logo and your domain. Nodux does not show up anywhere. For the supermarket, the bank or the chain you serve, the platform is yours, and that changes the contract renewal conversation more than any feature we could list here.
Each branch works with its own team and its own permissions; management sees the whole picture. A tech who works for two of your units does not need two accounts.
How you leave
It is the question every serious company asks before signing on, and we answer it first because a vendor who dodges it is a risk.
The data is yours. It exports in open formats whenever you want, with no paperwork and without asking anyone's permission. There are backups, there is a public status page, and what happens to your information if Nodux stops existing is in writing. It is not a salesperson's promise: they are pages you can read right now.
- What data we store and who can see it
- Backups and service continuity
- What happens if Nodux disappears
- System status, live
How to start without stopping anything
Nobody migrates twelve branches in one go, and a trial that cannot be measured cannot be approved inside a company. What works:
- One branch and one type of job for a month. Everything else stays as it is.
- A number agreed on in advance: time to close, work orders without evidence, customer calls asking about status. Whichever it is, but chosen before you start.
- No migrating the history. You start with what comes in from today on. Bringing in ten years of data before knowing whether the system works is the fastest way to make sure the pilot never starts.
If the number does not improve, there is nothing to undo. If it improves, the second branch is no longer a hard decision.