Skip to main content
Receiving Retail Orders: Setup Types

A description of different ways we can receive retail orders

D
Written by DCL Support
Updated over a week ago

DCL can receive retail orders in several ways, each requiring a different setup.

Please consult your Account Manager who can assist you with one of these setups.

Setup Types

Type

Mapping

Direct EDI Connection

Retailer (EDI) > DCL EDI Platform

Indirect EDI Connect

Retailer (EDI) > 3rd Party EDI Platform > DCL Webservices API

Manual Upload

Retail (EDI) > 3rd Party Platform or other > POs are manually uploaded into eFactory

Direct EDI Connection

For Direct EDI Connection, DCL works with the customer to connect directly to the Trading Partner (i.e. Retailer). DCL supports the appropriate EDI documents to receive retail orders and any required EDI documents, including confirmations, ASNs, etc.

Supported Documents (examples)

  • 850 - Purchase Orders

  • 860 - Advanced Ship Notification

  • 810 - Invoices

  • 860 - Change order request

Indirect EDI Connections

For Indirect EDI DCL doesn’t exchange the EDI documents directly with the Trading Partner but utilizes custom fields within our Webservice API's. Using those custom fields allows us to follow all requirements and provides the shipping details so the DCL customer or their 3rd party provider can send all EDI requirements and coordinate directly with the designated Trading Partner.

Connected EDI Partners

  • SPS Commerce

  • True Commerce

Manual Upload

For Manual Upload DCL doesn't exchange the EDI document directly with the Trading Partner but allows the customer to utilize our Mass Upload spreadsheet and upload the orders directly to eFactory.

Using the custom fields within eFactory within the document allows DCL to follow all requirements and provide the shipping details to the customer or their 3rd party provider to close the loop with the designated Trading Partner.

Learn more about how to do a Mass Upload here.

Did this answer your question?