Independent retailers: inventory manager using Django · Ample Computer
Independent retailers: inventory manager using Django
An inventory manager 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
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.Postgresverified
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
Buckets speak the S3 API with SigV4 credentials Ample Computer issues;ample bucket upload-urlreturns 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 createpassed as encrypted S3_* environment variablesA review of which independent retailers data classes may be handled at all; this blueprint models public information only
Exact tested configuration
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
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.
Workflow step 1. Model SKUs and stock movements; derive stock from movements.
Workflow step 2. Apply movements transactionally with an optimistic version check on the SKU.
Workflow step 3. Record an event per movement for history.
Workflow step 4. Deploy and verify history and rejected stale updates.
Deploy. Run the synchronous deploy once and read the result. Re-running with no change is a no-op.
$ 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=...
- Verify. Run the pattern self-test(s) from the example (/p/transactional-workflows) and your own acceptance checks for the independent retailers workflow.
$ 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
- 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-urlreturns presigned upload URLs.