Quickstart
Quickstart the EntryGo export protocol
This page is the orientation layer. The step-by-step implementation guide lives in /docs/quickstart.
Use this page to understand the path. Use /docs/quickstart to implement your first export.
Quickstart Summary
Use this page for orientation. Use /docs/quickstart for implementation.
This page explains the path. /docs/quickstart is the canonical guide for install, verification, and the first export loop.
Related Technical Paths
Implementation sequence
This is the shape of the first integration loop. Run the actual commands and payloads from /docs/quickstart.
Install SDK
Install @entrygo/sdk and initialize the EntryGo client in your supply-chain application.
Add API key
Set ENTRYGO_API_KEY so your application or AI agent can access the export orchestration layer.
Sync product and order
Create one product and one order through the EntryGo primitives so the first export loop has valid inputs.
Plan export
Send the first order into export planning and receive a structured export plan with readiness and routing context.
Execute export
Execute the export workflow so EntryGo can generate artifacts, notifications, and downstream routing outcomes.
Where exports can originate
The same protocol accepts export intent from merchant systems, warehouse systems, and automation workflows.
Merchant systems
ShipBundle and other commerce clients can originate export planning from order and product signals.
Warehouse systems
3PL and warehouse-facing systems can originate export activity from fulfillment and routing workflows.
Automation workflows
Internal automations and agent-driven systems can call the same protocol directly through the export API.
What to read next
Read the protocol overview for the model, /docs/quickstart for implementation, the API reference for endpoint detail, and events for the execution record.
Merchants and 3PL warehouses are entry points to the protocol. EntryGo standardizes how both feeds enter the same export infrastructure layer before routing work to brokers, carriers, and compliance workflows.