Zopping

Zopping is a hosted ecommerce platform from Zopping Technology Private Limited in HSR Layout, Bengaluru, aimed squarely at grocery, quick commerce and hyperlocal retail rather than at fashion-style D2C. Its distinguishing features are the ones a supermarket chain needs: sold-by-weight pricing, multi-store inventory, delivery area and slot management, picking and click-and-collect, and its own delivery staff apps. It claims "1000+ Happy Store Owners" across "50+ Countries". For an integrator the finding is simple and negative: as of 2026-09-22 Zopping publishes no API reference, no authentication guide and no webhook documentation anywhere public. The one machine-readable thing you can get without a login is the server-rendered configuration blob on any live Zopping storefront.

At a glance

What it is

Zopping is D2C and hyperlocal retail, not a marketplace: each customer runs their own branded store, web and apps, under their own domain or a *.zopping.com subdomain. The vertical pages cover grocery, medicine, restaurants, pets, jewellery, fashion, furniture, electronics, books and automobiles, but the platform's shape gives away its origin in grocery: the store object carries flags for click and collect, delivery hubs, picking and self checkout, and the product model supports weight-based selling. Zopping also ships its own admin and delivery Android apps; the storefront links the admin app as com.zopping.admin on Google Play. Media is served from i1.zopping.com under a zopsmart-media path, which points at ZopSmart as the engineering lineage behind the product.

Pricing is three tiers, Basic, Business and Enterprise, rendered client side with no figures we could read as text on 2026-09-22, plus a 14-day free trial.

API access

There is no developer programme, no console and no published credential path. Concretely, as of 2026-09-22:

• docs.zopping.com resolves and returns HTTP 200, but it is an Outline wiki instance whose content requires a team login. Nothing is readable anonymously. This is where internal or partner documentation most likely lives.
• api.zopping.com, developer.zopping.com and help.zopping.com all return HTTP 400 from the edge, which means the hostnames are not configured as public services.
• support.zopping.com redirects to a knowledge base running on DexKor, which rendered no readable article list to an automated fetcher.
• The full zopping.com sitemap is 35 URLs. None is a developer, API or documentation page. The integrations page lists only merchant-facing features, Google Analytics, Tawk.to live chat, courier and delivery area setup, order management and returns, product bundles, subscription products and custom fields, and mentions no API at all.
• The pricing page does not gate or mention API access on any tier.

No SDK, Postman collection or OpenAPI document is published in any language.

Authentication

Not published. Two observations, and no more than that:

1. The storefront origin responds to unknown paths with access-control-allow-headers: Authorization, Content-Type, x-requested-with, origin, true-client-ip, X-Correlation-ID and access-control-allow-methods: PUT, POST, GET, DELETE, OPTIONS, PATCH, plus an x-correlation-id on every response. That is an API gateway sitting in front of the storefront, and it expects bearer-style Authorization.
2. What the token is, how it is issued, whether a merchant can mint one, and what it scopes are all unknown.

Do not build against this. Ask Zopping for the documentation behind the Outline login.

Objects we can read

Store configuration, navigation and locations

Readable with no credentials on any live Zopping storefront. The server renders a JSON object into the page as window.__ECOM_DATA__. On a demo store on 2026-09-22 it was around 56 KB with these top-level keys:

organization.config carries address, basic, bulkOrderSupport, customFields, customer, languages, logistics, order, referralManagement, seo, social, tawkToLiveChat, wallet and website. organization.defaultStore is the most useful part for a unified model, because it is a real location record: address, addressLine1, addressLine2, clientId, countryCode, default, email, hasClickCollect, hasDeliveryHub, hasPicking, hasSelfCheckout, id, languages, latitude, longitude, metaData, name, phone, pickingStoreId.

No values are reproduced here, because the ones we saw belong to Zopping's own demo stores rather than to a customer.

Products and listings

Not available as a documented endpoint. Product and category pages render server side, so a crawl of a storefront gets titles, prices and availability. The client bundle addresses products by slug and orders by reference number, which tells you the identifier shapes but not an API contract.

Orders, inventory, shipments, returns, settlements, customers

None readable without credentials, and nothing documented with them. All of these exist as admin panel modules, including order management, returns, delivery management, delivery partner assignment and a customer wallet.

Writing back: listings, price and stock

Not available through any documented interface. The routes that exist are the admin panel and whatever bulk upload it offers, neither of which is documented publicly. organization.config includes a bulkOrderSupport key, which is a merchant feature for large orders rather than a catalogue import mechanism, so do not read it as one.

If you need automated writes, this has to be a conversation with Zopping, and the deliverable to ask for is the contents of the Outline wiki.

Webhooks and notifications

None published. Nothing to subscribe to and no documented endpoint to poll.

If an integration is eventually granted, and given the grocery and quick commerce use case, order events will be the thing that matters most and latency will matter more than on a fashion store. Raise push delivery in the first conversation rather than accepting a poll.

Rate limits and pagination

Not published. Nothing to record.

Mapping to the unified model

Only locations can be filled from a public surface today, and only for the store's own locations.

Gaps and open questions

• The entire API contract. Base URL, authentication, endpoints, schemas, pagination, limits, errors and versioning are all unknown.
• Whether merchants can get API credentials at all, or whether integrations are built by Zopping under an Enterprise contract.
• Whether docs.zopping.com holds the API reference. It is an Outline wiki, which is what a company uses for internal and partner documentation, but the content is not visible.
• Whether the admin Android app talks to the same gateway as the storefront, which would be the quickest way to learn the real contract if you have a merchant account and permission to inspect traffic.
• Whether Zopping has any relationship with EasyEcom, Unicommerce or Vinculum. None of them appears on the integrations page, which is unusual for an Indian retail platform and may simply mean the page is incomplete.
• Pricing figures could not be read, so the plan that would include API access, if any, is unknown.

Sources

• zopping.com and its full 35 URL sitemap, read 2026-09-22
• zopping.com/integrations, the complete integration list, with no API mention
• zopping.com/pricing, the three tiers and the 14-day trial
• zopping.com/about-us, the legal entity, Bengaluru address and the "1000+ Happy Store Owners" and "50+ Countries" claims
• docs.zopping.com, an Outline wiki returning a login-gated shell on 2026-09-22
• HTTP checks on api.zopping.com, developer.zopping.com and help.zopping.com, all HTTP 400 on 2026-09-22
• A live Zopping demo storefront on 2026-09-22, for the window.__ECOM_DATA__ key list, the CORS and correlation headers, and the client bundle's identifier shapes