> For the complete documentation index, see [llms.txt](https://docs.stylemixthemes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stylemixthemes.com/motors-theme-documentation/~/changes/70wBWN8w43jv4AA52cti/classified-layout-features/pay-per-listing.md).

# Pay Per Listing

The users can also pay individually for each listing. In this way, users have the opportunity to add listings using subscription plans or only pay for each added listing separately.

{% hint style="info" %}
This feature **does not** depend on [Pricing Plans](https://support.stylemixthemes.com/manuals/motors/#pricing_plans) and can work together or separately with this system
{% endhint %}

Under the **Pay Per Listing section** you can configure the price and period for the pay per listing option:

![](https://2954064479-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MDP3ivYPbpYO9Rs_wuB%2F-MYF777SnvoPHru6Z5fQ%2F-MYFIymOO85tWoEa1zZC%2Fimage.png?alt=media\&token=79b5558e-fe6c-4228-9570-e78ebfe31522)

### Enable Pay Per Listing

First, enable the option by turning on the **Enable Pay Per Listing**. 

![](https://2954064479-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MDP3ivYPbpYO9Rs_wuB%2F-MYF777SnvoPHru6Z5fQ%2F-MYFJCwx19zV2euzqG-g%2Fimage.png?alt=media\&token=1d44ffba-ad7f-49da-acd6-a034534654d3)

### Pay Per Listing Price

Then specify the listing price on the Pay Per Listing Price field:

![](https://2954064479-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MDP3ivYPbpYO9Rs_wuB%2F-MYF777SnvoPHru6Z5fQ%2F-MYFJljK_v6EdXufePGa%2Fimage.png?alt=media\&token=7dc0f9a7-d78d-4fd1-9270-0509f44c74fd)

### Pay Per Listing Period (days)

On the Pay Per listing Period field, define the number of days after what the listing will automatically labeled as draft and will not appear on the website.

![](https://2954064479-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MDP3ivYPbpYO9Rs_wuB%2F-MYF777SnvoPHru6Z5fQ%2F-MYFKADhJaFhMzOeA27z%2Fimage.png?alt=media\&token=9b4a1a0e-79dc-47f6-bfb6-95e834192aff)

After the user completes Order, you will receive an **Order Notification** and then you need to **publish** the Listing **manually** via Dashboard.

![](https://2954064479-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MDP3ivYPbpYO9Rs_wuB%2F-MYJEOMAEFC1IwZKgpfp%2F-MYJEp9_qpT9vaCqurCM%2Fimage.png?alt=media\&token=3655eaf8-059f-40e4-8e89-462f1b3d96fb)

When User/Dealer modifies the Listing, you will receive a notification with a **revision link** (with changes on Title and Content). Then only site admin can see those changes and **approve** or **decline** modification.


---

# 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://docs.stylemixthemes.com/motors-theme-documentation/~/changes/70wBWN8w43jv4AA52cti/classified-layout-features/pay-per-listing.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.