Set up EasyEcom

Connect EasyEcom (omni-channel OMS) to Zopping. Zopping pushes orders, product and inventory changes to EasyEcom. This is a built-in connector — generate your API credentials from the EasyEcom dashboard and register them here.

Prerequisite: the ThirdPartyIntegration extension must be enabled for the organization.

1. Configure credentials

Add your EasyEcom details to the organization's integration config under the EASYECOM key:

{
  "partnerIntegration": {
    "partnerCredentials": {
      "EASYECOM": {
        "baseURL": "https://api.easyecom.io",
        "apiToken": "<x-api-token>",
        "apiKey": "<x-api-key>",
        "integrationUserId": "<numeric-user-id>",
        "companyCarrierId": "181898"
      }
    }
  }
}

Field	Required	Notes
`baseURL`	yes	EasyEcom API host for your account.
`apiToken`	yes	From Account Settings → API. Used in the `x-api-token` header.
`apiKey`	yes	From Account Settings → API. Used in the `x-api-key` header.
`integrationUserId`	no	Numeric EasyEcom user id of the API user; sent as the courier aggregator user on AWB assignment during dispatch.
`companyCarrierId`	no	EasyEcom carrier id used when creating orders (defaults to `181898`).

Refer to the EasyEcom API docs at api-docs.easyecom.io.

2. Supported events

Direction: PUSH = Zopping → EasyEcom.

Direction	Events
PUSH	`ORDER_CREATE`, `ORDER_CANCEL`, `ORDER_PACK`, `ORDER_DISPATCH`, `ORDER_ADDRESS_EDIT`, `ORDER_COMPLETE`, `ORDER_RETURN`, `PRODUCT_CREATE`, `INVENTORY_UPDATE`

Enable delivery per event via event integrations.

Mapping notes

EasyEcom sku must be mapped to the Zopping clientItemId of the product.
After creating a product in EasyEcom, store the returned productId as easyecomProductId in the product's metadata in Zopping.

Going further

Integrations overview · Events & webhooks