# Independent retailers: product catalog using Django

A product catalog 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. 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 Django: 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).

## What it runs on

- [Computeverified](/content/discover/primitive/compute/index.html): Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.
- [Postgresverified](/content/discover/primitive/postgres/index.html): Managed PostgreSQL 16 with pgvector runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.
- [S3-compatible object storageverified](/content/discover/primitive/s3-compatible-object-storage/index.html): Buckets speak the S3 API with SigV4 credentials Ample Computer issues; `ample bucket upload-url` returns a presigned upload URL. PutObject and GetObject are checked by canary.

## You need

- A Django project (pip install into .ample/python from requirements.txt, then waitress serving project.wsgi from run.py reading PORT on the python-3.12 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

## Exact tested configuration

```bash
install python3 -m pip install --target .ample/python -r requirements.txt
runtime python
sizes -1vcpu-1gb
start PYTHONPATH=.ample/python:${PYTHONPATH:-} python3 run.py
template python-3.12
```

## 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. **Workflow step 1.** Model the SKU catalog with versioned updates
3. **Workflow step 2.** Record every catalog change as an event in the same transaction
4. **Workflow step 3.** Reject stale concurrent updates
5. **Workflow step 4.** 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.

```bash
$ ample deploy . --name <app-name> --public --start "python3 run.py" --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 (/p/transactional-workflows) and your own acceptance checks for the independent retailers workflow.

```bash
$ ample logs <deployment_id> --kind build
```

## How it was checked

✓ App responds on its public URL · http get/ → “ample canary django patterns”  
✓ Transactional-workflows self-test from the example · http get/p/transactional-workflows → “see the pattern fixture checks”

## Evidence

1. November 6, 2026 · canary run

Django pattern fixture deployed on Ample (pip install into .ample/python from requirements.txt, then waitress serving project.wsgi from run.py reading PORT on the python-3.12 template); the transactional workflows checks passed: 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). The blueprint's Independent retailers schema and workflow below build on that verified basis.

## Tested examples

- **Django pattern fixture.** Verified transactional workflows basis for this blueprint.

## What it doesn’t cover

- 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, built on that basis.
- Payment details belong to your payment provider; only order status and public catalog data are modeled here.
- Verified on the python-3.12 template at s-1vcpu-1gb.
- Managed PostgreSQL 16 with pgvector.
- Buckets speak the standard S3 API (PutObject and GetObject with path-style addressing are checked by the fixture); `ample bucket upload-url` returns presigned upload URLs.
