Getting started

NShop is one application that runs many shops. The shape of your experience depends on who you are.

If you're a shopper

You arrived at a store like acme.shop.example or bistro.shop.example. That subdomain is the tenant; everything you see — products, branding, colors, checkout — belongs to that one shop. Your account works across all NShop stores, so when you sign up at one, you're recognized at the next.

Start with the Shopping guide.

If you run a store on NShop

You have admin access to one tenant. Your admin workspace lives at /admin on your store domain. From there you manage:

• products, variants, categories, and stock,
• orders (shop fulfillment or restaurant kitchen flow), sold-out menu toggles,
• coupons and shipping,
• branding (logo, hero, colors),
• payments (Stripe Connect onboarding or manual),
• team members and roles,
• the storefront AI assistant's persona.

Start with the Admin guide.

If you're building on NShop

The platform is a Next.js 15 app on Cloud Run, Firestore + Firebase Auth + Storage, a small set of Cloud Functions, and a separate Python Cloud Run service for the ADK + AG-UI shopping agent. Tenant isolation runs through three layers: subdomain → tenant resolution, Firebase Auth custom claims, and Firestore security rules. Read Multi-tenancy first.

What you should know about the AI assistant

NShop ships two AI surfaces. The floating chat on every storefront is the casual one — it answers questions, suggests products, and looks up your orders. A second, more capable agent at /x/assistant uses Anthropic ADK, AG-UI generative UI, and per-tool authentication to actually act on your behalf: add to cart, fetch order details, remember preferences.

Both are detailed in AI features.