noon_catalog_ParentSkuDelete
DELETE parent SKUs from the noon catalog — DESTRUCTIVE and CASCADES: the non-sellable base product and every child SKU under it are removed.
destructivenoonnoon
Use it to remove an entire product; confirm intent first — it is irreversible. noon API · CatplatService_ParentSkuDelete · POST /catplat/v1/sku/parent/delete Docs: https://noon-docs.noonpartners.dev/docs/api-reference/catalog/catplat-service-parent-sku-delete Gate: approve — interactive: show the change (noon's preview first where one exists), wait for an explicit approve; autopilot: only when the seller's own words asked for this change; otherwise ask.
Call it
In an AI client (MCP)
{
"name": "noon_catalog_ParentSkuDelete",
"arguments": {
"store": "myStore-US"
}
}From code (Tool API)
curl -X POST https://api.sellersheetai.com/api/v1/tools/noon_catalog_ParentSkuDelete \
-H "Authorization: Bearer $SELLERSHEET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"store":"myStore-US"}'Early access — the Tool API is open on request, contact us.
Arguments
| Name | Type | Description |
|---|---|---|
storerequired | string | the noon account ref `<account>-<CC>` (name-country, e.g. 'myNoon-AE') — one of get_user_context's noon store_refs, verbatim. |
items | object[] | the rows to delete (required), each with EXACTLY ONE identifier — parent_partner_sku (the parent/base SKU) or zsku_parent (noon's parent ZSKU). A row with both, or neither, is refused: noon's identifier is a oneof, although the schema below marks both required. |
Result
Every tool answers {notification, data, human_action}; data carries:
data.items[]— parent_partner_sku, zsku_parent, variants[] {partner_sku, zsku_child} removed by the cascade, status {status_code, message}.
Body (noon schema): {items: [item]}, each item
parent_partner_sku*: string
zsku_parent*: string