Docs

Resource Variants, Price Modifiers and Unit Pricing

Split a resource type into variants such as 15 ft and 26 ft, add percent or fixed price modifiers for options, and price a flat rate per mile or per unit.

Many resource types come in versions that cost different amounts. A 26 ft box truck rents for more than a 15 ft one, a liftgate adds to the price, and a haul is billed by the mile. Rather than building a separate type for every version, you let the type's attributes drive the price. Each placed attribute has a Pricing setting with four choices: None, Variant, Modifier and Unit.

Variants

A Variant attribute splits a type into variants. A Select attribute named "Length" with the options 15 ft, 16 ft and 26 ft can give the Box Truck type one variant per length. A type can have more than one Variant attribute, and each variant is one combination of their values, such as "26 ft, White".

Variants matter in two places. Every inventory resource sits on exactly one variant, so the fleet table can tell a 15 ft truck from a 26 ft one. And each variant can carry its own rate card, so a request for a 26 ft truck prices from the 26 ft card instead of the type's default.

Only Select and Checkbox attributes can be Variant attributes. A Variant attribute is always required and active on both Procurement and Inventory, because a resource with no value for it cannot be placed on a variant and would price at the type's default.

Every type also has a hidden base variant. A type with no Variant attributes uses it for all of its inventory, and the add form shows it as Standard. A type that has Variant attributes cannot keep a resource on its base variant.

Create Variants

Set up the Variant attribute

On the type's Attributes tab, place a Select or Checkbox attribute and set its Pricing to Variant. A Select attribute needs at least two options.

Generate variants

Open the Variants tab and choose the combinations to create in Generate variants. Combinations that already exist are marked Exists.

Choose rate cards

In the variants table, pick a Rate card for each variant. Variants made with Generate variants start on the type's default card; variants made by adding a second Variant attribute start with no card.

Adding a second Variant attribute to a type that already has variants walks you through two steps: Rewrite existing variants, where each existing variant is given a value for the new attribute, and Create the new combinations. Existing variants keep their identity, so the inventory, rate cards and event copies that point at them carry over.

Removing a variant archives it. The base variant cannot be removed, and neither can a variant that inventory resources sit on or that a composite's component points at. Move those resources to another variant first from their inventory record.

Price Modifiers

A Modifier attribute adjusts the price when a request or resource has a particular value. A Checkbox named "Liftgate" can add a fixed amount, and a Select named "Finish" can add a percentage for its "Black" option.

Each modifier is set per option and has a cost side and a charge side, each Percent or Fixed, and applies either Per period or One time. Open the placement's pricing button to edit the modifiers, then choose Apply. Only Select and Checkbox attributes can be Modifier attributes, and they must be active on Procurement.

Changing a placement's Pricing away from Modifier, or removing the placement, deletes its modifiers. BackOps asks you to confirm first.

Unit Pricing

A Unit attribute is a Number that multiplies a rate. On a rate card, a Flat / per unit rate has a fixed part and a per-unit part. When the type has a Unit attribute such as "Miles", the per-unit part is multiplied by that number, so a haul can be priced as a base fee plus a rate per mile.

A type can have only one Unit attribute. It is always required and must be active on Procurement, because the number comes from the request.