The DCL Logistics connector links the app with DCL's eFactory warehouse management system (WMS). The app sends DCL your shipping requests, cancellations and inbound purchase order notices (arrivals). It brings back fulfillments with tracking, inventory levels and receipts. This keeps order status and stock levels in sync between the app and your DCL warehouses without manual updates.
With this connector, you can:
- Send shipping requests to DCL for fulfillment.
- Send order and shipping request cancellations to DCL.
- Get fulfillments and tracking numbers from DCL.
- Get inventory levels for each SKU and warehouse.
- Send arrivals (inbound PO notices) to DCL and get receipts back.
- Create a location in the app for each DCL warehouse.
Setup
Before you begin, make sure you have:
- API access to DCL eFactory. Your DCL account manager can give you an API username and password.
- Your DCL account number.
- The list of DCL warehouse codes you use, including each warehouse's inventory types (for example,
LAwithZLA,ZLAC). Your DCL contact can confirm these. - Your products already set up in DCL. The connector doesn't create products in DCL.
To connect DCL Logistics:
- Navigate to Integrations in the app.
-
Click Add Integration, and then select DCL Logistics.
[Screenshot: Connect DCL Logistics setup pop-up]
- Select the Environment. Use Sandbox while testing and Production when you go live.
- Enter your DCL Username and Password.
- Enter your Account Number.
- Enter a Default Location Code. This is a fallback warehouse code, such as
LA. - Enter your Freight Account if your DCL account requires one.
- Click Connect. The app checks your credentials with DCL.
- Enter each warehouse under DCL warehouses in the format
code:name:inventory types, for exampleLA:LA/Ontario:ZLA,ZLAC. - Toggle on the flows you want to use, and then click Save.
Settings
| Setting | Description | Options/Default |
|---|---|---|
| Environment | The DCL environment to connect to. Sandbox checks orders but processes them only when you ask DCL to. | Production, Sandbox. Default: Production |
| Default Location Code | The DCL warehouse code used when a shipping request's location has no DCL code. | Optional |
| Freight Account | The carrier account billed for outbound shipments. Some DCL accounts reject orders without it. | Optional |
| Pull locations from DCL | Creates a location in the app for each entry under DCL warehouses. | On/Off. Default: Off |
| DCL warehouses | One entry per warehouse in the format code:name[:inventory types]. The first code is used for orders and arrivals. The inventory types are used to match stock. |
For example, LA:LA/Ontario:ZLA,ZLAC
|
| Push shipping requests to DCL | Sends new and updated shipping requests to DCL. | On/Off. Default: Off |
| Push only shipping requests with specific order IDs | Sends only the shipping requests for the order IDs you list. Use this while testing. | Optional |
| When DCL cannot cancel a shipping request | The status the app applies when DCL refuses a cancellation because the order is already being picked. | Review required (default), Canceled, Failed |
| When DCL cancels an order | The status the app applies to the shipping request when DCL cancels the order. | Canceled (default), Canceled + Restock, Review required, Failed |
| Push order cancellations to DCL | When you cancel an order in the app, cancels the matching DCL orders. | On/Off. Default: Off |
| Push cancellations only for specific order IDs | Sends cancellations only for the order IDs you list. | Optional |
| Pull fulfillments from DCL | Gets shipped cartons and tracking numbers from DCL. | On/Off. Default: Off |
| Pull inventory from DCL | Gets the full inventory list from DCL on each run. | On/Off. Default: Off |
| Pull inventory only for specific SKUs | Gets inventory only for the SKUs you list. | Optional |
| Push arrivals to DCL | Sends arrivals to DCL as PO notices. | On/Off. Default: Off |
| Push only arrivals with specific order IDs | Sends only the arrivals for the order IDs you list. | Optional |
| Allow updating arrivals already pushed to DCL | Sends changes to a PO that DCL hasn't received yet, such as a new expected date or new lines. | On/Off. Default: Off |
| Pull receipts from DCL | Gets PO receipts from DCL, including the quantity received for each line and lot. | On/Off. Default: Off |
You can also start one-time pulls under Integrations → Actions. You can pull fulfillments by date or by external order ID, receipts by date or by external order ID, and inventory by SKU.
Flows
| Flow | Direction | Notes |
|---|---|---|
| Locations | Settings → Pipe17 | DCL has no locations API, so the app creates one location per entry under DCL warehouses. |
| Shipping requests | Pipe17 → DCL | Runs every 5 minutes. Each shipping request becomes one DCL order. Item descriptions longer than 100 characters are shortened. The app adjusts order numbers so an order split across several shipping requests doesn't create duplicate orders in DCL. |
| Cancellations | Pipe17 → DCL | DCL accepts a cancellation only while the order is still at Order Received (stage 10). If DCL refuses, the app adds a Late cancel exception to the shipping request and applies the status you selected. |
| Fulfillments | DCL → Pipe17 | Runs every 5 minutes. The app creates one fulfillment for each shipped carton, with its tracking number. If DCL cancels an order, the app applies the status you selected. |
| Inventory | DCL → Pipe17 | Runs every 5 minutes and gets the full inventory list each time. The app maps DCL's net available stock to Available and on-demand stock to Committed. |
| Arrivals | Pipe17 → DCL | Sent to DCL as PO notices. Updates are sent only if Allow updating arrivals already pushed to DCL is on. |
| Receipts | DCL → Pipe17 | Gets the quantities DCL received for each line and lot. |
| Products | Not supported | Create your products in DCL before you send orders or arrivals that use them. |
Troubleshooting
- A shipping request has a Late cancel exception
DCL had already started picking the order when the cancellation arrived. Ask your DCL Order Administration team to cancel it. DCL charges an Order Intervention fee for this. - Inventory doesn't sync for a warehouse
Inventory uses DCL's inventory type codes (such asZLA), not the warehouse code (such asLA). Add the inventory types to that warehouse's entry, for exampleLA:LA/Ontario:ZLA,ZLAC. To learn more, see Inventory. - DCL rejects shipping requests
The most common causes are SKUs that don't exist in DCL and a missing freight account. Create the products in DCL, or enter a Freight Account if your DCL account requires one. - Orders reach DCL but nothing ships
You may be connected to the Sandbox environment, which doesn't process orders unless you ask DCL to. Switch Environment to Production when you go live. - Fulfillments or receipts are missing for some orders
Run Pull fulfillments from DCL by external order ID or Pull receipts from DCL by external order ID from Integrations → Actions to pull them again. To learn more about shipping requests, see Shipping Requests in Pipe17.
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