curl --request POST \
--url https://{companyName}.api.joinluminous.com/external/api/v1/sales-orders/{salesOrderId}/fulfillment-orders \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{}'{
"data": {
"fulfillment_order_id": 5001,
"fulfillment_order_ids": [
5001
],
"destination_oms_id": 123,
"destination_oms_store_id": 123,
"destination_oms_store_set": true
}
}{
"message": "<string>"
}{
"message": "Sales order not found."
}{
"message": "No open quantity remains on this sales order."
}Create a fulfillment order (no stock checks)
Create one fulfillment order for a sales order’s open quantity, without stock or
threshold checks and without warehouse splits. Contrast with
POST /sales-orders/{salesOrderId}/auto-generate-fulfillment-orders, which always runs
Smart Fulfillment (stock thresholds and warehouse splits).
- Warehouse group:
warehouse_group_iddefaults to the sales order channel’s ship-from warehouse group. The request returns 422 when neither is set. - Lines: omit
linesto fulfill every line’s open quantity (quantity - quantity_fulfilled). Sendlinesto fulfill specific lines and quantities. - Duplicates: if the sales order already has a matching fulfillment order with the same line quantities, that order is returned instead of creating a duplicate. An existing order with smaller quantities does not count as a match.
- Push: this endpoint does not push the fulfillment order. When
destination_oms_store_setistrue, you can push it withPOST /fulfillment-orders/{fulfillmentOrderId}/push.
curl --request POST \
--url https://{companyName}.api.joinluminous.com/external/api/v1/sales-orders/{salesOrderId}/fulfillment-orders \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{}'{
"data": {
"fulfillment_order_id": 5001,
"fulfillment_order_ids": [
5001
],
"destination_oms_id": 123,
"destination_oms_store_id": 123,
"destination_oms_store_set": true
}
}{
"message": "<string>"
}{
"message": "Sales order not found."
}{
"message": "No open quantity remains on this sales order."
}Authorizations
Authenticate using a bearer token. To create a token, navigate to /settings/api-tokens and click Create API Token.
Path Parameters
Sales order ID
Body
Warehouse group to fulfill from. Defaults to the sales order channel's ship-from warehouse group.
Optional initial status for the fulfillment order. Omit to use the default.
pending, planned, awaiting_shipment, shipped Lines and quantities to fulfill. Omit to fulfill the open quantity on every line.
Show child attributes
Show child attributes
Response
Fulfillment order created (or the matching existing one returned)
Show child attributes
Show child attributes