WooCommerce

Source - Vendo imports WooCommerce commerce data from your WordPress store and turns orders, refunds, subscriptions, and customers into modeled events and profiles for downstream analytics destinations.

What Vendo Syncs

Vendo reads WooCommerce through the REST API v3 using a read-access API key.

Data	What it powers
Orders	Order, payment, fulfillment, refund, and revenue reporting
Subscriptions	Subscription lifecycle events when the WooCommerce Subscriptions extension is installed
Customers	Customer profiles, purchase history, and identity resolution
Products	Product catalog, categories, and optional product variation output
Coupons	Discount and promotion analysis

Events and Profiles

Vendo transforms WooCommerce tables into canonical commerce events and customer traits.

Event or profile	When it is created
Order Received	A WooCommerce order is created or updated into a received order state
Order Fulfilled	Fulfillment details are available for the order
Order Refunded	A full refund is recorded
Order Partially Refunded	A partial refund is recorded
Subscription Started	A subscription starts and has billing context
Subscription Cancelled	A subscription is cancelled
Subscription Renewed	A renewal order is recorded for an existing subscription
Customer Properties	Customer profile, purchase history, and billing traits are refreshed

Revenue Fields

WooCommerce revenue events use Vendo’s canonical revenue names:

Canonical field	WooCommerce source value
`amount`	Order cart total for received orders, refund amount for refund events
`reporting_amount`	Reporting-currency order total or refund amount
`currency`	Original WooCommerce order currency
`reporting_currency`	Reporting currency used by Vendo

WooCommerce does not provide Stripe-style net revenue or fee fields, so Vendo maps the available gross order, refund, renewal, discount, tax, and shipping values.

Identity and Deduplication

Identity - events use Vendo’s modeled user_id and fall back to customer email when needed.
Customer profiles - customer rows can be matched by modeled user_id, email, or woocommerce_customer_id.
Guest checkouts - guest orders are still imported when WooCommerce provides an email address.
Deduplication - imported resources use stable WooCommerce IDs, and modeled events carry deterministic insert IDs.

Platform Details

Setting	Value
Auth Method	WooCommerce REST API consumer key + consumer secret
API	WooCommerce REST API v3
Sync Method	Server-side scheduled import
Default Cadence	Daily, anchored at 04:00 account/runtime time
Incremental Cursor	`date_modified_gmt` for orders, subscriptions, customers, products, and coupons
Backfill Window	30-day chunks; full available store history can be imported
Rate Limit	Conservative host-dependent API pacing with retry/backoff on 429 and 5xx responses

Setup

In WooCommerce, open Settings > Advanced > REST API
Create a new API key with Read access
Copy the consumer key that starts with ck_
Copy the consumer secret that starts with cs_
In Vendo, navigate to Sources > WooCommerce
Enter the store URL, consumer key, and consumer secret
Select the resources to import and save the source

Verify Setup

Confirm the WooCommerce source status is active in Vendo
Trigger a manual sync or wait for the next scheduled import
Check that orders, customers, and products are landing in the destination or Vendo dataset
Review integration logs for WooCommerce API errors, rate limits, or missing subscription endpoints

Troubleshooting

Symptom	What to check
Credentials fail validation	Confirm the store URL includes `https://`, the key starts with `ck_`, the secret starts with `cs_`, and the key has Read access
Orders import but subscriptions do not	Confirm the WooCommerce Subscriptions extension is installed; stores without the extension return a missing subscriptions endpoint
Customer rows are missing identity	Check that WooCommerce includes email or customer ID on the order/customer record
Syncs are slow or intermittent	Check the WordPress host for API throttling; Vendo backs off on 429 and 5xx responses
Revenue does not include net or fees	WooCommerce does not expose Stripe-style net/fee values through this connector; use `amount`, `reporting_amount`, tax, shipping, and discount fields

Compatible Destinations

WooCommerce source data can be routed to analytics, messaging, warehouse, and CDP destinations that accept modeled events and user profiles, including:

Destination	What Vendo sends
Mixpanel	Commerce events and customer profiles
Amplitude	Commerce events and user/group properties
Segment	Event and profile streams
Customer.io	Customer traits and lifecycle events
BigQuery	Raw and modeled commerce tables