Independent retailers: inventory manager using Next.js

Summary

A inventory manager 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).

Resource Requirements

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

Infrastructure Requirements

• Compute: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.

  • Status: verified

• Postgres: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

  • Status: verified

• S3-compatible object storage: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

  • Status: verified

Workflow 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. Model SKUs and stock movements; derive stock from movements.
3. Apply movements transactionally with an optimistic version check on the SKU.
4. Record an event per movement for history.
5. Deploy and verify history and rejected stale updates.
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 and your own acceptance checks for the independent retailers workflow. Command: ample logs --kind build

Examples

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

Success Checks

• App responds on its public URL: Check path / expects response ample canary next js patterns.
• Transactional-workflows self-test from the example: Check path /p/transactional-workflows expects to see the pattern fixture checks.

Limitations

• No health, financial, privacy or other compliance claim is made. Payment details belong to your payment provider; only order status and public catalog data are modeled here.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Components:
  • App server size s-1vcpu-1gb: quantity 1.0, monthly amount 5.0
  • Managed PostgreSQL database size s-1vcpu-1gb: quantity 1.0, monthly amount 5.0
• Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

Evidence Summary

• Canary Run: Next.js pattern fixture deployed on Ample; the transactional workflows checks passed, verifying components like optimistic version check and event recording.

Last Verified At

• 2026-09-21T02:34:39Z

Next Actions

• Browse the catalog index
• Search published recipes by intent, stack and constraints
• Prepare a side-effect-free deployment plan for an authorized project
• Read the existing agent authentication setup
• Browse Independent retailers
• Browse Inventory manager
• Browse Next.js
• Browse Deploy web app