Standardise options
Presets reduce “everyone does it differently”.
Resources • builder • presets • pricing
Fire door builder guide for presets, catalogues and pricing
A practical guide to using a preset catalogue to standardise installs and configurations — and how to keep pricing consistent across builder presets and quotes.
- Builder
- Presets
- Catalogue
- Pricing overrides
Click to enlarge
Guide summary
Control edits
Catalogue changes should be deliberate and owned.
Keep pricing rules clear
One rule beats mixed approaches without explanation.
Who this is for / when to use it
Use the builder when you need repeatable configurations across installers — especially before scaling quoting and remedials.
- Install teams: consistent configurations, less interpretation on site.
- Estimators: pricing rules are predictable and explainable.
- Admins: presets are owned, reviewed, and kept consistent.
What the builder is for
The builder is a standardisation tool: it reduces variation in how teams describe and price common configurations.
- Consistency: fewer one-off descriptions and mismatched parts.
- Speed: faster quoting and planning once you’ve reviewed the included presets and your catalogue rules.
- Training: new installers follow the same catalogue.
Presets strategy (featured vs additional)
Start by reviewing the presets that ship with Fire Door App, pick a small featured set, then expand once the team is consistent.
- Featured presets: your most common configurations.
- Additional presets: edge cases and specialist options.
- Review cadence: monthly/quarterly clean-up to prevent sprawl.
Preset naming standard (recommended)
- Start with type: e.g. “FD60”, “FD30” (or whatever your team uses).
- Add key options: e.g. “w/ closers”, “smoke seals”, “vision panel”.
- Avoid free-text variations: pick one spelling and stick to it (“closer”, not “door closer / closers”).
How to build a Fire Door quote (practical flow)
Use this when you need door-by-door configurable quotes that stay linked to the configuration.
- Choose a preset: start from a standard configuration where possible.
- Configure: work through the steps and keep choices consistent with your catalogue rules.
- Add to basket: drop each configured door into the quote, repeating for multiple door types.
- Review narrative: check the wording that will appear on the PDF/email.
- Fill client & project intake: make sure contact/site details are correct for outputs.
- Save quote & PDF: generate the stored quote and download link.
Pricing keys and mapping concepts
Pricing stays clean when the same key/label is used across the catalogue and quote workflow.
- Use stable keys: avoid renaming keys every month.
- Keep units clear: per door vs per item vs per hour.
- Document exceptions: client-specific uplifts or regional rules.
Checklist: keys that won’t drift
- One meaning per key: don’t overload a key to mean two different scopes.
- Explicit unit: keep “per door” vs “per leaf” vs “per set” explicit in the label.
- Versioned changes: if a key changes meaning, treat it as a new key.
Overrides (when to use them)
Overrides are useful when catalogue pricing must diverge from the baseline for a specific configuration.
Quick rule of thumb
- Use mapping when pricing is driven by inspection findings/fail reasons.
- Use overrides when a builder configuration needs a different price from the baseline.
- Avoid mixing without a documented rule.
Rollout to installers + QA
Roll out the catalogue like a process change, not “just new buttons”.
- Pilot one project: confirm presets match real site work.
- QA naming: ensure outputs use consistent labels.
- Lock edits: restrict who can change presets once live.
Common pitfalls (catalogue drift)
Catalogues drift when teams work around rules instead of improving them.
- Duplicate presets: agree a naming rule so “almost the same” options don’t multiply.
- Silent pricing changes: record changes so quotes remain explainable after the fact.
- Overusing overrides: if overrides become common, fold them into the baseline preset/mapping.
- No ownership: assign a small set of people to maintain the catalogue.
Common questions
Quick answers on presets, pricing consistency, and governance.
Can we tailor presets per client?
Many teams start with a shared baseline catalogue, then agree a rule for client-specific variations. Keep the rule documented so installers and quotes stay consistent.
How do we keep pricing consistent?
Decide whether pricing comes from mapping (fail reasons → quote items), builder overrides, or a single baseline price list — then avoid mixing approaches without a clear rule.
Who should be allowed to edit presets?
Limit edits to owners/admins. Treat presets like a catalogue: changes affect consistency across projects.
Does the builder replace inspection records?
No. The builder supports standardisation and configuration; inspection records still need door-level identity, outcomes, and photos.
Next step
Standardise one catalogue, then scale.
Set a small preset set, lock edit permissions, and keep pricing rules clear.