Quick summary
- Create missing rates centrally instead of repeatedly adding them ad hoc from estimates.
Detailed guide
Catalog Rate Form
The rate form for defining reusable pricing rates used across estimates and quotes.
Use this form to create a clean record the first time or safely update an existing one without guessing which field drives downstream behavior.
Put it into practice
-
Start by checking for an existing rate that already fits the use case. Avoid near-duplicate rate cards that fragment pricing behavior.
InteractionsService Catalog > Rates (or resource rates area): search and review current rate names and values. -
Open the rate form and set a precise rate identity that clearly communicates when it should be used.
InteractionsRates area: click New Rate or edit the intended rate row. -
Enter numeric price and applicability fields exactly, then review for decimal and classification accuracy before saving.
InteractionsCatalog Rate Form: complete rate value and applicability controls. -
Save and confirm the rate appears correctly in the catalog list with expected labels and values.
InteractionsAfter save, return to rate list and inspect the row details. -
Validate estimate impact by confirming the rate is selectable where required in planning workflow.
InteractionsProject Estimate flow: review rate selector on relevant line items.Open workflow: Estimate Workflow
What to review
Page header and breadcrumb
Confirms whether you are creating or editing, gives you the back path, and is the quickest way to avoid updating the wrong record.
Primary form sections
The form is grouped so you can complete one block at a time instead of hunting for every field in a single long screen.
Required inputs and field labels
Every required label tells you what must exist before the record can be saved; blank or invalid values should be corrected before moving on.
Validation and inline errors
Use these messages as instructions, not warnings to dismiss. They tell you exactly which field blocks save and why.
Primary save action
Commits the record only after the form validates. Use it after reviewing every section because it is the action that changes workspace data.
Cancel or return action
Leaves the form and takes you back without finishing the workflow. Use it when you opened the wrong record or need to check related data first.
Rate identity
The rate name should tell users exactly when to use it.
Price fields
These are the core pricing values the rest of the app will consume.
Applicability fields
Use applicability fields to prevent the right rate from being hard to find later.
Guardrails
- Rates must be numerically valid and complete before estimate totals can rely on them.
- Rate changes can materially affect pricing, so access is typically restricted.
If it starts drifting
- If users still cannot find the rate, confirm the naming and classification match how the estimate UI filters it.