# Direct-to-consumer brands: order tracking using Next.js

## Summary
A order tracking blueprint for direct-to-consumer brands built with Next.js on Ample. Domain schema: products (sku, name, collection, price, active): product catalog; stock_movements (sku, warehouse, delta, reason, moved_at): fulfillment stock; orders (order_no, channel, 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 collections, shipping and returns policy, brand story. Kept out of scope until handling is reviewed: customer contact and payment details, discount codes tied to individuals. Checkout and payment are handled by your commerce provider; only catalog, stock and order status are modeled here.

## Technical Specifications
### 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.
- **Postgres**: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database.
- **S3-compatible object storage**: Buckets are S3-compatible with issued credentials.

### Framework
**Next.js**

### Workload
**Order tracking**

### Industry
**Direct-to-consumer brands**

### Release Status
**Published**

### Support Status
**Verified**

### Execution Status
**Ready**

## Workflow Steps
1. **Model the direct-to-consumer brands domain**: Create the tables products, stock_movements, orders, order_lines, events.
2. **Workflow step 1**: Model orders with explicit status transitions and order lines.
3. **Workflow step 2**: Apply status changes transactionally and record an event per change.
4. **Workflow step 3**: Expose status history to authorized callers only.
5. **Workflow step 4**: Deploy and verify history and conflict rejection.
6. **Deploy**: Run the synchronous deploy once and read the result.
7. **Verify**: Run the pattern self-test(s) from the example and your own acceptance checks.

## 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 direct-to-consumer brands schema and workflow were not executed as a separate application.
- No health, financial, privacy or other compliance claim is made.

## Cost Estimate
- **Monthly Amount**: $10.00 
  - **App server**: 1 x size s-1vcpu-1gb = $5.00
  - **Managed PostgreSQL database**: 1 x size s-1vcpu-1gb = $5.00  
*Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.*

## Next Actions
- **Browse the catalog index**: GET /v1/catalog
- **Search published recipes**: POST /v1/catalog/search
- **Prepare a side-effect-free deployment plan**: POST /v1/catalog/plan
- **Read the existing agent authentication setup**: GET /mcp/setup