Maghgo ecosystem and architecture
Maghgo connects the merchant dashboard and Android app, a store-owned web storefront, catalog and search, shopper chat, social entry points, coupons, QR links, checkout, payment providers, analytics, and merchant automation. Each shop remains the data boundary for its storefront, product suggestions, cart, checkout, and orders.
A merchant creates an account and manages the store from the Maghgo web dashboard or Maghgo Business Android app. The merchant adds products, prices, availability, stock, delivery settings, coupons, contact channels, and payment methods. A QR code and shareable store link bring shoppers to that storefront.
The page builder saves data-only page layouts in the store’s merchant_sites record. A merchant can create product and content pages, edit a page title, route, SEO title and meta description, add supported content blocks, delete draft pages, and publish. A ProductGrid reads available products for that merchant and places them in that store’s cart. Published custom pages are available at the store’s /pages/ route.
Typed and spoken queries search the current store catalog. Voice input uses browser speech-recognition support and requires the shopper’s microphone permission. Catalog search uses bounded per-store search indexes and PostgreSQL full-text search; eligible Maghgo AI plans can add semantic ranking. The shopper AI assistant receives a selected store slug and searches only that merchant’s product records for recommendations.
The shopper can open a product, add an AI-recommended product to the selected store’s cart, apply a valid coupon, enter delivery details, and continue to that store’s checkout. The server calculates prices and discounts from catalog and coupon data. Checkout displays only methods enabled by the merchant, such as Razorpay, Stripe, Cashfree, cash on delivery, UPI, or bank transfer when available.
When an online method is configured, the payment provider completes payment through its hosted or provider-managed flow. Maghgo checks the payment result against the stored order amount, merchant, provider order reference, and provider confirmation before recording payment status. AI chat does not collect card numbers. The shopper continues from chat to the regular checkout to finish an order.
Merchants can import products from their Facebook or Instagram Meta catalog. Supported WhatsApp, Instagram, Messenger, and Telegram workflows connect conversations to merchant or shopper tasks and share store links. A shopper following a product link places an order through the store checkout; Maghgo does not present a native Meta wallet payment as a built-in payment method.
Maghgo AI is a separate subscription family from store and Verified plans. Depending on active entitlement, model configuration, and available data, it provides Gemini chat and copy generation, reviewable storefront design suggestions, machine-learning forecasts, product recommendations, customer segments, and review signals. Merchant rules can respond to supported events such as low inventory, predicted stockout risk, high-value orders, or payment review. A payment-risk signal is for human review and never changes payment state by itself.
Implementation overview
Next.js, React, and TypeScript deliver the public storefront and merchant dashboard; the Maghgo Business APK is the Android merchant app.
Supabase-hosted PostgreSQL stores merchants, products, stock, orders, coupons, payment ledgers, and merchant_sites pages. Product and page queries include merchant scope so a store page and its shopping assistant use that store’s catalog.
MongoDB stores conversational history and shopper context for follow-up chat, plus design documents and revision snapshots. Read Maghgo’s privacy page for the current data handling and AI provider details.
Python Flask API routes validate merchant sessions and checkout requests. Payment provider credentials stay on the server. Stripe and Cashfree webhooks verify signatures; payment return handlers check the provider result and stored order before confirming an online payment.
Maghgo uses bounded, short-lived product caches and a per-store prefix index for suitable catalog sizes. Larger catalog search uses indexed PostgreSQL full-text candidates; semantic ranking is plan-gated. Published custom storefront routes use short revalidation windows and bounded product queries. These controls improve common response paths but are not a claim of unlimited traffic capacity or a load-test result.
Public routes publish page titles, descriptions, canonical links, structured data, robots rules, and a sitemap. Published merchant custom pages are added to the sitemap. The robots policy allows major search and answer-engine crawlers on public pages while excluding dashboard and API routes. These signals explain Maghgo to crawlers but cannot guarantee indexing, ranking, citations, or inclusion in an AI answer.
Merchant API operations require signed account tokens; store-facing product discovery is tenant-scoped; public responses exclude gateway secrets; online payment status is verified against provider data; and chat/checkout endpoints use request limits. Conversation turns and limited shopper preferences are saved for conversational continuity. Maghgo publishes its current storage and provider behavior in the privacy page and does not claim an external security certification here.
Store, Maghgo AI, and Maghgo Verified are billed as separate subscription families. The pricing page reads the current catalog and shows prices, GST, plan limits, and the feature list for each plan. Basic includes up to three storefront pages and a custom-domain connection without an extra Maghgo add-on fee; domain registration is separate.
View current Maghgo prices and plan features