Independent technical research by AumCreate. AumCreate is not the developer of WP All Import.
Short answer
For existing WooCommerce products, WP All Import can match a stock feed to records by an identifier such as SKU and update selected inventory fields. Variations require variation-level identity; an Existing Items import does not create or remove variations. If an ERP feed has inconsistent keys or conflicting sources, add a mapping and exception process instead of importing blindly.
The boundary between a stock feed and a catalog import
WP All Import documents a WooCommerce stock-sync workflow where an XML or CSV feed provides stock values and a matching identifier, commonly the SKU. That is different from repeating a complete product import. The safe design is to treat stock as a narrowly scoped update, not as permission to rewrite every field on a product.
Variable products need a variation-level key
The existing-data matching guide distinguishes updating existing records from creating or restructuring variations. It says an Existing Items import cannot add or remove variations, while specific variation data can be targeted using a variation ID or SKU. A parent SKU does not by itself identify every child variation.
Consider a wholesale catalog with one parent product and separately stocked size or finish combinations. The supplier file must supply a stable key at the level where WooCommerce stores the inventory. If the file contains only the parent SKU, first obtain a variant identifier or build an explicit mapping table; do not distribute one count across children.
A practical setup for the native import workflow
- Confirm whether WooCommerce manages stock at the parent product or each variation; inspect real records before setting a matching rule.
- Normalize supplier SKU values consistently, including leading zeros, whitespace and case. Store the normalized source key for traceability.
- Create a separate stock-only import when the incoming feed is limited to quantities and statuses.
- Match each source row to one existing product or variation. Stop and report unmatched and duplicate keys rather than creating unintended products.
- Choose only the inventory-related fields to update; preserve customer-facing copy, categories, media, prices and tax settings.
Suggested approach
WP All Import also documents selective field updates when an import is rerun. Use that boundary deliberately: a recurring feed should not quietly replace manually curated descriptions or product images. The vendor's stock-sync instructions explain the SKU-based matching approach and stock-specific mapping.
When the variation structure changes
A stock-only feed can update existing, identifiable variation records, but it is not a substitute for a controlled variation-creation process. New option combinations, discontinued variants or SKU renames change the identity problem. Treat them as catalog changes with separate approval, not as a side effect of setting stock.
Suggested approach
| Supplier change | Recommended handling | Primary risk |
|---|---|---|
| Quantity or stock status | Existing-record stock update | Wrong variation receives a count |
| New color or size combination | Catalog import or reviewed creation task | Unintended variation structure |
| Supplier SKU renamed | Explicit identity remapping | Duplicate or orphaned variant |
| Record missing from one feed | Exception queue until absence policy is confirmed | Accidental zeroing or deletion |
When to add a custom integration layer
Native import configuration is a good fit for consistent files with stable identifiers and a one-way stock feed. Custom integration becomes useful when multiple suppliers share SKUs, one supplier item maps to multiple storefront variants, inventory comes from an ERP API, or approval is required before large inventory changes. Those are architectural requirements, not claims that the plugin cannot handle every such scenario.
Suggested approach
- Use a staging table with source system, source SKU, target variation ID, feed timestamp and normalized quantity.
- Validate uniqueness before writes. Flag negative or implausible quantities, duplicate target mappings and unknown variations.
- Record a per-run import ID, before/after values and failed rows, with a replay mechanism for corrected records.
- Keep the source of truth explicit: an ERP feed may own stock while WooCommerce still owns descriptions and merchandising.
- Test a small set of parent and variation records in staging, then compare live stock values against source totals.
Operational checks before scheduling
Decide what a missing record means. Absence from a partial delta feed is not evidence that a product should become out of stock. Separately define the behavior for a full snapshot, a delayed feed and an intentionally discontinued SKU. Keep a timestamp and run identifier so a late file cannot overwrite newer inventory.
Suggested approach
Decision
If the supplier sends a predictable CSV or XML feed and each row matches one existing WooCommerce item, start with the documented stock import and restrict updated fields. If variation identity is inconsistent or stock updates need ERP reconciliation, design a mapping and exception-handling layer first. For that integration scope, AumCreate can help define matching rules, implement validation and build a maintainable WordPress workflow.
Sources
Product facts in this article are taken from the pages below.
- https://www.wpallimport.com/documentation/manual-record-matching/ — retrieved 2026-11-16
- https://www.wpallimport.com/documentation/syncing-stock/ — retrieved 2026-11-16
- https://www.wpallimport.com/documentation/update-import/ — retrieved 2026-11-16
AumCreate is not affiliated with the vendors of the products discussed here. Product names and trademarks belong to their owners.
AumCreate