Wholesale distributors: product catalog using Django · Ample Computer

Wholesale distributors: product catalog using Django

A product catalog blueprint for wholesale distributors built with Django on Ample. Domain schema: products (sku, name, category, case_size, list_price, active): SKU catalog with case sizes; stock_movements (sku, warehouse, delta, reason, moved_at): receipts, picks and adjustments; orders (order_no, account_reference, status, placed_at): trade orders with status transitions; order_lines (order_no, sku, cases, unit_price): order contents; events (seq, record_type, record_id, kind, at): application-owned history written in the same transaction. Public information: catalog with case sizes, minimum order and delivery terms, trade account application. Kept out of scope until handling is reviewed: account pricing tiers, credit terms, delivery addresses. Account-specific pricing and credit terms are confidential; the catalog shown publicly carries list prices only. 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

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 wholesale distributors domain. Create the tables products, stock_movements, orders, order_lines, events. Sku catalog with case sizes lives in products; keep the sensitive classes (account pricing tiers, credit terms, delivery addresses) 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.

    $ 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 wholesale distributors 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

  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 Wholesale distributors schema and workflow below build on that verified basis.

Tested examples

What it doesn’t cover