Logistics operators: vendor portal using Next.js · Ample Computer

Logistics operators: vendor portal using Next.js

A vendor portal blueprint for logistics operators built with Next.js on Ample. Domain schema:

Public information: service products and transit times, lanes served, tracking entry point. Kept out of scope until handling is reviewed: consignee addresses, commercial invoices, customs documents. Customs and consignee data are sensitive; only shipment status is modeled here. Technical basis verified on Next.js: 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).

What it runs on

You need

Exact tested configuration

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.

   $ ample deploy . --name <app-name> --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...  
  1. Verify. Run the pattern self-test(s) from the example (/p/private-document-library) and your own acceptance checks for the logistics operators workflow.
   $ ample logs <deployment_id> --kind build

How it was checked

Evidence

  1. November 5, 2026 · canary run

Next.js pattern fixture deployed on Ample (next build then next start -H 0.0.0.0 -p $PORT on the node-22 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). The blueprint's Logistics operators schema and workflow below build on that verified basis.

Tested examples

What it doesn’t cover