Connect it. Don't replace it.
max.dash is not a warehouse system and does not replace one. It reads yours read-only and delivers what your system does not carry: an SLA rate per client, labor performance, a portal for your clients, and the volumes you invoice on.
The systems we read.
Each linked system has a page of its own: which objects we read, how the access is set up in practice, and where the limits are. The systems without a link are used mainly in German-speaking markets - they connect the same way, they just have their page on the German site.
All product and company names are trademarks of their respective owners. They are named solely to state compatibility. No partnership, endorsement or certification is implied.
In detail.
What goes in, what comes out, what never happens.
Four things are enough
Orders, shipments, client, timestamps. If your system also hands over who handled a shipment, labor performance comes straight from it. If it does not, that number comes from your time tracking instead.
Proof and control
SLA rate per client against your own cutoff and working-day rules, throughput and daily forecast, labor performance, a client portal, billable volumes, cover, returns and receiving.
No interference
No write access to your warehouse system, no installation, no plugin, no process change on the floor. What we read is mirrored into a separate database, hosted in the EU.
How a connection runs.
Four steps, whichever system you run. The work on your side is in step one and three, and both are meetings rather than projects.
Clear the access
Read access in your system, or an export route if there is no interface. We tell you which permissions the connection needs and which it explicitly does not.
Map your clients
Whatever your system calls it - customer, goods owner, client, project - gets mapped to your brands. That is the line every report separates on later.
Rules and people
Cutoff time, working days, public holidays and exclusions, per client. Plus the mapping of scanner logins to your staff - without it you get volumes but no rate.
Sign-off
One real week is checked against what you already know. Only then does the connection go into regular operation.
Common questions.
Do I have to change my warehouse system?
No. max.dash is not a WMS and does not replace one. It reads your system read-only and puts the reporting on top that your system does not carry. Nothing changes about your logins, your processes or your data.
What if my system has no interface?
Then the connection runs on eight defined datasets, delivered by CSV or REST. The feature set is the same, the latency is hours instead of minutes. That is how an in-house system or an enterprise WMS without a public interface gets connected.
My system is not on the list. Now what?
The list shows the systems that have a page of their own, not the limit of what is possible. Any system that exposes orders, shipments, client and timestamps, or can export them, gets connected. Send us the name and we will tell you which route is shortest.
Does max.dash write into my system?
Never into your warehouse system. Access is read-only and the data is mirrored into a separate database. There is one exception outside the warehouse system: approved shifts from the shift planner go back into your time tracking tool.
Can I connect more than one system at once?
Yes. Several sites on different systems run into the same cockpit. One can be connected directly and a second through the import - for the reporting, and for your clients in the portal, the difference is invisible.
How long does a connection take?
A few days. Four steps: clear the access, map clients and objects, set your SLA rules and the user mapping, then sign off against one real week. You install nothing.
Tell us which system sits in your warehouse.
30 minutes, no commitment. We show you on the concrete route what comes out of your data.