### Independent retailers: inventory manager using Laravel

A inventory manager blueprint for independent retailers built with Laravel 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 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
- Independent retailers: inventory manager using Laravel  
- Where can I host Independent retailers: Inventory manager built with Laravel?  
- I need a genuinely specialized inventory manager workflow covering SKU catalog, stock movements and order statuses.

#### Resource Requirements
- primitive:compute  
- primitive:postgres  
- primitive:s3-compatible-object-storage

#### Infrastructure Requirements
1. **Compute**  
   - **Status:** verified  
   - **Summary:** 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**  
   - **Status:** verified  
   - **Summary:** 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**  
   - **Status:** verified  
   - **Summary:** Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

#### Workflow Steps
1. **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.
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.
7. **Verify**  
   - Run the pattern self-test(s) from the example (/p/transactional-workflows) and your own acceptance checks for the independent retailers workflow.

#### Success Checks
- app responds on its public URL  
    - **Kind:** http_get  
    - **Path:** /  
    - **Expect:** ample canary laravel patterns  
- transactional-workflows self-test from the example  
    - **Kind:** http_get  
    - **Path:** /p/transactional-workflows  
    - **Expect:** see the pattern fixture checks

#### Limitations
- The technical basis (transactional workflows on Laravel) was verified with the pattern fixture; the independent retailers 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. Payment details belong to your payment provider; only order status and public catalog data are modeled here.
- Verified on the php-8.5 template at s-1vcpu-1gb; region, request-duration limits and other sizes are unknown or unverified.