Mintsoft shipments, stock and goods in
Lesson 8 of 28 7 min read
Configure what comes back from Mintsoft (shipments, receipts and stock) and how goods-in records are created, plus the gotchas to check before go-live.
Orders out are only half the Mintsoft story. This lesson covers the four other groups: the shipments and receipts that come back, the stock levels, and the goods-in records you create.
Mintsoft Shipment
Shipments use the standard import window (setupDate, lastImportDate, importDelay) and
the same five filters as order import: order status, client, channel, courier service and
warehouse. Two more settings matter for matching and lines:
| orderNumberReferenceType | The reference type that carries the Mintsoft order number on imported shipments. |
|---|---|
| externalOrderReferenceType | The reference type that carries the original source order reference, so the shipment can be tied back to the ERP or storefront order. |
| skipBundleProcessing | When true, bundles on shipment lines are left as-is. When false or unset, they are expanded into components. |
| disableExpectedPayableTag | Stops the expected payable tag being added to imported shipments, skipping the check that calculated values match. |
Keep bundle handling consistent
If orders go to Mintsoft with bundles expanded but shipments come back with bundles left
as-is (or the reverse), the shipment lines will not line up with the order lines. Set
skipBundleProcessing the same way on both groups unless you have a reason not to.
Mintsoft Inventory
| lastImportDate | Managed by the system: each run fetches only stock changes since the last import. |
|---|---|
| includedWarehouseIds | Mintsoft warehouse ids to include. Empty includes all warehouses. |
| includedWarehouseCodes | Mintsoft warehouse codes to include, instead of or as well as ids. When both are set, stock is included if it matches either. |
A 3PL with several sites may hold stock you cannot sell from, such as a returns or quarantine warehouse. List only the warehouses that should count towards availability.
Mintsoft Goods Inbound
| goodsInType | The Mintsoft Goods In type assigned to the inbound records Supply Lens creates. |
|---|
Ask the 3PL which Goods In type they expect for supplier deliveries.
Mintsoft Goods Inbound Receipt
Receipts use the import window plus three filters:
| filterByAsnStatusId | Only receipts linked to ASNs in these statuses are imported. |
|---|---|
| filterByClientId | Only receipts for these Mintsoft clients. |
| filterByWarehouseId | Only receipts at these Mintsoft warehouses. |
Choose the ASN statuses deliberately
If you only want receipts the warehouse has finished booking in, filter to those ASN statuses. Ask the 3PL which status ids mean that in their Mintsoft account.
Fernhill Teas' first stock import
Fernhill's 3PL runs two Mintsoft warehouses: MAIN and RETURNS. The first stock import
shows returned, unsellable tins as available in Unleashed. The implementer sets
includedWarehouseCodes to MAIN only, and the next run brings availability back in line.
Mintsoft gotchas checklist
filterByClientIdset on every import group if the 3PL account is shared.skipBundleProcessingconsistent across Order and Shipment.- Reference types chosen so shipments match their orders.
- Inventory limited to sellable warehouses.
automaticallyCancelOrdersleft on unless someone owns manual cancellations.
Recap
- Shipments and receipts use the standard import window and filters, including client and warehouse.
- Reference types on shipments tie each despatch back to its order.
- Inventory can be limited by warehouse id or code; either match includes the stock.
- goodsInType sets the Goods In type for inbound records; receipts can be filtered by ASN status.
- Keep bundle handling the same for orders and shipments.
Quick guides for this topic
Your progress is saved in this browser. Create a free account to keep it everywhere, take quizzes and earn certificates.