Documentation Service Catalog Catalog Offering Form
Detailed guide

Catalog Offering Form

The offering form for defining reusable client-facing scope blocks in the catalog.

Use this form to create a clean record the first time or safely update an existing one without guessing which field drives downstream behavior.

Open demo page Back to overview
Quick summary Step by step Guardrails Troubleshooting Related workflows

Quick summary

  • Create or correct reusable offerings before estimate builders start improvising with one-off lines.

Put it into practice

  1. Start by confirming the offering does not already exist under a similar name. Reuse before creating to avoid duplicate pricing paths.

    InteractionsService Catalog > Offerings: search by name and review matching rows before opening the form.

  2. Open the offering form and set a clear, reusable identity first so estimate builders can select the correct scope block later.

    InteractionsOfferings tab: click New Offering (or edit an existing offering).

  3. Complete pricing and structure fields, including phase/group alignment, so downstream estimate lines inherit predictable behavior.

    InteractionsCatalog Offering Form: complete pricing and structure sections, including inline phase controls when needed.

  4. Save and validate by checking the offering appears with the expected attributes in the offerings table.

    InteractionsAfter save, return to Offerings list and verify the new or updated row.

  5. Confirm the offering is selectable in estimate workflow before closing the task.

    InteractionsProject Estimate workflow: open line selector and verify offering availability.
    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.

Offering identity

The offering name is what users will look for later in estimates.

Pricing and structure fields

These settings define how the offering behaves when reused.

Inline add phase controls

The inline phase controls let you add missing delivery phases without leaving the form.

Guardrails

  • Offering structure and phase data should validate before save so downstream estimates remain predictable.
  • Offering maintenance is a shared-pricing permission, not a basic project permission.

If it starts drifting

  • If the phase you need is missing, use the inline phase controls instead of abandoning the form.