Events
The EntryGo event system
EntryGo uses protocol events to keep developers, warehouses, and automation systems aligned on what happened during export planning, customs artifact generation, routing, and execution.
What Are Protocol Events?
Protocol events are the inspectable record of what happened during export execution.
They give merchants, warehouses, brokers, operators, and automations a common, durable history instead of fragmented status updates across inboxes and partner tools.
Related Technical Paths
Core events
The event model gives every client surface a durable record of export workflow state. Merchants, warehouse systems, and automations can inspect the same protocol outcomes without relying on disconnected status tracking.
EXPORT_PLANNED
Recorded when the protocol produces a structured export plan from merchant or warehouse-originated signals.
EXPORT_BATCH_CREATED
Recorded when planned export work is grouped into an export batch for downstream handling.
CUSTOMS_ARTIFACT_GENERATED
Recorded when customs-oriented export artifacts are generated for review and routing.
BROKER_NOTIFIED
Recorded when broker routing and notification steps are dispatched.
WAREHOUSE_NOTIFIED
Recorded when warehouse-facing instructions or notifications are dispatched.
EXPORT_EXECUTED
Recorded when the export workflow has been executed and the protocol state has advanced.
What events enable
Operational monitoring
Teams can monitor the lifecycle without reconstructing status from inboxes, spreadsheets, or partner follow-up.
Automation workflows
Integrations and agent systems can react to export state transitions through a stable event stream.
Warehouse coordination
3PL and warehouse systems can align on the same execution signals and downstream handoff state.
Merchant visibility
Merchants get a clearer view of what has been planned, routed, executed, and shared downstream.
Example event payloads
Event payloads are designed to be readable by humans and machine clients. They provide explicit event type, export identity, origin surface, and structured workflow data.
Pair the event stream with the protocol lifecycle, the quickstart, and the API reference to understand how plan, execute, inspect, and events fit together.
EXPORT_PLANNED
{
"eventId": "evt_01HXYZPLANNED",
"type": "EXPORT_PLANNED",
"exportId": "exp_01HXYZ123",
"occurredAt": "2026-03-11T18:12:44Z",
"source": {
"client": "shipbundle_shopify",
"origin": "merchant"
},
"data": {
"orders": ["ord_1001", "ord_1002"],
"destinationCountry": "US",
"readinessState": "ready_for_execution"
}
}EXPORT_EXECUTED
{
"eventId": "evt_01HXYZEXECUTED",
"type": "EXPORT_EXECUTED",
"exportId": "exp_01HXYZ123",
"occurredAt": "2026-03-11T18:19:03Z",
"source": {
"client": "entrygo_warehouse_client",
"origin": "warehouse"
},
"data": {
"batchId": "bat_01HXYZ789",
"brokerNotificationState": "sent",
"warehouseNotificationState": "sent",
"artifacts": ["commercial_invoice", "packing_list"]
}
}