page:blueprints:wholesale distributors:inventory manager:laravel

Wholesale Distributors: Inventory Manager Using Laravel

Summary

A inventory manager blueprint for wholesale distributors built with Laravel on Ample. Domain schema:

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 Laravel: 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).

Representative Queries

Resource Requirements

Infrastructure Requirements

  1. Compute: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
  2. 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.
  3. S3-compatible object storage: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary.

Prerequisites

Workflow 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. Model SKUs and stock movements: Derive stock from movements.
  3. Apply movements transactionally: With an optimistic version check on the SKU.
  4. Record an event: Per movement for history.
  5. Deploy: Run the synchronous deploy once and read the result. Re-running with no change is a no-op. Command: ample deploy . --name --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...
  6. Verify: Run the pattern self-test(s) from the example (/p/transactional-workflows) and your own acceptance checks for the wholesale distributors workflow. Command: ample logs --kind build

Limitations

Cost Estimate

Evidence Summary