Qpe

QPe is a no-code Indian store builder operated by Appernity Technologies Private Limited, founded in 2021 and based in Delhi NCR, with its terms placing jurisdiction in Faridabad. It claims to power "45000+ eCommerce entrepreneurs, enterprise and d2c brands" and positions itself directly against Shopify, WooCommerce and BigCommerce with side-by-side price comparisons. The live site is goqpe.com; the older qpe.co.in no longer resolves, and the product is mid-rebrand to "DiziCommerce", with both names appearing on the same pages as of 2026-09-22. For an integrator the useful finding is narrow but real: QPe sells webhooks as a plan feature on its two upper tiers, and publishes nothing at all about what they contain.

At a glance

What it is

QPe is D2C only: a hosted storefront per merchant, not a marketplace, though the top tier adds a "Multivendor Marketplace" module and "B2B/Wholesale". Around the storefront it sells themes, shipping, invoicing, inventory with warehouse locations, a POS, global selling and a plugin directory. It is aimed at Indian small and mid-sized sellers, with vertical landing pages for produce, furniture and similar categories, and a set of free business tools such as a GST calculator and invoice generator used as acquisition bait.

Published prices on 2026-09-22, billed yearly and inclusive of taxes: Starter at 1,400 rupees a month, Advanced at 3,000, Growth at 7,000, and a top tier branded Qpe-pro+ whose price the page presents alongside a separate enterprise track that requires a demo booking. A 7 day free trial is offered with no card. The pricing page runs its own Shopify price comparison next to each tier, which is worth knowing when reading its numbers.

API access

No developer programme, console, documentation or SDK exists. Checks on 2026-09-22:

• docs.goqpe.com, developer.goqpe.com and api.goqpe.com have no DNS records.
• qpe.co.in, the older marketing domain still indexed by search engines, no longer resolves.
• The goqpe.com sitemap is 25 URLs: home, pricing, demo, about, themes, contact, integrations, three Shopify and WooCommerce comparisons, four case studies, affiliate, careers, legal pages and checkout URLs. There is no developer page.
• The word API does not appear on the home page at all.
• The terms of service contain no API clause, no developer terms and no data export clause.
• The merchant application lives at accounts.goqpe.com and admin.goqpe.com, both of which are login-gated.

So the only way to learn the webhook contract is to hold a Growth or Qpe-pro+ account, or to ask QPe support.

Authentication

Not published. Nothing can be written here honestly.

The one place QPe does document credentials is the opposite direction, its plugin directory, which is the merchant supplying third party keys to QPe. Its own description of how a plugin is connected is "Just click on the plugin and enter your credentials, API key etc and you are good to go." That is QPe consuming Razorpay, Shiprocket, Delhivery, Klaviyo and the rest, and tells you nothing about how QPe would authenticate an inbound call.

Objects we can read

Nothing can be specified. QPe names no API object anywhere public.

The surfaces that do exist:

1. Webhook deliveries, on Growth and above. Contents unknown.
2. The storefront, as an unauthenticated crawl of the merchant's domain, giving titles, prices and in-stock state.
3. Panel exports and reports, which the pricing table lists under "Reports, Analytics & Management" with "Customer Data", "Invoice Management" and "Invoice Templates" rows. Formats are not documented.

Inventory with warehouse locations, B2B pricing and multivendor seller records all exist as panel modules on the upper tiers, so the data model is richer than a basic cart. None of it is exposed in a documented way.

Writing back: listings, price and stock

Not available through any documented interface. The admin panel at admin.goqpe.com is the only route, plus whatever bulk upload it offers, whose template is not published.

There is no catalogue feed, no bulk job API and no import endpoint documented. If you need automated writes, this is a support conversation, and the thing to ask for is whether the Growth-tier webhook feature has an inbound counterpart or is outbound only.

Webhooks and notifications

Yes, sold, and undocumented. The pricing comparison table carries a "Webhooks" row marked absent for Starter and Advanced and present for Growth and Qpe-pro+. That is the entire published record.

Unknown and worth asking for in one message: the event list, the HTTP method and content type, the request body schema, whether deliveries are signed and with what header, the retry policy, the delivery timeout, and whether the seller can set custom headers on a subscription.

The practical approach is the same as for any undocumented webhook: have the merchant point one subscription at a request bin, trigger a real order, capture the body, and build from the capture. Snapshot it, because an undocumented contract can change without a changelog.

If webhooks are not available on the merchant's plan, there is nothing to poll: no public read endpoint exists.

Rate limits and pagination

Not published, in either direction. No numbers, no headers, no pagination model. Treat a storefront crawl as an ordinary web crawl and keep it slow.

Mapping to the unified model

Nothing can be mapped from published material. Use qpe as the orders.channel and listings.channel value, key channel_account_id on the merchant's store domain, and store the entire first webhook delivery in orders.raw before mapping a single field.

Two structural notes for when the contract arrives. The upper tiers support multiple warehouse locations, so inventory.location_id is likely to be meaningful rather than a constant. And the top tier supports a multivendor module, so a QPe store may carry a seller dimension that has to be preserved rather than collapsed.

Gaps and open questions

• The entire webhook contract, which is the only integration surface QPe sells.
• Whether any read API exists at all for merchants on the enterprise track. The enterprise page promises "Custom features and third party integrations" without saying what that means technically.
• Whether the rebrand to DiziCommerce changes hostnames, and whether goqpe.com will keep resolving.
• The panel export formats, which are the fallback for reads.
• Whether the multivendor and B2B modules expose seller and price-list data in any machine-readable way.
• The Qpe-pro+ price, which the pricing page presents inconsistently enough that no figure is quoted here.

Sources

• goqpe.com and its 25 URL sitemap, read 2026-09-22
• goqpe.com/pricing, for the plan names, the rupee prices quoted above and the "Webhooks" row in the feature comparison
• goqpe.com/integrations, the plugin directory and the "enter your credentials, API key etc" wording
• goqpe.com/about-us, the Appernity Technologies Private Limited operator, 2021 founding, Delhi base and the 45,000 merchant claim
• goqpe.com/terms-of-service, Faridabad jurisdiction and the absence of any API clause
• DNS and HTTP checks on qpe.co.in, docs.goqpe.com, developer.goqpe.com, api.goqpe.com, accounts.goqpe.com and admin.goqpe.com, 2026-09-22