v1.6.2: Faster Repeat Migrations with True Fast Skip
Ecwid2Woo v1.6.2 makes repeat migrations substantially faster when most of the source catalog has not changed. The release adds true Fast Skip comparison windows that can inspect up to 100 categories or products at a time, while keeping the smaller, conservative limits used for real WooCommerce imports and updates.
Comparison Work and Mutation Work Are Different
Checking whether an item changed is much less expensive than loading and updating a WooCommerce object. Previous batches treated those two kinds of work too similarly, which limited throughput even when a catalog was already synchronized. v1.6.2 separates them: a comparison window can scan up to 100 source items, but the plugin still applies cautious server-aware limits as soon as it finds work that will modify WooCommerce.
Bulk-Loaded Skip Data
At the start of a comparison window, the plugin bulk-loads the source fingerprints and Ecwid-to-WooCommerce mappings it needs. An unchanged item can then bypass WooCommerce object loading and the normal import-validation path. That removes repeated database and object-model work from the most common repeat-sync case without weakening the checks used for new or changed items.
No Cooldown for an All-Skip Window
When every item in a window qualifies for Fast Skip, the next comparison can begin after 500 milliseconds. Batches that perform an import or update continue to use the cooldown detected for the current server. Large, unchanged catalogs therefore move quickly, while mutation-heavy migrations retain the pacing that protects shared hosting and low-resource servers.
Exact Continuation Offsets
Ecwid API order is preserved throughout the larger comparison windows. If only part of a window can be handled, the response points to the exact next source offset instead of advancing by an assumed batch size. Paused, interrupted, and deadline-limited migrations can resume without missing items or comparing the wrong slice of the catalog.
Hierarchy-Safe Category Skips
Fast category skips include one additional safeguard: the plugin verifies that the expected local WooCommerce parent is still correct before bypassing hierarchy reconciliation. A matching category fingerprint alone is not enough if its local parent relationship has drifted.
What Changes for Store Owners
No new setting is required. The optimization is most visible after an initial migration, when a later Full Sync needs to confirm that thousands of products and categories remain unchanged. Stores with real changes still receive the same conservative import behavior, while unchanged stretches of the catalog are compared with far less overhead.