KatanaPIM Configuration

When to disable: Only disable if you need to temporarily stop all PIM synchronization without uninstalling the module. Useful during major catalog restructuring or PIM migrations.

Connect your Magento store to your KatanaPIM instance.

Where to find your API key: In KatanaPIM, navigate to your account settings or contact your KatanaPIM administrator.

Tip: Always test credentials after entering them. A failed connection will prevent all synchronization.

Fine-tune how the extension processes data during synchronization.

Batch Size Settings

Control how many entities are processed per batch. Smaller batches use less memory but take longer; larger batches are faster but may hit memory limits.

When to adjust:

• Lower values if you experience memory errors or timeouts during sync
• Higher values if you have a powerful server and want faster imports
• Asset page sizes are typically the most memory-intensive - start conservative

Async Update Settings

When to adjust: Lower this if you see Redis connection errors or "too many connections" errors. The default is usually safe, but high-traffic stores may need to reduce it.

Reindex Data

Warning: Not recommended for production stores with large catalogs. Reindexing can cause performance issues during business hours. Instead, schedule reindex via cron during off-peak times.

When to enable: Only on development/staging environments, or small catalogs where reindex completes quickly.

Store Filter

If your KatanaPIM account has multiple stores, you can filter which store's data to import.

When to use: Multi-brand setups where different Magento instances connect to different KatanaPIM stores. Leave empty to import from all stores.

Import New Products in Websites

Important: This only affects NEW products. Existing products keep their current website assignments. Select all websites where PIM products should be visible.

Map KatanaPIM languages to your Magento store views for multi-language product data synchronization.

Finding Your KatanaPIM Language Codes

In your KatanaPIM backend, navigate to Configuration > Languages to see all available languages and their codes.

Common language code formats:

• nl-NL - Dutch (Netherlands)
• en-US - English (United States)
• fr-FR - French (France)
• de-DE - German (Germany)
• it-IT - Italian (Italy)
• es-ES - Spanish (Spain)

Mapping the Default Language

To map KatanaPIM's default language (marked with checkmark in "Is default" column), use the string default (lowercase) as the Katana Language Code.

Example mapping:

How It Works

1. When products sync, the extension checks which languages are mapped
2. For each mapped language, it pulls the translated product data from KatanaPIM
3. The data is saved to the corresponding Magento store view
4. Unmapped languages are ignored during sync

Tip: Only map languages you actually use in Magento. Mapping unused languages increases sync time without benefit.

Log locations:

• Debug log: var/log/katanapim/debug.log
• Error log: var/log/katanapim/error.log

When to enable: Only when troubleshooting issues. Debug mode logs extensive information and can grow large quickly. Disable after resolving issues.

SKU matching explained: When enabled, if a product in KatanaPIM has the same SKU as an existing Magento product, they'll be linked. Future syncs will update that Magento product instead of creating a duplicate.

When to enable SKU matching:

• Migrating from another PIM system
• Connecting KatanaPIM to an existing catalog
• Merging product data sources

When to disable: Fresh installations where all products come from KatanaPIM.

Map KatanaPIM attributes to core Magento product fields. Select which KatanaPIM attribute should populate each Magento field.

Tip: These dropdowns show all available KatanaPIM attributes. If you don't see the attribute you need, run an attribute import first from Katana PIM → Attributes.

Control how images and videos from KatanaPIM are handled.

Image hash comparison: When enabled, the extension compares file hashes before importing. This prevents re-downloading identical images and speeds up incremental syncs significantly.

When to disable hash comparison: If images in PIM are being updated but hashes aren't changing (rare), or during initial import for speed.

Set default values for newly created products. These apply only when creating products - existing products are not affected.

Recommended workflow: Import products as Disabled/Not Visible, review them in Magento, then enable in bulk after QA.

When to disable: If prices are managed in Magento (promotions, customer-specific pricing) rather than PIM. Enabling this will overwrite any Magento-side price changes.

Category matching explained: When enabled, if a KatanaPIM category has the same name as a Magento category at the same tree depth, they're linked. This preserves your existing category URLs and SEO.

Example: KatanaPIM category "Clothing > Shirts" will match Magento category "Clothing > Shirts" if both are at depth 2.

When to enable: Connecting KatanaPIM to an existing catalog with established categories.

When to disable: Fresh installations, or if you want completely separate category structures.

Auto-create settings: Control whether the automated sync can create new entities or only update existing ones.

Conservative approach: Disable auto-create initially. New products appear in the Katana PIM grid but aren't created in Magento until you manually approve them.

Hands-off approach: Enable both for fully automated catalog management. New products in PIM automatically appear in Magento.

Recommended schedule:

• Full Update: Weekly or daily (off-peak hours)
• Incremental Update: Every 1-4 hours

Full vs Incremental:

• Full sync fetches everything from PIM, ensuring Magento matches PIM exactly. Slower but catches any missed changes.
• Incremental sync only fetches items modified since the last sync. Much faster for day-to-day updates.

Tip: If products seem out of sync, run a manual full sync from the admin grid or CLI.