# Wholesale Distributors: Inventory Manager Using Laravel

## Summary
A inventory manager blueprint for wholesale distributors built with Laravel 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 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
- Wholesale distributors: inventory manager using Laravel
- Where can I host Wholesale distributors: Inventory manager built with Laravel?
- I need a genuinely specialized inventory manager workflow covering case-pack units, B2B catalog visibility and volume order imports.

## Resource Requirements
- **Compute**
- **Postgres**
- **S3-compatible object storage**

## 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
- A Laravel project (composer install --no-dev from composer.lock, then FrankenPHP serving public/ (php-server with the index.php fallback) reading PORT on the php-8.5 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 wholesale distributors data classes may be handled at all; this blueprint models public information only

## 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
- The technical basis (transactional workflows on Laravel) was verified with the pattern fixture; the wholesale distributors schema and workflow are an original design for this blueprint and were not executed as a separate application.
- No health, financial, privacy or other compliance claim is made. Account-specific pricing and credit terms are confidential; the catalog shown publicly carries list prices only.
- Public content and synthetic examples only until actual data-handling requirements have been reviewed.
- Verified on the php-8.5 template at s-1vcpu-1gb; region, request-duration limits and other sizes are unknown or unverified.
- Managed PostgreSQL 16 only; extensions, connection limits, and backup or restore procedures are not verified.

## Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.0
- **Basis**: Size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
- **Components**:
   - App server: s-1vcpu-1gb, quantity: 1.0, monthly amount: 5.0
   - Managed PostgreSQL database: s-1vcpu-1gb, quantity: 1.0, monthly amount: 5.0
- **Note**: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

## Evidence Summary
- **Kind**: canary_run
- **Summary**: Laravel pattern fixture deployed on Ample (composer install --no-dev from composer.lock, then FrankenPHP serving public/ (php-server with the index.php fallback) reading PORT on the php-8.5 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).
- **Observed At**: 2026-09-20T20:36:21Z
- **Implementation Revision**: 118ad1c6d7d23d4c2ce069254bab9ec9d37cd57b-dirty (CLI 118ad1c)
- **Expires At**: 2027-03-19T20:36:21Z
- **Scope**: {"checks":["/p/transactional-workflows"],"pattern":"pattern:transactional-workflows","template":"php-8.5"}
