Delete SKU Create from Shopify
POST/api/shopify/:integrationInstance/fulfillments/:salesOrderFulfillment/create-from-shopify/:shopifyFulfillment
Replace the SKU fulfillment with Shopify's: the SKU fulfillment is deleted (its stock movements are reversed) and Shopify's fulfillment is recorded in its place with the items and quantities Shopify shipped, so their stock is deducted again. Resolves mismatches where Shopify is the source of truth.
This endpoint currently requires session authentication; Personal Access Token scope support is in progress.
Authentication: Requires Bearer token.
Both fulfillments must belong to the same order of this Shopify store; any other pairing returns 403 and nothing is changed.
If none of the items Shopify's fulfillment shipped match a line of the sales order, the request returns 422 and the SKU fulfillment is kept. Link the two fulfillments or update the Shopify tracking instead.
The new fulfillment does not send the customer a shipment notification (Shopify already sent one). Shipping cost recorded on the SKU fulfillment is lost: the response then carries a warning.
A 200 with success: true can still report that Shopify's shipment could not be recorded (for example when it predates the inventory start date); the SKU fulfillment is removed in that case, so check the order's notes for what is still unshipped.
Request
Responses
- 200
- 401
- 403
- 404
- 422
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden
Response Headers
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Unprocessable Entity
Response Headers
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.