SKREP WooCommerce Importer Guide

What does SKREP WooCommerce Importer do?

SKREP WooCommerce Importer turns SKREP extension exports into WooCommerce products without manual copy-paste. It supports product data from Shopee, Tokopedia, and Lazada, including simple or variable products, pricing, stock, SKU, attributes, images, and supported media.

Prepare WordPress before importing

Plugin 0.3.5 declares these minimum requirements:

• WordPress 7.1+ and PHP 7.4+.
• WooCommerce 11.1.1+ as a required dependency.
• YITH WooCommerce Featured Video 1.57.0–1.58.0 as the verified required dependency for supported featured-video binding.
• YITH WooCommerce Product Add-ons & Extra Options 4.33.0+ is optional.
• Variation Swatches for WooCommerce is optional/recommended.

Open SKREP Importer → Welcome and select Check Environment. When your WordPress account can install/activate plugins, SKREP can help install or activate missing required dependencies.

Install and activate the importer

1. Open WordPress Admin → Plugins → Add New Plugin → Upload Plugin.
2. Select SKREP-WooCommerce.zip.
3. Choose Install Now, then Activate Plugin.
4. Open SKREP Importer in the WordPress sidebar.
5. Connect your SKREP account with Continue with Google. The importer stays locked without an active login.
6. After sign-in succeeds, run Check Environment until all required dependencies are ready.

Use a SKREP export that matches the source contract

Open the SKREP extension for the source marketplace, capture products, inspect the result, then export a supported JSON or CSV file. The importer detects source and format automatically.

• Files can come from Shopee, Tokopedia, or Lazada.
• Do not remove SKREP provenance columns, metadata, or payloads before import.
• Woo-style CSV that relies on provenance sidecar data must include Meta: skrep_source_payload. Legacy CSV without the sidecar is blocked with CSV_SIDECAR_REQUIRED so stock, SKU, and media are not guessed.
• If the structure does not match a known SKREP contract, the analyzer stops with SOURCE_SCHEMA_UNKNOWN.

Analyze the file before writing products

1. Open SKREP Importer → Import Products.
2. Drop the file into the upload area or choose it from your computer.
3. Wait for Analyzing file….
4. Review Import Preview / Summary: source marketplace, product, variation, media, and video counts plus data warnings.
5. Review non-blocking warnings before continuing. Blocking contract or dependency errors must be resolved first.
6. When the preview is correct, select Start Import.

Let the durable job finish the work

After Start Import, the plugin runs server-backed work and persists progress. You can leave the page or sign out; already scheduled work can continue.

The progress screen tracks Products, Variations, Media, and Videos. During import, the importer preserves genuine source SKU where available, creates a deterministic fallback only when necessary, keeps source-aware stock semantics, writes native WooCommerce variations, and localizes remote media with deduplication.

100% means required work has been verified

During Final verification, progress displays 99% while the plugin checks product totals, variation totals, SKU integrity, image bindings, and relevant featured-video bindings. Only a verified result becomes 100% / Import complete.

If required work fails, the job becomes Import needs attention. Successful products remain preserved. Use Retry Failed Items when the failed items are retryable and let final verification run again.

Manage completed work through Import History

Open SKREP Importer → Import History to filter jobs by source, import status, review state, filename, or ID. Mark as complete changes review state only and does not delete imported WooCommerce products.

Common issues

• CSV_SIDECAR_REQUIRED: re-export the CSV with a current SKREP extension.
• SOURCE_SCHEMA_UNKNOWN: confirm the file is a supported SKREP export.
• Dependency not ready: return to Welcome and run Check Environment.
• Upload/connection failure: inspect WordPress connectivity, PHP/upload limits, security plugins, proxy rules, and server timeout.
• Media failure: make sure WordPress can reach the source URL over HTTP/HTTPS and remote downloads are not blocked.