Zopping
Get a token

Set up eFactoCloud

Push Zopping customers and orders to eFactoCloud. On each customer signup the customer is pushed to eFacto CRM, and on each order create the order (with items and completed payments) is pushed to eFacto. This is a built-in connector.

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

1. Configure credentials

Add your eFacto details to the organization's integration config under the EFACTO key:

{
  "partnerIntegration": {
    "partnerCredentials": {
      "EFACTO": {
        "baseUrl": "efactoapidevelopment.efacto.cloud",
        "code": "<environment-code>",
        "storeMapping": "1:EF_STORE_1,2:EF_STORE_2"
      }
    }
  }
}
FieldRequiredNotes
baseUrlyeseFacto API host without scheme. Zopping prepends https:// and appends paths like /api/Crm/Customer and /api/CustomerOrder.
codeyeseFacto environment code. Sent as the Code header on every request.
storeMappingyesMap of Zopping store clientId → eFacto storeId.

2. Supported events

Direction: PUSH = Zopping → eFactoCloud.

DirectionEvents
PUSHCUSTOMER_CREATE, CUSTOMER_BASIC_EDIT, ORDER_CREATE, ORDER_ITEMS_EDIT, ORDER_ADDRESS_EDIT, ORDER_RESCHEDULE, ORDER_PACK, ORDER_COMPLETE, ORDER_PACKING, ORDER_DISPATCH, ORDER_PICKING, ORDER_PICKED, ORDER_CANCEL

Enable delivery per event via event integrations.

Mapping notes

  • The Zopping store clientId must equal the eFacto storeId (sent as storeId on each order).
  • The Zopping product clientItemId must equal the eFacto itemCode.
  • The customer's 10-digit mobile number is the customer identifier on eFacto — enable SSO with Email & Mobile or Mobile Number on your store, since eFacto requires the mobile number on registration.

Going further