Time and quantity. From the same source.
max.dash reads your Linnworks read-only and turns the pickwave's time fields into minutes per parcel per picker, an SLA rate per client, and a portal where each of your clients sees only its own numbers.
Linnworks is a product of Linn Systems 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 order management doesn't prove.
Linnworks runs your locations, your channels and your stock. For a fulfillment operator running several clients under one roof, a whole layer of reporting is still missing - and that layer is exactly what your clients ask about.
- The SLA rate is calculable, not defined. The order and shipment 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 separated per client.
- Locations and channels aren't client separation. They sort warehouse locations and sales channels, not clients. Anyone running several clients through one Linnworks account has to map that dividing line onto locations and channels themselves - the system doesn't hand it to you.
- The pickwave's time fields sit in raw data, not in a report. Who worked a pickwave, when it started and ended, and how much got done - all of it is there. It only becomes a report across days, shifts and pickers once somebody pulls those fields together and calculates.
- Your client has no window of their own. So they email. Every day, per brand, asking where an order is.
What we read out of Linnworks.
The connection runs through the REST API with self-serve application credentials, set up in the Linnworks application store. Third-party developers are explicitly welcome there and rate limits are documented - no sign-off from the vendor is needed outside that route, and no extra module goes into Linnworks.
Scroll table sideways
| What we read | From | What it becomes |
|---|---|---|
| Orders and shipments | order records | throughput, backlog, the SLA clock |
| Locations and channels | order header | the client separation, everywhere |
| Who worked the pickwave | the pickwave | performance per picker |
| Time on the pickwave | the pickwave | minutes per parcel, without estimating |
| Quantity per pickwave | the pickwave | weighting, points per parcel content |
| Stock and movements | stock records | cover, receiving, returns |
We do not read pricing, margins, or end-customer data beyond name and delivery address. Running a warehouse doesn't require them, so they stay out of the connection.
Minutes per parcel, straight from the source.
Across the systems we've reviewed, Linnworks carries the most complete time fields of the field. A pickwave doesn't just carry the handler and the quantity - it carries the start, the end and the time actually spent, in the same record.
The result isn't an assumption, it's one division inside a single record: time worked divided by quantity handled gives the rate - minutes per parcel, straight from the pickwave. Because time and quantity come from the same source, max.dash doesn't need to reconstruct anything from time windows and doesn't need to guess at breaks or walking time. On other systems, either the time span or the quantity link is missing. Here, both sit next to each other in the same place. How this rate is weighted across days and shifts, and combined with a points system by parcel content, is what turns it into a full labor report and a KPI dashboard your clients can be shown in the portal.
What max.dash builds from it.
Not a second warehouse system. The reporting layer your Linnworks account was never built to hand you for several clients under one roof.
Scroll table sideways
| Capability | With Linnworks | Built from |
|---|---|---|
| SLA tracking per client | yes | order and shipment data, your cutoff and working-day rules |
| Throughput and daily forecast | yes | pickwaves per hour, history |
| Labor report per picker | yes | pickwave handler data |
| Minutes per parcel | yes | time and quantity from the pickwave |
| Points system by parcel content | yes | quantity and order volume per pickwave |
| Client portal | yes | locations and channels as the dividing line |
| Billing report | yes | shipments, returns, special handling |
| Cover and stock value | yes | stock per client |
How the connection runs.
Four steps, a few days. You install nothing and your Linnworks account is never written to.
Create application credentials
You set up access with read rights in the Linnworks application store. Third-party developers are explicitly welcome there - we tell you which rights the connection needs, and which it explicitly doesn't.
Map locations and channels
Your locations and sales channels get mapped onto your clients. That's the line every report, every KPI dashboard and every portal login separates on afterward.
Check the pickwave report
We check against real pickwaves how completely handler, time and quantity are kept in your account, before the minutes calculation goes live.
Sign-off
One real week is checked against what you already know: SLA rate, volumes, labor report. Only then does the connection go into regular operation.
When a second system sits next to it.
Plenty of 3PLs don't run one system but two or three - per site, per client, per acquisition. That's 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 doesn't, there's 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. What that route needs is laid out on connecting a custom system.
Common questions.
Do I have to change or extend Linnworks?
No. Linnworks stays your system and nothing about it changes. max.dash reads along through the existing REST API and puts a reporting layer on top. No system change, no extra module inside Linnworks.
Does max.dash write anything back into Linnworks?
No. Access is read-only, through application credentials with read rights issued from the Linnworks application store. What we read is mirrored into a separate database and evaluated there. Nothing is created, changed or deleted inside Linnworks.
Can Linnworks track SLA per client on its own?
Linnworks gives you the order and shipment data an SLA rate can be calculated from. What's missing is the definition work: cutoff time, working days, public holidays, exclusions, and the separation by client across locations and channels. That calculation is what max.dash takes over, per client, every day.
How do minutes per parcel come out without max.dash estimating?
Linnworks records the time spent and the quantity handled for a pick run from the same source - so the rate per parcel follows directly, without estimating. Nothing is reconstructed from time windows and nothing is assumed.
How long does the connection take?
A few days. Set up application credentials, map locations and channels, check the pickwave report, then sign off against one real week of data. You install nothing.
See your own labor report before you decide.
30 minutes, no commitment. We show you on real numbers what comes out of your Linnworks data.