> 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/update-or-pause-marketplace-participation.md).

# Update or pause Marketplace participation

Pause, resume, or remove one Inventory package from new Marketplace bookings.

Use this task when you need to change whether one published Inventory package can receive new Marketplace bookings. You can pause demand, resume demand, or remove the package from Marketplace booking. Direct sales remain available when Marketplace demand is paused or removed.

The Podigee Audio Video Ad Server stores each change as a new dated policy. It does not rewrite the previous participation history. A scheduled change starts at the time that you set.

## Before you start

You need:

* Access to **Monetization > Marketplace** or **Monetization > Revenue jobs**.
* Permission to operate Marketplace participation for the correct workspace and package.
* A published Inventory package with Marketplace enrollment.
* The reason for the change and the time when it must start.

Check the package before you change it:

1. Open **Monetization > Marketplace**.
2. Find the package in **Sellable packages**.
3. Read its media formats, markets, sales window, delivery methods, and current Marketplace state.
4. Check for active or scheduled Marketplace deals that use the package.

![Published audio and video Inventory package with markets, delivery methods, and a preparation action.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-0f587a291c88bbd7c378d1c91f17854d8da85339%2Fdoc-monetization-021-published-inventory.jpg?alt=media)

*Use the package details as the starting point before you change Marketplace participation.*

## 1. Open the participation action

From the Marketplace page, select the package and choose **Manage participation**. You can also:

1. Go to **Monetization > Revenue jobs**.
2. Open **Marketplace transactions**.
3. Select **Manage marketplace participation**.

The action page shows the package, the current saved version, the current participation state, and the choices that will be recorded. If the page shows **Setup needed** or **No eligible item yet**, the package is not ready for this action. Create or select a published, enrolled package first.

## 2. Choose the Marketplace access

Use **Marketplace access** to choose one action:

| Action     | Result                                                                                   |
| ---------- | ---------------------------------------------------------------------------------------- |
| **Pause**  | Stops new Marketplace bookings for the selected channels. Direct sales remain available. |
| **Resume** | Allows new Marketplace bookings again when the package and current policies are valid.   |
| **Remove** | Removes the package from Marketplace booking. Direct sales remain available.             |

Pause is the normal choice for a temporary supply or policy change. Use Remove when the package must no longer be offered through Marketplace. Do not use Pause to cancel an existing deal. Review that deal in its own Campaign or Marketplace workflow and follow its change or cancellation rules.

## 3. Choose the Marketplace demand channels

In **Marketplace demand**, select the channels that the change affects:

* **Private marketplace deals** for approved private demand.
* **Open marketplace demand** for open Marketplace demand.

This is a controlled multi-select. Do not type channel names. If you pause only one channel, the other selected or permitted channel can still receive new demand when all other checks pass. Direct sales are not controlled by this selection.

![Published Inventory package and controlled Marketplace terms.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-df277358279f499f9848363f336df1b0faf3d3f0%2Fdoc-monetization-009-enrollment-terms.png?alt=media)

*Participation changes do not rewrite the package price, revenue split, or publisher rules.*

## 4. Set the start time and reason

1. Set **Change takes effect** to the time when the new state must apply.
2. Select a reason when one is available.
3. Add a short operational note in **Reason** when another operator needs context.

Use the current time for an immediate change. Use a future time when you need to finish a notice period or coordinate a package update. Keep the note factual. Include the affected package, channel, and expected next action. Do not put credentials or private buyer data in the note.

## 5. Review and apply the change

Before you select **Apply action**, confirm:

* The package name and saved version are correct.
* The access action is correct.
* The selected Marketplace channels are correct.
* The start time is correct and uses the intended time zone.
* The reason is clear enough for the next operator.
* You understand which existing deals are not changed by this action.

Select **I reviewed these details and authorize this action**, then select **Apply action**. The action is immediate when the start time is now. Do not submit the form again while the result is loading.

## 6. Check the result

The result page records:

* The package and saved version.
* The new state: **Accepting demand**, **Paused**, or **Removed**.
* The selected Marketplace channels.
* The effective time.
* The reason and the recorded operation.

Return to **Monetization > Marketplace** and confirm that the package row shows the expected state. For a future change, the page shows the scheduled state until the effective time. A paused or removed package must not receive a new Marketplace booking. Direct-sold Campaigns can continue when their own readiness and delivery checks pass.

## Change a package version safely

When the Inventory package terms, formats, markets, or delivery methods change, create and publish the replacement package version first. Then use **Update package** or the package supersession action to connect the current Marketplace enrollment to the replacement.

The replacement must be a newer, published, compatible package version. The system keeps the prior package version and its history. Existing Campaigns and deals keep their recorded package version until you change them in their own workflow. New Marketplace bookings use the replacement only after its effective time and all eligibility checks pass.

## Resume after a pause

1. Open **Manage marketplace participation** for the package.
2. Select **Resume**.
3. Select the private or open demand channels that can accept new bookings.
4. Set the effective time and record the reason.
5. Confirm the package, current enrollment, buyer rules, content rules, and delivery methods.
6. Apply the action and check the result.

If the package changed while it was paused, update or supersede the package first. If the page says that no eligible item exists, do not force the change. Complete the missing package or enrollment step and return to this action.

## Common problems

| Problem                         | What it means                                                                             | What to do                                                                                         |
| ------------------------------- | ----------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
| No eligible item                | The package is not published, enrolled, or linked to the current saved version.           | Create or publish the package, enroll it, then return to the action.                               |
| The package is already paused   | A pause policy is already active.                                                         | Check the effective time and existing policy. Create a new change only when the state must change. |
| The package needs an update     | The current package version no longer matches the Marketplace enrollment.                 | Publish a compatible replacement and use the package update action.                                |
| A new booking is rejected       | Marketplace participation is paused, removed, expired, or missing for the booking window. | Check the package state, channel, effective time, and booking dates.                               |
| An existing deal still delivers | This action changes new Marketplace eligibility, not an existing Campaign.                | Review the Campaign and its delivery controls. Do not expect participation changes to cancel it.   |
| Apply action is disabled        | The package, effective time, required confirmation, or permission is missing.             | Read the field guidance, correct the missing value, and confirm the details again.                 |

## Result

The selected Inventory package has a clear, dated Marketplace state. New Marketplace demand follows that state and the selected channels. Direct sales, existing Campaign records, package history, and financial evidence remain separate and can be managed in their own workflows.

Next, read [Create and commit a Marketplace deal](/documentation/grow-and-monetize/monetization/create-and-commit-a-marketplace-deal.md) when the package is accepting demand, or [Update an Inventory package safely](/documentation/grow-and-monetize/monetization/update-an-inventory-package-safely.md) when the package terms changed.


---

# 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/update-or-pause-marketplace-participation.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.