MasonHub ERP Integration home pagelight logo
  1. Catalog
  2. Delete SKUs
DELETE
/skus
curl --request DELETE \
     --url https://sandbox.masonhub.co/dragonfly-cosmetics-demo/api/v1/skus \
     --header 'Authorization: Bearer <token>' \
     --header 'Content-Type: application/json' \
     --data '{
  "customer_identifier": "<string>"
}'

Delete one or more SKUs from the MasonHub catalog. This endpoint marks SKUs as deleted using their customer_identifier.

Data Retention: SKU deletion removes the item from active catalog views, but does not delete historical data. When a physical unit is present, MasonHub still tracks its inventory counts and history in perpetuity. Even if all units have been shipped, consumed, or relabeled, all previous history is maintained.

​
Request Body

The request body accepts an array of objects, each containing the customer_identifier of the SKU to delete.

customer_identifier
required
string

The unique customer SKU identifier of the SKU to delete.

curl -X DELETE "https://app.masonhub.co/{account}/api/v1/skus" \
  -H "Authorization: Bearer your_jwt_token" \
  -H "Content-Type: application/json" \
  -d '[
    {
      "customer_identifier": "pants4523"
    },
    {
      "customer_identifier": "shirts450293"
    }
  ]'

{
  "records_submitted": 2,
  "records_processed": 2,
  "records_failed": 0,
  "records_succeeded": 2,
  "results": [
    {
      "customer_identifier": "pants4523",
      "status": "deleted"
    },
    {
      "customer_identifier": "shirts450293",
      "status": "deleted"
    }
  ]
}

​
Important Considerations

Deleting a SKU does not remove any inventory for that SKU. Physical units in the warehouse will continue to be tracked.

​
What Happens When You Delete a SKU

1

Catalog Removal

The SKU is removed from active catalog views and search results

2

Inventory Preserved

Any existing inventory remains tracked in the system

3

History Maintained

All order history, shipment records, and inventory transactions are preserved

4

Cannot Reorder

The SKU cannot be included in new orders until re-created

​
Moving Inventory to a New SKU

If you need to move inventory from a deleted/inactive SKU to a new SKU:

Relabeling Request

Contact the MasonHub operations team to request a relabeling operation. This will transfer physical units from the old SKU to a new SKU while maintaining proper inventory tracking.

​
Batch Deletion

Delete multiple SKUs in a single request by including multiple objects in the array:

[
  { "customer_identifier": "sku-001" },
  { "customer_identifier": "sku-002" },
  { "customer_identifier": "sku-003" }
]

The response will include the status of each individual deletion in the results array.

​
Partial Failure Handling

If some SKUs in a batch cannot be deleted (e.g., not found), the API will still attempt to delete the remaining SKUs:

{
  "records_submitted": 3,
  "records_processed": 3,
  "records_failed": 1,
  "records_succeeded": 2,
  "results": [
    {
      "customer_identifier": "sku-001",
      "status": "deleted"
    },
    {
      "customer_identifier": "sku-002",
      "status": "deleted"
    },
    {
      "customer_identifier": "sku-003",
      "status": "failed",
      "error": "SKU not found"
    }
  ]
}

​
When to Delete vs. Deactivate

Delete SKU

  • Product permanently discontinued
  • SKU was created in error
  • No future inventory expected

Keep SKU

  • Temporarily out of stock
  • Seasonal products
  • May need historical reporting

Since SKU history is preserved even after deletion, you can safely delete SKUs when they are no longer needed for active operations.