Skip to content

Features

Nudova ships a complete commerce stack you own: a storefront, a staff admin app, the catalog and commerce capabilities behind them, CRM and CMS when your purchase includes them, and a hardened self-hosted platform. This page is the full tour of what merchants and operators get.

A complete Next.js storefront with honest scarcity, trust-first ordering, and one clear action per screen — without dark patterns. See The Nudge Framework for the honesty defaults; these are the shipping pages and behaviours:

  • Every selling page, designed and built — home, category listing with faceted filters, product page (with dedicated modes for one-of-one, limited and everyday products), cart, single-page checkout, thank-you page, order tracking, search, collections & lookbook, full account area, and the supporting content pages (about, FAQ, size guide, store locator, policies).
  • Phone-first guest checkout — cash-on-delivery by default, a Bangladesh Division → District → Area address picker, and phone OTP verification that quietly becomes the returning-customer login. Guests are never forced to register.
  • Honest scarcity — live stock drives everything: “held for you” reservations at checkout, low-stock notes, sold-out variants shown disabled (never hidden), one-of-one pieces marked claimed when gone. No countdown timers, no fake “3 people are viewing this”.
  • Thank-you page offer — shoppers can accept a one-time offer after checkout (or decline it); accepted items append to the same order without a second checkout.
  • Customer account, light by design — order history with one-click reorder (only what’s still in stock — skipped lines are told to you), saved address book, wishlist with back-in-stock alerts, notification preferences.
  • Content-managed without deploys — the homepage hero and section bands, editorial collections, “shop the look”, FAQs, size-guide charts, policy pages and search trending terms all come from the admin. Edit there, live here.
  • Bangla-ready — Bangla locale, Taka formatting with Bangla numerals, festival merchandising (Eid, Pohela Boishakh) built into collections.
  • Your brand, one image — token-driven theming with presets you can switch; rebrand at runtime via config, no rebuild (see Tokens & branding).

Staff admin — run the store from one screen

Section titled “Staff admin — run the store from one screen”

A fast, dark, glassy back office (see the Admin Guide) covering the whole retail day:

Sell

Live dashboard (today’s sales, orders, AOV, 7-day sparklines, alert queues) · orders with full timelines · status lifecycle with guarded transitions · manual & phone order entry with drafts · invoices and packing slips, print-ready.

Stock

Catalog with a variant matrix editor (colour × size) · per-variant SKU, price override and stock · size-scale templates (alpha, waist×length, boys year-based) · inventory adjustments with a full movement ledger · low-stock thresholds · reservations · back-in-stock waiter queue · CSV export.

Protect

COD guardrails — set a maximum COD value and a phone-risk threshold, and an order that breaks them is held automatically before anyone can book a courier. Then fraud review: each held order carries a delivery-history risk signal for its phone number (prior orders, cancellations, courier success rate) so you confirm or cancel with evidence, not gut feel.

Grow

Store discount codes (percent/fixed, minimum order, usage limits, scheduling) · merchandising curation — collections, complete-the-look sets, one-time-offer rules · CMS editing for every storefront content surface · customer profiles with order history, wishlist and staff notes.

Plus store operations: a first-run setup wizard, delivery zones & fees, payment/courier/SMS/phone-risk provider credentials (stored encrypted, never echoed back) and notification templates.

And a real team model: five role presets (owner, manager, orders staff, inventory staff, custom) over a permission catalog you can tailor per store — enforced by the API, not just hidden from the menu. Settings and integrations stay owner-only by construction. Plus a workspace 2FA policy, and per-user device sessions you can revoke when a phone goes missing.

When your purchase includes Catalog, shoppers can browse products and staff can manage the product library (see Catalog):

  • Products with a true variant matrix — brands, categories, tags/occasions, size scales, responsive image sets.
  • “Request a quote” inquiries — a catalog-focused shop has no cart, so a shopper acts on interest by submitting name, contact and an optional message against a product; staff work the inbox like a lightweight lead queue.

When your purchase includes Commerce, shoppers get a full cart and checkout, and staff get the order desk. See Commerce for the reference-level breakdown:

  • Three stock modes — one-of-one unique pieces, limited runs, and continuously replenished depth — each with matching storefront behaviour.
  • Oversell-proof inventory — atomic reservations with TTL, commit on payment, automatic release on expiry. The checkout hold window is a store setting (admin Settings → Checkout: on/off, 5–60 minutes).
  • Orders as immutable snapshots — names, SKUs and prices are frozen at purchase; later catalog edits never rewrite history. COD reconciliation fields built in.
  • Checkout orchestration — server-side pricing (discounts, delivery fees with free-delivery threshold, optional tax), stock held through payment, COD confirmation or SSLCommerz redirect from one endpoint.
  • Payments — Cash on Delivery, SSLCommerz (bKash, Nagad, cards) and Stripe, with webhooks and refund handling.
  • Couriers — Pathao, Steadfast and RedX from the order screen: book consignments and fetch labels. Pathao and Steadfast also track via webhooks and a polling refresh, advancing the order timeline automatically; RedX booking works today, live tracking updates are still to come.

When CMS is included, staff edit storefront content from the admin: homepage bands, collections and lookbooks, FAQs, size guides, policy pages, and search trending terms. Changes go live without rebuilding the storefront. See CMS.

A working sales CRM: contacts, accounts, leads, pipelines with kanban deal boards, activities with due-date reminders, an activity timeline and a CRM dashboard — with role and team visibility rules. Run a shop book, an agency book, or both. See CRM and the CRM admin guide.

When included in your purchase:

  • Blog — a full staff admin module: drafting, workflow, SEO, webhooks and content health. See Blog / journal. Add the optional Blog Autopilot add-on for AI-planned, human-approved article generation on a schedule.
  • Marketing — campaigns and posts across connected social channels (LinkedIn, Meta, X), with an approval queue and performance metrics. See Marketing and the Marketing admin guide.
  • Helpdesk — ticket and support workflows over the API / deep-ops console. No dedicated Next.js admin module yet.
  • Kanban — board-style work tracking over the API / deep-ops console. No dedicated Next.js admin module yet.

When Copilot is included, it’s a tool for the team building on Nudova, not for shoppers: give it a free-text requirement and it drafts OpenProject work packages (epics, features, tasks, bugs) with estimates, priorities and test stubs, using a project knowledge base and a human approval step before anything reaches OpenProject. See Copilot and the Copilot admin guide.

Commerce doesn’t ship a built-in affiliate/referral module today. If your agency needs one, the add-on system is built for exactly this: a sellable feature parented on one domain, wired in without touching that domain’s code.

These ship as capabilities you enable when they are part of your purchase. SMS, payments, couriers and phone-risk are each a provider package — a shared, versioned adapter you select and configure rather than code you write:

  • SMS — phone OTP login, SMS MFA, and SMS notifications. See SMS provider.
  • Payments — Cash on Delivery, SSLCommerz and Stripe. See Payment providers.
  • Couriers — booking and tracking with Pathao, Steadfast, and RedX where connected. See Courier providers.
  • Phone-risk / fraud — COD phone-risk checks that feed auto-hold and fraud review. See Phone-risk provider.
  • Push notifications — mobile/web push when included.
  • Media Studio — AI image/video generation, when that optional platform group is included.
  • SaaS billing — plans, subscriptions, invoices, and a card ledger when that optional group is included in your purchase.

Some AI-powered features inside an installed domain are licensed even more finely than this — see Entitlements if a feature you’d expect (an AI-read in Blog, a specific Marketing channel) doesn’t appear.

What operators get day to day (details in Deployment shape, Requirements, and Quickstart):

  • You own it — Docker images on your VPS, your data in your PostgreSQL. Size the box for lite or full on the Requirements page. One image, any brand: configuration is runtime, so you never rebuild to rebrand.
  • Batteries-included deploy — Caddy with automatic HTTPS, nightly database backups, a job scheduler, health checks and log rotation — wired on first boot.
  • Setup wizard — one guided command seeds a new store and theme preset (Provision a store).
  • Identity & auth — JWT sessions, social login (Google/Facebook/LinkedIn), email & phone verification, device/session tracking, roles and permissions.
  • Notifications — email, SMS, push and in-app, with store templates and event-driven triggers (order placed, tracking link, back in stock).
  • Operational hygiene — audit trail, GDPR tooling, encrypted integration credentials, file/S3 storage, feature flags, and a realistic demo seed (catalog, images, content, deliberate edge cases) for evaluation.

Honesty cuts both ways. There are no fake reviews, no invented urgency timers, no hidden fees at checkout, and no dark-pattern unsubscribe mazes — the Nudge Framework explains what we ship instead. Reviews & ratings arrive later by design: they ship when your store has real history to show, not before.