eZCom Integration

Julie  Houlton
Julie Houlton
  • Updated

In this article:



When growing an e-commerce business, implementing, connecting, and managing an Electronic Data Interchange (EDI) is no small feat. To help merchants better navigate selling their products through new channels and retailers, they can rely on Whiplash’s integration with eZCom. Together, we provide a complete solution to manage e-commerce data, inventory, orders, and fulfillment across both direct-to-consumer and retail.

eZCom integration with Whiplash’s Warehouse Management System (WMS) is available to all customers with an eZCom Lingo account. The integration allows:

  • Importing orders created on Lingo to Whiplash.
  • Fulfilling orders managed by e-commerce platforms or ERPs integrated with eZCom (see the alternative flow).

Back to top


Leveraging Whiplash and eZCom for your wholesale orders allows you to:

  • Stay up-to-date with retailer rules to avoid costly chargebacks and slowdowns.
  • Work with routing and compliance specialists to ensure accurate shipment routing and maintaining compliance with your retail trading partners.
  • Leveraging advanced wholesale solutions for your business and partner with eZCom’s existing retailers, e-commerce platforms, and ERPs (additional costs may apply from eZCom).
  • Take advantage of automated processes that increase warehouse efficiency and reliability.
GS1 labels and templates are supported for customers with an eZCom integration. If you're a Whiplash customer, see GSI Label Overview for more information.

Back to top

How it works

eZCom - Customer - Process Flow Diagrams (8).png

  1. Wholesale orders are received in Lingo from the wholesaler.
    Note: Items in Lingo must contain the Whiplash SKU in the Warehouse Xref attribute regardless of the other attributes in which this same SKU may appear.

  2. A. Orders details are pushed from Lingo to Whiplash.
    Note: If an order comes in from Lingo that contains new SKUs, these new SKUs are automatically created in Whiplash.

    B. Additionally, if an e-commerce platform (i.e., Shopify) or ERP is integrated with eZCom, Lingo will also push orders to this system (additional costs from eZCom may apply).

  3. Wholesale orders are batched in Whiplash and items are picked and packed at the warehouse.

  4. The Whiplash team prepares the cartons for shipping, including printing the GS1/UCC labels and applying them to corresponding cartons.

  5. Whiplash notifies Lingo of a new shipment with carton content details.

  6. The pickup, if applicable, is scheduled with the wholesaler and Lingo is updated with pickup details.

  7. If a small parcel is used, a label is purchased, and Lingo is updated with tracking details.

  8. Whiplash team prepares a master BOL including all shipments going to the wholesaler.

  9. When the order is picked up, shipment is confirmed in both Whiplash and Lingo.

  10. Lingo notifies the wholesaler that the shipment is on the way and an ASN is created.

  11. If an e-commerce platform (i.e., Shopify) or ERP is integrated with eZCom, Lingo will notify this system that orders have shipped (additional costs from eZCom may apply).

Back to top


Information sharing

Lingo pushes these order details to Whiplash:

  • SKU
  • SKU quantity
  • Order type
  • Recipient’s full name
  • Shipping method
  • Carrier
  • Shipping address
  • Billing address
  • Contact phone
  • Shipping notes
  • Tracking data
  • Whether signature is required
  • Whether order contains alcohol
  • Estimated delivery date
  • Return address

Lingo pushes product information to Whiplash with each order:

  • SKU
  • Vendor name
  • Product name
  • Description
  • Weight
  • Dimensions
  • Price
  • Country of origin

Whiplash notifies Lingo of the following shipment details for each shipment:

  • Order Number
  • Store #
  • UPC
  • Quantity in Carton
  • Carton Number
  • Package weight

Back to top

Getting started

Getting started is easy with these simple steps:

  1. Contact your Customer Success Manager at Whiplash to request the eZCom integration.

  2. Be a current customer of eZCom and have a Lingo account.
    Interested but don’t have an account with eZCom yet? Contact our Partnerships team to find out more.

  3. Notify eZCom that you will be working with Whiplash and request a warehouse Lingo account from eZCom.
    Please note that you may be asked to provide the following information when making this request to your Customer Success Manager:
    • Your ideal go-live date.
    • If you would want to include orders and items from before your ideal go-live date.
    • Contact details of the person who can provide the warehouse Lingo account and API key.
      For your security, please DO NOT send this information via email.
      Our warehouse team will require a login to eZCom.  Please note that there may be an additional cost on eZCom for this login.
    • Routing guide per wholesaler.

Back to top


Initial setup requirements

During the go-live setup process, it’s necessary to set tags that reflect the status of the orders and items that flow to Whiplash. The eZCom team will assist the customer with the following:

  • Enabling “Custom document/Item tags” 
  • Setting up initial tags for orders:
    • Whiplash Order Export Failed
    • Whiplash Order Export Pending
    • Whiplash Order Export Successful
  • Setting up initial tags for items:
    • Whiplash Item Export Failed
    • Whiplash Item Export Successful

Additionally, for each partner (wholesaler) that will be part of this integration, the eZCom team will also assist configuring the default document tag for that partner’s orders to “Whiplash Export Pending”.

Note: These requirements are not applicable if the customer uses the alternative flow, where the ERP communicates directly to Whiplash.

Back to top

Ongoing responsibilities

  • Customers must maintain their item catalog in Lingo.
  • Customer is responsible for the initial setup of items in Lingo.
  • Customer is responsible for adding/deleting items in Lingo.
  • Customer must maintain, per item, the Whiplash SKU in the “Warehouse XRef” even if this is the same SKU used in any other field.
  • Item’s Country of Origin column must have a valid 2-character ISO-3166 Country Code.
Note: These responsibilities don’t apply if the customer uses the alternative flow, in which the ERP communicates directly to Whiplash.

Back to top


Will we need to provide a Lingo login for the Whiplash team?

Yes, you will need to provide the Whiplash team with a Lingo login with access to the Lingo APIs.  This will be used by the integration and by the operations team to complete some steps of the fulfillment process.  Additional costs from eZCom may apply for this login.


How will my orders flow to my e-commerce platform or ERP?

We recommend that you reach out to eZCom to integrate your e-commerce platform or ERP.


Where in Lingo do I add the Whiplash SKU?

The Whiplash SKU must be in the Item’s "Warehouse Xref" attribute in Lingo.  To view or enter this information, in Lingo navigate to Administration > Item/Carton Maintenanace > Edit Item.  Scroll down to the “External Inventory/Warehouse System” section.


Why do I see duplicate SKUs?

On the initial sync, the integration will first create duplicate SKUs in Whiplash, which we will auto merge with the existing Whiplash SKU. If any new SKUs are added after the initial sync, it will be up to the customer to merge them.

For more information on how to handle duplicate SKUs, click here.


Why are my orders not flowing from Lingo to Whiplash?

Please check the rules you have set up in Lingo on which orders to tag to flow to Whiplash. 

During the go-live setup process, eZCom team will assist you with the initial setup of these rules. I.e., configure initial tags for orders (Whiplash Order Export Failed, Whiplash Order Export Pending, and Whiplash Order Export Successful) and items (Whiplash Item Export Failed and Whiplash Item Export Successful).

Also, please confirm that items have the Whiplash SKU in the Item’s "Warehouse Xref" in Lingo.


Where can I find a list of country of origin codes?

The ISO 3166 country codes can be found at here


Should I send orders both to Lingo and to Whiplash?

No, orders should only be sent to Lingo.

The automated processes should push those orders from Lingo to Whiplash.  During the go-live setup process, it is strongly advised to stop other processes that you may currently have in place to send orders directly to Whiplash to prevent duplicate orders.


What are the units of measure that Whiplash supports?

Currently, Whiplash only supports “each” as a unit of measure.


How can I setup a new trading partner?

If you wish to set up a new trading partner with eZCom and RyderShip, you'll need to confirm what the requirements are in the trading partner's routing guide. This can be reviewed by your operations team, eZCom and the RyderShip integration team. For example, if the trading partner requires truck IDs or grouping shipments into pallets, we will need to review those to confirm the proper workflow.


Can I use this integration if I still want my ERP to control the release of orders to Whiplash?

Yes, we offer an alternative flow if you’d like to continue to use your existing ERP integration to send orders and items to Whiplash via the Whiplash APIs.

Here’s what the alternative flow would look like:


Only the first couple of steps vary from the main flow, given the ERP communicates directly to Whiplash. You will not need to maintain the Whiplash SKU in the Lingo Item’s "Warehouse Xref", but you will still have to provide Whiplash with a Lingo warehouse account.

Additionally, you may need to make changes to make sure all the following data is included in your Whiplash API request.  See API request below for details. 

Back to top

API request

"order_type": "wholesale" or "dropship",
//... order details 
"order_items": [
        "item_originator_id": "3105681659", // sku, or id can be used to indicate the item instead 
        // ... other order item details
        "originator_id": "1", // This could be the line number in the edi file or the line number in NetSuite 
        "quantity": 1
"meta_fields": {
    "fields": {
        "ezcom_documentId": "5610689846", // Document id of the order in ezcom that will be updated by the integration. 
        // ... other edi and meta fields
        "edi_vendor": "",
        "edi_distribution_center": "",
        "edi_department": "",
        "edi_department_description": "",
        "edi_merchandise_type_code": "",
        "edi_vendor_number": "",
        "edi_start_date": "",
        "edi_cancel_date": "",
"edi_po_number": "",
"edi_store": ""

    "association_fields": {
        "order_items": [
            "originator_id": "1", //same as the coresponding order_items.originator_id 
            "edi_line_no": "0001", //this is the line number in the edi file 
            // ... other edi and meta fields 
            "edi_item_alias": "",
            "edi_item_color": "",
            "edi_item_size": "",
            "edi_customer_style": ""

Back to top


Related questions:

What does the eZCom integration do?

What are the benefits of eZCom?

How does eZCom work?

How do I start/set up my integration with eZCom?

What are the setup requirements for eZCom?