> For the complete documentation index, see [llms.txt](https://docs.2checkout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.2checkout.com/json-rpc-api-reference/json-rpc-api-6.0/api-requests/product-sku/delete-sku-by-code.md).

# Delete SKU by code

Use the **deleteSkuByCode** method to remove SKU information using the unique identifier you assign to the SKU schema. 

When requesting to delete SKU by code, the system will verify if the specific SKU is valid for that product code or pricing configuration code. If not, the 2Checkout system will return an error. The method supports multiple combinations of product code, pricing configuration code and SKU code in one call.

## Request parameters <a href="#request-parameters" id="request-parameters"></a>

<table><thead><tr><th width="235.3333740234375">Parameters</th><th>Type / Description</th></tr></thead><tbody><tr><td><code>ProductCode</code></td><td><p><strong>Required (string)</strong></p><p>The product code that you can define for each of your offerings. Needs to be unique.</p></td></tr><tr><td><code>PricingConfigurationCode</code></td><td><p><strong>Optional (string)</strong></p><p>Unique identifier of the pricing configuration.</p></td></tr><tr><td><code>SkuCode</code></td><td><p><strong>Optional (string)</strong></p><p>Unique identifier of the SKU.</p></td></tr></tbody></table>

## Response parameters <a href="#response-parameters" id="response-parameters"></a>

<table><thead><tr><th width="124.4000244140625">Parameters</th><th>Type / Description</th></tr></thead><tbody><tr><td><a href="/pages/e18c8c2343ece4047946c0789ca6a3c364341339"><code>Product</code></a></td><td><p><strong>String</strong></p><p>Unique identifier of the product.</p></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.2checkout.com/json-rpc-api-reference/json-rpc-api-6.0/api-requests/product-sku/delete-sku-by-code.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.