TokoNusa

Run one store or fifty, all from one dashboard.

TokoNusa is a multi-tenant commerce platform for Indonesian merchants, agencies, and franchise operators who need to manage multiple online shops from one place. It centralizes catalogs, orders, customers, payments, and reporting across tenants while keeping each store’s data isolated and configurable.

Business Goals

  • Reach 100 paying tenant accounts within 6 months of launch.
  • Convert at least 20% of trial tenants to paid plans within 30 days.
  • Keep monthly churn below 5% by month 9.
  • Achieve 95% of orders synced into the system within 60 seconds of ingestion.
  • Drive 30% of active tenants to manage at least 3 stores on the platform by the end of year 1.

User Goals

  • Create and switch between multiple store workspaces without logging in again.
  • Import products, inventory, and orders from existing channels into one view.
  • Assign staff roles per store so teams only see what they need.
  • Track sales, fulfillment, and stock by store and across the full business.
  • Receive alerts when orders fail, stock is low, or payments are pending.

Non-Goals

  • Building a consumer-facing marketplace for shoppers to browse and buy products.
  • Providing full ERP accounting, payroll, or tax filing features.
  • Replacing every marketplace seller tool for Shopee, Tokopedia, or TikTok Shop.
  • Supporting custom warehouse automation hardware in the first release.

Shop Owner Dina, 34 - Dina runs three fashion stores across Shopee, Tokopedia, and Instagram order links. She needs one place to see sales, inventory, and staff activity without spending her day in spreadsheets.

Shop Owner Dina, 34

  • As a shop owner, I want to see all store performance in one dashboard, so that I can quickly spot which store needs attention.
  • As a shop owner, I want to update prices and stock for one product across selected stores, so that I avoid manual repetition and overselling.
  • As a shop owner, I want automated low-stock alerts by store, so that I can reorder before sales are lost.

Operations Manager Rudi, 41 - Rudi manages fulfillment for a franchise with several branches and multiple store admins. He needs role-based access and reliable order processing across stores.

Operations Manager Rudi, 41

  • As an operations manager, I want to assign branch-specific permissions, so that staff only access the stores they handle.
  • As an operations manager, I want to filter orders by status, store, and SLA, so that I can prioritize shipping work.
  • As an operations manager, I want to export daily order and inventory data, so that I can reconcile with warehouse records.

Agency Admin Sari, 29 - Sari runs an e-commerce agency that manages stores for clients. She needs clean tenant separation, client reporting, and easy onboarding for new accounts.

Agency Admin Sari, 29

  • As an agency admin, I want to create a new tenant for each client, so that their data stays isolated and organized.
  • As an agency admin, I want to view each client’s performance without mixing data, so that I can report accurately.
  • As an agency admin, I want to invite client staff with limited permissions, so that I can collaborate safely.

Multi-Tenant Workspace Management · High priority

  • Each tenant represents one business client or store group, with strict data isolation and configurable settings.
  • Users can create, rename, archive, and switch tenants from a single account.
  • Tenant-level settings include branding, currency IDR, tax settings, notification preferences, and store labels.
  • All records are scoped by tenant_id and cannot be accessed across tenants without explicit admin membership.
  • Support tenant invitations with email-based onboarding and role assignment.
  • Show tenant switcher in the global header with search when the user belongs to more than five tenants.

Store and Catalog Management · High priority

  • Users can manage product catalogs, variants, inventory, pricing, and store-specific publishing across connected sales channels.
  • Create products with variants, images, SKU, barcode, cost, and channel-specific price overrides.
  • Bulk import and export products via CSV templates in Bahasa Indonesia and English.
  • Detect duplicate SKUs and warn before publish when stock is zero or negative.
  • Support per-store product visibility and draft vs published states.
  • Allow bulk stock adjustments with audit history and reason codes.

Orders and Fulfillment · High priority

  • Users can consolidate incoming orders across stores and track them through packing, shipment, delivery, and cancellation states.
  • Order list supports search, filters, and saved views by store, status, payment status, and fulfillment SLA.
  • Orders ingest from integrations and can also be created manually for offline channels.
  • Order detail includes items, customer info, payment status, shipping method, notes, and timeline.
  • Support fulfillment actions like packing, partial shipment, cancellation, and refund request marking.
  • Alert on failed syncs, duplicate orders, and unsupported status transitions.

Roles, Permissions, and Audit Logs · Medium priority

  • The platform must support secure collaboration for owners, staff, and external agencies while preserving accountability.
  • Roles include Owner, Admin, Manager, Warehouse, and Viewer with configurable permissions.
  • Per-tenant invitations expire after 7 days and can be resent or revoked.
  • Audit log records changes to products, orders, inventory, settings, and access control.
  • Sensitive actions require re-authentication for owners and admins.
  • Admin users can restrict export access and bulk edits for staff roles.

Reporting and Notifications · Medium priority

  • Users need fast visibility into sales, stock, fulfillment, and sync health across tenants and stores.
  • Dashboard shows daily sales, order volume, average ticket size, and low-stock counts by tenant and store.
  • Reports can be filtered by date range, channel, store, and product category.
  • Notification center supports email, WhatsApp, and in-app alerts for stock, orders, and integration failures.
  • Weekly summary emails provide key metrics and anomaly highlights.
  • Export reports as CSV and XLSX with locale-aware formatting for Indonesia.

First-Time Tenant Setup

  • Sign up with email, Google, or phone number.
  • Create the first tenant and choose business type: single store, multi-store, or agency.
  • Connect sales channels such as Shopee, Tokopedia, Shopify, or manual order entry.
  • Import products and current inventory using CSV or channel sync.
  • Invite team members and assign roles.
  • Reach first usable dashboard in under 10 minutes, with a clear success checklist.

1. Tenant Dashboard

  • Users land on a tenant-specific dashboard that summarizes sales, orders, inventory risk, and sync status.
  • Show a clear tenant context at all times to prevent cross-tenant confusion.
  • Display blank-state guidance for new tenants with next-step actions.
  • Flag sync problems and overdue fulfillment items at the top of the page.

2. Connect Stores and Import Data

  • Users connect external commerce channels or manually add stores, then import products and orders.
  • Validate integration credentials before enabling sync.
  • Map incoming fields to the platform schema with preview and error handling.
  • If a sync fails, keep existing data intact and show retry guidance.

3. Manage Catalog and Inventory

  • Users edit products, variants, pricing, and stock across selected stores from one interface.
  • Support bulk editing with row-level validation and partial success reporting.
  • Prevent publishing of products with missing required fields like SKU or price.
  • Keep an immutable history of stock adjustments with who, when, and why.

4. Process Orders

  • Users review incoming orders, pack items, update status, and manage exceptions.
  • Allow inline status updates and batch actions for eligible orders.
  • Warn when an order is already fulfilled or cancelled in the source channel.
  • Provide customer and shipment history on one screen for quick decisions.

5. Review Performance

  • Users inspect reports by tenant and store to understand sales, stock, and operational bottlenecks.
  • Offer date range presets for today, last 7 days, and last 30 days.
  • Let users drill into metrics by channel, product, and branch.
  • Handle empty data states with clear explanations and suggested actions.

Power Features and Edge Cases

  • Cross-tenant analytics for agency owners with strict permission boundaries.
  • Store-level branding and custom domains for agencies or franchise groups.
  • Scheduled reports sent to email or WhatsApp on a daily or weekly cadence.
  • Support for offline/manual orders when a marketplace API is unavailable.
  • Conflict resolution flow for duplicate orders, out-of-sync inventory, and partial refunds.
  • Localized support for Bahasa Indonesia, IDR, WIB/WITA/WIT time zones, and local date formats.

Interface Principles

  • Fast, dense admin UI optimized for desktop first, with mobile-responsive critical actions.
  • Clear tenant coloring and labels to reduce mistakes when switching contexts.
  • High-contrast text, keyboard navigation, and screen-reader friendly controls.
  • Tables with sticky filters, bulk actions, and progressive disclosure for complex data.
  • Performance target of sub-2 second initial dashboard load on standard broadband.

Dina used to check three store dashboards, download CSV files, and reconcile stock in spreadsheets every night. When one store oversold a popular hijab style, she did not notice until orders were already delayed and customers were upset.

With TokoNusa, Dina connects her stores once and sees inventory, orders, and sales in a single tenant dashboard. She updates stock across selected stores, gets low-stock alerts before products run out, and resolves fulfillment issues faster.

Within a week, Dina spends less time on manual admin and more time on buying and promotions. Her team works from one source of truth, and the business avoids oversells, missed orders, and messy reporting.

User-Centric Metrics

  • 80% of new tenants complete setup and connect at least one store within 10 minutes.
  • 70% of active tenants use the dashboard at least 3 days per week.
  • Average order processing time drops by 30% within 60 days of adoption.
  • Low-stock incidents decrease by 25% for tenants using inventory alerts.
  • At least 60% of users rate onboarding as easy or very easy in post-setup survey.

Business Metrics

  • 20% trial-to-paid conversion within 30 days.
  • Monthly active tenant retention above 85% after month 3.
  • Net revenue retention above 110% through seat and store expansion.
  • Less than 5% monthly logo churn by month 9.
  • 30% of new paid tenants manage three or more stores within 90 days.

Technical Metrics

  • 99.9% uptime for core dashboard and order workflow.
  • P95 dashboard API latency under 300 ms.
  • P95 sync job processing under 60 seconds for standard integrations.
  • Zero cross-tenant data leakage incidents.

Tracking Plan

  • tenant_created
  • integration_connected
  • catalog_import_started
  • catalog_import_completed
  • order_synced
  • inventory_adjusted
  • role_invite_sent
  • report_exported
  • low_stock_alert_triggered
  • sync_failed

Technical Needs

  • Frontend: Next.js with React and TypeScript for fast admin UI.
  • Backend: NestJS or Express with TypeScript for modular APIs.
  • Database: PostgreSQL with tenant_id scoping and row-level security where practical.
  • Queueing: Redis and BullMQ for sync jobs, notifications, and report generation.
  • Search and filtering: PostgreSQL indexes plus optional Elasticsearch for larger catalogs.
  • File storage: S3-compatible object storage for imports, exports, and product images.
  • Observability: OpenTelemetry, Sentry, and structured logs for auditability.

Integration Points

  • Shopee API for order and product sync.
  • Tokopedia API for marketplace data ingestion.
  • Shopify Admin API for connected storefronts.
  • WhatsApp Business API for operational alerts.
  • Google OAuth and email/password authentication via Auth0, Clerk, or custom auth.

Data Storage & Privacy

  • Store tenant data in logically isolated records with strict authorization checks on every request.
  • Encrypt sensitive data at rest and use TLS in transit for all services.
  • Minimize stored personal data; retain customer PII only as required for order operations and reporting.
  • Provide export and deletion workflows to support GDPR-style access and deletion requests where applicable.
  • Audit all admin actions and preserve logs according to a defined retention policy, such as 12 months.

Scalability & Performance

  • Support many small tenants and a smaller number of high-volume tenants using asynchronous sync jobs.
  • Use caching for dashboard aggregates and frequently accessed lookup data.
  • Paginate all large lists and use cursor-based pagination for high-volume orders.
  • Isolate slow external integrations so one failing channel does not block the whole tenant.

Potential Challenges

  • Marketplace API rate limits and changing schemas; mitigate with adapters, retries, and schema versioning.
  • Cross-tenant data leakage risk; mitigate with tenant-scoped authorization middleware and automated tests.
  • Sync conflicts between source channels and local edits; mitigate with source-of-truth rules and conflict prompts.
  • Large CSV imports causing timeouts; mitigate with background processing and resumable uploads.
  • User confusion across multiple stores; mitigate with strong tenant context, color cues, and confirmation dialogs for destructive actions.

Team & resourcing - Small team - 2 backend engineers, 1 frontend engineer, 1 designer, part-time PM, and QA support as needed.

Phase 1: MVP Workspace and Orders · Weeks 1–4

  • Authentication and tenant creation
  • Tenant switcher and role-based access
  • Manual store setup
  • Basic order list and order detail
  • Dashboard with core KPIs
  • Audit log for critical actions

Phase 2: Catalog and Inventory Sync · Weeks 5–8

  • Product CRUD with variants and SKU support
  • CSV import/export
  • Inventory adjustment flows
  • Shopee and Tokopedia integration scaffolding
  • Low-stock alerts and sync status indicators

Phase 3: Reporting and Collaboration · Weeks 9–12

  • Sales and inventory reports
  • Saved filters and exports
  • Team invitations and permission management
  • WhatsApp/email notifications
  • Weekly summary emails
  • Improved onboarding checklist

Phase 4: Hardening and Scale · Weeks 13–16

  • Performance optimization and caching
  • Retry and dead-letter handling for sync jobs
  • Security hardening and tenant isolation tests
  • Localization for Bahasa Indonesia and IDR
  • Monitoring dashboards and admin support tools

Paste this into Cursor, Bolt, Lovable, or v0 to start building.

Build a multi-tenant commerce admin web app called TokoNusa for Indonesian merchants, agencies, and franchise operators.

Core concept:
Users can create and switch between tenants, where each tenant represents one business/client/store group. All data must be tenant-scoped with strict isolation. The app centralizes stores, products, inventory, orders, staff roles, notifications, and reporting.

Primary screens and flows:
1. Auth: email/password and Google sign-in
2. Tenant setup: create tenant, choose business type, set currency IDR, timezone, and notification preferences
3. Tenant switcher in global header
4. Dashboard: sales, orders, low-stock, sync health, recent activity
5. Stores/integrations page: connect Shopee, Tokopedia, Shopify, and manual store setup
6. Products page: CRUD products, variants, SKU, barcode, price overrides, bulk CSV import/export
7. Inventory page: stock by store, bulk adjustments, low-stock alerts, audit history
8. Orders page: list, filters, detail drawer/page, status updates, batch actions, timeline
9. Team and permissions: invite users, roles Owner/Admin/Manager/Warehouse/Viewer, per-tenant access
10. Reports page: sales by date/store/channel/product, exports CSV/XLSX
11. Notification center and audit log

Data model:
User, Tenant, TenantMembership, Role, Store, IntegrationConnection, Product, ProductVariant, InventoryItem, Order, OrderItem, Customer, Notification, AuditLog, ReportExport.
Each record must include tenant_id. Support created_at, updated_at, and soft delete where appropriate.

Tech stack default:
Frontend: Next.js 14, React, TypeScript, Tailwind CSS, shadcn/ui
Backend: NestJS or Next.js server actions with REST endpoints
Database: PostgreSQL with Prisma ORM
Auth: Clerk or Auth0
Queue/jobs: BullMQ with Redis
File storage: S3-compatible storage
Analytics/logging: PostHog, Sentry, OpenTelemetry
Deployment: Vercel for frontend and managed container service for backend

Implementation requirements:
Use a clean, responsive desktop-first admin UI with Bahasa Indonesia-ready labels. Include strong tenant context in the header, role-based access control, loading and empty states, validation for CSV uploads, and optimistic UI where safe. Add seeded demo data for at least 2 tenants and multiple stores.

Build the MVP first with tenant management, dashboard, products, orders, inventory, and team permissions. Structure the codebase for future marketplace integrations, webhooks, and reporting jobs.

Business Idea

multi tenant shop indonesia

Make My PRD

Design by The Resonance | Powered by GPC – The AI Transformation Company

    PRD: multi tenant shop indonesia