Daily packer performance. Not your login.
max.dash reads your ShipHero warehouses through the GraphQL API - without you ever sharing your own credentials - and turns it into ShipHero reporting that covers labor performance, an SLA rate with the right timezone on record, and a client portal where every brand sees only its own numbers.
ShipHero is a product of ShipHero LLC. 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 3PL warehouse system doesn't prove on its own.
ShipHero runs your warehouse, cleanly, on one of the stronger APIs in the field. It still isn't built to show your clients, day by day, that you hit the number the contract promises - and that is exactly what they ask you for.
- ShipHero SLA tracking is calculable, not defined. The shipment data is all there. What's missing is the rule: which timezone applies per warehouse, which holidays count, when the clock starts - and all of it split by account, because every client contract reads differently.
- Labor sits in the raw data, not in a report. ShipHero does report pick and pack volume per worker per day. Turning that into a labor report across days, shifts and multiple warehouses is possible, but it doesn't come pre-built.
- Your client has no window of their own. So they email. Every day, per brand, per warehouse, asking for the numbers you already have.
- Billable volumes get assembled by hand. Shipments, special handling, storage lines - at month end, out of several exports, stitched together manually.
What we read out of ShipHero.
The connection runs through the GraphQL API. The documentation is open, there is an active community forum alongside it, and none of it needs a sign-off from ShipHero or an extra module inside the account.
Scroll table sideways
| What we read | From | What it becomes |
|---|---|---|
| Shipments | the shipping process | throughput, the SLA clock, worker reference |
| Daily picking performance | daily picking summary | labor performance |
| Daily packing performance | daily packing summary | labor performance |
| Built-in performance dashboard | ShipHero's own performance overview | cross-check at sign-off |
| Warehouses and accounts | account structure | the client separation, everywhere |
We do not read pricing, margins, or end-customer data beyond what a shipment itself carries. Running a warehouse doesn't require either, so both stay out of the connection.
Multi-account operation isn't a bolt-on inside ShipHero, it's the premise the platform runs on - which is what you'd expect from software built for 3PLs rather than for a single brand with a warehouse attached. Your ShipHero accounts become your clients in max.dash without inventing a separation field anywhere.
The ShipHero labor report: what holds up, what doesn't.
This is the one section where sounding capable matters less than being precise, so here is the honest version.
The honest limit: tying the picker to one specific shipment is, by multiple accounts on ShipHero's own community forum, a known gap in the system. Daily labor performance per worker is reliable and comes straight out of ShipHero's daily summaries. Attributing a single shipment to exactly one person is not always possible, and that isn't a knock against ShipHero - it's a boundary worth knowing before you set expectations with a client. Whoever needs that depth gets it through a time tracking connection instead, paired with a mapping of scanner logins to people. That route calculates minutes and volume per person independently of what any warehouse system chooses to expose, and it works the same way across every system in your stack.
What max.dash builds a ShipHero KPI dashboard out of.
Not a second warehouse system. The reporting layer, billing report and client portal that ShipHero itself was never built to hand you as a finished product.
Scroll table sideways
| Capability | With ShipHero | Built from |
|---|---|---|
| SLA rate per client | yes | timestamps, accounts, your timezone and holiday rules per warehouse |
| Throughput and daily forecast | yes | shipments per warehouse and window |
| Labor performance | yes* | daily pick and pack volume per worker |
| Points per order content | via line items | order lines per shipment |
| ShipHero client portal | yes | accounts as the dividing line |
| ShipHero billing report | yes | shipments and special handling per account |
| Location comparison | yes | several warehouses in parallel |
| SLA with timezone rule | yes | the timezone on record per warehouse |
* at the daily, per-worker level. Tying one specific shipment to one person is a known limit - see the labor section above.
How the connection runs.
Four steps, a few days. You install nothing and your ShipHero account is never written to.
Create a third-party developer
You create a third-party developer inside your own ShipHero account and grant it the access the connection needs. Your own login is never shared - one of the cleaner onboarding routes in the field.
Map warehouses and accounts
Warehouses and accounts get mapped to your clients. That's the line every report, every portal login and every billing report separates on afterward.
Set timezone and SLA rules
Timezone per warehouse, holidays and cutoff times get fixed in writing. Running across several US timezones, this is the step that prevents an hours-long argument later.
Sign-off
One real week gets checked against ShipHero's own performance dashboard and the numbers you already trust. Only once the SLA rate, volumes and labor figures hold up 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 ShipHero?
No. ShipHero stays your warehouse system and nothing about it changes. max.dash reads along through the GraphQL API and puts a reporting layer on top. No migration, no extra module inside ShipHero.
Does max.dash write anything back into ShipHero?
No. Access is read-only through the GraphQL API. What we read is mirrored into a separate database and evaluated there. Nothing is created, changed or deleted inside ShipHero.
Do I have to share my own ShipHero login?
No. You create your own third-party developer inside your ShipHero account and grant it only the access the connection needs. Your own login never leaves your hands - compared to most other warehouse systems, this is about as clean as onboarding gets.
Can ShipHero show the picker for one specific shipment?
Not reliably. ShipHero reports pick and pack volume per worker per day, plus a built-in performance dashboard of its own - daily labor performance is solid. Tying one specific shipment to exactly one person is a known gap in the system according to multiple reports on ShipHero's own community forum. Whoever needs that depth gets it through a time tracking connection instead.
How are timezones and holidays handled in the SLA?
ShipHero clients mostly run warehouses across the US and Canada, often spread over several timezones. The timezone per warehouse and the holidays that feed the SLA clock are set explicitly during setup - otherwise the cutoff calculation drifts by hours without anyone noticing.
See your own SLA rate before you decide.
30 minutes, no commitment. We show you on real numbers what comes out of your ShipHero data.