Direct-to-consumer brands: inventory manager using Django · Ample Computer

Direct-to-consumer brands: inventory manager using Django

An inventory manager blueprint for direct-to-consumer brands built with Django 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 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

You need

Exact tested configuration

installpython3 -m pip install --target .ample/python -r requirements.txt
runtimepython
sizes-1vcpu-1gb
startPYTHONPATH=.ample/python:${PYTHONPATH:-} python3 run.py
templatepython-3.12

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 SKUs and stock movements; derive stock from movements

  3. Workflow step 2. Apply movements transactionally with an optimistic version check on the SKU

  4. Workflow step 3. Record an event per movement for history

  5. Workflow step 4. Deploy and verify history and rejected stale updates

  6. 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=...
  1. 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.
   $ 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 Direct-to-consumer brands schema and workflow below build on that verified basis.

Tested examples

What it doesn’t cover

The technical basis (transactional workflows on Django) was verified with the pattern fixture; the direct-to-consumer brands schema and workflow are an original design for this blueprint, built on that basis.