> For the complete documentation index, see [llms.txt](https://docs.eu-pactum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eu-pactum.com/procurement-api/negotiation-statuses-api.md).

# Negotiation statuses

There are two levels of statuses in the product: Event level & negotiation (supplier) level. One negotiation event (e.g. a requisition) can include one or more negotiations. The event determines the scope of what is being negotiated (general information, which suppliers, what items, etc.) and includes one negotiation per each supplier in the event. For single supplier negotiations there is only one negotiation per negotiation event.\\

**Negotiation Event Statuses**

A negotiation event has four statuses:

* `DRAFT`
* `IN_PROGRESS`
* `CONCLUDED`
* `REJECTED`

`DRAFT`: The negotiation event has not been started yet and negotiations haven"t been created.

`IN_PROGRESS`: The negotiation event has been started and negotiations have been sent out to suppliers. Both negotiation and negotiation event parameters can no longer be modified (Unless the event is withdrawn). A negotiation event stays in `IN_PROGRESS` status until all negotiations in the event have reached a concluded state (`AGREEMENT_REACHED`, `EXPIRED`, `DECLINED`)

`CONCLUDED`: The negotiation event has been concluded and there are no active negotiations.

`REJECTED`: The negotiation event was rejected during preparation due to non-negotiable conditions (e.g., attachment classified as invoice or document already signed by buyer organization).

When a negotiation event is withdrawn, it will go back to `DRAFT` status and previous negotiations will no longer exist in the event. The `withdrawnAt` field specifies the timestamp when the latest event was withdrawn.

**Negotiation Statuses (Supplier)**

Individual negotiations with suppliers can have more detailed statuses:

* `IN_PROGRESS`
* Concluded statuses:
  * `AGREEMENT_REACHED`
  * `EXPIRED`
  * `DECLINED`

`IN_PROGRESS`: The negotiation event has been started and negotiations have been sent out to suppliers. Negotiation and event parameters can no longer be modified (Unless the event is withdrawn).

`AGREEMENT_REACHED`: The negotiation has been concluded and the supplier has finished the negotiation with an outcome. This outcome could either be that nothing changed (agreement on original terms) or there were some improvements (additional savings, changes in negotiable terms, etc.).

`EXPIRED`: The negotiation has reached its deadline without the supplier finishing the negotiation.

`DECLINED`: The negotiation could not be finished successfully based on some input. The reasons for why a negotiation can go into a "declined" status can be different and can change over time. A declined status could be triggered by the supplier (e.g. they said in the negotiation they could not provide the items being negotiated). Irrespective of the specific reason of why the negotiation was declined, it still behaves the same way and has the same status.

**Feedback Field**

In addition to the above statuses, there can be additional context about the negotiation and statuses included in the "feedback" field. This can include information about reasons for negotiation being in "declined" status, supplier comments and feedback, etc.

Reasons why a negotiation can end up being "declined":

*PS! This list is not meant to be stable or comprehensive, since these can change over time, and can vary based on configurations.*

* "Wrong terms" - input data is wrong
* "Wrong contact" - not the right contact for negotiation (if no alternate contact was provided)
* "Already delivered" - items/services have already been delivered
* "Can’t deliver" - unsuitable location or need by date (configuration dependent)

**Suite statuses and information**

In the Suite, we show an aggregation of the above information to make it easier to consume for the user through the interface. This means there can be some differences between how data is displayed in the Suite and how it is consumed through the API, but both of these interfaces still operate in a logically consistent way.

In the Suite, instead of the generic "declined" status, we display the specific declined reason instead of the status ("wrong contact", "can’t deliver", etc.), which can be found in the feedback field in the API. When the status is colour-coded red, it is treated as a "declined" status.

Another difference you can observe in the Suite is related to aggregated event statuses for competitive negotiation events where there are multiple negotiations in a single event. There, the following rule-set is being followed for the negotiation event:

* The event is "expired" if all negotiations have expired.
* The event is "declined" if all negotiations have been either declined or expired, but at least one must be declined.
* The event is "agreement reached" if there is at least one supplier that completed a negotiation.
* The event is "signed" if the winning supplier’s contract is signed (for contract negotiations).

\
\\
