Shopify WMS: choose and connect warehouse data
Choose a Shopify WMS for reliable stock and order handoffs. Map locations, allocations and fulfilment updates to the delivery promises customers see.
- Published
- Last updated
A Shopify warehouse management system (WMS) connects warehouse stock and dispatch records to your store through a supported app or connector. Choose it by location-level stock ownership and the order updates it sends back, including partial shipments and returns.
ShipHero suits retailers that need warehouse allocation rules and partial shipping. Mintsoft suits retailers connecting their own warehouse or an existing fulfilment partner through configurable Shopify connections. The deciding question is whether each system preserves the item, quantity and location behind the customer’s order.
Decide when Shopify needs a WMS
Add a WMS when warehouse allocation and dispatch need a separate operational record that stays consistent with Shopify. A WMS records warehouse inventory and the work required to fulfil orders. Inventory software can track quantities across channels without controlling that warehouse work. A carrier-label tool buys postage and produces labels, which alone doesn’t establish what each warehouse must fulfil.
Shopify already supports stock at multiple locations and routes online orders between them. Multiple warehouses alone don’t require another system. A separate WMS becomes useful when allocations, partial dispatches or warehouse-partner updates require more coordination than your existing process provides.
For example, staff might currently reconcile a warehouse spreadsheet against Shopify before answering whether an order has shipped. A WMS connection can replace that reconciliation only if the dispatch record reaches the correct Shopify order lines. Printing a label without sending the fulfilment update leaves the support problem in place.
Compare systems by the Shopify handoff
Compare WMS options against the same order flow, including what happens when only part of an order ships. Use this illustrative retail scenario: one Shopify store, two warehouses and 2,000 orders per month, with occasional split shipments and returned goods.
ShipHero
ShipHero is the stronger fit when you want warehouse allocation rules and explicit partial-shipping controls. Its native Shopify integration synchronises orders and inventory, with tracking sent back to Shopify. This is a documented connector, beyond a generic claim that software has an application programming interface (API).
ShipHero’s order settings include multi-warehouse allocation rules and an import boundary based on order ID. Orders usually arrive within seconds, although several minutes can occur. Its partial-shipping instructions explain that Allow Partial cannot be enabled on merged orders. That restriction changes the setup if you also combine customer orders.
ShipHero’s returns API supports receiving a returned line and optionally restocking it at a warehouse location. Set up return creation separately from receipt and restocking. Include that route in your implementation alongside location mapping and allocation rules. ShipHero directs pricing enquiries to a quote, so its recurring charge for this scenario is quote-based.
Mintsoft
Mintsoft is the stronger fit when your fulfilment partner already uses it or you need configurable warehouse connections. Its official public Shopify app imports orders and sends stock and dispatch updates back. The connection includes warehouse selection and separate timing controls for stock, orders and dispatch.
Mintsoft can import partially fulfilled Shopify orders when that setting is enabled. It also documents importing third-party order splits as separate orders. Its guidance favours an import delay for those splits and warns against combining them with webhook imports. These are implementation choices, so budget for configuring the connection and proving its import boundaries.
Mintsoft’s Shopify troubleshooting guide says it updates stock only at its designated Shopify location. It also warns that restocking a refund in Shopify can double-add stock after a Mintsoft return. For outsourced fulfilment, that makes the partner’s return receipt and your refund action separate responsibilities.
Compare the same warehouse requirements
Use the documented differences below to choose what to configure for the two-warehouse scenario.
| Requirement | ShipHero | Mintsoft |
|---|---|---|
| Multiple locations | Warehouse-to-Shopify-location stock mapping and allocation rules | Warehouse connection with a designated Shopify location |
| Split fulfilment | Allow Partial, with a restriction on merged orders | Partial-order import setting and controls for externally split orders |
| Returned goods | Return receipt and optional restocking through its returns API | Warehouse return processing must be coordinated with Shopify refund restocking |
| Implementation work | Map locations, set allocation and partial-shipping rules, limit historical imports | Configure warehouse connections, import timing and partially fulfilled orders |
| Recurring cost | Supplier quote for the required account and warehouses | Core subscription based on the applicable package, with order volume and users affecting cost |
Mintsoft’s pricing model separates core software from additional modules, onboarding and support options. Mobile user licences also affect the package. For 2,000 monthly orders across two warehouses, compare the full recurring package with ShipHero’s quotation, plus each supplier’s one-off implementation charge. A headline entry tier doesn’t establish the total for that scenario.
If you run both warehouses, your team owns both location mappings and the allocation policy. With a third-party logistics (3PL) partner, the partner owns its warehouse records. Your store needs the partner’s accepted fulfilment instructions and dispatch updates. Connect its established WMS before buying a second system that would write to the same stock.
Assign stock and allocation ownership
Assign one system to publish warehouse quantities for each mapped location, then document how Shopify’s order commitments affect that number. Don’t let two connectors independently overwrite the same quantity.
Shopify’s inventory model connects each product variant to an inventory item. An inventory level connects that item to a location. Save those identities alongside the warehouse item code, or stock keeping unit (SKU). A matching product name alone can’t identify the correct size or colour.
| Record | Meaning and ownership to agree |
|---|---|
| On-hand stock | Units physically present at the warehouse, including units held aside |
| Committed stock | Units Shopify has committed to orders or other supported commitments |
| Reserved quantities | WMS allocations or other holds, mapped to their actual Shopify state |
| Available to sell | Sellable quantity after the applicable commitments and unavailable stock |
| Fulfilment instruction | Shopify order lines, remaining quantities and assigned location sent to the warehouse |
| Dispatch record | Shipped lines and quantities returned by the WMS, with parcel tracking |
In Shopify’s inventory states, committed and reserved are distinct API quantities. Reserved stock appears within Unavailable in the admin. Don’t map a WMS field called “reserved” by name alone. Establish whether it means order allocation, a quality hold or something else.
For an illustrative location, 10 on-hand units with two committed and one unavailable leave seven available. If the WMS already sends seven sellable units, subtracting the two commitments again would incorrectly show five. The connector’s destination field determines how that value must be applied.
ShipHero documents one-way inventory publication from its available quantity to Shopify when inventory management is enabled. Shopify quantity edits don’t flow back. Make the correction in the warehouse owner’s record before its next stock publication overwrites a store-side edit.
A cancellation must release the allocation once. Confirm the warehouse has stopped work before releasing stock for sale. For a return, record receipt and condition before restoring sellable quantity. Shopify’s return-processing workflow separates restocking from refund timing. Keep the financial refund and physical stock change separate in your integration too.
Keep customer availability and order status accurate
Keep stock answers tied to sellable quantities and delivery answers tied to the actual shipment records. A warehouse’s total on-hand stock can include goods unavailable to online customers.
Shopify’s location rules determine which locations fulfil online orders and how orders are routed. A stock update at an ineligible location doesn’t make that quantity available for the same online promise.
Consider an illustrative order for a coat and a scarf. The coat is allocated to Perth and the scarf to Melbourne. Shopify’s fulfilment-order model groups work by assigned location. It distinguishes the instruction to fulfil from the fulfilment record created when work progresses.
- The connector imports the assigned lines and quantities into the warehouse records.
- Perth dispatches the coat and returns its line quantity with tracking.
- The scarf remains unfulfilled until Melbourne sends its own dispatch update.
- The customer sees the coat’s tracking while the scarf retains its separate status.
If Melbourne’s update is late, support must distinguish a missing message from goods that haven’t shipped. Keep parcel-specific tracking and the remaining quantity available to whoever answers the order question. The guide to split shipments explains how to communicate that item-level difference.
Connect and check the warehouse workflow
Connect a limited set of orders first, with expected records written down before enabling broad imports or stock publication. Use an isolated test store and the provider’s supported test environment where available.
- Map every warehouse to its intended Shopify location. Match each SKU to its variant and inventory item. Record which locations can fulfil online orders.
- Authorise the official app and review its requested permissions. Custom inventory integrations require inventory read/write access. Fulfilment-order access depends on the locations the app manages.
- Set import boundaries before activating order processing. Decide which existing open orders migrate and which remain with the old process. Prevent the same order entering both queues.
- Reconcile starting quantities with stock publication paused. Enable one direction for each owned field, then run the controlled orders below.
- Compare both systems after their configured sync interval. Inspect the customer-facing order status as well as the connector’s success log.
| Controlled order | Expected warehouse and Shopify records |
|---|---|
| Normal order | One import, correct warehouse allocation, one shipped quantity and matching tracking |
| Split shipment | Separate shipped line quantities and tracking, with the remaining item still unfulfilled |
| Cancellation before dispatch | Warehouse confirms stopped work, remaining fulfilment is cancelled and the allocation is released once |
| Returned item | Receipt records the item and location, sellable stock rises once after approval and the refund stays distinct |
A fulfilment service that has accepted a request uses a cancellation-request process. A store-side cancellation instruction alone doesn’t prove the warehouse stopped. Include that acknowledgement in the cancellation check before the workflow goes live.
Handle failed or conflicting updates
Trace a failed update from the source record to the destination response before replaying it. A retry is safe only when you know whether the first attempt changed stock or created a shipment.
| Symptom | Records to compare | First action |
|---|---|---|
| Stalled fulfilment | Warehouse dispatch state, connector attempt and Shopify fulfilment response | Establish whether dispatch occurred before resending status |
| Stock at the wrong location | Warehouse ID, Shopify location ID and inventory item ID | Correct the mapping before the next stock publication |
| Duplicate dispatch | Shipment ID, shipped line quantities and existing Shopify fulfilment | Stop retries and reconcile the existing shipment first |
| Extra stock after a return | Return receipt, restock action and Shopify inventory history | Identify which system restored the quantity twice |
Mintsoft specifically documents orders remaining Picked after labels are printed. Its dispatch update requires the order to reach Dispatched. Changing the stock total won’t repair that missing event.
The retailer owns the customer promise and authorises corrections. The warehouse confirms what physically shipped or returned. The connector provider owns diagnosis and replay of failed integration messages. Keep the affected identifiers and original responses with the escalation.
Where the connector supports a repeat-safe operation, reuse its original operation identifier. Otherwise reconcile the existing destination record before authorising another write. ShipHero’s return API, for example, adds received and restocked quantities incrementally on each call. Repeating that write blindly can change the stock again.
For quantity-specific recovery, use the Shopify inventory sync guide. Resume normal imports only after the affected orders and location quantities agree, with one named person responsible for releasing the paused queue.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.