
FTMPUB PRODUCT IMPORT FROM CSV
FTMPUB Product Import from CSV translation compatibility with REEID Translate
FTMPUB Product Import from CSV translation compatibility is documented for 1 translatable content type from official documentation. Manual REEID verification is still pending.
AWAITING VERIFICATION
Documented translation surfaces for FTMPUB Product Import from CSV.
The listed visitor-facing values are supported by the current integration evidence. REEID manual compatibility verification is still pending.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
DOCUMENTED CONTENT
1 translatable content type are identified in the current integration evidence.
VERIFICATION STATE
Documented translation scope is kept separate from manual REEID compatibility verification.
DOCUMENTED TRANSLATION SCOPE
How documented FTMPUB Product Import from CSV content is evaluated
01 · Review documented content
Start with the content identified in the official documentation.
02 · Preserve plugin behaviour
Keep FTMPUB Product Import from CSV structure, configuration, validation, logic and runtime behaviour under plugin control.
03 · Validate multilingual output
Check each documented content surface in the actual integration before treating the workflow as manually verified.
04 · Record verified scope
Mark the integration as verified only after REEID testing confirms the documented content and plugin behaviour.
SUPPORTED CONTENT
Translation scope
product description
Product description is included in REEID translation scope for this integration.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- Bulk update WooCommerce product fields including short description, long description, and slug from CSV files.
- Preview every row before applying changes to ensure data integrity during import.
- One-click rollback functionality to restore modified products to their previous state.
- Flexible product matching options using ID, SKU, or Slug with automatic delimiter detection.
- Supports updating Yoast SEO Title and Meta Description if the plugin is active.
- Generates a post-import report detailing updated, ignored, and failed rows with specific reasons.
Dynamic content
Dynamic or runtime content behavior remains limited to what is explicitly documented in the official plugin evidence.
SEO and metadata
SEO and metadata behavior is documented only where it is explicitly established by official plugin information.
URLs and navigation
URL and navigation behavior remains outside translation scope unless explicitly represented by the integration category.
Forms and commerce
Forms and commerce behavior is limited to factual capabilities documented for this plugin.
TRANSLATION BOUNDARY
Documented content scope and verified compatibility are separate states.
Official documentation identifies this content, while FTMPUB Product Import from CSV remains responsible for plugin-specific structure, configuration and functionality.
Manual REEID verification is still pending for this integration.
LIMITATIONS & QA
Verification notes
- Translation scope is limited to the documented visitor-facing content: product description.
FREQUENTLY ASKED QUESTIONS
FTMPUB Product Import from CSV and REEID Translate FAQ.
Which FTMPUB Product Import from CSV content is documented for translation?
The Supported Content section lists the content currently identified in the official documentation.
Has REEID manually verified FTMPUB Product Import from CSV compatibility?
Not yet. This page documents the currently identified translation scope while manual REEID verification remains pending.
What happens before FTMPUB Product Import from CSV becomes verified?
REEID tests the documented content in the actual integration and confirms that plugin-controlled behaviour remains intact.
RELATED GUIDES
Explore more compatibility guides.
MULTILINGUAL WOOCOMMERCE
Review the documented FTMPUB Product Import from CSV multilingual content surfaces.
The current integration record identifies documented translatable content while manual REEID verification remains pending.
Use the Supported Content section as the documented scope until verification is completed.