Source connector

WooCommerce connector

WooCommerce integration for databases, warehouses and BI tools

WordPress ecommerce storefront and order data. Datrise captures WooCommerce entities such as orders, products, customers, coupons, refunds and order line items, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The WooCommerce REST API v3 authenticates with API key, HTTP Basic, incremental runs key on modified_after.

Of the 6 objects, 5 sync as upserts keyed on the primary key and 1 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `woocommerce_orders`) with a schema derived from the WooCommerce API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the WooCommerce pipeline page, and join the waitlist to get the WooCommerce connector with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What WooCommerce data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
orders	woocommerce_orders	Upsert by primary key, incremental on updated-at
products	woocommerce_products	Upsert by primary key, incremental on updated-at
customers	woocommerce_customers	Upsert by primary key, incremental on updated-at
coupons	woocommerce_coupons	Upsert by primary key, incremental on updated-at
refunds	woocommerce_refunds	Append-only, incremental by timestamp
order line items	woocommerce_order_line_items	Upsert by primary key, incremental on updated-at

WooCommerce API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	WooCommerce REST API v3
Authentication	API key, HTTP Basic — Over HTTPS the API uses HTTP Basic Auth with the Consumer Key as username and Consumer Secret as password; over plain HTTP it requires OAuth 1.0a one-legged signing instead, not OAuth2.
Pagination	page — Collection endpoints default to 10 items per page (`per_page`, capped at 100) selected with `page`; responses also carry `X-WP-Total`/`X-WP-TotalPages` and RFC 5988 Link headers.
Rate limit	Not published
Incremental cursor	modified_after — `modified_after`/`modified_before` are documented on Orders (and work on Products/Customers) but use an exclusive `>`/`<` comparison, so a record modified exactly on the boundary timestamp is skipped.
Webhooks	Yes — WooCommerce Webhooks (order.created/updated/deleted, product.created/updated/deleted, customer.created/updated/deleted, coupon.*)
Bulk export	Yes — Per-resource batch endpoints (`POST /wc/v3/<resource>/batch` with `create`/`update`/`delete` arrays)
Deletes detectable	Yes — Deleting without `force=true` sets the resource to `status=trash` (soft delete, still retrievable by filtering on that status); `force=true` permanently deletes and returns HTTP 200 instead of the usual 202.

Official API reference

What bites when replicating WooCommerce

Collection endpoints such as `/wc/v3/products` default to 10 items per page via `per_page` (max 100), with `page` selecting the offset, per the official REST API docs.
`modified_after`/`modified_before` on Orders use WordPress's `WP_Date_Query` `after`/`before` keys, which generate a strict `>`/`<` SQL comparison rather than `>=`/`<=`.
Deleting without `?force=true` only trashes the item (still visible via `status=trash`); permanent deletion requires `force=true` and returns HTTP 200 instead of 202.
WooCommerce publishes no platform-wide REST API rate limit — throughput on a self-hosted WordPress store is capped only by the hosting provider or reverse proxy, not by WooCommerce itself.

Compare this against every other documented API

Popular destinations for WooCommerce

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

WooCommerce connector FAQ

What WooCommerce data does the connector extract?: 6 objects: orders, products, customers, coupons, refunds and order line items. Each lands in its own table with types preserved; history-style objects (1: refunds) load as append-only streams.
Is the WooCommerce integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load WooCommerce data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each WooCommerce → destination pair has its own page with the object-to-table mapping.

Related sources

Other sources in the same category, each with its own connector page.

Early access

Launch your WooCommerce pipeline with guided onboarding

Join the waitlist to get priority access for WooCommerce integrations with guided setup, schema-aware mapping, and production-grade incremental sync.