Check whether a product can be deleted
AI agents: read /llms.txt; add .md to any page URL. This page as Markdown: /reference/products/v1-product-delete-check.md. Index of every page and the rules for every call: /llms.txt. Guides and concepts in one file: /llms-full.txt. OpenAPI: /openapi.json.
POST/
Checks whether a product can be safely deleted. Returns a report under product (id, deletable, blockers, warnings, and phased_out).
Deleting is blocked (blockers) when any of the following apply (for variant products, checked across all sizes and colors, including deleted ones for sales):
- The product was ever on a published sales order or quote (including removed lines and deleted orders).
- Stock is still incoming on an open purchase order line.
- A stock operation (transfer or adjustment) is pending.
- A customer currently owns stock of the product.
Non-blocking warnings (warnings) include:
- Shop stock currently exists.
- The product appears on draft sales orders or quotes.
- Active pricing rules apply to the product.
A reason about documents gives their count, their lines, and up to five examples.
Path parameters
Your team slug, shown as Team ID next to your API key in Profile.
- Example
your-team
- Example
The product's id (
idfrom List products). A hash id from an earlier answer; unique keys and document numbers (such asPO0042) don't work here.- Example
EDhVUaC6jbLbed
- Example
Request body
This operation takes no request body.
Response
200Successful response.
Child fields (1)
Child fields (5)
Fields of each item (5)
A simple product that is phased out, or a variant product with no live size or color still on sale (including one with none left at all): "phase out instead" has nothing left to do.
Errors
401The API key is missing or wrong (
unauthenticated).403You are not allowed to do this.
api_access_not_in_plan: your team's plan doesn't include API access (Pro and above, with an active subscription or trial), so every request answers this until the team upgrades. When your role lacks the permission the operation needs, the body is only{"message": "Insufficient Permission"}. Other refusals use the error envelope, withunauthorizedoruser_is_not_authorized.- When
- Your role cannot update products. This 403 has a short body,
{"message": "Insufficient Permission"}, with nosuccessorerror. - Fix
- Ask a team owner to set Manage Products to "Users CAN view, update and create products".
404Not found.
page_not_found: the team slug is unknown, you are not a member of the team, or an id in the path is not one of this team's.code: null, with a message that starts "No query results for": there is no record with that id.- When
- No live product with this id.
error.codeis null anderror.messagenames the record type. - Fix
- Check the id.
Notes
- When
deletableis false andphased_outis false, phase the product out instead.
Related
- DELETEDelete a product
/v1/ api/ store/ {team_slug}/ product/ {hash_id} - POSTPhase out a simple product
/v1/ api/ store/ {team_slug}/ product/ {hash_id}/ phase_out
