Wholesale distributors: order tracking using Next.js · Ample Computer

Wholesale distributors: order tracking using Next.js

An order tracking blueprint for wholesale distributors built with Next.js on Ample. Domain schema: products (sku, name, category, case_size, list_price, active): SKU catalog with case sizes; stock_movements (sku, warehouse, delta, reason, moved_at): receipts, picks and adjustments; orders (order_no, account_reference, status, placed_at): trade orders with status transitions; order_lines (order_no, sku, cases, unit_price): order contents; events (seq, record_type, record_id, kind, at): application-owned history written in the same transaction. Public information: catalog with case sizes, minimum order and delivery terms, trade account application. Kept out of scope until handling is reviewed: account pricing tiers, credit terms, delivery addresses. Account-specific pricing and credit terms are confidential; the catalog shown publicly carries list prices only. Technical basis verified on Next.js: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected).

What it runs on

You need

Exact tested configuration

Steps

  1. Model the wholesale distributors domain. Create the tables products, stock_movements, orders, order_lines, events. Sku catalog with case sizes lives in products; keep the sensitive classes (account pricing tiers, credit terms, delivery addresses) out of this schema.
  2. Workflow step 1. Model orders with explicit status transitions and order lines.
  3. Workflow step 2. Apply status changes transactionally and record an event per change.
  4. Workflow step 3. Expose status history to authorized callers only.
  5. Workflow step 4. Deploy and verify history and conflict rejection.
  6. Deploy. Run the synchronous deploy once and read the result. Re-running with no change is a no-op.
    $ ample deploy . --name <app-name> --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...
    ```
7. **Verify.** Run the pattern self-test(s) from the example (/p/transactional-workflows) and your own acceptance checks for the wholesale distributors workflow.
$ ample logs <deployment_id> --kind build
```

How it was checked

✓ app responds on its public URL.
✓ transactional-workflows self-test from the example.

Evidence

  1. November 5, 2026 · canary run
    Next.js pattern fixture deployed on Ample; the transactional workflows checks passed: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected). The blueprint's Wholesale distributors schema and workflow below build on that verified basis.

Tested examples

What it doesn’t cover