Warehousing and transport in one system. Proof of delivery in neither.
max.dash reads your CartonCloud read-only and turns it into an SLA rate per customer, a client portal where each brand sees only its own numbers, and the billable volumes you invoice on - warehousing and transport together, not as two separate views.
CartonCloud is a product of CartonCloud Pty Ltd. 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.
What a combined warehouse-and-transport system doesn't prove.
CartonCloud runs your warehouse and, if you offer it, your transport too - one system for both, which is rare enough to matter. What it isn't built for is proving to your customers, month after month, that you delivered what the contract says. CartonCloud reporting stops at your own screen; it was never meant to sit in front of a client.
- The SLA rate per customer is calculable, not defined. The consignment data is all there. What's missing is the rule: when the clock starts, when your cutoff falls, which days count, which orders are excluded - and all of it per customer, because every contract reads differently.
- A driver assignment is not a pick-and-pack assignment. CartonCloud tells you which driver takes a consignment to the recipient - not who picked or packed it in the warehouse. Read one as the other and you get a labor number, just the wrong one.
- Warehouse and transport performance sit next to each other, not together. If you run both for a customer, the warehouse figures and the delivery figures live in different corners of the system - not as one report per client across the whole order.
- Your customer has no window of their own. So they email. Every day, per brand, asking where a consignment is - and every unanswered email costs trust rather than time.
What we read out of CartonCloud.
The connection runs through the open REST API using OAuth2, self-serve. Webhooks for status changes are set up by the CartonCloud team rather than through self-serve - that's a setup step worth planning for, not a missing feature.
Scroll table sideways
| What we read | From | What it becomes |
|---|---|---|
| Consignments and shipments | consignment records | throughput, backlog, the SLA clock |
| Customers | account structure | the client separation, everywhere |
| Driver assignment | delivery-side records | proof of delivery, not picking performance |
| Order lines | consignment detail | weighting, points per order content |
| Inventory and movements | stock records | cover, receiving, returns |
| Timestamps | consignment and shipment events | cycle time, cutoff check |
We do not read pricing, margins, or end-customer data beyond name and delivery address. Running a warehouse and a fleet does not require them, so they stay out of the connection.
Multi-client operation isn't an add-on bolted onto CartonCloud - it's the premise the whole platform is built on, which is exactly what you'd expect from software written for logistics providers rather than for merchants with a warehouse attached. Over 600 companies run on it, according to the vendor. Your customers there become your clients in max.dash without inventing a separation field anywhere. And because warehousing and transport commonly sit in the same account, one consignment can carry both sides of the job - the connection reads it as one order, not two.
Where the CartonCloud labor report actually comes from.
This is the one place where being precise matters more than sounding capable, so here is the honest version.
CartonCloud tracks which driver is assigned to a consignment - the delivery side of the job. It does not tie a warehouse worker to a pick or a pack. Those are two different roles, often two different people, and CartonCloud keeps them apart: there is no labor or productivity view for the warehouse floor, only the assignment on the delivery side. There is no CartonCloud labor report that connects picking to a person, and treating the driver field as if there were gets you a number - just not the right one.
So max.dash does not claim that figure from the warehouse system. It builds it from a second source that is independent of what any WMS chooses to expose: your time tracking system, plus a mapping of scanner logins to the people behind them.
The advantage of this route is that it doesn't depend on a vendor roadmap. It works the same way whether CartonCloud ever exposes a pick-and-pack assignment or not, and it works identically across every system in your estate - warehouse, transport, or both.
What max.dash makes of it.
Not a second CartonCloud KPI dashboard. The reporting layer your warehouse-and-transport system was never built to carry.
Scroll table sideways
| Capability | With CartonCloud | Built from |
|---|---|---|
| SLA tracking per customer | yes | timestamps, consignments, your cutoff and working-day rules |
| Throughput and KPI dashboard | yes | consignments per hour, history |
| Labor report | via time tracking | time tracking plus scanner mapping |
| Points per order content | via time tracking | order lines, weighted over the tracked window |
| Client portal | yes | customers as the dividing line |
| Billing report | yes | consignments, returns, special handling |
| Cover and stock value | yes | inventory per customer |
| Returns and receiving | yes | stock movements |
How the connection runs.
Four steps, a few days. You install nothing and your CartonCloud account is never written to.
Clear the OAuth2 access
You set up an OAuth2 connection in your CartonCloud account. We tell you which scopes the connection needs - and which it explicitly does not.
Map your customers
Your CartonCloud customers become clients in max.dash. That is the line every report, every invoice figure and every portal login separates on later - for warehouse and transport orders alike.
Request webhooks
Webhooks for status changes are set up by the CartonCloud team, not by you through self-serve. We file that request together with you, so the connection runs close to real time instead of waiting on polling.
Sign-off
One real week is checked against what you already know. SLA rate, volumes, performance. Only then does the connection go into regular operation.
When a second system sits next to it.
Plenty of 3PLs do not run one system but two or three - per site, per client, per acquisition. That is the normal case, not the exception.
max.dash reads several sources into the same cockpit. Where an interface exists, it works as described here. Where it does not, there is a defined import: eight datasets by file or REST, same feature set, hours of latency instead of minutes. For your clients in the portal, the difference is invisible.
Common questions.
Do I have to move off CartonCloud?
No. CartonCloud stays your system and nothing about it changes. max.dash reads along through the existing connection and puts a reporting layer on top. No migration, no extra module inside CartonCloud.
Does max.dash write anything back into CartonCloud?
No. Access is read-only. What we read is mirrored into a separate database and evaluated there. Nothing is created, changed or deleted inside CartonCloud.
Can CartonCloud track SLA per customer on its own?
CartonCloud gives you the consignment and shipment data an SLA rate can be calculated from. What is missing is the definition work: when the clock starts, what your cutoff is, which days count as working days, which orders are excluded - and all of it separated by customer. That calculation is what max.dash takes over, per customer, every day.
How does labor performance work if CartonCloud only gives me a driver assignment?
CartonCloud tracks which driver is assigned to a consignment - who drives it to the recipient, not who picked or packed it in the warehouse. There is no assignment from a warehouse worker to a pick or pack inside CartonCloud. The second route carries the answer: through your time tracking system plus a mapping of scanner logins to people, max.dash calculates minutes and volumes per person, independent of the driver assignment.
Does max.dash cover my transport business too, or just the warehouse?
CartonCloud holds warehousing and transport in one system, and many consignments carry both sides. max.dash reads them together and reports SLA rate, volumes and the client portal per customer across the whole order, not only the warehouse half. What max.dash does not provide is fleet dispatch or route planning - that stays CartonCloud's job.
See your own SLA rate before you decide.
30 minutes, no commitment. We show you on real numbers what comes out of your CartonCloud data.