Skip to main content
Industry

Shipping, returns and "where is my order?"

Most retail questions are already answered in your policies. The rest need the order system. SupaCortex does the first from your documents and the second from your own API - for the signed-in shopper only.

  • Policies, cited
  • Order lookups for signed-in shoppers
  • Confirmation before changes

How do online retailers use SupaCortex?

Retailers load shipping, returns, warranty and sizing policies into a project and put the widget on the store and in the app. Anonymous visitors get cited policy answers. Signed-in shoppers can also ask about their own orders through lookups you describe on your order system, and request changes such as a cancellation, which always need their confirmation. Agents handle what is left with cited reply drafts in the help desk.

  • Public mode for policy questions; identified mode for order questions.
  • Custom HTTP connectors: describe endpoints or import an OpenAPI file.
  • Actions always need the shopper's confirmation; every call is audited.
  • Only lookups marked public-safe run for anonymous visitors.
  • Credit packs never expire - useful for sale-season peaks.
Typical questions

Questions it answers for retailers

"Do you deliver to Guwahati, and how long does it take?"

From the shipping policy, with the delivery-time table cited.

"Can I return a sale item?"

From the returns policy - including the exceptions people usually miss.

"Does this kurta run small?"

From your size guide and product notes, if you have written them down.

"Where is my order?"

A lookup on your order system for the signed-in shopper, and only for them.

"Cancel my order, please."

An action on your API - the shopper confirms before anything changes.

"My refund hasn't arrived."

Escalated to an agent, who starts from a draft citing the refund timelines.

Set-up

How retailers set it up

  1. 01

    One project per store or brand

    Each with its own policies, widget colours and greeting.

  2. 02

    Feed the policy pages

    A website feed re-reads shipping and returns pages, so a policy change is answered the same day.

  3. 03

    Describe the order API

    Order status as a lookup, cancellation as an action; test each with the "Try" button.

  4. 04

    Widget on store and app

    Script tag on the site; the mobile URL in your Android or iOS app's WebView.

Honest limits

What to know before you start

Retail support lives on WhatsApp and Instagram in India. We are not there yet.

  • No WhatsApp channel yet - it is on the roadmap.
  • No ready-made Shopify, WooCommerce or marketplace connectors; you describe the APIs.
  • It does not recognise products from photos; text only.
  • Order lookups need a signed-in shopper - anonymous visitors get policy answers only.
Frequently asked

Questions people ask before they start

Yes, for signed-in shoppers. Your site signs a short-lived token for the customer and you describe an order lookup on your API. The customer is identified from the token, never from what they typed, so nobody can ask about someone else's order.

If you describe that action on your API, yes - and it always asks the shopper to confirm before calling it. Every call is audited. Actions never run for anonymous visitors.

Not with a ready-made connector. You can describe any HTTPS API - including a platform's or your own middleware's - as a custom connector, or import an OpenAPI file.

Each plan includes a monthly number of widget sessions and AI credits, with alerts at 80% and 100%. Credit packs never expire, so many retailers keep one in reserve for festival season.

Answer the next sale's questions before they reach your inbox.

Book a 30-minute demo on your own documents. We set up a 14-day trial workspace for you - no credit card, no setup fee.

Questions first? Email info@greatdevelopers.com or call +91 8585953085.

Still curious? Ask your favorite AI about SupaCortex.