### Independent retailers: order tracking using Django

#### Summary
A order tracking blueprint for independent retailers built with Django 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.

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

#### Resource Requirements
- **Compute**
- **Postgres**
- **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.
- **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.
- **S3-compatible object storage**: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

#### Framework
Django

#### Workload
Order tracking

#### Industry
Independent retailers

#### Execution Status
Ready

#### 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 and verify** history and conflict rejection.
6. **Verify**: Run the pattern self-test(s) from the example and your own acceptance checks for the independent retailers workflow.

#### Limitations
- The technical basis (transactional workflows on Django) 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
- **Components**:
  - App server: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: 5.0
  - Managed PostgreSQL database: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: 5.0

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

#### Evidence Summary
- **Canary run**: Django pattern fixture deployed on Ample; the transactional workflows checks passed.
- **Last Verified At**: 2026-09-20T03:31:44Z
  
#### Examples
- **Django pattern fixture**: Verified transactional workflows basis for this blueprint.

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