Show your clients that you delivered.
SLA rate, labor performance and a portal where each of your brands sees only its own numbers - in writing, straight out of the system your warehouse already runs on.
You deliver well. But can you prove it?
"Where is my order?"
Your clients email for status every day. Every email costs you time, and every unanswered one costs trust.
You track SLA in a spreadsheet, or not at all.
The contract says shipped within 24 hours. Proving cleanly that you held it is not something your warehouse system does.
Client billing eats your Friday.
Orders per client, returns, special handling - collected by hand out of exports. Again, every month.
A cockpit for you. A portal for your clients.
max.dash is a read-only operations cockpit for third-party logistics providers. We read along in your warehouse system and deliver SLA reporting per client, labor performance per person, a client-separated portal and billable volumes as an export - without a migration.
Your own cockpit
See how the warehouse is running right now, instead of reconstructing it at month end.
- Throughput per day and per person
- SLA rate, live, per client
- Return rate, stock value, cycle time
The client portal
Every brand gets its own login and sees only its own numbers. The daily status emails stop.
- Strictly separated - only their own brand
- Shipment status, SLA rate, stock
- More professional than any spreadsheet
What you see after you log in.
Six views from a running operation. The screenshots come from our demo tenant - real interface, anonymised numbers. The interface is shown in German here; it runs in English too.
You see the 24h rate before your client does.
Every brand gets its own rules: cutoff, working days, holidays, which orders count. The page shows the rate against target, the trend across the month, and the orders that still have to leave today - including the ones already past their deadline.
- 24h and 48h kept apart, with average cycle time
- Due today, overdue and "waiting on stock" separated
- Monthly trend, so one bad day does not become the argument
Every single day stays accountable.
Parcels against forecast, shift hours, rate per hour, and how the volume split across your clients. The comparison with the same weekday last week tells you immediately whether the day was genuinely bad or simply a Monday.
- Actual against forecast, in percent
- Parcels per hour over the day, against last week
- Share of the day's volume per brand
Minutes per parcel instead of gut feeling.
A ranking across the running month, normalised for products per parcel. Someone who only looks fast because their orders were small no longer slips through - and someone who is genuinely quick finally shows up as such.
- min/parcel and min/product, switchable
- Deviation from the average in percent, per person
- Days, parcels and products per parcel as context
You see where the shift runs thin - beforehand.
Stations, hours and utilisation on one sheet: 119 hours planned, 79 hours of station capacity still open, roughly 4,300 parcels achievable. Who is standing where, and where a gap is left, sits next to it - before the shift, not in the post-mortem.
- Utilisation per hour, not as a daily average
- Free stations and per-station gaps marked
- View by station, by person, or across the week
Every merchant gets a portal of their own.
You create one dashboard per brand, switch on exactly the pages that client should see, and send the invitation. Until you release it they see nothing. After that, only their own brand - never anybody else's data.
- Pages enabled individually: orders, stock, returns, cycle times
- More than one dashboard per brand if you need it
- Invitation by email, the release stays with you
Ask your warehouse a question in plain language.
Type "which items are below minimum stock?" instead of building a report or asking somebody to. The answer comes back with SKU, shortfall and inbound quantity - and with the assumption it was based on stated openly.
- Answers from live data, not from yesterday's export
- Read-only. No write access to any system, ever
- The queries it used can be expanded and read
On top of that: warehouse monitor, returns, and billable volumes per client. Click through the live demo yourself - it runs on the German interface, on the same data you see above.
Whichever system runs your warehouse.
max.dash is not a warehouse system and does not replace one. It reads yours read-only - through its interface, or through eight defined datasets if there is no interface. Each system has a page of its own with the concrete route.
Your time tracking tool is the second source: the warehouse system says how much went out, time tracking says how long it took. Only together do they produce a rate per person.
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.
SLA reporting that holds up against your contract.
Shipped within 24 hours sounds simple until someone asks you to prove it. When does the clock start, what is your cutoff, which days count, which orders are excluded - and all of it per client, because every contract is different. max.dash carries those rules and produces the number every day.
- Cutoff time, working days and public holidays per client
- Exclusions defined once instead of argued each time
- The rate your client sees is the rate you see
Your data moves. Your system stays put.
Orders run through your ERP and your warehouse exactly the way they do today. max.dash reads alongside, read-only - and hands every client a portal of their own.
max.dash is not another warehouse system. Nothing moves, nothing migrates, and nothing about the operation you are running today is put at risk. We mirror your data read-only into a secure cloud and build the cockpit on top of it.
Built by someone who has stood on the packing floor.
max.dash comes from Nils Schade and his team - out of the day job in fulfillment, not off a whiteboard. It runs in a live warehouse operation every day, which is also where most of what it does came from in the first place.
"Every Friday used to disappear into building Excel reports for our clients. Now each of them looks into their own portal - and we can tell before the first coffee whether we are holding the 24-hour rate."
One tier to start on. One you will actually end up on.
Cockpit
- Shipping KPIs and throughput
- Performance per person
- Returns, stock value, cycle time
SLA
- Everything in Cockpit
- SLA per client - working days, cutoff, exclusions
- Monthly view, report export, early warning
Portal
- Everything in SLA
- A login of their own per merchant
- Strictly separated by client
What you want to know before you book.
Do I have to move off my warehouse system?
No. max.dash sits on top and your system stays exactly as it is. It is not a WMS migration, it is a layer above one.
Which warehouse systems does max.dash connect to?
Any system that exposes orders, shipments, client and timestamps, or can export them. Several systems have a page of their own with the concrete route, and everything else runs on eight defined datasets delivered by file or REST.
Do you really only read, never write?
Yes. Read-only access, mirrored into a separate database. Your production system is never written to and stays untouched.
Can my warehouse system track SLA per client on its own?
Almost none can. Warehouse systems show you order data, but not an SLA rate per client with cutoff times, working days, public holidays and exclusions. That is where max.dash starts, and it delivers that figure per client, every day.
Do my clients only see their own data?
Yes, strictly separated. Every login sees exactly one brand and never the data of another client.
How long does setup take?
A few days. We set up the sync and your SLA rules, and you install nothing.
See your own warehouse in numbers it has not shown you yet.
30 minutes, no commitment, on your real data.