# Independent retailers: order tracking using Next.js

## Summary
A order tracking 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).

## Framework
Next.js

## Workload
Order tracking

## Industry
Independent retailers

## Release Status
Published

## Support Status
Verified

## Execution Status
Ready

## 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 independent retailers data classes may be handled at all; this blueprint models public information only

## Tested Configuration
- **Template**: node-22
- **Runtime**: node
- **Size**: s-1vcpu-1gb
- **Install**: npm install
- **Build**: npm run build --if-present
- **Start**: npm run start

## 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 orders** with explicit status transitions and order lines.
3. **Apply status changes** transactionally and record an event per change.
4. **Expose status history** to authorized callers only.
5. **Deploy**: Run the synchronous deploy once and read the result. Re-running with no change is a no-op.
6. **Verify**: Run the pattern self-test(s) from the example (/p/transactional-workflows) and your own acceptance checks for the independent retailers workflow.

## Examples
- **Next.js pattern fixture**: Verified transactional workflows basis for this blueprint.

## Success Checks
- App responds on its public URL.
- Transactional-workflows self-test from the example.

## Limitations
- The technical basis was verified with the pattern fixture; the independent retailers schema and workflow are an original design for this blueprint and were not executed as a separate application.
- Public content and synthetic examples only until actual data-handling requirements have been reviewed.

## Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.0
- **Basis**: size prices from pricing.toml (loaded by the API).
- **Components**:
  - App server s-1vcpu-1gb: $5.0
  - Managed PostgreSQL database s-1vcpu-1gb: $5.0

## Evidence Summary
- Next.js pattern fixture deployed on Ample; the transactional workflows checks passed.

## Next Actions
- **Browse the catalog index**: /v1/catalog (GET)
- **Search published recipes** by intent, stack, and constraints: /v1/catalog/search (POST)
- **Prepare a side-effect-free deployment plan** for an authorized project: /v1/catalog/plan (POST)