Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
Control fulfillment, ERP, and record creation behavior.
routing object on the request.
{
"routing": {
"sendToFulfillment": true,
"sendToErp": true,
"createInStateset": true
}
}
{
"routing": {
"sendToFulfillment": true,
"sendToErp": false,
"createInStateset": true
}
}
{
"routing": {
"sendToFulfillment": false,
"sendToErp": false,
"createInStateset": true
}
}
{
"routing": {
"fulfillmentProvider": "dcl",
"dclLocation": "LA"
}
}
| Flag | On | Off |
|---|---|---|
createInStateset | The order exists in StateSet and is visible to agents, returns and reporting | It does not — nothing downstream can reference it |
sendToFulfillment | The 3PL is told to pick and ship | Nothing ships until you dispatch it yourself |
sendToErp | The ERP receives the order for finance and inventory | Finance never sees it |
createInStateset: false with either of the others on is the combination
that goes wrong. Fulfilment and ERP dispatch reference the StateSet order, so
turning the record off while leaving dispatch on produces an order that ships
with nothing to reconcile it against — no returns path, no agent visibility,
no reporting row. If you want a record-only integration, turn the other two
off; if you want dispatch, leave the record on.