The CRM Settings area controls the classifications, defaults, numbering rules, currencies, and reusable reference data used throughout the Fabritec CRM module.These settings determine how enquiries are created, displayed, grouped, forecasted, converted, and analysed.Changes made in CRM Settings can affect:Pipeline stages and grouping
Dashboard and analytics calculations
Commercial-line quantities
Enquiry and project numbering
Currency conversion and consolidated reporting
Because these settings are shared across the CRM module, they should be managed by authorized administrators or CRM managers.
π Where to Find CRM Settings#
The CRM Settings menu displays the configuration pages available to your organization.To manage these pages, the user normally requires the following permission:User Management β Roles β Manage CRM Settings
The General settings page controls the default values used when users create new CRM enquiries.CRM β Settings β General settingsThe page contains two main sections:CRM Defaults#
CRM defaults reduce repetitive data entry and help ensure that new enquiries begin with consistent values.The available settings are:Default Measurement Unit#
Select the unit that Fabritec should use by default when a new enquiry or commercial line is created.Other units available in the shared Fabritec unit catalog
The selected value is only the default. Users can select another available unit when entering commercial-line quantities.To update the default unit:1.
Open CRM β Settings β General settings
2.
Select the required Default Measurement Unit
Default Open Status#
Select the status automatically assigned when a new enquiry is created.Only active statuses with the Open outcome category are available for selection.To update the default status:1.
Select an active open status
The selected status becomes the starting stage for newly created enquiries unless another value is selected during entry or import.Tonnage Visibility#
The Show tonnage in CRM option controls whether derived tonnage information is displayed throughout the CRM module.When enabled, tonnage may appear in:Enquiry commercial summaries
Won-and-lost performance summaries
When disabled, Fabritec hides tonnage from CRM pages.Turning this option off only hides tonnage. Existing tonnage values continue to be calculated and retained.To change tonnage visibility:1.
Turn Show tonnage in CRM on or off
The Statuses page defines the stages and final outcomes through which an enquiry can move.CRM β Settings β StatusesThe Pipeline Kanban board
Examples of configured statuses include:Statuses Table#
The drag handle beside each status can be used to change its display order.The configured order affects how statuses appear in CRM selectors and pipeline views.Outcome Categories#
Every status must belong to one of the following outcome categories:Open#
Used for active commercial opportunities that are still progressing.Open enquiries contribute to the active pipeline and weighted forecast.Hold#
Used when an opportunity is temporarily paused but has not been closed.Hold enquiries remain visible in the pipeline and may still contribute to forecast calculations based on their assigned probability.Won#
Used when the opportunity has been awarded.A won enquiry can later be:Linked to an existing project
Converted into a new Fabritec project
Lost#
Used when the opportunity was not awarded.Users may be required to select a configured loss reason when marking an enquiry as lost.Cancelled#
Used when the opportunity is no longer proceeding and should not be treated as a commercial loss.Cancelled enquiries are excluded from standard win-rate calculations.Adding a Status#
1.
Navigate to CRM β Settings β Statuses
3.
Enter the status information
Name#
Enter the status name that users will see in the Pipeline and enquiry forms.Use clear commercial stage names such as:Color#
Select the color used to identify the status visually.The selected color may appear in:Use clearly distinguishable colors to make the pipeline easier to review.Outcome Category#
Select the commercial meaning of the status:The outcome category controls how Fabritec treats the enquiry in forecasts and analytics.Allowed Probabilities#
Select the probability percentages users can assign while the enquiry is in this status.Open and Hold statuses can use one or more configured probabilities below 100%.The probabilities must first exist on the Probabilities page.Default Probability#
Select one of the allowed probabilities as the default for the status.When an enquiry moves into this status, the default probability can be applied unless the user selects another permitted value.Exactly one default must be selected from the allowed values.Status Rules#
The following rules apply:Every status must have an outcome category.
Open and Hold statuses may use configured probabilities below 100%.
Lost and Cancelled statuses use 0%.
The default probability must be included in the statusβs allowed probabilities.
Only active Open statuses can be selected as the default open status.
Statuses already used by enquiries should be archived rather than replaced without review.
The Probabilities page defines the likelihood percentages available for CRM enquiries.CRM β Settings β ProbabilitiesProbabilities are used to calculate the weighted forecast for each enquiry.The general calculation is:Weighted Forecast = Total Amount Γ ProbabilityTotal Amount: USD 500,000
Weighted Forecast: USD 250,000
Probabilities Table#
Configured values are automatically ordered from 0% to 100%.Adding a Probability#
1.
Navigate to CRM β Settings β Probabilities
Not duplicate an existing probability
After it is created, the probability can be assigned to one or more Open or Hold statuses.Protected Probabilities#
Some probability records may display a lock instead of an archive action.A lock means the probability cannot currently be removed.Required outcome values such as 0% and 100%
Values currently assigned to statuses
Values already referenced by CRM data
Review status configurations before attempting to archive a probability.Probability Best Practices#
Use a controlled set of percentages rather than creating many similar values.A practical structure could be:10% β Initial or unqualified enquiry
25% β Qualified opportunity
50% β Quotation submitted
75% β Strong commercial position
90% β Verbal confirmation or final negotiation
The exact structure should match your companyβs sales process.
The Scopes of work page maintains reusable work classifications available across CRM and project workflows.CRM β Settings β Scopes of workScopes of work can be used on:Forecast Dashboard filters
Project records created from won enquiries
Scopes of Work Table#
Users can search, filter, export, edit, and archive scope records.Archived scopes can be restored by editing them.Adding a Scope of Work#
1.
Navigate to CRM β Settings β Scopes of work
3.
Complete the scope information
Name#
Enter a clear and unique scope name.Structural Steel Fabrication
Code#
Enter an optional internal code for the scope.Codes help maintain consistent classification, especially during enquiry imports and integrations.Scope Usage#
A scope can be assigned at two levels:Enquiry level β Represents the overall opportunity scope
Commercial-line level β Identifies the scope associated with a particular quantity, price, or cost line
Keeping scopes consistent improves filtering, reporting, and opportunity analysis.
The Industries page maintains the industry classifications available on CRM enquiries.CRM β Settings β IndustriesIndustries help classify opportunities by customer market or commercial sector.Industries Table#
Configured industries appear in:Imported enquiry validation
Adding an Industry#
Name#
Enter the name as it should appear across CRM enquiry forms and filters.Avoid creating duplicate or overlapping industry names.
The Competitors page maintains the competitor catalog used for opportunity tracking and win-and-loss analysis.CRM β Settings β CompetitorsCompetitors can be assigned to enquiries when another supplier, contractor, or fabricator is competing for the same opportunity.Configured competitor information contributes to the Competitor win/loss matrix in CRM Analytics.Competitors Table#
Adding a Competitor#
1.
Navigate to CRM β Settings β Competitors
3.
Enter the competitor details
Name#
Enter the competitorβs company or trading name.Notes#
Use this field for information such as:Internal commercial observations
Do not use the notes field for unsupported or sensitive personal information.Why Record Competitors?#
Consistent competitor tracking helps management understand:Which competitors appear most frequently
How many opportunities were won against each competitor
Which opportunities remain open
Competitor-specific win/loss performance
The Loss reasons page defines the reasons users can select when an enquiry is marked as lost.CRM β Settings β Loss reasonsLoss reasons support structured analysis instead of relying only on free-text explanations.Loss Reasons Table#
Rows can be dragged to control the order in which loss reasons appear to users.Adding a Loss Reason#
Name#
Enter a short and clear reason that users can select during the lost-enquiry workflow.Customer Budget Cancelled
Loss Reason Reporting#
The selected reason is used in CRM Analytics to group lost opportunities and lost commercial value.This helps management identify recurring causes of lost work and take corrective action.
The Units page displays the shared Fabritec unit catalog available for CRM commercial lines.CRM β Settings β UnitsCRM uses the shared Fabritec unit catalog rather than maintaining a separate CRM-only unit list.The CRM default unit is selected under:CRM β Settings β General settingsUnits Table#
Cubic Centimeter β cmΒ³
The Units page is a reference page. Unit creation and editing are not performed from the CRM Settings area.
The Numbering page manages tenant-wide automatic numbering for CRM enquiries and project job numbers.CRM β Settings β NumberingThe available sequences include:Numbering Table#
The CRM enquiry number sequence is marked as:This means automatic CRM enquiry numbering cannot be disabled.Project job numbering may be configured for automatic or manual use, depending on your organizationβs settings.Editing a Numbering Template#
1.
Find the required sequence
3.
Update the numbering configuration
Changes apply to future numbers only.Existing CRM enquiry numbers and project job numbers remain unchanged.Numbering Template Fields#
Template#
Defines the structure of the generated number.Prefix#
Defines the fixed text placed at the beginning of the number.Padding#
Defines the number of digits used for the sequence.For example, padding of 5 generates:Current Value#
Shows the last allocated sequence value.The next automatic number uses:For example, when the current value is 3, the next sequence value is 4.Administrators should change the current value only when intentionally continuing from a previous numbering range.Reset Rule#
Defines when the sequence counter starts again.The displayed configuration uses:With yearly reset, the sequence can restart when the year changes.Automatic Numbering#
When enabled, Fabritec generates the next number from the configured template.When disabled for an eligible sequence, users enter the number manually.CRM enquiry numbering is mandatory and remains automatic.Supported Numbering Tokens#
{PREFIX} β Configured prefix
{YYYY} β Four-digit year
{SEQ} β Sequence number
{SEQ:n} β Sequence with a defined number of digits
{COUNTRY} β Country name
{COUNTRY_ISO2} β Two-letter country code
{COUNTRY_ISO3} β Three-letter country code
{CUSTOMER_CODE} β Customer code
{CUSTOMER_NAME} β Customer name
{PROJECT_NAME} β Project name
Numbering Examples#
Another possible template:{PREFIX}-{COUNTRY_ISO2}-{YY}-{SEQ:4}Use only tokens for information that will be available when the number is generated.
The Currencies page manages the currencies and exchange rates shared across Fabritec features.CRM β Settings β CurrenciesCurrency configuration allows enquiries to be entered in different currencies while dashboards and analytics compare values using one base reporting currency.Exchange-rate update settings
Base Currency#
The base currency is the reporting currency used when Fabritec aggregates and compares monetary values.The displayed example uses:To change the base currency:1.
Select the required currency
Changing the base currency can affect how converted values are presented in CRM reports and dashboards.Review the change carefully before saving it.Exchange-Rate Updates#
The Exchange-rate updates section controls how Fabritec refreshes exchange rates from the configured public provider.Available settings include:Synchronization frequency
Last successful synchronization
Update Mode#
Select how exchange rates should be maintained.The displayed configuration uses:In automatic mode, Fabritec requests updated rates according to the selected synchronization frequency.Synchronization Frequency#
Defines how often automatic exchange-rate updates occur.The displayed example uses:Last Successful Synchronization#
Displays the date and time of the most recent successful rate update.Use this information to confirm that automatic synchronization is operating correctly.Synchronize Rates Now#
Click Synchronize rates now to request an immediate exchange-rate update.This can be useful before:Preparing management reports
Reviewing a large multi-currency pipeline
Closing a reporting period
Confirming recently changed market rates
After changing the update mode or frequency, click Save settings.Currency Table#
The currency table includes:The base currency has a Rate to base of 1.Adding a Currency#
1.
Navigate to CRM β Settings β Currencies
3.
Select or enter the required currency information
4.
Configure its exchange-rate behavior
Only currencies required for your commercial activity should be activated.Currency Actions#
Depending on the currency and its usage, the Actions column may allow users to:Review exchange-rate information
Archive an eligible currency
Do not archive a currency before confirming that it is no longer required by active enquiries or reporting workflows.Common Settings Page Controls#
Most CRM Settings tables include the following controls:Excel Export#
Exports the visible settings data to Excel.PDF Export#
Exports the visible settings data to PDF.Refresh#
Reloads the table and displays the latest saved information.Clear Filters#
Removes active column filters.Search#
Searches the visible records by relevant text fields.Columns#
Allows users to show or hide table columns.Reset Cache#
Reloads cached configuration data.Use this when a recently saved setting is not yet appearing in another selector or CRM page.Actions#
Depending on the page and record, available actions may include:Some protected or currently used records may display a lock instead of an archive action.
Governance Rules#
CRM Settings should follow these governance rules:Only authorized users should receive the Manage CRM Settings permission.
Status outcome categories must accurately represent the commercial result.
Won statuses must use 100% probability.
Lost and Cancelled statuses must use 0% probability.
Open and Hold status probabilities must come from the configured probability list.
The selected default probability must be allowed for the status.
Duplicate scopes, industries, competitors, and loss reasons should be avoided.
Reference records used historically should be archived rather than renamed to represent unrelated information.
Numbering changes affect future numbers and should be documented.
CRM enquiry automatic numbering is mandatory.
Base-currency changes should be approved before they are applied.
Exchange-rate synchronization should be reviewed regularly.
Hiding tonnage does not delete or stop its calculation.
β Best Practices#
Configure CRM Settings before importing historical enquiries
Use a small, clearly defined set of statuses
Align probability stages with your actual sales process
Avoid creating many similar probability percentages
Use clear scope and industry names
Add standardized internal codes where useful
Record competitors consistently for meaningful win/loss analysis
Use specific loss reasons rather than general entries such as βOtherβ
Keep the default enquiry status at the true starting stage
Use a numbering template that remains readable and unique over time
Avoid changing the current sequence value without a documented reason
Review currency synchronization before month-end reporting
Archive unused values instead of creating duplicate replacements
Use Reset Cache after configuration changes when an updated value does not immediately appear
π Related Articles#
Modified atΒ 2026-07-20 11:48:50