Learn how to add multiple warehouse locations, map external e-commerce provider location IDs, and handle unrecognized warehouse alerts.
To support mid-market brands with distributed logistics, our platform supports multi-warehouse routing. Because tax calculations and shipping fees are determined based on the physical dispatch country and the customer's delivery country, keeping your stock locations accurately mapped is critical.
If you operate multiple dispatch nodes, you must map each warehouse's physical location and its corresponding ID from your external e-commerce store (e.g., Shopify Location ID).
Your primary warehouse is designated as the default. This location is used as the default shipping origin for calculating proximity zones and estimating delivery times.
To automate stock level syncs, you must link your warehouse to the corresponding location in your e-commerce platform. Here is how to find your Location ID across all supported platforms:
Note for Future Integrations: If you are connecting custom platforms or future integrations, the mapping rule remains the same: identify the unique identifier, slug, or code that your storefront uses to group inventory for that warehouse, and enter it in the Provider Location ID field.
Self-Healing Sync: If you fulfill an order from a warehouse location ID that is not mapped in your Salp settings, the system will not block the sync. Instead, it will auto-create a pending warehouse record, log a sync error, open a support ticket, and show an alert banner on your dashboard. You can resolve this instantly by editing the pending warehouse record in settings and filling in its address.