Plan Production for Send Plan Product
POST/api/send-plans/:sendPlan/products/:product/production
Put a manufactured product's or kit's shortfall on the Master Production Schedule as demand, so the next MRP run plans production for it. There is one planner demand line per product and warehouse: raising it again (a newer plan, a different date) replaces the earlier one instead of adding to it. Get Send Plan Product Detail returns the suggested values in production.
send-plans:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Authentication: Bearer Personal Access Token with the send-plans:write scope. The token's user also needs permission to edit the send planner and to run MRP.
Body fields:
- warehouse_id (integer, required): one of the plan's source warehouses.
- quantity (integer, required, 1-10000000): units to produce.
- need_by (string, required, Y-m-d, today or later): when production must be ready at the warehouse.
- send_plan_line_id (integer, optional): the plan line the demand is for (ignored when it is not one of the product's lines).
Returns 201 with the schedule entry. Returns 422 when the product is not in the plan, is not manufactured or a kit, or the warehouse is not one of the plan's sources.
Request
Responses
- 201
- 401
- 403
- 404
- 422
- 429
Created
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
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.