Understanding Integration Import Modes and Settings
Learn how Smartcat handles existing translations during integration import
Overview
When setting up integrations in Smartcat, you can configure how existing translations are handled during import and how the workflow processes confirm content. These settings directly impact your translation workflow efficiency and Smartwords consumption.
Key concepts and terminology
Term | Definition |
Import mode | Controls whether Smartcat uses existing translations from your source system or translates everything fresh |
Confirmation settings | Determines at which workflow stage imported translations are marked as complete |
Requirements and Limitations
Integration must be configured and connected before import settings take effect
Import mode settings apply to content with existing translations in the source system
Confirmation settings affect workflow status, not translation quality
Smartwords are consumed based on source word count, regardless of integration type
⚠️ Changing import settings after initial sync may require re-importing content to apply new rules.
How it works
Import mode options
Import modes control how Smartcat handles content that already has translations in your source system:
Option | Behavior | Use case |
Skip existing translations | Ignores any translations already present in the source system. All content is treated as new and translated from scratch. | When you want to re-translate everything or don't trust existing translations |
Import existing translations once | Brings in existing translations from the source system during the first import. Only new or changed content is translated afterward. | When you have quality existing translations you want to preserve and only translate new content |
Confirmation settings
Confirmation settings control the workflow status of imported translations:
Option | Behavior | Use case |
Don't approve | Imported translations enter the workflow as unconfirmed segments requiring review | When you want linguists to review all imported content |
Confirm at the first stage | Imported translations are confirmed at the first workflow stage (e.g., Translation) but still pass through subsequent stages (e.g., Review) | When imported translations are trusted for translation but need editing or proofreading |
Confirm at the last stage | Imported translations are confirmed at all workflow stages and are ready for export immediately | When imported translations are fully trusted and ready for export |
Smartwords consumption in integrations
Smartwords consumption in integrations follows the same rules as standard projects:
Action | SW consumed |
AI translation | 1 SW per source word |
TM match insertion | 1 SW per source word |
Human translation | 0 SW (no AI involved) |
Image translation | 1,000 SW per image (flat rate) |
Salsify:
Smartwords are consumed when product content is translated
Only selected properties are translated (you choose which)
Consumption is based on total word count of selected properties
Figma:
Smartwords are consumed for text within frames
Each text object is counted
Automatic translation mode consumes Smartwords immediately
Human review mode consumes Smartwords when translations are confirmed
Troubleshooting
Problem: Existing translations are not being imported
Solution: Verify that "Import existing translations once" is selected in your integration settings. If you changed this setting after initial sync, you may need to re-import the content.
Problem: Imported translations require review when they shouldn't
Solution: Check your confirmation settings. Select "Confirm at the last stage" if you want imported translations to bypass all review stages.
Problem: Higher than expected Smartwords consumption
Solution: Review which content types are being translated. Image translation (1,000 SW per image) and AI dubbing (10 SW per word) consume significantly more Smartwords than standard text translation.