> For the complete documentation index, see [llms.txt](https://docs.podigee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podigee.com/documentation/grow-and-monetize/monetization/decide-a-deal-specific-marketplace-exception.md).

# Decide a deal-specific Marketplace exception

Review and decide a bounded Marketplace exception for one exact deal version.

Use this task when a negotiated Marketplace deal does not fit the active publisher or Marketplace policy and an authorized policy approver must decide whether to allow a narrow exception. The exception applies to one exact deal version. It does not change the baseline policy or create a general rule for other buyers, brands, or packages.

The Podigee Audio Video Ad Server keeps this decision in the same exact-version review surface used for other governed changes. You do not edit the base policy from the exception review.

## Before you start

You need:

* Access to **Monetization > Approvals**.
* Permission to decide the request for the correct publisher, commercial, or Marketplace scope.
* A pending approval request created for the exact deal version.
* The negotiated exception details from the deal owner.

The request must identify the exact brand, buyer seat, category or other scope, expiry, reason, and policy version. If one of these details is missing, return the request for more information. Do not approve a broad or permanent exception.

## 1. Find the exception request

1. Go to **Monetization > Approvals**.
2. Set **State** to **Pending**.
3. Search by the deal number, buyer, brand, request message, or short reference.
4. Confirm that the item type and request purpose match the Marketplace deal.
5. Select **Open**.

![The current One Podigee Approvals page shows search, state and item type filters, and a list of review requests.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-9b06f9ffac8b268818d85c7300eb5c62c213ba72%2Fdoc-monetization-069-approval-list.png?alt=media)

*Filter the inbox before you open the request. This reduces the risk of deciding a different deal.*

If the request is approved, returned, rejected, canceled, or expired, do not decide it again. Open the current request for the current deal version.

## 2. Check the exact deal and policy

Read the review page before you choose an action.

![The current One Podigee review page shows a pending request for Northstar Coffee, the decision threshold, the item version, and the Campaign commercial approval policy.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-81a9c4c62554e0d620a7b5a0aa58cf40362931b4%2Fdoc-monetization-069-review.png?alt=media)

*Confirm the deal version, review rule, policy, and expiry before you decide.*

Check:

* **State** is Pending.
* **Item version** is the deal version named in the request.
* **Reference** and **version fingerprint** identify the exact saved version. Use the copy button when another operator needs the full value.
* **Review rule** tells you whether the workspace uses solo confirmation, optional review, or an independent reviewer.
* **Expires** is still in the future.
* **Why this review is needed** explains the requested policy exception.
* The deal details show the buyer, brand, package, media, billable unit, markets, categories, price, fee, capacity, and schedule that the exception would affect.

The exception must be narrower than the baseline policy. Check that the request names:

1. The exact buyer or buyer seat.
2. The exact brand, when the policy controls brands.
3. The exact markets, categories, or other scope.
4. The start and expiry boundary.
5. The reason and the policy version that normally blocks the deal.

Do not approve an exception that would bypass tenant isolation, seller or media rights, consent requirements, buyer credit controls, duplicate billing prevention, or evidence rules. These controls are not optional Marketplace exceptions.

## 3. Choose an outcome

Scroll to the decision controls.

![The current One Podigee review page shows actions to approve the displayed version or return or reject it with written feedback.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-6df545c3f9a001baa7751760a8063d5559ad2346%2Fdoc-monetization-069-decision-actions.png?alt=media)

*Approve only the bounded exception shown. Return or reject when the request is not safe or complete.*

Choose one action:

* Select **Approve version** when the exception is specific, time-limited, supported by the deal evidence, and safe under the policy boundaries.
* Select **Return for changes** when the deal may be safe after the requester narrows the scope, adds evidence, changes the expiry, or gives a clearer reason. Enter the exact next action in **Decision feedback**.
* Select **Reject** when the exception conflicts with a non-bypassable control, has no acceptable business or policy basis, or cannot be made safe. Enter the reason in **Decision feedback**.

When the review rule requires another person, the deal owner cannot approve the request. Ask an authorized reviewer to decide it. When the rule is **Solo confirmation**, one authorized operator can decide it without an unnecessary handoff.

## 4. Record the decision

1. Confirm that the request still shows the exact deal version you inspected.
2. Enter clear feedback when you return or reject the request.
3. Select the decision action.
4. Wait for the result page. Do not submit the same decision again while it is running.

The system binds the decision to the exact request, deal version and digest, policy version, review mode, reviewer authority, and any structured change request. A later deal version needs a new review.

![The current One Podigee review page shows an approved request with one recorded decision out of one required decision.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-771385da4d4dc63f8d2e4aee6356b7f3b01d6ddf%2Fdoc-monetization-069-approved.png?alt=media)

*An approved request records the decision against the reviewed deal version.*

For a returned request, the decision and feedback remain with the reviewed version. The deal owner can narrow the exception or add evidence, then submit a new version for review.

![The current One Podigee review page shows a returned request with one recorded decision and a confirmation that the decision was recorded.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-9e37f89a80b42c3d18730fd9c3371f8017b9b741%2Fdoc-monetization-069-returned.png?alt=media)

*A returned request keeps the next action visible without changing the baseline policy.*

## 5. Continue the deal workflow

After approval:

1. Return to **Monetization > Marketplace** or the deal workspace.
2. Confirm that the exception is shown for the exact deal version.
3. Check that the deal still matches the package, buyer qualification, price, fee, settlement, payout, targeting, and delivery rules that were not excepted.
4. Synchronize the deal with the buyer or demand platform when the deal requires it.
5. Continue Campaign readiness checks.

Approval does not upload a creative, create a break, reserve new capacity, publish a Campaign, or change the baseline policy. Complete those jobs in their own workflows.

## Common problems

| Problem                               | What it means                                                              | What to do                                                                  |
| ------------------------------------- | -------------------------------------------------------------------------- | --------------------------------------------------------------------------- |
| No pending request                    | The deal does not have an open exception review.                           | Ask the deal owner to create a request for the current exact version.       |
| Request is for another version        | The deal changed after the request was created.                            | Do not decide it. Ask for a new request with the current version.           |
| Missing scope or expiry               | The exception is too broad to decide safely.                               | Return it with the missing fields and a narrower boundary.                  |
| Review rule requires another reviewer | The current user cannot provide the required separation.                   | Ask an authorized independent reviewer to decide it.                        |
| Deal still fails after approval       | The exception did not cover the failed condition, or another check failed. | Read the failed check. Do not assume the exception bypasses other controls. |
| Request expired                       | The approval window ended before a decision was recorded.                  | Create a new request with a current deal version and expiry.                |

## Result

The exact Marketplace deal has an approved, returned, or rejected exception decision with a clear scope, expiry, reason, and policy reference. The baseline policy remains unchanged, and the deal can continue only when every non-excepted commercial, rights, delivery, and readiness check passes.

Next, read [Create and commit a Marketplace deal](/documentation/grow-and-monetize/monetization/create-and-commit-a-marketplace-deal.md) when the exception is approved and the deal can continue.


---

# 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.podigee.com/documentation/grow-and-monetize/monetization/decide-a-deal-specific-marketplace-exception.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.