Commerce Operations Platform

A full-stack operations system for cross-border commerce teams. It brings product data, marketplace orders, procurement, inventory, fulfilment and finance into one auditable workflow instead of a collection of spreadsheets.

This repository is a sanitized engineering snapshot: databases, customer and order records, uploaded media, exports, credentials, backups and production configuration are intentionally excluded.

What it covers

• Product and SKU master data with spreadsheet import/export and image caching
• Marketplace order intake, status handling and special-order workflows
• Purchase pool, cart, ledger, exception costs and domestic tracking
• Inventory reservations, warehouse dispatch and return templates
• Settlement, fee accrual, reconciliation, refund and low-margin review flows
• Role-based administration, configurable stores, warehouses and exchange rates
• Operational controls for backups, disk monitoring, Nginx and PM2 deployment

Architecture

Browser
  └─ Next.js App Router (React + Server Actions)
       ├─ Authentication and workflow services
       ├─ Import/export and reconciliation services
       └─ Prisma ORM
            └─ SQLite

The schema models the full lifecycle from a product and marketplace order through procurement, stock reservation, warehouse fulfilment and financial settlement. Business rules are kept in src/lib, while route-specific actions and UI live under src/app.

Stack

• Next.js 16, React 19 and TypeScript
• Prisma ORM and SQLite
• Tailwind CSS
• ExcelJS, SheetJS, csv-parse and iconv-lite
• Nginx and PM2 deployment examples

Run locally

Requires Node.js 20+ and SQLite.

npm ci
cp .env.example .env
npx prisma db push
npx prisma generate
npm run dev

Set AUTH_SECRET in .env to a long random value before using the authentication flow. The repository contains no seeded account or production data.

Quality checks

npm run lint
npm run build

The sanitized snapshot has been checked with Prisma client generation, ESLint and a production build.

Data and security boundary

Only source code, the database schema and generic deployment examples belong in version control. Local databases, .env files, backups, generated exports, logs and uploaded assets are ignored. A real deployment should additionally use encrypted off-host backups, restricted filesystem permissions and a dedicated secret manager.