Wholesale distributors: product catalog using Next.js

Summary

A product catalog 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).

Representative Queries

• Wholesale distributors: product catalog using Next.js
• Where can I host Wholesale distributors: Product catalog built with Next.js?
• I need a genuinely specialized product catalog workflow covering case-pack units, B2B catalog visibility and volume order imports.

Resource Requirements

• primitive:compute
• primitive:postgres
• primitive:s3-compatible-object-storage

Infrastructure Requirements

Prerequisites

• A Next.js project (next build then next start -H 0.0.0.0 -p $PORT on the node-22 template)
• A PostgreSQL driver reading DATABASE_URL (auto-provisioned when omitted)
• Bucket credentials from ample bucket create passed as encrypted S3_* environment variables
• A review of which wholesale distributors data classes may be handled at all; this blueprint models public information only

Workflow 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. Model the SKU catalog with versioned updates.
3. Record every catalog change as an event in the same transaction.
4. Reject stale concurrent updates.
5. Deploy and verify history and conflict handling.
6. Run the synchronous deploy once and read the result. Command: ample deploy . --name --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...
7. Run the pattern self-test(s) from the example (/p/transactional-workflows) and your own acceptance checks for the wholesale distributors workflow. Command: ample logs --kind build

Examples

• Next.js pattern fixture: Verified transactional workflows basis for this blueprint. Source

Success Checks

1. App responds on its public URL.
   • Kind: http_get
   • Path: /
   • Expect: ample canary next js patterns
2. Transactional-workflows self-test from the example.
   • Kind: http_get
   • Path: /p/transactional-workflows
   • Expect: see the pattern fixture checks

Limitations

• The technical basis (transactional workflows on Next.js) was verified with the pattern fixture; the wholesale distributors schema and workflow are an original design for this blueprint and were not executed as a separate application.
• No health, financial, privacy or other compliance claim is made. Account-specific pricing and credit terms are confidential; the catalog shown publicly carries list prices only.
• Public content and synthetic examples only until actual data-handling requirements have been reviewed.
• Verified on the node-22 template at s-1vcpu-1gb; region, request-duration limits and other sizes are unknown or unverified.
• Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified.
• PutObject and GetObject with path-style addressing are verified; other S3 operations and CDN cache rules are not verified.