N Nexus Docs
Getting Started

Quick Start Guide

Get NexusCommerce running and your first marketplace connected in under 10 minutes.

Overview

NexusCommerce is a multi-marketplace SaaS platform that unifies your Amazon, eBay, Shopify, Walmart, Bol.com, Zalando, and Kaufland operations into a single command center. This guide walks you from zero to your first live sync in under 10 minutes.

The platform has three capability tiers:

  • Foundation: Dashboard, Products, Orders, Returns, Inventory, Connections
  • Intelligence: AI Pricing Engine, ClickHouse Analytics, Ad Automation, AI Studio, Review Analytics
  • Advanced: Review Intelligence, Return Analytics, LLM Visibility Tracking, Subscription Billing

Key Concepts

Tenant — Your organization in NexusCommerce. All data is isolated per tenant. Your tenant ID is shown under Settings > API Keys.

Connection — An authenticated link between NexusCommerce and one marketplace account. A single tenant can have multiple connections to the same marketplace (e.g., an Amazon EU account and an Amazon US account).

Adapter — The integration layer for each marketplace. Adapters handle authentication, rate limiting, and field mapping. See Marketplace Adapters for per-marketplace details.

SKU / Listing — A SKU is your internal product identifier. A Listing is a marketplace-specific representation of that SKU (ASIN on Amazon, item ID on eBay, etc.).

Job — An AI-worker task dispatched to the Python FastAPI workers. Jobs handle pricing recalculation, review sentiment, return classification, and LLM visibility scoring.

Getting Started

Step 1: Create your account

Navigate to your NexusCommerce instance and sign up. If you are self-hosting, follow the Installation guide first.

After sign-up you land on the Onboarding screen. The platform creates a default tenant bound to your email domain.

Step 2: Connect your first marketplace

From the Onboarding screen, click Connect a Marketplace or navigate to Connections in the left sidebar.

Select a marketplace, enter your credentials, and click Test Connection. A green status badge confirms the connection is live. See First Connection for credential details per marketplace.

Step 3: Trigger an initial sync

After connection, click Sync Now on the connection card. NexusCommerce will pull your existing catalog, open orders, and inventory into the unified database. Depending on catalog size, the initial sync takes 1–15 minutes.

Step 4: Explore the Dashboard

Navigate to Dashboard. You will see:

  • Revenue, orders, returns, and inventory-value stat cards
  • Active alerts (low stock, pricing conflicts, failed syncs)
  • Onboarding progress checklist

Step 5: Configure pricing rules (optional)

Navigate to Pricing and create your first rule. Even a simple floor-price guard prevents margin erosion before you set up full AI pricing.

Features

Unified Catalog

Every product you sell across all marketplaces is stored once. NexusCommerce maintains a mapping table between your internal SKU and each marketplace's native identifier (ASIN, EAN, GTIN, etc.).

Real-time Order Sync

Orders from all connected marketplaces flow into NexusCommerce within seconds via webhooks (where supported) or polling intervals (configurable per adapter).

AI Workers

Background jobs run in the Python FastAPI worker fleet. Workers are dispatched via the NestJS API and results are written back to Supabase. Current worker types:

  • pricing_recalculate — Recomputes optimal price using competitor data and margin targets
  • review_sentiment — Runs NLP sentiment classification on new reviews
  • return_classify — Classifies return reasons and flags anomalies
  • llm_visibility_score — Queries LLM shopping assistants and scores product visibility

Configuration

SettingLocationDescription
Default sync intervalSettings > ConnectionsHow often adapters poll for updates (15m, 1h, 4h, daily)
Pricing currencySettings > GeneralBase currency for margin calculations
Alert thresholdsSettings > NotificationsStock level and revenue drop thresholds
Team membersSettings > TeamInvite team members with role-based access

Next Steps