The Mintsoft connector sends your shipping requests, products, and arrivals from the app to Mintsoft, and brings warehouses, fulfillments, inventory, and receipts from Mintsoft back into the app. You can connect with a Mintsoft API key or with your Mintsoft user name and password.
With this connector, you can:
- Create locations in the app from your Mintsoft warehouses.
- Send shipping requests to Mintsoft as orders, and cancel them in Mintsoft when you cancel them in the app.
- Bring fulfillments with tracking details from Mintsoft into the app.
- Create and update products, including bundles, in Mintsoft.
- Pull inventory changes from each Mintsoft warehouse.
- Send arrivals to Mintsoft as ASNs and bring completed receipts back into the app.
Setup
Before you begin, make sure you have:
- An active Mintsoft account.
- Either a Mintsoft API key, or the user name and password that you use to sign in to Mintsoft.
- At least one warehouse set up in Mintsoft.
To connect Mintsoft:
- Navigate to Integrations in the app.
- Click Add Integration, and then select Mintsoft.
- Do one of the following:
- Enter your API key in the Mintsoft Api Key field.
- Enter your Mintsoft user name in the Mintsoft user name field and your password in the Mintsoft password field.
- Click Connect.
- After you connect, toggle on the flows you want to use. Pull locations from Mintsoft is on by default.
Settings
| Setting | Description | Options/Default |
|---|---|---|
| Process only shipping requests with specific order IDs | Sends only the shipping requests for the order IDs you list. Use this while testing. | Optional. Empty sends all |
| When shipping request is canceled in Mintsoft, apply the following status to Pipe17 | The status the app gives a shipping request when its order is canceled in Mintsoft. | Review required, Canceled, Canceled Restock, or Failed. Default: Canceled Restock |
| Mintsoft Order Status ID for cancelled orders | The Mintsoft order status ID that means “Cancelled.” The app checks it before it cancels an order in Mintsoft. | Default: 3 |
| Allow updating products already existing in Mintsoft product catalog | Updates products that already exist in Mintsoft. When off, the app only creates new products. | On/Off. Default: On |
| Process only products with specific SKUs | Sends only the products with the SKUs you list. After you change this list, turn on Force product catalog resync. | Optional. Empty sends all |
| Force product catalog resync | Sends your full product catalog to Mintsoft again. A full resync can take several days. Turns off automatically when the sync starts. | On/Off. Default: Off |
| Process inventory information only for products with specific SKUs | Pulls inventory only for the SKUs you list. You can enter an exact SKU or a regular expression enclosed in slashes. | Optional. Empty pulls all |
| Process inventory for bundles | Pulls inventory from Mintsoft for bundle SKUs. When off, the app skips bundles. | On/Off. Default: Off |
| Force inventory resync | Pulls all inventory from Mintsoft again. A full resync can take several days. Turns off automatically when the sync starts. | On/Off. Default: Off |
| Process only arrivals with specific order IDs | Sends only the arrivals for the order IDs you list. Use this while testing. | Optional. Empty sends all |
| Force receipts resync | Pulls receipts from Mintsoft again. Turns off automatically when the sync starts. | On/Off. Default: Off |
Flows
| Flow | Direction | Notes |
|---|---|---|
| Locations | Mintsoft → Pipe17 | Runs every 5 minutes. Creates a location in the app for each new Mintsoft warehouse. |
| Shipping requests | Pipe17 → Mintsoft | Runs every 5 minutes. Sends shipping requests that are ready for fulfillment to Mintsoft as orders. Sent shipping requests move to Sent to Fulfillment. If Mintsoft rejects one, its status changes to Failed. |
| Cancellations | Pipe17 → Mintsoft | When you cancel a shipping request in the app, the app cancels the order in Mintsoft. If Mintsoft can’t cancel it, the shipping request gets a late cancellation exception with Mintsoft’s message. |
| Fulfillments | Mintsoft → Pipe17 | Runs every 5 minutes. Brings shipped Mintsoft orders into the app as fulfillments with tracking number, tracking URL, carrier, and ship date. If an order is canceled in Mintsoft, the app applies the status from the cancel setting. If an order fails in Mintsoft, the shipping request moves to Failed. |
| Products | Pipe17 → Mintsoft | Runs every 5 minutes. Sends published products. For a bundle, the app first creates any component products that don’t exist in Mintsoft. |
| Inventory | Mintsoft → Pipe17 | Runs every 5 minutes. Pulls inventory changes for each Mintsoft warehouse that has a location in the app. |
| Arrivals | Pipe17 → Mintsoft | Runs every 5 minutes. Sends shipped arrivals for Mintsoft locations to Mintsoft as ASNs. Sent arrivals move to Expected. |
| Receipts | Mintsoft → Pipe17 | Runs every 5 minutes. Brings completed ASNs into the app as receipts and matches them to arrivals by PO reference. |
| Shipping methods | Mintsoft → Pipe17 | Once a day, the app adds your Mintsoft courier services as shipping methods. |
Troubleshooting
The connection fails or the integration stops with an authorization error
The API key, user name, or password is wrong or has changed in Mintsoft. Update the credentials in the connection settings, and then reconnect.A shipping request fails with “Warehouse mismatch”
The shipping request is assigned to a location that isn’t a Mintsoft warehouse. Make sure Pull locations from Mintsoft is on, and route the shipping request to a Mintsoft location. To learn more, see Getting Started with Locations in Pipe17.A shipping request has the status Failed
Mintsoft rejected the order or marked it as failed. Check the error on the shipping request, fix the data it points to, such as an address or SKU, and then send the shipping request again.A canceled shipping request has a late cancellation exception
Mintsoft couldn’t cancel the order, often because it’s already being picked or shipped. Contact your warehouse to stop the order in Mintsoft.A shipped order in Mintsoft has no fulfillment in the app
The app matches Mintsoft orders to shipping requests by order number. If the order was created in Mintsoft directly, or its order number changed, the app can’t find the shipping request and skips the fulfillment.
Need Help?
If you need additional assistance:
- Use Ask Pippen, our AI agent, located at the top of the platform page.
- Submit a support request with as much relevant detail as possible. Learn how to submit a request.
We’re here to help you succeed with your operations.
Comments
0 comments