A Customer custom field captures attributes specific to your account base — for example, a customer type, a regulatory ID, an account manager assignment, or a sales region. The field appears on every customer record, can be filtered in customer views, and most importantly, syncs to your CRM, where customer master-data typically lives. This guide walks through the full lifecycle in three steps.Documentation Index
Fetch the complete documentation index at: https://docs.qwoty.io/llms.txt
Use this file to discover all available pages before exploring further.
What you’ll build
In this example, you’ll add two custom fields used to qualify customers:| Field | Type | Purpose |
|---|---|---|
| Customer type | Text | Prospect, Key Account, Partner, Reseller |
| VAT number | Text | Legal tax ID for cross-border invoicing |
Step 1: Create the field in the Data model
Fill in General Information for Customer type
- Name:
Customer type - API Name: Qwoty generates
customer_type. Edit if you need a different identifier. - Data Type: pick
Text
Step 2: Configure the field on the customer
Like Product, Customer custom fields appear on every customer record once enabled — they’re not gated by a template.Open a customer
Find the Custom Fields section
Configure the properties
- Mandatory: check for
Customer type(segmentation should always be filled), uncheck forVAT number(only relevant for B2B / cross-border) - Editable by sale ✓ — sales reps maintain customer qualifications during onboarding
- Display for customer — leave unchecked. These are internal — the customer doesn’t need to see how you qualify them
Set values per customer
Step 3: Sync with your CRM (recommended)
Customer custom fields are the #1 use case for CRM sync. The CRM is typically the source of truth for customer master-data, and Qwoty needs the same view to make smart quoting decisions.Find the custom fields mapping section
Custom: Customer type and Custom: VAT number.Pick a sync direction
- Customer type → Bidirectional — both systems need the same segmentation, and either may be edited
- VAT number → CRM → Qwoty — typically maintained by sales-ops in the CRM; Qwoty just needs to read it
Select the matching CRM field
- HubSpot: a Single-line text or Dropdown property on the Company object
- Salesforce: a Picklist or Text field on Account
- Pipedrive: a Single-option or Free-form field on Organization
Common Customer custom fields
Beyond type and VAT, here are fields that come up often:| Field | Type | Sync direction (typical) |
|---|---|---|
| Account manager | Text (or future relation) | Bidirectional |
| Industry | Text | CRM → Qwoty |
| Annual revenue | Number | CRM → Qwoty |
| Region / Territory | Text | Bidirectional |
| NAICS / SIC code | Text | CRM → Qwoty |
| Strategic flag | Text (or future boolean) | Bidirectional |
| Last QBR date | Date | CRM → Qwoty |
Troubleshooting
The field doesn't appear on the customer detail view
The field doesn't appear on the customer detail view
The CSV import didn't populate my customer custom field
The CSV import didn't populate my customer custom field
My CRM field type is 'multi-select' but Qwoty's Text doesn't accept the comma-separated values
My CRM field type is 'multi-select' but Qwoty's Text doesn't accept the comma-separated values
Strategic, Renewal, Risk, Qwoty stores that whole string. Either parse the values in your CRM workflows before sync, or open multiple Text fields in Qwoty for each tag.Bidirectional sync sometimes overwrites changes
Bidirectional sync sometimes overwrites changes
A customer was created in the CRM but doesn't appear in Qwoty
A customer was created in the CRM but doesn't appear in Qwoty

