Deposco is an omnichannel supply chain fulfillment platform providing warehouse management (WMS) and order management (OMS) capabilities. The Deposco connector links your Deposco account to the app so product, order, and inventory data stays in sync between both systems without manual entry.
With this connector, you can:
- Push your product catalog to Deposco
- Push shipping requests to Deposco for fulfillment
- Pull inventory updates from Deposco
- Pull fulfillments from Deposco
- Push arrivals to Deposco
- Pull receipts from Deposco
- Pull locations from Deposco
Setup
Before you begin, make sure you have:
- A Pipe17 account. If you do not have one yet, book a demo with a Pipe17 team member to get started.
- Access to your Deposco admin account.
- Your Deposco connection details: Tenant, Business Unit, Username, and Password. Contact Deposco support to obtain these values.
To connect Deposco:
- Navigate to the Integrations tab in your portal and click Add Integration in the upper right corner.
- Find the Deposco connector and click Add.
- Leave the toggles on the Connection Flow Settings page turned off for now. You can enable them after the connection is established (see Settings below).
- Click Next.
- Enter your Tenant, Business Unit, Username, and Password in the corresponding fields.
- Click Connect.
Settings
All connection flow settings are toggles that are off by default. Each flow processes updates starting from the datetime when the Deposco integration was enabled.
| Setting | Description | Options/Default |
|---|---|---|
| Push products to Deposco | Pushes product catalog updates from the app to Deposco. | Off by default |
| Push shipping requests to Deposco | Pushes shipping request updates from the app to Deposco. | Off by default |
| Pull inventory from Deposco | Pulls inventory updates from Deposco into the app. | Off by default |
| Pull fulfillments from Deposco | Pulls fulfillment updates from Deposco into the app. | Off by default |
| Push arrivals to Deposco | Pushes arrival updates from the app to Deposco. | Off by default |
| Pull receipts from Deposco | Pulls receipt updates from Deposco into the app. | Off by default |
| Pull locations from Deposco | Pulls location updates from Deposco into the app. | Off by default |
Deposco settings
These settings are available on the integration after the connection is established.
Locations
| Setting | Description | Options/Default |
|---|---|---|
| Facility names | Deposco facilities cannot be automatically retrieved. Specify the names of your Deposco facilities to be used with the connector. | Text field |
Shipping requests
| Setting | Description | Options/Default |
|---|---|---|
| Order ID filter | Add one or more Order IDs to process only Shipping Requests associated with these specific Order IDs. Useful during the testing stage. | Empty (all orders processed) |
| Do not push shipments (create sales orders only) | By default, both a sales order and a shipment are created in Deposco. Select this option to prevent the creation of a shipment. | Off by default |
| Do not reuse shipments exported to Deposco | By default, canceled or otherwise unused shipping requests can be reused. Enabling this option prevents shipments that have been exported to Deposco from being reused in the app. Each shipping request retains a reference to its corresponding order in Deposco, and reusing it could interfere with that existing order. | Off by default |
| Send shipping labels with shipments | When enabled, the app attempts to send shipping labels to Deposco for any shipments that have labels. Not all Deposco environments support receiving labels, and some label formats may not be supported. | Off by default |
Fulfillments
| Setting | Description | Options/Default |
|---|---|---|
| Group fulfillments shipped together | Groups fulfillments with close Actual Ship Dates. Only the first batch can be grouped. | Off by default |
Products
| Setting | Description | Options/Default |
|---|---|---|
| SKU filter | Add one or more SKU values to push/pull Products exclusively for these SKUs. | Empty (all SKUs processed) |
| Force products resync | Triggers a complete resynchronization of the product catalog. The switch turns off automatically once the sync is initiated. | Off by default |
Inventory
| Setting | Description | Options/Default |
|---|---|---|
| SKU filter | Add one or more SKU values to push/pull Inventory exclusively for Products with these SKUs. Useful during the testing stage. | Empty (all SKUs processed) |
| Process inventory for bundles | Processes inventory for bundle products. | Off by default |
| Skip business unit filtering | Inventory is not filtered by the configured business unit. | Off by default |
| Allow merged locations | Allows inventory updates to use merged locations from another integration. | Off by default |
| Force inventory resync | Triggers a complete inventory resynchronization. The switch turns off automatically once the sync is initiated. | Off by default |
Arrivals
| Setting | Description | Options/Default |
|---|---|---|
| Order ID filter | Add one or more Order IDs to process only Arrivals associated with these specific Order IDs. Useful during the testing stage. | Empty (all orders processed) |
Receipts
| Setting | Description | Options/Default |
|---|---|---|
| Generate partial receipts | Creates receipts incrementally as Deposco updates received quantities. | Off by default |
| Force receipts resync | Triggers a complete receipts resynchronization. The switch turns off automatically once the sync is initiated. | Off by default |
Flows
| Flow | Direction | Notes |
|---|---|---|
| Products | Pipe17 → Deposco | Syncs product catalog updates. |
| Shipping requests | Pipe17 → Deposco | Creates orders in Deposco for fulfillment. Created as sales orders by default; see Creating customer orders below. |
| Inventory | Deposco → Pipe17 | Syncs inventory updates. |
| Fulfillments | Deposco → Pipe17 | Syncs fulfillment updates, including shipped lot numbers when applicable. |
| Arrivals | Pipe17 → Deposco | Syncs arrival updates. |
| Receipts | Deposco → Pipe17 | Syncs receipt updates. |
| Locations | Deposco → Pipe17 | Syncs location updates. |
Creating customer orders
By default, shipping requests pushed to Deposco are created as sales orders. You can configure the integration to create customer orders instead. This option is enabled per integration through the shipments mapping — no integration setting or code change is required.
Before you begin
- Confirm your Deposco account has the Enterprise Order Management (EOM) subscription. Customer order creation fails without it.
- Obtain your Deposco trading partner code and primary sales channel code. There is no API to list these values, so request the exact values from your Deposco account.
- Make sure the Deposco V2 connector is connected with the shipping requests push flow enabled.
Enable customer orders
- Open your Deposco integration and navigate to the Shipments outbound mapping.
- Open the mapping editor. Editing creates a custom copy for this integration only — the default mapping is unchanged for all other integrations.
- Find the rule labeled
customerOrder OFF-switch: disable this rule to create Customer Orders instead of Sales Orders (requires Deposco EOM)and disable it. With this rule off, the connector creates customer orders instead of sales orders. -
Find the
customerOrder.tradingPartnerrule and enter your trading partner code in the empty quotes. Leave$businessUnit$as is — it fills in automatically.// before ({ code: '', 'businessUnit.code': '$businessUnit$' }) // after ({ code: 'ACME_TP', 'businessUnit.code': '$businessUnit$' }) - Find the
customerOrder.primarySalesChannelrule and enter your sales channel code the same way. If the channel varies per order, map it from an order field instead of a constant. - Save the mapping. Leave the other
customerOrder.*rules unchanged — they build the rest of the order.
Verify the configuration
- Push one shipping request to Deposco.
- Check that Deposco shows a customer order (not a sales order) and that the order is not stuck in Review status. Review status usually means a wrong or unknown trading partner or sales channel code.
- Check that the shipping request in the app moves to
sentToFulfillment. If it moves tofailed, the error message names the incorrect field.
Revert to sales orders
Re-enable the OFF-switch rule in the mapping editor, or revert to the default mapping. New shipping requests are created as sales orders again.
Keep in mind:
- Shipping requests already sent as sales orders remain sales orders. Fulfillments come back for both order types.
- Lot numbers are not sent on the order. Deposco selects the lot and returns the shipped lot number on the fulfillment.
Troubleshooting
-
A customer order is stuck in Review status in Deposco
The trading partner code or primary sales channel code in the shipments mapping is wrong or unknown to Deposco. Verify the exact values with your Deposco account and update the mapping. -
A shipping request moves to failed status
The error message on the shipping request names the field that caused the failure. Correct the value in the shipments mapping and resend the shipping request. -
Customer order creation fails even though the mapping is configured correctly
Your Deposco account may not have the Enterprise Order Management (EOM) subscription, which is required for customer orders. Confirm the subscription with Deposco. -
The connection fails during setup
The Tenant, Business Unit, Username, or Password value is incorrect. Verify the values with Deposco support and enter them again.
Need Help?
If you need additional assistance:
- Use Ask Pippen, our AI agent, located at the top of the app page.
- Submit a support request with as much relevant detail as possible. Learn how to submit a request.
- For urgent issues, email us directly at support@pipe17.com.
We're here to help you succeed with your operations.
Comments
0 comments