Service and custom proposals
Beyond the two built-in proposal types (digital and printed), an administrator can define custom proposal types for selling services, production work, or any other revenue that does not fit the standard models. These custom types use directory-style pricing — manually entered prices for catalog items — but can sell against the same digital or printed inventory that the built-in types use.
|
What this page describes is the mechanism. The specific kinds — document types, fields, statuses — are defined for your organization; yours may differ. See the entity system. |
How custom proposal types work
Every custom proposal type has two characteristics, as described in proposals:
-
Its pricing model is always directory — prices are entered manually per item, with no automated frequency or daily-rate calculation.
-
Its inventory binding is chosen by the administrator when the proposal type is created. The binding can point to the digital inventory catalog, the printed inventory catalog, or a custom directory catalog.
When a custom type is bound to digital or printed inventory, the proposal sells against real screens or surfaces. Price lists associated with the custom type determine the available prices.
The occupancy rule
Only proposals that use the digital or printed pricing model count toward availability and saturation. Because every custom proposal type uses the directory pricing model, proposals of a custom type are never counted toward availability or saturation — regardless of which inventory they sell against.
This means:
-
A custom proposal bound to digital inventory prices against real screens and syncs to CS Play for campaign playback.
-
That same proposal does not contribute to the saturation timeline and does not trigger busy-inventory warnings when other proposals book the same display.
This behavior is correct when the custom type represents a service (installation, production, consulting) that should not consume advertising airtime. When defining a new custom proposal type, consider whether the items it sells should occupy inventory — if they should, use the built-in digital or printed type instead.
Custom fields on proposals
A proposal type is an entity type. The administrator can add custom fields (data types) to it through the entity system, the same way fields are added to any entity type.
Custom fields defined on a proposal type appear on the proposal form alongside the built-in fields. They are available for filtering, document rendering, and export.
See the entity system for how entity types and fields work.
Per-item pricing
Each item row in a custom proposal carries:
-
Cost for period — entered manually or resolved from a matching price list.
-
Discount — a percentage reduction, adjustable by the user.
-
Cost with discount — the after-discount amount.
The system does not recompute the price from the price list when the proposal is saved. The values the user edits are what get persisted.
Custom price-list surcharges (non-default price list types) apply to custom proposals the same way they apply to digital and printed proposals. Surcharges do not receive a discount.