## Direct-to-consumer brands: order tracking using Laravel

### Summary
A order tracking blueprint for direct-to-consumer brands built with Laravel 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 basis verified on Laravel: 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
- Direct-to-consumer brands: order tracking using Laravel
- Where can I host Direct-to-consumer brands: Order tracking built with Laravel?
- I need a genuinely specialized order tracking workflow covering product variants, branded media and fulfillment-state handling.

### Resource Requirements
- `primitive:compute`
- `primitive:postgres`
- `primitive:s3-compatible-object-storage`

### Infrastructure Requirements
1. **Compute**
   - Verified
   - Summary: 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**
   - Verified
   - Summary: 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**
   - Verified
   - Summary: 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 direct-to-consumer brands domain**  
   Create the tables products, stock_movements, orders, order_lines, events. Product catalog lives in products; keep the sensitive classes (customer contact and payment details, discount codes tied to individuals) out of this schema.
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. Re-running with no change is a no-op.
7. **Verify**  
   Run the pattern self-test(s) from the example (/p/transactional-workflows) and your own acceptance checks for the direct-to-consumer brands workflow.

### Limitations
- The technical basis (transactional workflows on Laravel) was verified with the pattern fixture; the direct-to-consumer brands 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. Checkout and payment are handled by your commerce provider; only catalog, stock and order status are modeled here.
- Public content and synthetic examples only until actual data-handling requirements have been reviewed.
- Verified on the php-8.5 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.
  
### Cost Estimate
**Currency**: USD
**Monthly Amount**: 10.0
- **Basis**: size prices from pricing.toml 
- **Components**:
  - app server: size: s-1vcpu-1gb, quantity: 1.0, monthlyAmount: 5.0
  - managed PostgreSQL database: size: s-1vcpu-1gb, quantity: 1.0, 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.

### Additional Information
**Last Verified At**: 2026-09-20T20:36:21Z
**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 Direct-to-consumer brands
- Browse Order tracking
- Browse Laravel
- Browse Deploy web app

### Evidence Summary
- **Canary run**: Laravel pattern fixture deployed on Ample (composer install --no-dev from composer.lock, then FrankenPHP serving public/ (php-server with the index.php fallback) reading PORT on the php-8.5 template);