Set up Petpooja

Push Zopping orders to Petpooja (restaurant POS) and pull the menu/catalog back. Order-status updates flow back to Zopping via crons. This is a built-in connector — register the credentials issued by the Petpooja integrations team.

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

1. Configure credentials

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

{
  "partnerIntegration": {
    "partnerCredentials": {
      "PETPOOJA": {
        "baseURL": "https://api.petpooja.com",
        "appKey": "<app-key>",
        "appSecret": "<app-secret>",
        "accessToken": "<access-token>",
        "storeMapping": "1:rest_123,2:rest_456",
        "user": "<integration-user-id>",
        "email": "ops@example.com"
      }
    }
  }
}

Field	Required	Notes
`baseURL`	yes	Petpooja integration host. Zopping appends paths like `/save_order` and `/update_order_status`.
`appKey`	yes	Sent in the request body as `app_key`.
`appSecret`	yes	Sent in the request body as `app_secret`.
`accessToken`	yes	Sent in the request body as `access_token`.
`storeMapping`	yes	Map of Zopping store `clientId` → Petpooja restaurant ID (e.g. `1:rest_123,2:rest_456`). Resolves `restID` on every request.
`user`	no	Integration user ID.
`email`	no	Contact email for integration notifications.

2. Supported events

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

Direction	Events
PUSH	`ORDER_CREATE`, `ORDER_CANCEL`, `ORDER_PACK`, `ORDER_DISPATCH`, `ORDER_COMPLETE`, `TRIP_START`, `ORDER_PICKING`
PULL	`PRODUCT_PULL` (menu & categories)

Enable delivery per event via event integrations.

Mapping notes

The Zopping variant must carry a VariationId custom field that matches the Petpooja variation ID.
The Zopping order referenceNumber is sent as clientorderID.

Going further

Set up Petpooja Invoice — the retail-POS invoicing variant.
Integrations overview · Events & webhooks