Developers are migrating from the deprecated fulfillment.json endpoint to the new fulfillment_orders.json API to handle partial fulfillments in their ERP integrations.
Initial Challenge:
The original poster struggled to understand the correct API flow for complete and partial fulfillments, initially receiving empty responses from the fulfillment_orders endpoint.
Working Solution:
GET /orders/{order_id}/fulfillment_orders.json to retrieve fulfillment order IDs and line item IDs
POST to /fulfillments.json with a body containing:
fulfillment_order_by_line_items array
fulfillment_order_id from step 1
fulfillment_order_line_items with line item IDs and quantities
Optional tracking info and customer notification settings
Key Troubleshooting Tip:
If receiving empty arrays from the fulfillment_orders endpoint, try updating app permissions or creating a new private app.
Ongoing Issues:
Several users report receiving empty fulfillments arrays in responses despite using correct IDs and API version 2024-04, suggesting potential permission or configuration problems. The discussion remains open with users seeking additional guidance on proper implementation.
Summarized with AI on November 9.
AI used: claude-sonnet-4-5-20250929.
Iâm also facing issues in creating fulfillment for an order using REST API service, as of now my current configuration for Orders is âmark order as un-fulfilled initiallyâ. Can you please share the endpoint and process that youâre following now to achieve this as per api version 2023-01.