Mintsoft WMS Setup
Connect your Mintsoft warehouse so the chatbot can answer order, stock and return questions, and so cancellations and order changes reach the warehouse first.
Do I need this?
Only if your orders are picked and shipped from a warehouse running Mintsoft — your own, or a 3PL’s. If your warehouse uses Ongoing WMS, see the Ongoing WMS Setup guide instead.
Mintsoft is in beta
It works end to end, but every Mintsoft warehouse names its own order statuses and we are still learning them from live stores. If something looks wrong, contact Supportify support.
What this integration does
Answers from the warehouse
The chatbot can tell a customer where their order is, what was in it, whether their return has been booked in, and what is in stock — read from Mintsoft at the moment they ask.
Cancellations and order changes reach the warehouse first
When a customer cancels an order or changes it (a new delivery address, a different size), Supportify checks the order in Mintsoft and sends the change there before it reaches your shop. The same applies when your team cancels or edits an order from the Supportify inbox. Without this, the shop is changed and the warehouse still ships what it was given.
Return registration (optional)
When a return is agreed in chat, Supportify registers it in Mintsoft so the warehouse knows to expect the parcel.
Before you start: the API key
Create an API key in Mintsoft
- In Mintsoft, go to Settings → Client User Settings.
- Pick the user the integration should act as. It needs access to the client this shop sells from.
- Choose Actions → Generate API Key and copy the key.
- On the same user, choose Actions → Set API Key to Never Expire.
If your 3PL runs Mintsoft for you, ask them to do this, or to give you a user that can.
Do not skip “Set API Key to Never Expire”
Without it, Mintsoft stops accepting the key 24 hours after it was created. The integration then goes quiet: the chatbot can no longer answer order questions, and Supportify reports “Mintsoft rejected the API key” (a 401 error). To fix it, generate a new key, set it to never expire, and paste it into Supportify again.
Setup
Connect Mintsoft in Supportify
- Go to Settings → Integrations → Mintsoft and click Connect.
- API key — paste the key and click Test connection.
- Client & warehouse — pick the client this shop sells from. Optionally pick a warehouse; leave it on “All warehouses” unless this shop ships from one of several, in which case stock answers are limited to that site.
- What reaches the warehouse — choose the sync settings below.
- Review & save.
What is a client?
Mintsoft’s name for a brand the warehouse holds stock for — what Ongoing calls a goods owner. A 3PL’s key can often see many clients. Pick the one whose stock and orders belong to this shop.
Sync settings
- Cancel in Mintsoft too (on by default) — a cancelled order is cancelled in the warehouse first, and refused if the warehouse has already started it.
- Send order changes to Mintsoft (on by default) — a new delivery address or a changed item reaches the warehouse.
- Register returns in Mintsoft (off by default) — a return agreed in chat is registered in the warehouse.
- Verify the customer’s email first (on by default) — the customer confirms a code before the chatbot reads out anything about an order.
With the first two off, a change made in your shop does not reach the warehouse, so a cancelled order can still be shipped.
How cancellations and changes stay safe
The warehouse picks and ships whatever it holds, so every rule below errs towards leaving the order alone and handing it to a person.
Only your client’s orders
Orders are looked up only within the client you chose, never among another brand’s orders at the same 3PL.
Once the warehouse has started, nothing is changed
If the order is being picked, has been packed or has been despatched, the chatbot will not cancel or change it. It tells the customer that a colleague will follow up, and the case goes to your team.
A status name we don’t recognise counts as started
Mintsoft lets every warehouse name its own order statuses. Supportify recognises the common ones, and treats any name it does not recognise as “already started” — so the worst case is a colleague following up, never a cancelled order that still ships.
If your 3PL uses custom status names, cancellations and changes will be blocked for those orders. Contact Supportify support with the status names so we can add them.
Several matching orders means no automatic change
Some 3PLs renumber orders, for example by adding a prefix, so Supportify sometimes has to search more loosely than the exact order number. If several warehouse orders match and nothing tells them apart, nothing is cancelled or changed automatically.
Added items wait for payment
If a change adds an item the customer has not paid for yet, the order is set to Awaiting Payment in Mintsoft so it is not picked, and released as soon as the payment arrives.
FAQ
It worked yesterday and today the chatbot can’t find any orders
Almost always the API key expired because Set API Key to Never Expire was not chosen. Generate a new key in Mintsoft, set it to never expire, and paste it in under Settings → Integrations → Mintsoft.
Why was a cancellation refused for an order nobody has picked?
Most likely the order’s status in Mintsoft has a name Supportify does not recognise yet, which it treats as started. Contact Supportify support with the status name shown in Mintsoft and we will add it.