> 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-an-inventory-package-safely.md).

# Update an Inventory package safely

Create, check, review, and publish a successor version without rewriting Inventory package history or existing reservations.

A published Inventory package can change when capacity, delivery cost, formats, markets, dates, or publisher rules change. The Podigee Audio Video Ad Server records the change as a governed successor version. It does not rewrite the package that operators used for earlier decisions.

Existing reservations keep their recorded capacity while the successor is prepared. New bookings pause until the successor is published. Complete the update promptly so planners do not work from an unresolved package state.

## Before you start

You need:

* Access to **Monetization** and permission to update inventory.
* A published Inventory package.
* Current source media and publisher authority.
* The reason for the change.
* Current analytics, reservations, and delivery evidence when the change affects capacity.
* Current cost evidence when the change affects delivery economics.
* The active Inventory publication review rule.

## 1. Open the published package

1. Go to **Monetization > Inventory**.
2. Find the published package.
3. Check its formats, markets, sales window, delivery methods, capacity, and delivery cost.
4. Select **Update package**.

Podigee opens a prefilled successor form. The update notice identifies the next draft version and explains the booking boundary.

![The successor form for version 3 of Harbor and Pine Audio Availability Review with the current show, package name, and media selection.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-559d9eb4815ee645affd90b82e84a406dee67287%2Fdoc-monetization-024-successor-boundary.jpg?alt=media)

*The successor keeps the package identity and source while separating the proposed change from its published history.*

The publisher is fixed for this successor. Create a separate package when the legal publisher or commercial authority must change.

## 2. Review the affected work

Before you change the package, check:

* Active reservations and Campaigns that use it.
* Forecasts that depend on its current capacity.
* Marketplace deals or proposals that refer to its published terms.
* Media or authority changes that caused the update.
* The effective date needed for the new commercial facts.

Existing reservations retain their recorded capacity. Do not assume that a new capacity estimate changes a prior commitment. Resolve any real conflict through the Campaign or reservation workflow.

## 3. Edit only the facts that changed

The successor form starts with the current package values. Update the necessary fields:

* Package name.
* Audio or video selection.
* Markets.
* Capacity for each selected format.
* Delivery cost, currency, and confidence.
* Sales start and end.
* Reason for the update.

Use current evidence. For example, increase capacity only when recent analytics, publishing plans, break coverage, and reservations support the increase.

![A successor package with audio capacity changed to 3,100,000, delivery cost changed to 0.46 EUR per 1,000, and confidence set to High.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-301157e374a8cd1cc2df933ee36e0e6b77a7327a%2Fdoc-monetization-024-successor-changes.jpg?alt=media)

*The successor changes the estimate without editing the prior published values.*

## 4. Prepare the successor draft

1. Enter a clear **Reason** for the change.
2. Select **Prepare inventory draft**.
3. Review the new draft card.

The draft has the same package reference and a new version. It is not bookable. The prior package history and existing reservation evidence remain available.

![Version 3 of Harbor and Pine Audio Availability Review in Draft state beside another published Inventory package.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-ba31ab239cd9d281bb2ecc59a5b90394ecfddbc5%2Fdoc-monetization-024-successor-draft.jpg?alt=media)

*A successor draft makes the pending change visible without presenting it as a published offer.*

## 5. Check and review the successor

Select **Check sellability**. Podigee checks the exact successor for current content authority, source media, supported delivery and measurement, capacity, delivery cost, markets, and dates.

When the result is **Ready for commercial approval**, complete the review required by the workspace:

* For **Solo confirmation**, select the exact-version confirmation and publish.
* For a required second person, request approval and publish only after the exact successor is approved.

If you edit the successor after review, the prior decision does not apply to the changed version. Run the check and review again.

## 6. Verify the replacement

After publication, confirm that the package card shows:

* A later package version.
* **Published**.
* The intended formats, markets, dates, and delivery methods.
* The revised capacity, delivery cost, currency, and confidence.
* **Published and ready for booking**.

![The revised Harbor and Pine audio package published as version 4 with the same package reference.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-82b90f2b0d932fb14ae293710b0b4799e4b48876%2Fdoc-monetization-024-successor-published.jpg?alt=media)

*Publication activates the successor and keeps prior version history.*

The preparation, assessment, approval, and publication steps can each create a recorded version. For this reason, the final published version number can be later than the draft number shown when the update started.

## Safe update rules

* Use **Update package**. Do not create a duplicate package for a normal revision.
* Keep the same publisher authority for a successor.
* Do not lower capacity below committed reservations without resolving the commitments.
* Do not add a format that lacks current source media, delivery, or measurement support.
* Do not extend the sales window beyond the publisher's authority.
* Do not treat a draft or readiness result as a published commercial offer.
* Do not rely on an approval after the exact package version changes.
* Confirm the published card before planners use the revised package.

## If Podigee blocks the update

* **The source changed:** Review the current audio or video version and run the check again.
* **Authority expired or was revoked:** Reestablish the authority before publication.
* **Capacity is below commitments:** Resolve the affected reservations or use a supported capacity plan.
* **A delivery method is unavailable:** Remove the format or repair the delivery setup.
* **The sales window is invalid:** Enter dates within the current authority window.
* **The review is no longer valid:** Request review for the current exact successor.
* **The draft is no longer wanted:** Do not publish it. Correct the successor before bookings resume, and use the package history to preserve the reason for the change.

## Result

The current package contains the approved commercial facts for new planning and booking. Earlier versions, decisions, and reservations remain attributable to the facts that were active when those records were created.

Next, prepare the episode ad breaks that define where this supply can carry advertising.


---

# 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-an-inventory-package-safely.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.