Independent retailers: product catalog using Next.js · Ample Computer

Independent retailers: product catalog using Next.js

A product catalog blueprint for independent retailers built with Next.js on Ample. Domain schema: products (sku, name, category, price, active): the SKU catalog; stock_movements (sku, location, delta, reason, moved_at): receipts, sales and adjustments; orders (order_no, customer_reference, status, placed_at): orders with status transitions; order_lines (order_no, sku, qty, unit_price): order contents; events (seq, record_type, record_id, kind, at): application-owned history written in the same transaction. Public information: product catalog and availability, store locations and hours, returns policy. Kept out of scope until handling is reviewed: customer contact and payment details, supplier cost prices. Payment details belong to your payment provider; only order status and public catalog data are modeled here. 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

build npm run build --if-present

install npm install

runtime node

sizes-1vcpu-1gb

start npm run start

template node-22

Steps

  1. Model the independent retailers domain. Create the tables products, stock_movements, orders, order_lines, events. The sku catalog lives in products; keep the sensitive classes (customer contact and payment details, supplier cost prices) out of this schema.

  2. Workflow step 1. Model the SKU catalog with versioned updates

  3. Workflow step 2. Record every catalog change as an event in the same transaction

  4. Workflow step 3. Reject stale concurrent updates

  5. Workflow step 4. Deploy and verify history and conflict handling

  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=...
  1. Verify. Run the pattern self-test(s) from the example (/p/transactional-workflows) and your own acceptance checks for the independent retailers workflow.
   $ ample logs <deployment_id> --kind build

How it was checked

✓ app responds on its public URL· http get/ → “ample canary next js patterns”
✓ transactional-workflows self-test from the example· http get/p/transactional-workflows → “see the pattern fixture checks”

Evidence

  1. November 5, 2026 · canary run
    Next.js pattern fixture deployed on Ample (next build then next start -H 0.0.0.0 -p $PORT on the node-22 template); 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 Independent retailers schema and workflow below build on that verified basis.

Tested examples

What it doesn’t cover