Primitive
Export Planning
Design cheaper shipments before execution starts.
POST /api/exports/plan turns customs-ready inputs into shipment design, cleaner customs-entry construction, routing context, and inspectable state before anything side-effecting runs.
This is the stage where teams consolidate intelligently, reduce freight waste, and make customs-entry construction cleaner before execution and broker handoff begin.
Planning is the pre-execution protocol action. It computes what is ready, what is blocked, and what execution should inherit before freight and customs-entry costs are locked in.
POST /api/exports/plan
Planning is where shipment cost gets decided
Planning exists so shipment design is explicit. This is where teams decide whether one order or many orders should become one customs entry, how freight waste can be reduced, and whether execution should inherit a clean enough structure to proceed.
Consolidate intelligently
Combine one or many orders into one cleaner shipment and customs-entry structure when that lowers freight and entry waste.
Design the shipment on purpose
Make shipment design explicit before execution inherits it, instead of letting freight structure happen by accident.
Reduce freight and entry waste
Return routing and customs-entry context execution can inherit without rebuilding shipment and entry logic later.
A deterministic read on whether execution should proceed.
The one-or-many-order structure that keeps freight waste and customs-entry cost under control.
The broker, warehouse, and entry-construction context operators should inspect before side effects.
Planning keeps execution and brokerage cleaner
A stable plan gives developers and operations teams one place to inspect readiness before anything side-effecting runs. Teams can follow that state into events and confirm how execution should behave through the exports API.
That keeps consolidation, shipment design, and customs-entry construction out of background jobs and broker cleanup while giving compliance managers and operators a cleaner pre-execution review surface.
Starter Prompt
Copy a planning prompt
Paste this into your LLM to model planning inputs, readiness rules, and response contracts.
You are helping me design an EntryGo Export Planning integration.
Goal:
- model the inputs required for POST /api/exports/plan
- define export readiness logic before execution
- structure planning responses, artifacts, and routing context
- think in EntryGo primitives instead of ad hoc workflow code
- prepare the integration for production rollout
Tasks:
1. List the minimum planning inputs and where each should come from.
2. Define readiness checks and blocking conditions before planning succeeds.
3. Propose a planning response shape with readiness, artifacts, and routing context.
4. Show how planning should hand off into execution and inspection.
5. Produce a JSON schema draft and implementation checklist for a production integration.