Integrations

Zopping ships with built-in integrations across sales channels, logistics and payments. Check this list before building your own — if a provider is already supported, you only configure it; you don't implement it. If it isn't here, the patterns below show how a new one is added.

What's built in

Channels & marketplaces (inbound)

Sync catalog, inventory and orders with external sales channels, ERPs and POS:

• Shopify — storefront channel sync
• Petpooja — restaurant POS (menu, stock, order callbacks)
• Unicommerce — omni-channel OMS (orders, inventory)
• Logic ERP, GoFrugal — retail ERP / POS

Logistics & couriers (outbound)

Hand off deliveries and receive status / tracking:

• Shiprocket, Delhivery, Borzo, Dunzo, Porter, Shadowfax, Loadshare, Bluedart

Payment gateways

Collect online payments — processed by ZopPay, Zopping's payment product (gateway setup, callbacks and signatures live there):

• Razorpay, PayU, Cashfree, Paytm, PhonePe, CCAvenue, Cybersource, HyperPay, Stripe

Providers are configured per organization (credentials in the org's integration config) and gated by the relevant extension (e.g. OnlinePaymentSupport for online payments). Confirm whether the provider you need is already enabled before integrating.

Worked setups: Set up Shopify (channel) · Set up Razorpay (payments).

Integration patterns

Most integrations take one of three shapes:

1. Inbound channel sync. An external channel (Shopify, Petpooja) pushes catalog/stock/order changes to Zopping, or Zopping pulls them. Inbound calls arrive on partner webhook endpoints (e.g. /api/partner-integrations/petpooja/webhook/...) and map to catalog/order operations. Use this to keep an external system and Zopping in sync.
2. Outbound push. On an event (order placed, packed, dispatched), Zopping pushes to a provider — a courier like Shiprocket, or an ERP. You subscribe via event integrations and Zopping delivers to the provider. See Events & webhooks.
3. Payment gateway. A gateway is configured with credentials; checkout initiates a payment and the gateway calls back to confirm. See Accept payments and Integrate a payment gateway.

Inbound endpoints (channel → Zopping)

External systems push changes to Zopping on dedicated endpoints. Each is a POST under https://zopping.com/api/partner-integrations, and (except the Logic ERP one) ends with your organizationId. The connector maps each call to the right catalog/order/customer operation.

Example full URL for organization <org-id>: https://zopping.com/api/partner-integrations/orders/create/<org-id>. The Shopify guide has the topic → endpoint mapping.

Outbound events (Zopping → provider)

For the other direction, subscribe to events and Zopping pushes them to the provider (a courier, an ERP) as they happen — order created, packed, dispatched; inventory or product changes. The event catalog and subscription API are in Events & webhooks.

Using a built-in integration

1. Confirm the provider is supported (above) and the matching extension is enabled.
2. Supply the provider's credentials in the organization's integration config.
3. For channels, point the channel's webhooks at the Zopping endpoint; for couriers and payments, Zopping handles delivery and callbacks.

Building a new integration

Not supported yet? A new connector follows the same patterns — an inbound webhook endpoint (channel → Zopping) and/or an event subscription (Zopping → provider), plus credential configuration. The Events & webhooks model is the backbone for both directions.