Skip to content

SKU in use

HTTP 409sku_taken

When the API answers 409 sku_taken, and how to fix it.

Version v1.1, updated

The type field of every sku_taken response links to this page.

On this page

Another product of the company already has this SKU. A write refuses a SKU that a product of either kind already has.

At a glance

  • Status: 409 Conflict

  • Code: sku_taken

  • Retry: No. Fix the cause first: the same request gets the same answer.

Causes and fixes

Likely cause

How to fix it

The product exists already, created earlier or in BIRP.

Find it with GET /v1/products?sku=..., then update it, or link your external id to it.

Two products of your system share a SKU.

Give each product its own SKU in your system, then sync again.

Example

409 sku_takenJSON
{
  "code": "sku_taken",
  "detail": "Another product of the company already has this SKU.",
  "errors": [
    {
      "field": "sku",
      "message": "is used by another product of the company"
    }
  ],
  "instance": "/v1/products",
  "request_id": "a1b2c3d4-0000-4000-8000-0000000000ee",
  "status": 409,
  "title": "SKU in use",
  "type": "https://birp.io/developers/errors/sku_taken"
}

Related

  • sync-products
  • products
  • sku-ambiguous