> For the complete documentation index, see [llms.txt](https://wiki.theshop.dev/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.theshop.dev/docs/frontstore/basic-selling-flow/product-detail/availability-and-count-info-in-products.md).

# Availability and count info in products

There are three ways of showing the product availability:

* In stock
* Available for order
* Not available

## Availability

### In stock

If a product has `count` greater than 0, it means it can be ordered directly.

### Available for order

If a product does not have `count` but has `is_available_for_order` parameter set to `true`, you can show availability info in `order_availability` (plain text). This product will always be added to the shopping cart, also if `count === 0`.

### Not available

If a product does not have `count` and also is `is_available_for_order` set to `false`, it means that this product is not available to order.

## Showing sold out products

By default, API does not return sold out products. If you want to have these products shown in the listing, add `showSoldOut=true` parameter to the request.


---

# 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://wiki.theshop.dev/docs/frontstore/basic-selling-flow/product-detail/availability-and-count-info-in-products.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.