page:blueprints:logistics operators:vendor portal:next js

Logistics operators: vendor portal using Next.js

Summary

A vendor portal blueprint for logistics operators built with Next.js 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. 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).

Representative Queries

• Logistics operators: vendor portal using Next.js
• Where can I host Logistics operators: Vendor portal built with Next.js?
• 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

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.

Prerequisites

• A Next.js project (next build then next start -H 0.0.0.0 -p $PORT on the node-22 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.

   Command: ample deploy . --name --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...

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.

   Command: ample logs --kind build

Success Checks

• App responds on its public URL

  • Kind: http_get
  • Path: /
  • Expect: ample canary next js patterns

• Private-document-library self-test from the example

  • Kind: http_get
  • Path: /p/private-document-library
  • Expect: see the pattern fixture checks

Limitations

• The technical basis (private document library on Next.js) 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.
• No health, financial, privacy or other compliance claim is made. Customs and consignee data are sensitive; only shipment status is modeled here.
• Verified on the node-22 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
    • Monthly Amount: 5.0
  • managed PostgreSQL database
    • Size: 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: Next.js pattern fixture deployed on Ample with verified private document library checks passed.
• Observed At: 2026-09-21T02:34:39Z
• Implementation Revision: 1d28ae0-dirty (CLI 0.1.21)

Next Actions

• Browse the catalog index

  • Operation ID: catalog_index
  • Method: GET
  • Relative Path: /v1/catalog

• Search published recipes

  • Operation ID: search_recipes
  • Method: POST
  • Relative Path: /v1/catalog/search

• Prepare a side-effect-free deployment plan

  • Operation ID: plan_deployment
  • Method: POST
  • Relative Path: /v1/catalog/plan

• Read the existing agent authentication setup

  • Operation ID: existing_auth_setup
  • Method: GET
  • Relative Path: /mcp/setup

• Browse Logistics operators

  • Operation ID: browse_node
  • Method: GET
  • Relative Path: /v1/catalog/nodes/industry%3Alogistics-operators

• Browse Vendor portal

  • Operation ID: browse_node
  • Method: GET
  • Relative Path: /v1/catalog/nodes/workload%3Avendor-portal

• Browse Next.js

  • Operation ID: browse_node
  • Method: GET
  • Relative Path: /v1/catalog/nodes/stack%3Aframework-next-js

• Browse Deploy web app

  • Operation ID: browse_node
  • Method: GET
  • Relative Path: /v1/catalog/nodes/intent%3Adeploy-web-app