Assigned is not packed.
max.dash reads your Mintsoft read-only over an API key and turns it into an SLA rate per client, a client portal where each brand sees only its own numbers, and the actual labor performance behind an order - not just who it was assigned to.
Mintsoft is a product of The Access Group. 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 UK 3PLs can't get out of their WMS.
Mintsoft runs your warehouse and is widely used among fulfillment providers in the UK market. It isn't built to prove to your clients, month after month, that you delivered what the contract says.
- The SLA rate per client is calculable, not defined. The order 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 client, because every contract reads differently.
- Assigned is not packed. Mintsoft shows which staff member an order was assigned to. Whether that person actually packed it is a different question, and the system doesn't answer it - more on that below.
- Your client has no window of their own. So they email. Every day, per brand, asking where an order is - and every unanswered email costs trust rather than time.
- Billable volumes per client get assembled by hand. Shipments, returns, special handling. At month end, out of exports, again.
What we read out of Mintsoft.
The connection runs through the Mintsoft REST API. Access is self-serve: an API key is requested and is typically available within 24 hours. No extra module inside Mintsoft is required.
Scroll table sideways
| What we read | From | What it becomes |
|---|---|---|
| Orders and shipments | order management | throughput, backlog, the SLA clock |
| Clients | your list of clients | the client separation, everywhere |
| Order assignment | assignment on the order, single and batch | the planned distribution of work per staff member |
| Timestamps | order and shipment events | cycle time, cutoff check |
| Order lines | shipment detail | weighting, points per order content |
| Inventory and movements | stock per client | cover, receiving, returns |
We do not read pricing, margins, or end-customer data beyond name and delivery address. Running a warehouse does not require them, so they stay out of the connection.
Assigned versus actually done, kept apart.
Mintsoft can assign an order to a staff member. That's a real feature with its own place in the system - it just measures something other than what the name suggests.
Mintsoft assigns one or more orders to a specific staff member, including whole batches of orders at once. That's the plan: who is meant to be responsible for which order. What it doesn't record is who actually picked and packed it. The assignment tells you who an order was assigned to. It does not tell you who packed it in the end. Assignment says nothing about whether the assigned person handled the order themselves, passed it to someone else, or never touched it at all.
That doesn't make the plan useless. It shows how work was distributed and scheduled, and it's the basis of any reasonable shift plan. It just isn't measured performance - and a report that mixes the two up credits packages to the wrong person.
For the actual, measured labor report, the route runs around Mintsoft: through your time tracking system plus a mapping of scanner logins to your people, max.dash calculates minutes and volume per person, regardless of who an order was assigned to.
What max.dash makes of it.
Not a second warehouse system. The reporting layer your warehouse system was never meant to carry.
Scroll table sideways
| Capability | With Mintsoft | Built from |
|---|---|---|
| SLA tracking per client | yes | timestamps, client, your cutoff and working-day rules |
| Throughput and KPI dashboard | yes | orders and shipments 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 | client as the dividing line |
| Billing report | yes | shipments, returns, special handling |
| Cover and stock value | yes | inventory per client |
| Returns and receiving | yes | movements, stock records |
How the connection runs.
Four steps, a few days. You install nothing and your Mintsoft account is never written to.
Request an API key
You request an API key in Mintsoft's self-serve. It's typically available within 24 hours - we tell you which rights the connection needs, and which it explicitly does not.
Map your clients
Your Mintsoft clients become clients in max.dash. That is the line every report, every invoice figure and every portal login separates on later.
Connect time tracking
Cutoff time, working days, public holidays and exclusions, per client. If you want labor performance, this is where time tracking gets connected and scanner logins get mapped to people.
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 Mintsoft?
No. Mintsoft stays your warehouse system and nothing about it changes. max.dash reads along through an API key and puts a reporting layer on top. No migration, no extra module inside Mintsoft.
Does max.dash write anything back into Mintsoft?
No. Access is read-only. What we read is mirrored into a separate database and evaluated there. Nothing is created, changed or deleted inside Mintsoft.
Can Mintsoft track SLA per client on its own?
Mintsoft gives you the order 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 client. That calculation is what max.dash takes over, per client, every day.
Is an order assignment in Mintsoft the same as actual packing performance?
No, and the difference matters. Mintsoft records who an order was assigned to - that is the planned distribution of work, even for whole batches of orders at once. A record of who actually packed the order does not exist. So you know who an order was assigned to. You do not know who packed it. For the actual, measured performance, max.dash connects your time tracking system and maps scanner logins to people.
How long does the connection take?
A few days. Request an API key - typically available within 24 hours - map your clients, connect time tracking if you want it, then sign off against one real week of data. You install nothing.
See your own SLA rate before you decide.
30 minutes, no commitment. We show you on real numbers what comes out of your Mintsoft data.