Zopping
Get a token

Set up RDEP

Connect RDEP for store-level inventory availability checks and order hopping. On each Zopping order create, items are checked against RDEP inventory at the store; unavailable orders are hopped back in Zopping with a rejection reason. Zopping also pulls stock from RDEP. This is a built-in connector.

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

1. Configure credentials

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

{
  "partnerIntegration": {
    "partnerCredentials": {
      "RDEP": {
        "baseURL": "rdep.example.com",
        "userName": "<api-username>",
        "password": "<api-password>",
        "email": "ops@example.com"
      }
    }
  }
}
FieldRequiredNotes
baseURLyesRDEP host without scheme (e.g. rdep.example.com). Zopping prepends https:// and calls /auth-service/api/auth, /inventory-service/api/inventory/checkAvailability and /cart-service/api/createCart.
userNameyesRDEP API username, sent in the auth request body.
passwordyesRDEP API password. The returned Authorization header is reused as a Bearer token on subsequent calls.
emailnoContact email for integration notifications.

2. Supported events

Direction: PUSH = Zopping → RDEP; PULL = Zopping pulls from RDEP.

DirectionEvents
PUSHORDER_CREATE, ORDER_CANCEL, ORDER_PACK
PULLPRODUCT_INVENTORY_CHANGE

Enable delivery per event via event integrations.

Mapping notes

  • The Zopping store clientId must equal the RDEP storeCode.
  • The Zopping product clientItemId must equal the RDEP sku.
  • If any item is unavailable at the mapped store, the order is hopped in Zopping with reason Items unavailable on RDEP store.

Going further