> For the complete documentation index, see [llms.txt](https://features.scnd.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://features.scnd.com/v2.0/front-office/rendering-types/commoditized-rendering-types/product/show-a-listing-product.md).

# Show a Listing (Product)

Instructions for listing pages

### Definition

This page describes how a **Product** listing appears to buyers on the platform's front office, once it has been published by the vendor.

### Listing card (search results / homepage)

A Product listing appears as a card with:

| Element       | Description                                                        |
| ------------- | ------------------------------------------------------------------ |
| Price badge   | Displayed in the top-left corner of the thumbnail (e.g. *€16,000*) |
| Favorite icon | Heart icon, top-right corner, to save the listing                  |
| Location      | Displayed above the title (e.g. *Nice*)                            |
| Title         | Listing title                                                      |

<figure><img src="https://2306631548-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fn4EIoqjZx1xWQIo6LnjB%2Fuploads%2F7ZJFvhrmpMKU2qPrzLb3%2Fimage.png?alt=media&amp;token=90609a0a-8fc6-438a-be20-7b1f90fe2b1c" alt=""><figcaption></figcaption></figure>

### Listing page

Breadcrumb: **Homepage > \[Category] > \[Subcategory] > \[Listing title]**

The page is organized into three tabs:

| Tab             | Content                                                     |
| --------------- | ----------------------------------------------------------- |
| **Medias**      | Image / video gallery                                       |
| **Description** | Free-text description entered by the vendor                 |
| **Attributes**  | Attributes of the product                                   |
| **Location**    | Interactive map (Google Maps), with zoom and satellite view |

#### Sidebar

A fixed sidebar displays:

* The **price**, prominently shown
* A **BUY** button (only if the product is available for online purchase)
* A **Contact me** button

#### About the offerer

This block summarizes the vendor's trust indicators:

* **Member since** \[date]
* **Email verified / not verified**
* **ID verified / not verified**
* **Has completed X booking(s)**
* **I represent an individual person** (account type)

Buttons: **My profile** / **Contact me**

#### Delivery

A dedicated block indicates whether delivery is available for this item (*"Delivery available"*), reflecting the **Delivery available** setting configured by the vendor (see *Edit a Listing (Product)*, Address tab).

#### Similar Listings

A section at the bottom of the page suggests other listings, which may belong to different rendering types — for example, listings priced *"PER SERVICE"* or *"PER HOUR"* (Flat Rate / Time Based) can appear alongside Product listings.

### Related resources

* [**Create a Listing (Product)**](/v2.0/front-office/rendering-types/commoditized-rendering-types/product/create-a-listing-product.md) — initial listing deposit process
* [**Edit a Listing (Product)**](/v2.0/front-office/rendering-types/commoditized-rendering-types/product/edit-a-listing-product.md) — managing an existing listing
* [**Buy a Listing (Product)**](/v2.0/front-office/rendering-types/commoditized-rendering-types/product/buy-a-listing-product.md) — the purchase flow triggered from this page


---

# 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://features.scnd.com/v2.0/front-office/rendering-types/commoditized-rendering-types/product/show-a-listing-product.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.