Configuration: Catalog-Priced Services

The catalog-priced services archetype is for businesses that sell work at a price their catalog already states: reviews, inspections, tests, visits. A quoted unit is one service, a row in a fee table, and its price is given rather than worked out from cost. This article lists what the archetype declares, what your tenant layer adds, and where each setting is read. How the layers fit together is in How Quote Generator Is Configured.

A unit is one service, as the document or the opportunity lists it. It has no parts, no materials and no lines beneath it. A service is priced either as a lump sum or as a rate times a quantity, and the reader keeps whichever the document states. A scope paragraph describes a service already on the quote; it is never a second one. An optional service keeps its price whether or not the customer chooses it.

This archetype declares the pricing direction given, and it is the one declaration everything else follows:

• Each service’s price is carried as entered. Nothing works it out from cost.
• The quote total is the sum of the services that count: a service the customer declined still prints its price and is left out of the total.
• A service can also carry its internal cost for reporting. That cost is never part of the customer’s price.

Configuration key	What it declares	Where it is read
pricing_policy.direction	given: each service’s price is an input.	The quote total, the proposal, and which pages and steps the app draws.
line_types	None, deliberately. A service has no lines to classify.	There is no Line types page on this shape.
product_families	One family, Service. Every service is priced the same way, so kinds of service are catalog categories instead.	Every quoted service belongs to it.
quote_sections	One section, Services, with no labor placement.	The proposal, where each service prints as a row.
specifications	Three fields on every service: Expenses, a footnote marker of Expenses Included or Plus Expenses; Scope Paragraph, the service’s scope wording; and Row Note, a line printed under the row.	The proposal’s fee table, and each service on the quote.
formula_slots	Per service: the given price, quantity mode, unit and extended price, and the billed price. Per quote: the services with an unknown quantity, and the service quote total.	The quote’s totals. Pricing → Formulas shows them.
prompt_blocks	A unit is a service; one row per service as the document lists it; the header to read, including the project site; and that nothing here is a line item.	The document reader. Operations → Prompt Management shows them.
training	The in-app walk for setting up a family skips the presets step.	The training walk in the app.

• The catalog of services and their prices, which arrives through an integration. Catalog counts them as Products.
• catalog_categories: the kinds of service you sell.
• margin_tiers: on this shape a 0% tier is what lets a given price pass through untouched.
• The fee menu, under Pricing → Fee standards.
• labor_departments and their rates, where a fee standard allocates hours to roles.
• The rest of the pricing policy: recurrence if you sell subscriptions, and the contingency, margin and delivery_aro switches. A tenant layer that declares a pricing policy replaces the archetype’s whole, so it restates direction: given.

Because prices are given, several pages describe machinery this shape cannot have, and they are not drawn:

• Line types, Manufacturers and Manufacturer tiers.
• Presets, Preset mining and Kits.
• Allowances and Generic costs.
• The approved-manufacturer sections of a customer’s record.

Some appear only on this shape:

• Fee standards, Product Configuration and Product groups.
• Products per opportunity seed, among the model knobs.

Families, specifications and formulas that come only from the archetype are shown read-only, each with a note that it comes from the archetype. On a quote, the steps are the quote’s settings, its lines, the proposal and sending; there is no document-reading or vendor-pricing step.

A service is missing what its price needs: a quantity on a rate-times-quantity service, a price basis in the catalog, or a price at all. The quote names the services. See Quantity or Lump Sum.

The tenant layer declared a pricing policy without direction: given, which replaces the archetype’s whole. Contact support; the direction is restated in your tenant layer.

• How Quote Generator Is Configured
• Quantity or Lump Sum
• Product Families and Their Names
• Optional Units and Lines
• Quote Generator Help