# Time-Based rendering type

* [Why](#id-1.14.x-basicsolution-businessrules-why)
* [Which context](#id-1.14.x-basicsolution-businessrules-whichcontext)
* [Interfaces](#id-1.14.x-basicsolution-businessrules-interfaces)
* [Configurations](#id-1.14.x-basicsolution-businessrules-configurations)
* [Workflows](#id-1.14.x-basicsolution-businessrules-workflows)
  * [Users workflows](#id-1.14.x-basicsolution-businessrules-usersworkflows)
  * [Listing status](#id-1.14.x-basicsolution-businessrules-listingstatus)
  * [Search & Bookings](#id-1.14.x-basicsolution-businessrules-search-and-bookings)
  * [Workflow and complete scenario by roles](#id-1.14.x-basicsolution-businessrules-workflowandcompletescenariobyroles)
* [Special rules](#id-1.14.x-basicsolution-businessrules-specialrules)
  * [Reviews](#id-1.14.x-basicsolution-businessrules-reviews)
    * [Reviews statuses](#id-1.14.x-basicsolution-businessrules-reviewsstatuses)
  * [Listing, Booking, and User ID (UID)](#id-1.14.x-basicsolution-businessrules-listing-booking-anduserid-uid)
  * [Invoice ID](#id-1.14.x-basicsolution-businessrules-invoiceid)
  * [Availability and unavailability (calendar)](#id-1.14.x-basicsolution-businessrules-availabilityandunavailability-calendar)
  * [Users status](#id-1.14.x-basicsolution-businessrules-usersstatus)
  * [Listing status](#id-1.14.x-basicsolution-businessrules-listingstatus.1)
  * [Booking status](#id-1.14.x-basicsolution-businessrules-bookingstatus)
  * [Free listing](#id-1.14.x-basicsolution-businessrules-freelisting)

## Why <a href="#id-1.14.x-basicsolution-businessrules-why" id="id-1.14.x-basicsolution-businessrules-why"></a>

Offerors offer their services through a listing per time unit (per hour, per day, per night) and set their general availabilities.

Askers select the start time, end time, and duration for the booking.

## Which context <a href="#id-1.14.x-basicsolution-businessrules-whichcontext" id="id-1.14.x-basicsolution-businessrules-whichcontext"></a>

The basic solution is mostly used for marketplaces offering services per time unit (e.g. rentals, freelancing, home caring services).

## Interfaces <a href="#id-1.14.x-basicsolution-businessrules-interfaces" id="id-1.14.x-basicsolution-businessrules-interfaces"></a>

Learn more about the interfaces here:

* [Super Back-Office (SBO)](/v2.0/superadmin.md)
* [Front Office](/v2.0/front-office.md)
* [User dashboard](/v2.0/dashboards.md)

## Configurations <a href="#id-1.14.x-basicsolution-businessrules-configurations" id="id-1.14.x-basicsolution-businessrules-configurations"></a>

Additionally, authorized administrators must configure the platform’s time unit, either as:

* **Daytime**: the service is booked over a full 24-hour day which starts at 00:00 day X and ends at 23:59 day X.

To configure the platform’s time unit as daytime, enter the following values:

{% code lineNumbers="true" %}

```
cocorico_time.time_unit: 1440
cocorico_time.time_unit_allday: true
cocorico_booking.allow_single_day: false
cocorico_booking.end_day_included: false
cocorico_time.days_display_mode: duration
```

{% endcode %}

* **Nightime**: the service is booked over a full 24-hour period which starts on day X and ends on day X+1 to cover a full night.

To configure the platform’s time unit as nighttime, enter the following values:

{% code lineNumbers="true" %}

```asciidoc
cocorico_time.time_unit: 1440
cocorico_time.time_unit_allday: false
cocorico_booking.allow_single_day: false
cocorico_booking.end_day_included: false
cocorico_time.days_display_mode: duration
```

{% endcode %}

## Workflows <a href="#id-1.14.x-basicsolution-businessrules-workflows" id="id-1.14.x-basicsolution-businessrules-workflows"></a>

### Users workflows <a href="#id-1.14.x-basicsolution-businessrules-usersworkflows" id="id-1.14.x-basicsolution-businessrules-usersworkflows"></a>

<figure><img src="/files/CLX06JwnRplvcU9bGzTi" alt=""><figcaption></figcaption></figure>

### Listing status <a href="#id-1.14.x-basicsolution-businessrules-listingstatus" id="id-1.14.x-basicsolution-businessrules-listingstatus"></a>

<figure><img src="/files/wxZESqT6LSIouLcGrDj8" alt=""><figcaption></figcaption></figure>

### Search & Bookings <a href="#id-1.14.x-basicsolution-businessrules-search-and-bookings" id="id-1.14.x-basicsolution-businessrules-search-and-bookings"></a>

<figure><img src="/files/zX6egqUJVrZ9MjY79qTW" alt=""><figcaption></figcaption></figure>

### Workflow and complete scenario by roles <a href="#id-1.14.x-basicsolution-businessrules-workflowandcompletescenariobyroles" id="id-1.14.x-basicsolution-businessrules-workflowandcompletescenariobyroles"></a>

<figure><img src="/files/ByUMuDOMKhlD1q4Q9KZi" alt=""><figcaption></figcaption></figure>

## Special rules <a href="#id-1.14.x-basicsolution-businessrules-specialrules" id="id-1.14.x-basicsolution-businessrules-specialrules"></a>

These special rules applied to all bundles

### Reviews <a href="#id-1.14.x-basicsolution-businessrules-reviews" id="id-1.14.x-basicsolution-businessrules-reviews"></a>

Reviews enhance our search result algorithm’s output. Better reviewed users and listings will be ranked higher in search results should the search criteria be relevant.&#x20;

#### Reviews statuses <a href="#id-1.14.x-basicsolution-businessrules-reviewsstatuses" id="id-1.14.x-basicsolution-businessrules-reviewsstatuses"></a>

* Published: Everyone can see all reviews
* Hidden: Only authorized administrators and the emitter of the review can see the review

Reviews can be managed in the SBO. Learn more through the following documentation: [Reviews management](/v2.0/superadmin/bookings/reviews-management.md)

### Listing, Booking, and User ID (UID) <a href="#id-1.14.x-basicsolution-businessrules-listing-booking-anduserid-uid" id="id-1.14.x-basicsolution-businessrules-listing-booking-anduserid-uid"></a>

The sequential numbering of Listing, Booking and User UIDs allows deducing critical and strategic information of a platform. To prevent this type of analysis on the platform, these UIDs are randomly generated to return a number between 10,000 and 2,147,483,640.

### Invoice ID <a href="#id-1.14.x-basicsolution-businessrules-invoiceid" id="id-1.14.x-basicsolution-businessrules-invoiceid"></a>

The ID invoice generating by its own rules.

For each invoice, the ID starts with YYYY/MM/DD, the end is an ID that is incremented. The incremental number doesn’t depend on the date.

### Availability and unavailability (calendar) <a href="#id-1.14.x-basicsolution-businessrules-availabilityandunavailability-calendar" id="id-1.14.x-basicsolution-businessrules-availabilityandunavailability-calendar"></a>

There are four statuses for availability on the calendar; "undetermined", "available", "unavailable" and "booked". The statuses "indeterminate" and "available" are displayed as being available to the public, which means that by default the advertiser is always available if he does not declare any unavailability. The statuses "unavailable" and "booked" are displayed as being unavailable to the public.

### Users status <a href="#id-1.14.x-basicsolution-businessrules-usersstatus" id="id-1.14.x-basicsolution-businessrules-usersstatus"></a>

* In review: Users cannot add listings, contact other users or make bookings.
* Live: Users have access to all user features.
* Invalidated: The user can no longer log in.

### Listing status <a href="#id-1.14.x-basicsolution-businessrules-listingstatus.1" id="id-1.14.x-basicsolution-businessrules-listingstatus.1"></a>

* 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.

### Booking status <a href="#id-1.14.x-basicsolution-businessrules-bookingstatus" id="id-1.14.x-basicsolution-businessrules-bookingstatus"></a>

* Draft: The asker did not complete the request.
* Pending: The booking request is awaiting a response from the offeror.
* Paid: It is when the offeror has accepted the request and the booking has been paid by the asker. A voucher is created with the Booking request number, Name and last name of the asker, Address, phone number, date, duration et listing title.
* Refused by user: The offeror has declined the booking request.
* Canceled by asker: this appears when the asker cancels a booking.
* Expired: The offeror has not responded in time and the request has expired.
* Mediation appears when a user declares litigation or when an offeror requests a cancellation.
* Payment error: this appears if the platform manages payments and payment was declined by the bank.

### Free Listing <a href="#id-1.14.x-basicsolution-businessrules-freelisting" id="id-1.14.x-basicsolution-businessrules-freelisting"></a>

Free listings are available on platforms, to do so you will have to manage some configurations.

Free listings are available for:

* [Time-Based](#id-1.14.x-basicsolution-businessrules-freelisting)
* [Flat-Rate](https://features.scnd.com/v2.0/core-concepts/pages/lWLBRAc8lML4KFYdxwZ1#id-1.14.x-servicesbundle-businessrules-freelisting)
* Seat-Based


---

# Agent Instructions: 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:

```
GET https://features.scnd.com/v2.0/core-concepts/time-based-rendering-type.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.