The commerce platform behind every store we run.

Where Dhisa runs the platform itself. Each client is a tenant, isolated and individually configured.

• Tenants created with a wizard: one schema or a dedicated database each, a subdomain and custom domains, master data seeded from a workbook.
• Modules per tenant with dependencies. Winding down and switching off are refused while a tenant's open work still needs the module.
• Tenant bundles: export and import a whole tenant, and move it between platforms.
• Order and subscription flows drawn on a canvas from a palette, validated by a rules table, versioned, published and assigned per tenant or per store.
• Maintenance: rename, reload, rotate, suspend, resume, backups, and delete only with the slug typed.
• Operators and roles, open-as-support into a tenant with an audit trail, and postal-code data shared platform-wide.

One organisation, any number of stores, each with its own branding, staff and settings.

• Stores with branding, a setup checklist, per-store permissions, payment methods, shipping carriers, delivery zones and slots, and departments.
• Staff, roles and permissions, designations, users and access at organisation and store level.
• Master-data engine: generic tables scoped to the organisation or a store, with Excel import and export.
• Branding and palettes, the tenant's own domain, and an installable app with manifest and icons generated from the branding.
• Calendar of working days and holidays, announcements, messaging, a help desk and a notification outbox with templates.
• Activity log and reports.

Built for Indian retail: sizes and packs, HSN codes, tax classes and segment pricing are first-class.

• Categories, brands and attributes; products and items with sizes and packs, media, units and barcodes.
• Price lists tied to customer segments; tax classes and rates; HSN codes.
• Bundles: kits sold as one line and packed from their components, with GST classification and availability from component stock.
• Subscribable products, sets and bundles feed directly into subscription plans.

Stock is tracked per location, per lot, with the paper trail an auditor expects.

• Stock per location, receipts, movements, adjustments, counts, transfers and alerts.
• Lots with expiry dates and printed price.
• Assortment per store.
• Suppliers, purchase orders and goods receipts.

The public shop each client's customers see, on the client's own domain and in their own brand.

• Customer accounts with one-time-code sign-in, addresses, segments, wishlist, orders and tracking.
• Managed pages and sections, themes and collections. Marketing edits pages without a developer.
• Badges, reviews and leads, and store-level shop features.
• Coupons in the basket, and a sandbox gateway page for development and demos.

An order's life is a drawn flow: approvals, checkpoints, waits, notifications and decisions, run by a state machine.

• Carts and checkout, quotes, cash on delivery, pay at pickup, and online gateways (Razorpay, Stripe, sandbox) with webhooks and a worker.
• Shipments, combined boxes, carrier booking and tracking, COD remittances and return-to-origin.
• Delivery priced by distance bands.
• Returns with inspection; refunds before or without a return; replacements; credit notes.
• Order amendments before shipping, with the difference refunded or collected by link.
• Point of sale: counter sales and parked baskets.

• Coupons with schedules, minimums, limits and scopes, plus organisation rules for how codes combine.
• Subscription offers: subscribe-and-save, and term offers that grant extra deliveries, a free item, or a discount from the k-th delivery.

Recurring orders with the messy real-world cases handled: skips, moves, stock-outs, failed payments and substitutions.

• Plans for a product, a set, or a bundle with component rules.
• Schedules: weekly, every N days, monthly with a last-day rule, or chosen dates, with a calendar of estimated deliveries and cut-offs.
• Customer controls: skip, move, add an item, pause, resume, cancel, change from a day, approve a substitution.
• Store controls: hold for stock or review, release, substitute.
• Payments: payment links and auto-pay mandates with crash-safe charge attempts, and tools for a person to resolve an unknown outcome.
• A drawn flow for reminders, review, the out-of-stock rule, the unpaid rule, renewal and win-back messages.
• Terms with earned benefits and coupons scoped to subscriptions.
• Books checks on every subscription order.

Double-entry books inside the platform, so the store and the accounts never disagree.

• Books: chart of accounts, journal and entries, years and periods with locks and the year-end close, reports and export.
• Supplier bills and payments, purchase returns, gateway settlements and expenses.
• Background postings by a worker, with a retry list for refused postings.
• Reconciliation: a books check per order with fifteen invariants, a findings list, a rolling scan and a probe matrix.
• GST for India: registrations, place of supply, the CGST/SGST or IGST split, e-invoices and e-way bills.