WooCommerce Product Data: Extracting and Syncing from WordPress Stores

Authentication

WooCommerce uses consumer key and consumer secret pairs for authentication. These are generated in the WordPress admin under WooCommerce Settings and can be scoped to read-only, write, or read/write access. For HTTPS sites, you pass credentials as query parameters or use HTTP Basic Auth.

Key Endpoints

The API follows RESTful conventions with predictable URL patterns:

• - GET /wp-json/wc/v3/products - List all products
• - GET /wp-json/wc/v3/products/{id} - Single product details
• - GET /wp-json/wc/v3/products/{id}/variations - Product variants
• - GET /wp-json/wc/v3/products/categories - Category list
• - GET /wp-json/wc/v3/products/reviews - Product reviews

Pagination and Filtering

Results are paginated with a default of 10 items per page (max 100). Use the per_page and page parameters to control pagination. Filter by category, status, date range, or search terms using query parameters. The response includes X-WP-Total and X-WP-TotalPages headers for pagination metadata.

Simple Products

A single product with one price, one SKU, and one stock level. This is the most straightforward type to extract. Fields include name, description, short description, price, regular price, sale price, SKU, stock quantity, weight, dimensions, and images.

Variable Products

A parent product with multiple variations (e.g., a t-shirt in different sizes and colors). The parent holds common attributes while each variation has its own price, SKU, stock level, and image. Extracting variable products requires capturing both the parent and all child variations.

Grouped Products

A collection of related simple products displayed together. Common for products sold in sets or families. Each grouped child is a standalone product with its own page and data. The parent serves as an organizational container.

External/Affiliate Products

Products listed on the WooCommerce store but purchased elsewhere. These include an external URL and button text instead of add-to-cart functionality. The product data (price, description) is maintained locally even though the purchase happens on another site.

1. Initial Full Sync

Start with a complete extraction of all products and variations. For API access, paginate through the products endpoint. For scraping, use the sitemap to discover all product URLs, then extract data from each page. Store this as your baseline dataset with timestamps.

2. Incremental Updates

After the initial sync, only process changes. The WooCommerce API supports filtering by modified_after date, returning only products changed since your last sync. For scraping, compare extracted data against your stored baseline to identify changes in price, availability, or descriptions.

3. Change Detection

Hash product data to efficiently detect changes. Compute a hash of the key fields (price, stock status, description) for each product. On each sync cycle, compare hashes to identify which products have changed. Only process and store products with hash mismatches, reducing storage and processing costs.

4. Error Handling and Retry

Production pipelines must handle failures gracefully. Implement retry logic with exponential backoff for transient errors. Track failed extractions and retry them in the next cycle. Maintain a dead letter queue for persistently failing products that require manual investigation.