### 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).

#### Representative Queries
- Independent retailers: product catalog using Next.js
- Where can I host Independent retailers: Product catalog built with Next.js?
- I need a genuinely specialized product catalog workflow covering SKU catalog, stock movements, and order statuses.

#### Resource Requirements
- Compute
- Postgres
- S3-compatible object storage

#### Infrastructure Requirements
1. **Compute**  
   Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.  
2. **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.  
3. **S3-compatible object storage**  
   Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not 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 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. **Deploy**  
   Run the synchronous deploy once and read the result. Re-running with no change is a no-op.  
   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. **Verify**  
   Run the pattern self-test(s) from the example and your own acceptance checks for the independent retailers workflow.  
   Command: `ample logs --kind build`

#### Cost Estimate
- **Currency:** USD
- **Monthly Amount:** 10.00
- **Basis:** Size prices from pricing.toml (loaded by the API) at build revision.  
**Components:**  
- **App server:** s-1vcpu-1gb - monthlyAmount: 5.0  
- **Managed PostgreSQL database:** s-1vcpu-1gb - monthlyAmount: 5.0  
*Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.*

#### Success Checks
1. App responds on its public URL for `ample canary next js patterns`.
2. Run the transactional-workflows self-test from the example and verify.

#### Limitations
- The independent retailers schema and workflow are an original design for this blueprint and were not executed as a separate application.
- No compliance claim is made. Only order status and public catalog data are modeled here.
- Verified on the node-22 template at s-1vcpu-1gb; other configurations may vary without verification.