> ## Documentation Index
> Fetch the complete documentation index at: https://docs.interchange.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Multi-package products

> A single storefront product that delivers through more than one package — distinct flight windows, each with its own budget, pacing, and delivery reporting.

<Note title="Beta">
  Multi-package products are in beta. How the packages beneath a product are
  surfaced to sellers may evolve before general availability.
</Note>

A **package** is the delivery unit a buy actually runs on: it carries its own
budget, pacing strategy, and bid price, and reports its own delivery. Most
products deliver through a single package. A **multi-package product** is a
product delivering through more than one — a single product the buyer selected
once that fans out into several packages when the buy executes.

The common case is **flight windows**: a buyer splits their campaign into dated
runs — say a pre–Black Friday flight, the Black Friday–Cyber Monday peak, and a
holiday push. On execution, your product produces one package per window, each
with its own budget slice and pacing, all delivering against the same product.

<Note>
  You don't create packages, and neither does the buyer — the system creates them
  automatically when the buy executes, one per flight window the buyer set on their
  campaign. For the full package model, see the buyer's
  [Package](/v2/buyer/campaigns/packages) reference.
</Note>

## What it means for your product

* **Independent pacing per window.** Each package paces its own budget (`even`,
  `asap`, or `front_loaded`) instead of averaging spend across the whole flight —
  a holiday-peak window can spend fast while the lead-up paces evenly.
* **Per-window delivery reporting.** Each package reports its own `impressions`,
  `spend`, and `clicks`, so delivery against your inventory is visible window by
  window, not as one blended number.

## How it delivers

When the buy executes, one package is created per flight window, and each rolls up
under the buyer's media buy:

```
Media Buy
└── Package (Pre–Black Friday)   budget · pacing · delivery
└── Package (Black Friday peak)  budget · pacing · delivery
└── Package (Holiday push)       budget · pacing · delivery
```

## Related

<CardGroup cols={2}>
  <Card title="Package (buyer)" href="/v2/buyer/campaigns/packages" icon="box">
    How packages sit under a media buy and report delivery.
  </Card>

  <Card title="Product composition" href="/v2/storefront/products/product-composition" icon="layer-group">
    Products assembled to a brief by the Merchandising Agent.
  </Card>
</CardGroup>