Logistics operators: vendor portal using Laravel

Summary

A vendor portal blueprint for logistics operators built with Laravel on Ample. Domain schema: service_products (sku, name, mode, transit_days, price_basis): shipping services as SKUs; capacity_movements (sku, lane, date, delta, reason): capacity as stock movements; shipments (shipment_no, lane, status, booked_at): shipments with status transitions; shipment_lines (shipment_no, sku, units): shipment contents; document_access (document_id, principal_reference, role, granted_at): who may read which document. Public information: service products and transit times, lanes served, tracking entry point. Customs and consignee data are sensitive; only shipment status is modeled here.

Representative Queries

• Logistics operators: vendor portal using Laravel
• Where can I host Logistics operators: Vendor portal built with Laravel?
• I need a genuinely specialized vendor portal workflow covering shipment state, partner access and delivery exception reporting.

Resource Requirements

• primitive:compute
• primitive:postgres
• primitive:s3-compatible-object-storage

Infrastructure Requirements

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

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 logistics operators data classes may be handled at all; this blueprint models public information only

Workflow Steps

1. Model the logistics operators domain: Create the tables service_products, capacity_movements, shipments, shipment_lines, document_access. Shipping services as SKUs lives in service_products; keep the sensitive classes (consignee addresses, commercial invoices, customs documents) out of this schema.
2. Workflow step 1: Model vendors scoped to the agency with roles.
3. Workflow step 2: Authorize document access by vendor and role (401, 403 negative tests).
4. Workflow step 3: Store vendor documents in the private bucket.
5. Workflow step 4: Deploy and verify the negative tests and an authorized download.
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/private-document-library) and your own acceptance checks for the logistics operators workflow.

Limitations

• The technical basis (private document library on Laravel) was verified with the pattern fixture; the logistics operators schema and workflow are an original design for this blueprint and were not executed as a separate application.
• Customs and consignee data are sensitive; only shipment status is modeled here.
• Verified on the php-8.5 template at s-1vcpu-1gb; region, request-duration limits and other sizes are unknown or unverified.

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, size: s-1vcpu-1gb, quantity: 1.0, monthlyAmount: 5.0
  • managed PostgreSQL database, size: s-1vcpu-1gb, quantity: 1.0, monthlyAmount: 5.0

Evidence 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 private document library checks passed: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok).

Next Actions

• Browse the catalog index
• Search published recipes by intent, stack and constraints
• Prepare a side-effect-free deployment plan for an authorized project
• Read the existing agent authentication setup
• Browse Logistics operators
• Browse Vendor portal
• Browse Laravel
• Browse Deploy web app