This guide covers building an Operations rate card, publishing it as an immutable version, and overriding it per customer.
Before you start
- You need the operations rate-card permission to author, publish and assign rate cards.
- A rate card is versioned: editing a published card cuts a new draft version, leaving the published one untouched.
- Money on a rate line is entered as a decimal amount, never a raw float.
Steps
- Go to Operations β Rate cards and start a new card.
- Complete the card header:
- Code β required. Uppercase letters, digits, hyphen or underscore, up to 60 characters.
- Name β required. Up to 180 characters.
- Description β optional.
- Default β optional toggle (set later once published).
- Add at least one rate line. Each line prices an activity, role or service:
- Rate type β Activity, Role or Service.
- Rate code β required. Must be unique within the card for its rate type.
- Label β required.
- Currency β a 3-letter code.
- Unit rate β required, zero or more.
- Unit and Display order β optional.
[screenshot: the rate-card editor with priced lines]
- Choose Publish to freeze the open draft version. A published version is immutable; the cardβs header points at it.
- Choose Make default on a published card so it applies where no override exists.
- Assign a customer override by picking a CRM account and the rate card to use for it, with an optional note. There is at most one assignment per account; re-assigning replaces it.
[screenshot: assigning a rate card to a customer]
Result
Published rate cards resolve the applicable rate for an activity, role or service, honouring a customer override first, then the default. Editing a published card cuts a fresh draft to publish next.
