"Package" causes more UI confusion than any other term in the platform, because it means something specific and the word suggests several things. Here's the precise version.
What a package is
A package is inventory sold as a bundle by a media owner: one parent listing containing multiple child units, priced as a whole. Examples: a transit package spanning stations, a digital network sold as a group, a rotary bulletin program. You buy the parent; you receive the children. It is not a pricing discount construct, a seasonal grouping, or something you assemble yourself; those are plans (your working collection of units), and the plan/package distinction resolves most confusion.
Why counts look wrong (they aren't)
A plan containing one package shows one line, but that line represents many physical units; unit counts and cart counts can therefore appear inconsistent depending on whether the view counts parents or children. When a count surprises you, expand the package to its child list; the child list is always the truth of what you're buying.
Evaluating a package
Always review the child units: exact locations, formats, and how many of each. Package pricing can be excellent (bundles often price below the sum of parts) but only relative to children you actually want; a package where half the children miss your geography is not a deal. Ask whether packages can be modified; some owners flex composition, others sell fixed bundles.
Building, copying, and scaling
Plans (including their packages) can be duplicated and edited: the standard workflow for variants like the same structure across brands, or a location swap between otherwise identical proposals.
Who owns package assembly?
Either side: build plans yourself or brief your AdQuick contact; see the proposal process article.
