> For the complete documentation index, see [llms.txt](https://help.roolz.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.roolz.net/en/offers-editing-activity-and-statuses.md).

# Offers: editing, activity and statuses

### How long will the offer be active?

{% tabs %}
{% tab title="Freight offer" %}

* Freight offer is active and has "‎Published" status on the exchange until the end of the first loading time specified in the offer. For example, if the first loading is from the 13th to the 14th day of the month at 16:00, then the offer will be automatically removed from publication on the 14th at 16:00.
* When creating an offer, you can also specify your own duration of the offer publication, but upon reaching the last time of the first loading, the offer will still be removed from publication.
  {% endtab %}

{% tab title="Vehicle offer" %}
Transport offer can have:

* Specific dates or date range. For example, you specify that transport will be able to accept an offer from the city that you need only on the 17th. In this case, the offer will be automatically removed from publication on the 17th at 23:59.
* Open dates, i.e. when the period of possibility to accept the order is not limited. The time is specified as "From today" and until the moment of receiving the offer. This option is convenient when carrier has a fleet of vehicles in the specified directions to search for offers constantly.
  {% endtab %}
  {% endtabs %}

{% hint style="danger" %}
**Note!** Your transport and freight offers can be removed manually by you when your offer becomes irrelevant. Also, an offer can be automatically removed from publication when it receives many complaints or remains published for a long time although you did not log in to the system. Such mechanisms are needed to prevent offers from being on the exchange (in the "‎Published"‎ status) when they have actually lost their relevance (for example, they were forgotten)
{% endhint %}


---

# 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://help.roolz.net/en/offers-editing-activity-and-statuses.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.