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.
Overview
Qwoty enforces uniqueness on certain fields to prevent duplicate records and ensure data integrity. Understanding these constraints is essential for successful imports — especially when you want to update existing records rather than create new ones.Default unique fields
| Object | Unique fields |
|---|---|
| Master products | product_id, product_api_name |
| Products | product_id, product_api_name, inventory[sku] (when used as a deduplication key) |
| Prices | id |
| Customers | id, custom unique fields you define |
product_id, id field (depending on the object) is Qwoty’s internal identifier, auto-generated for each record. It uses UUID format (for example, c776ee49-f608-4a77-8cc8-6fe96ae1e43f).
The *_api_name fields are human-readable, stable identifiers that you control. They’re useful when migrating between environments or when you want a permanent reference that survives data resets.
Custom unique fields
For manageable objects like Customer and Contract Model, you can define additional unique fields under Settings → Data → Data model:Use cases for custom unique fields
- External IDs — store IDs from other systems (Salesforce ID, HubSpot ID, ERP customer code)
- Business identifiers — employee numbers, customer codes, internal product references
- Alternative contact info — VAT numbers, registration numbers
The field name
id is reserved for Qwoty’s internal UUID. Use a different name like external_id, legacy_id, or erp_id for identifiers from other systems.Import behavior
Creating new records
If a unique field value doesn’t exist in Qwoty, a new record is created. Leave the ID column empty in your CSV — Qwoty generates a fresh UUID automatically.Updating existing records
If a unique field value matches an existing record, that record is updated with the new data. Only the columns present in your CSV are modified — other fields stay untouched.Duplicate detection during import
During the Confirm step, Qwoty validates your file:- Duplicates within your file are flagged as validation errors
- Records with unique values that conflict with existing Qwoty records are flagged
- You can go back to the Mapping step or fix your source CSV before proceeding
Best practices
- Remove duplicates from your file before importing — sort by the unique field in your spreadsheet to spot them quickly
- Check for existing records by exporting first, comparing against your file, and choosing whether to update or create
- Use external IDs when migrating from other systems — they make round-trip imports straightforward
- Include the ID column when you want to update existing records, and leave it empty when you want to create new ones
Related
Field mapping
How fields are matched between your CSV and Qwoty.
Import relations
How to link records to their parents during import.
Data model
Add custom fields and mark them as unique.
Error handling
What validation errors mean and how to fix them.