Sign In
Book a Demo

DCL Logistics Integration for Outsourced Fulfillment

The DCL Logistics integration connects Pipe17 to DCL’s eFactory platform. Pipe17 routes each order to the right DCL warehouse, publishes only the stock DCL counts as available, and records the inbound stock each warehouse receives.
Book a demo
DCL Logistics logo tile for the Pipe17 DCL Logistics integration

The Solution for DCL Logistics Integration & Fulfillment Operations

DCL Picks and Packs. Pipe17 Decides Which DCL Warehouse Gets Each Order.

Wiring DCL in yourself takes an iPaaS to move orders and a legacy OMS to pick the warehouse, and your stock feed still reads DCL’s gross count. Pipe17’s Order Operations Platform replaces both. Its managed connector for DCL Logistics makes each DCL warehouse a location your routing rules can choose, with one stock count for every channel.
iPaaS & Custom Builds Legacy OMS Pipe17
Native API-First Connectivity ✅ ❌ ✅
Pre-Configured Commerce Connectors ❌ ❌ ✅
Custom Integration Mappings ✅ ❌ ✅
Advanced Order Orchestration ❌ ✅ ✅
Exception Management & Alerts ❌ ❌ ✅
Unified Inventory Management ❌ ✅ ✅
Rapid to Implement & Go-Live ❌ ❌ ✅
Easy to Add / Swap Channels & Flows ❌ ❌ ✅
Low Total Cost of Ownership (TCO) ❌ ❌ ✅

Future-Ready Brands and Fulfillment Providers Run on Pipe17

DCL Shipments, Stock, and Receipts Reach Pipe17 Without Re-Keying

Box with checkmark overlaid, representing a verified, completed or fulfilled order

Route Ecommerce and B2B Orders to the DCL Warehouse That Should Ship Them

Order routing sends each order to the DCL warehouse that should ship it, ready to pick, with carrier and ship-by date already set.

Two-tone icon of a computer dashboard with charts controls and gears symbolizing visibility and system control.

Sell Net Available, Not Gross On Hand

Pipe17 reads DCL's net available count rather than gross on hand, and your channels list nothing DCL has already promised to another order.

Two-tone icon of a multi-step process symbolizing completed purchase order fulfillment

Record Receipts Against the Inbound Shipment Pipe17 Announced

Pipe17 announces each inbound shipment to the DCL warehouse receiving it, then records every receipt DCL posts against that shipment, down to the lot.

Automated DCL Logistics Data Flows

Pipe17 pushes shipping requests, cancellations, and inbound shipment notices into DCL’s eFactory platform and brings fulfillments, inventory snapshots, and receipts out, on a continuous cycle in each direction. Your channels and Pipe17 see the same orders and the same count for each DCL warehouse.
  • Push Shipping Requests to DCL. Each order routed to a DCL warehouse becomes a DCL order in eFactory carrying the ship-to address, carrier and service, shipping instructions, the customer’s purchase order number, and lines with SKU, quantity, price, and ship-by and do-not-ship-before dates. Ecommerce, B2B, and transfer orders all travel this path.
  • Push Cancellations to DCL. When an order is canceled in Pipe17, Pipe17 cancels the DCL order behind each shipping request while DCL still holds it at Order Received. Once a pick list has printed, Pipe17 raises a Late cancel exception instead and lets the shipment and tracking finish syncing.
  • Push Inbound Shipments to DCL. Each inbound shipment headed for a DCL warehouse goes to that warehouse as a purchase order (PO) notification with the expected delivery date and lines. Pipe17 can also push changes to an announced PO, a setting that is off by default.
  • Map SKUs to DCL Item Numbers. Pipe17 matches each SKU once to the item number already set up for it in eFactory, and SKU Mapping carries that match across orders, inventory, fulfillments, and receipts.
  • Pull Fulfillments from DCL. Each carton DCL ships comes back as its own fulfillment with tracking number, carrier, service, ship date, expected delivery date, and weight, plus the SKU, quantity, serial numbers, lot, and expiration date of the units inside. A short-shipped line is reported as a rejected fulfillment.
  • Pull Inventory from DCL. A full snapshot per SKU and warehouse arrives with on hand, available, committed, on hold, and unavailable quantities. The available figure is DCL’s net figure, and units claimed by open orders never count as sellable.
  • Pull Receipts from DCL. Every receiving event DCL posts against an announced purchase order (PO) is recorded with its date and the quantity received per line and lot, with lot numbers and expiration dates. A PO received in several deliveries produces one receipt per delivery.
  • Create a Location for Each DCL Warehouse. Pipe17 builds one location per DCL warehouse from the list you enter and folds DCL’s separate order and inventory codes for that building into it. Routing and stock counts both point at it.

DCL Logistics Joins the Rest of Your Commerce Stack

Pipe17 builds and maintains the DCL Logistics connector on the Order Operations Platform, and your team writes no code. What DCL ships, holds, and receives reaches Pipe17 mapped to your SKUs, with nothing re-keyed.

Add DCL Warehouses Without Writing or Maintaining the Integration

Book a demo to see Pipe17 send an order to a DCL warehouse and put tracking in front of your customer before they ask where it is.
Book a demo
DCL Logistics horizontal logo

is better with

Pipe17 horizontal svg logo black

DCL Logistics Integration FAQs

The DCL Logistics integration sends orders, cancellations, and inbound shipment notices from Pipe17 to eFactory, the platform the 3PL runs its warehouses on, and brings fulfillments with tracking, inventory, and receipts back through a connector Pipe17 manages. Each DCL warehouse becomes a routable location. DCL runs the warehouse, while your channels, from Shopify to Amazon, and an ERP such as NetSuite work from one set of orders and one count.

An order reaches DCL when order routing, which runs in Pipe17 on every incoming order, assigns it to a DCL warehouse. Pipe17 then creates the DCL order in eFactory with the carrier, service, and ship-by date the order needs. Once Pipe17 pulls the fulfillment from DCL, the tracking number posts to the originating channel, with nothing re-keyed.

Pipe17 pulls a full inventory snapshot per SKU and DCL warehouse and treats DCL's net available figure as the sellable quantity, which it publishes to your channels alongside stock at your other locations. Net available already excludes units committed to open orders, on hold, or in process, and the sync can be limited to chosen SKUs.

Pipe17 cancels the DCL order behind each shipping request as long as DCL still holds it at Order Received. After a pick list prints, the cancellation has to be arranged with DCL's Order Administration team, and Pipe17 raises a Late cancel exception and sets the shipping request to the status you chose: review required (the default), canceled, or failed. DCL-initiated cancellations take a separate status you set.

Pipe17 announces each inbound shipment you create for a DCL warehouse as a purchase order (PO) notification, DCL's form of an advance ship notice (ASN), with the expected delivery date and lines. Each receiving event DCL posts comes back dated, with quantities per line and lot, and Pipe17 records it against that inbound shipment. Pipe17 ends up with what DCL received, not the quantity you announced, even across several loads.

Yes, ecommerce and B2B orders both reach DCL from Pipe17 as shipping requests carrying carrier, service, and shipping instructions. Routing decides which orders go to DCL and which DCL warehouse ships them, alongside the warehouses, stores, and other 3PLs you connect through the Pipe17 Network. Tracking from DCL returns to the channel each order came from, and DCL stock counts toward what every channel can sell.

Setup is credentials from DCL, a connection in Pipe17, a warehouse list, and SKU mappings. Ask your DCL account manager for eFactory API access (a username and password) and note your account number and warehouse codes. In Pipe17, pick Sandbox or Production, enter the credentials, and connect. List your DCL warehouses to create one location each, map SKUs to DCL item numbers, and switch on the flows you need.

Connect to DCL's Sandbox environment first, where DCL validates each order batch and processes it only on request, then switch the connection to Production when you are ready. While testing, restrict the shipping requests and inbound shipments Pipe17 pushes to specific order IDs and limit the inventory pull to a few SKUs. Your Pipe17 team can also re-pull fulfillments, receipts, and inventory on demand for any date range or order.