Skip to main content

PointNXT engineering

PointNXT is a multi-tenant order management and warehouse management platform for omnichannel commerce. The backend is one NestJS codebase that runs as an API, a worker, and a scheduler. Operators use the admin web app. Warehouse floors use the Expo app. Marketplaces and couriers talk to the API.

This site explains how that system is actually built so you can find the code, follow a workflow, and change it without guessing. It is checked against backend commit b5bd463f on 2026-10-01. Where the repository does not establish intent, the page says Unknown.

What should I read first?

  1. PointNXT overview
  2. System architecture
  3. Backend architecture
  4. Tenancy and the domain model
  5. Local development
  6. An important business flow — create an order
  7. Trace the order code

Quick links

ArchitectureThree processes, five areas, outbox, and tenancy.DomainsOrders, inventory, channels, fulfillment, and the rest of the model.API referenceHow to use the generated OpenAPI document. Endpoints are not copied here.Local developmentCompose, migrations, and the three processes you must run.IntegrationsMarketplaces, couriers, Razorpay, Meta, and platform services.TroubleshootingBoot, database, Redis, queues, auth, sync, and labels.

What breaks if you only start the API

The API commits orders and outbox rows. The worker dispatches the outbox and runs Bull processors. The scheduler enqueues channel sync and other crons. Running only the API leaves fulfillment, wallet debits, inventory publish, and marketplace sync sitting unprocessed.

Source links in these pages open pnxt-api-nestjs on GitHub. Override the repository with BACKEND_REPO_URL and BACKEND_REPO_BRANCH before you build. Admin and warehouse apps are documented by workspace path because this pass did not record their Git remotes.