intelligent.pageDocs

Shopaccino

Shopaccino sells "Product & Order APIs" on its Scale plan and above, but publishes no developer portal, endpoints or auth model: credentials and docs come from support.

Shopaccino is an Indian hosted ecommerce platform covering D2C storefronts, B2B wholesale, multi-vendor marketplaces and a POS, run by I Solution Microsystems Private Limited (CIN U72200RJ2009PTC030152, registered in Rajasthan in 2009). It matters to this catalogue because it sits in the same bracket as StoreHippo and Dukaan for Indian mid-market brands, and because it does have an API, sold explicitly as a plan feature. What it does not have, as of 2026-09-21, is any public documentation of that API: no developer subdomain, no endpoint reference, no authentication guide and no SDK. This page records the gap and everything that can be established about the integration surface without a seller login.

At a glance

What it is

Shopaccino is a SaaS store builder, not a marketplace: each merchant runs their own storefront and owns their orders. It targets Indian small and mid-sized brands and pushes hard into vertical niches, with landing pages for jewellery, fashion, furniture, grocery, footwear and handicrafts. Beyond plain D2C it sells a B2B module with wholesale pricing and credit sales, multi-warehouse inventory, cross-border and multi-currency selling, a web POS and a mobile app add-on. Published plan prices on 2026-09-21, billed annually plus 18 percent GST: StartUp at 18,984 rupees a year, Scale at 49,980, ProCommerce at 99,984, and TailorMade at custom pricing. No merchant count or order volume is published.

API access

The API is a paid plan feature, gated at Scale. The pricing comparison chart is the only first-party statement of what it does, and it is two lines long:

  • "Product & Order APIs", with the sub-line "Add or update products, push orders to your systems and integrate any third-party app".
  • "Content API for Google Shopping", with the sub-line "Auto-sync your catalog to Google Shopping ads".

Note the direction implied by "push orders to your systems": order egress is framed as Shopaccino pushing to you, which would mean a callback or a feed rather than a poll, but the wording is marketing copy and should not be read as a specification.

There is no developer console, no published application process, no versioning statement, no changelog and no SDK in any language. The partner programme does have a "Technology & Solution Partners" track described as integrating "ERPs, payment gateways, logistics and custom apps with Shopaccino's platform", on a 20 percent first-year and 10 percent lifetime revenue share, but it links to no technical material. Getting the API spec means becoming a Scale customer or a partner and asking support: the site lists +91-99502 44448 for sales and partnership and +91-99502 44447 for help and support.

Warning

Do not budget this connector from the plan blurb. Two facts that normally decide the shape of a commerce connector, the authentication model and whether order delivery is push or poll, are both unknown here. Get the document from Shopaccino before estimating.

Authentication

Not published. Nothing can be written here honestly.

For contrast, the one place Shopaccino does document API credentials is the other direction: connecting a courier account, where the panel asks the merchant for the carrier's credentials. Its shipping help article says "A form will appear asking for API Key, Auth Token, or Client ID/Secret" depending on the provider, and names Shiprocket, Pickrr, NimbusPost and Shyplite. That is Shopaccino consuming a carrier API, not exposing its own, and it tells you nothing about how Shopaccino authenticates inbound calls.

Objects we can read

Nothing can be specified. The plan text names products and orders and nothing else. Inventory, shipments, returns, settlements, customers and locations all exist as panel features, including multi-warehouse inventory and an order and return management module, but none is named as an API object.

Until the spec is in hand, the readable surfaces are:

  1. The storefront, as an unauthenticated crawl of the merchant's own domain, giving titles, prices and in-stock state only.
  2. The order management vendor, if the merchant runs one. Shopaccino ships app-directory integrations for EasyEcom, Unicommerce, Zoho Inventory, GoFrugal and Uphance, each described the same way: they "pull inventory from ... software to your website" and "automatically push orders from your website to ..." software. Every one of those vendors has its own documented API, and reading orders and stock there is usually less work than waiting on Shopaccino.
  3. Panel exports, which exist for products and orders but whose formats are not documented publicly.

Writing back: listings, price and stock

Three routes, only one of them programmatic and none of them specified.

  • The Product API, on Scale and above, per "Add or update products". Endpoint, request shape, batch size and confirmation model are all unpublished.
  • XLSX bulk import, in the panel. The product help article says only that "we offer a bulk import option that allows you to add products using an XLSX file". Column names and the template are not published; download the template from a trial store.
  • Google Sheet Inventory Sync, an app in the directory that updates stock only. You "map SKU and Quantity columns", connect the sheet once, and "the sync runs automatically thereafter". No price field is mentioned, so treat it as a stock-only channel. This is the cheapest stock write route on Shopaccino and needs no API credential.

The Content API for Google Shopping is a catalogue egress to Google, not a way to write into Shopaccino.

Webhooks and notifications

None published. No webhook configuration screen, event list or endpoint appears in the docs, the app directory or the pricing chart. The only push mechanisms named anywhere are customer-facing: order status email and SMS, WhatsApp through a third party provider such as Interakt, and mobile push through the app add-on. None of those is a machine-readable event feed.

If nothing turns up when you ask support, the fallback is a poll against whatever order read the API offers, or a poll against the order management vendor. Given the unknown rate limits, a five to fifteen minute order poll and a nightly catalogue refresh is a safe opening position.

Rate limits and pagination

Not published, in any form. No numbers, no headers, no pagination model. Assume nothing, and ask for the limits in the same conversation as the spec.

Mapping to the unified model

Nothing can be mapped from published material. Use shopaccino as the orders.channel and listings.channel value, key channel_account_id on the merchant's store domain, and keep the whole record in orders.raw from the first real response. The rest of the mapping has to wait for the document.

If the merchant is on EasyEcom, Unicommerce, Vinculum, Zoho Inventory or GoFrugal, map from that vendor instead and record Shopaccino as the storefront in orders.raw rather than building a second connector.

Gaps and open questions

  • Everything operational: base URL, authentication, endpoints, object schemas, pagination, rate limits, error format, versioning.
  • Whether "push orders to your systems" means webhooks, a callback URL, a scheduled feed or just a readable orders endpoint described loosely.
  • Whether the API covers the B2B module, multi-warehouse inventory, returns and the marketplace seller ledger, or only the two objects the pricing page names.
  • Whether ProCommerce or TailorMade unlock more API than Scale. The comparison chart marks the API row once and does not differentiate above Scale.
  • The XLSX import template columns, which are the practical fallback for a bulk catalogue write.
  • The EasyEcom and Unicommerce app pages describe behaviour but not mechanism, so it is unverified whether those integrations use the same public API or a private one.

Sources