Launch a SupaCommerce Store
Build a storefront from your existing BU products and connect verified checkout.
Open interactive lesson and quizWhat you will learn
- Create a rule-based store draft
- Control its visible catalog and shared channel stock
- Explain verified payment and order reconciliation
A retail BU has a real product catalog but no online store. Prepare a branded draft, check inventory and payments, then publish deliberately.
Lesson 1
A store starts with real BU data
SupaCommerce uses predefined industry rules and existing BU details, Products and SKUs. It does not generate a website with AI. Demo trial products are hidden. Several stores in the same BU may use a shared sales channel, while each store keeps its own design and visibility choices.
Lesson 2
Draft and live versions
Rearrange, duplicate or hide predefined sections and choose a palette in the designer. Autosave updates the draft. Publishing copies that draft into a live version; later edits do not appear publicly until the next publish. Unpublish closes the public store.
Lesson 3
Pages and country prices
Edit, add, hide or delete store pages in Pages. They share the same draft and published version as the design. Each country uses the merchant's explicit local price; a product without a price in a different currency is hidden there. Check catalog visibility and shipping terms for each market.
Lesson 4
Customer accounts and history
Customers use a six-digit email code to verify their address and may set a password. An existing BU Contact with that email is linked without replacing its saved name or phone. Verified customers can sign in, check past Orders and use their account details at checkout.
Lesson 5
Stock, payment and reconciliation
Allocate stock to the SupaCommerce sales channel before publishing. A shopper can check a coupon at checkout to see the eligible discount and final total before continuing; the server validates the same code and stock again when starting the order. Free orders need no payment method. A paid store can use a Stripe or Razorpay merchant account with a signed webhook, or send direct payment instructions by email. Direct payments remain pending until an Orders manager verifies the bank or UPI receipt and confirms the request; stock and coupon availability are checked again. The entered receipt number and confirming BU user are saved with the payment; the confirming user becomes the Order owner. Find these fields in Payments and Data Finder. If an order cannot be saved after payment, it is marked for review or refunded when the provider supports it.
Lesson 6
Conversion and customer value
SupaCommerce counts store page views, product views, cart activity, checkouts and saved purchases. Confirmed Orders link to Contacts and can be queried with Business Events in Data Finder. The Customers tab shows purchase count and LTV by currency, excluding cancelled and returned Orders. Set low and high value thresholds for each currency there; customer labels update from their actual LTV. One Store customer values record is saved per store, Contact and currency, with purchase count, LTV and value group. Choose that object in Audiences and relate it to Contact to target high, mid or low value customers; always check consent and preview eligible recipients. LTV filters and Data Finder's LTV field use normal currency amounts (for example, enter 84000 for ₹84,000). Internal minor units remain available in Data Finder for reconciliation. Previously saved minor-unit audience rules retain their original thresholds. Without a threshold, the value group is Not set.
Practice · Prepare a store draft
- Create a store from a BU with real products
- Review the industry template, edit an About page and hide an irrelevant section
- Set product visibility, country prices and channel stock
- Preview desktop and mobile, then test the chosen payment path before publishing