> 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/core-concepts/product-rendering-type.md).

# Product rendering type

Used when vendor wants to sell a physical, single-unit item at a fixed price

* [Why](#why)
* [Which context](#which-context)
* [Interfaces](#interfaces)
* [Configurations](#configurations)
* [Special rules](#special-rules)

### Why

To offer the possibility to sell a physical, single-unit item at a fixed price — purchased directly online, or via a request sent directly to the offeror through their listing.

### Which context

Product is a commoditized rendering type: the item, its price, and its conditions (delivery / hand-off) are defined precisely enough by the offeror that an asker can purchase it online without prior discussion.

Unlike Time-Based, Seat-Based, or Flat-Rate — which price a service by unit of time, by session, or as a fixed service fee — Product carries no time or session dimension at all: the transaction is the transfer of a specific physical item, not the booking of a service.

#### Interfaces

Please, find all interface documentation related to the Product rendering type, here:

**Front:**

* [Show a Listing (Product)](/v2.0/front-office/rendering-types/commoditized-rendering-types/product/show-a-listing-product.md)
* [Buy a Listing (Product)](/v2.0/front-office/rendering-types/commoditized-rendering-types/product/buy-a-listing-product.md)

**Dashboard:**

* [Create a Listing (Product)](/v2.0/front-office/rendering-types/commoditized-rendering-types/product/create-a-listing-product.md)
* [Edit a Listing (Product)](/v2.0/front-office/rendering-types/commoditized-rendering-types/product/edit-a-listing-product.md)

### Configurations

SBO > Other > Features > Platform configuration > Platform mode

### Special rules

#### Booking status

**Pending:** the initial state of a booking, once payment has been authorized (not captured) at checkout. A countdown to expiration applies.

**Paid:** the offeror has accepted the booking; payment is captured and contact information is revealed to both parties.

**Completed:** the asker has confirmed receipt of the item ("Mark as received").

**Declined :** the offeror has declined the booking; the payment captured is canceled.

**Expired : t**he offeror did not accept in time; the request has expired.

#### Listing status

**In review:** Listing is only visible by the offeror that added it. Only the admin can change the status.

**Published:** Listing is visible to all users.

**Invalidated:** Listing is only visible by the offeror that added it. Only the admin can change the status.

**Hidden:** Listing is only visible by the offeror that added it.

**Reserved:** once the associated booking reaches Paid, the listing itself switches to this status. Unlike other commoditized rendering types, a Product listing is not meant to be booked again afterward.

**Sold:** once the associated booking reaches Completed, the listing itself switches to this status.

#### Fee model

The platform charges a service fee on both sides of the transaction: a fee deducted from the offeror's payout, and a separate fee added to the amount the asker pays.

#### Payment hold

Payment is authorized at checkout but held (escrow) by the platform until the offeror accepts the booking, and only released once the asker confirms receipt.

#### Contact & address disclosure

The asker's and offeror's contact information, as well as the listing's exact address, are only revealed to the other party once the offeror has accepted the booking.


---

# 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://features.scnd.com/v2.0/core-concepts/product-rendering-type.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.