> For the complete documentation index, see [llms.txt](https://apidocs.akinon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://apidocs.akinon.com/commerce-openapis/basket/introduction/unavailable-product-scenarios.md).

# Unavailable Product Scenarios

The system automatically handles products that become unavailable after being added to the basket:

**Automatic Removal:**

* On basket retrieval (GET /basket/), unavailable products are automatically removed
* Removed products are listed in `unavailable_basket_products` response field
* Includes product details and quantity that was removed

**Unavailability Reasons:**

* Product becomes inactive (`is_active = false`)
* Product type changes to non-purchasable (product\_meta, grouped)
* Insufficient stock for requested quantity
* Product deleted from system
* Marketplace: Datasource becomes inactive or product mapping removed

**Response Handling:**

* `unavailable_basket_products` array contains removed items
* Each entry includes: `pk`, `name`, `unavailable_quantity`
* Promotional offers are recalculated without removed items
* Client should display notification about removed products


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://apidocs.akinon.com/commerce-openapis/basket/introduction/unavailable-product-scenarios.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.