Independent retailers: product catalog using Laravel

Summary

A product catalog 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 includes product catalog and availability, store locations and hours, returns policy, while customer contact and payment details, supplier cost prices are kept out of scope until handling is reviewed.

Representative Queries

• Independent retailers: product catalog using Laravel
• Where can I host Independent retailers: Product catalog built with Laravel?
• I need a genuinely specialized product catalog workflow covering SKU catalog, stock movements and order statuses.

Resource Requirements

• Compute
• Postgres
• S3-compatible object storage

Infrastructure Requirements

• Compute: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle.
• Postgres: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned.
• S3-compatible object storage: Buckets are S3-compatible with issued credentials.

Prerequisites

1. A Laravel project (composer install --no-dev from composer.lock).
2. A PostgreSQL driver reading DATABASE_URL.
3. Bucket credentials from ample bucket create passed as encrypted S3_* environment variables.
4. Review of which independent retailers data classes may be handled at all.

Workflow Steps

1. Model the independent retailers domain by creating the tables products, stock_movements, orders, order_lines, events.
2. Model the SKU catalog with versioned updates.
3. Record every catalog change as an event in the same transaction.
4. Reject stale concurrent updates.
5. Deploy and verify history and conflict handling.
6. Run the synchronous deploy once and read the result.
7. Run the pattern self-test(s) and your own acceptance checks.

Examples

• Laravel pattern fixture: Verified transactional workflows basis for this blueprint.

Success Checks

1. App responds on its public URL.
2. Transactional-workflows self-test from the example.

Limitations

• The independent retailers schema and workflow are an original design.
• No compliance claim is made. Payment details belong to your payment provider.
• Verified on the php-8.5 template.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Basis: Size prices from pricing.toml.

Evidence Summary

• Laravel pattern fixture deployed on Ample; the transactional workflows checks passed.

Next Actions

• Browse the catalog index: GET /v1/catalog
• Search published recipes by intent, stack and constraints: POST /v1/catalog/search
• Read the existing agent authentication setup: GET /mcp/setup
• Browse Independent retailers: GET /v1/catalog/nodes/industry%3Aindependent-retailers