Store owners
See yesterday's orders, sales and refunds every morning.
Read & reportControlled changes
See your WooCommerce numbers in MySQL.
Compare products, variations, customers, coupons and refund events beside orders. Changes you can allow for teammates and AI tools: product, price, stock, order, customer, coupon and refund changes. Allowed changes apply right away and are recorded in history.
- Orders, products and stock in a sheet that refreshes itself
- Sales and refunds over time without exporting from WooCommerce
- Fix product text from Datapipe, with every change recorded
MySQLStart free Connect WooCommerce
Updated November 2026
| Product name | SKU | Current price |
|---|---|---|
| Wool coat | COAT-01 | 80.00 |
| Canvas tote | TOTE-01 | 25.50 |
| Gift card | GIFT-01 | 50.00 |
- SetupPaste a key or token
- Reads188 report fields across 17 datasets
- Changes11 change actions
- RefreshDaily to every 15 minutes
Who uses Datapipe with WooCommerce
Merchandisers
Catch low stock and messy product data before customers do.
Agencies
Report store results next to ad spend for each client.
What you can do with WooCommerce
Read and report
Read sixteen additional datasets covering catalog/variation stock, registered customers, coupons, refund events and selected-order refunds, tax/catalog metadata, native sales and tax summaries/time buckets, a bounded top-seller ranking and store currency.
- WooCommerce orders
- Product inventory
- Variations for a product
- Customers
- and 13 more
Controlled changes
- Update product name or descriptions
- Change a product's regular or sale price
- Set a product's stock quantity or stock status
- Publish a product, or make it draft, pending or private
- Replace a product's categories or tags
- Change an order's status
- Add a note to an order
- Change a customer's name, email, phone or company
- Create a coupon
- Move a coupon to the trash
- Refund part or all of an order
Changes stay off until you allow them. Allowed changes apply to WooCommerce right away, and history keeps the values before and after.
Full read details
Current inventory, order dates and refund dates retain separate meanings.
Examples for your team
Keep refunds separate from order sales
Read refunds by their own creation dates, including refunds for older orders.
- Scheduled refresh
- Latest WooCommerce data
- Updated report
Limit: Retain parent-order currency instead of assuming every refund uses the store's default currency.
Review stock and sales with the right context
Check product and variation stock beside native sales and tax reports.
- Scheduled refresh
- Latest WooCommerce data
- Updated report
Limit: Current stock is not historical stock, and provider sales totals use their own accounting rules.
Keep an order report current
Refresh the order report for your store review.
- Scheduled refresh
- Latest WooCommerce data
- Updated report
Limit: Send the supported order and amount columns to the destination your team already uses.
Refresh an existing product description
A teammate writes replacement copy for an existing product's name or descriptions.
- Allowed
- Applied
- Recorded
Limit: The storefront updates right away, and history keeps the old copy.
Fix things in WooCommerce without opening it
Spot it, fix it
See the problem in your report, then make the fix in Datapipe instead of opening WooCommerce, finding the record and retyping it.
More people can help
Teammates and AI tools you allow can make changes without getting edit access to WooCommerce.
You decide what can change
Changes stay off until you allow them. Every change is recorded with who made it and the values before and after.
Jobs you can stop doing by hand in WooCommerce
Update product name or descriptions
Write short descriptions for best sellers
TodayOpen each product in WordPress and write the short description from scratch.
With DatapipeSort your product report by units sold. ChatGPT drafts a short description for each top product and saves it. History keeps the old text.
Standardize product names
TodayFix names like "tee - blue - L" and "Blue Tee" one product at a time.
With DatapipeSort the product report by name to see the mix. Set a consistent name for each product. Prices, stock and URLs stay unchanged.
Update descriptions after a material change
TodaySearch products for the old wording and edit each description in the editor.
With DatapipeWrite the new description after comparing it with the current text. WordPress may tidy the formatting when it saves.
Exactly what this can change
Changes an existing product's storefront content. WordPress may format or sanitize descriptions, and store plugins may react. Prices, stock, publication status, URLs, variations and orders are unchanged.
Supported fields: Product name, Product description, Short description.
Change a product's regular or sale price
Update prices for next season
TodayEdit each product's regular price in WordPress and check the sale prices still make sense.
With DatapipeStart from the product report. Set the new regular price for each product after checking the current one. Price changes can be set to need approval first.
End a sale on time
TodayRemember to clear each sale price when the promotion ends.
With DatapipeClear the sale price for each product on the last day of the sale.
Exactly what this can change
Changes what customers pay for one simple or external product, in the store's currency, from the moment it's saved. A sale price must be lower than the regular price; leave it empty to end the sale. Variable and grouped products are refused. Existing orders and stock are unchanged.
Supported fields: Regular price (for example 24.00), Sale price (empty ends the sale).
Set a product's stock quantity or stock status
Correct stock after a count
TodayType the counted quantity into each product's inventory tab.
With DatapipeCompare your count with the stock report and set the counted quantity per product.
Mark a product as on backorder
TodayChange the stock status on each product by hand.
With DatapipeSet On backorder for products that don't track a quantity.
Exactly what this can change
Sets the stock quantity of one product that has stock management on, or the stock status (in stock, out of stock, on backorder) of one that doesn't. Customers can buy according to the new stock, and WooCommerce may send low-stock emails to the store. Price is unchanged.
Supported fields: Stock quantity, Stock status.
Publish a product, or make it draft, pending or private
Publish products that are ready
TodayOpen each draft and click Publish.
With DatapipePublish each finished draft from Datapipe. Customers can buy it straight away.
Hide a product while you fix its photos
TodaySwitch it to draft and remember to publish it again.
With DatapipeSet it to draft now and back to published later. Both changes are recorded in history.
Exactly what this can change
Published products are on the storefront and can be bought. Draft, pending review and private products are hidden from customers. Nothing is deleted. Price, stock and descriptions are unchanged.
Supported fields: Status.
Replace a product's categories or tags
Sort products into new categories
TodayEdit categories on each product page.
With DatapipeSet the new category IDs for each product. Categories left out are removed.
Tag products for a gift guide
TodayOpen each product and add the gift guide tag.
With DatapipePick products from the sales report and set their tags with the gift guide tag added.
Exactly what this can change
Replaces the categories or tags of one product with the given IDs, so ones left out are removed. Shop pages, menus and filters show the change. Price, stock and status are unchanged.
Supported fields: Category IDs, separated by commas, Tag IDs, separated by commas (empty removes all).
Change an order's status
Complete orders that were delivered
TodayOpen each processing order and mark it completed.
With DatapipeSpot delivered orders in the order report and set each one to Completed. WooCommerce may email the customer.
Put an order on hold while you check stock
TodayChange the status by hand and add a note.
With DatapipeSet the order to On hold. Nothing is charged or refunded.
Exactly what this can change
Changes the status of one order. WooCommerce may email the customer about it (for example when an order is completed), and cancelled or failed orders can return their items to stock. Nothing is charged or refunded; Refunded comes only from a real refund and isn't offered.
Supported fields: New status.
Add a note to an order
Leave a staff note on an order
TodayWrite the note in the order screen so the next person sees it.
With DatapipeA teammate adds a staff-only note from Datapipe.
Tell a customer their order is delayed
TodayWrite a customer note and check it emails the right person.
With DatapipeWrite a note to the customer and read it before you add it. WooCommerce emails it right away.
Exactly what this can change
Adds one note to an order. A private note is for staff only. A note to the customer is shown on their order and WooCommerce emails it to them straight away. Notes can't be edited afterwards. The order itself is unchanged.
Supported fields: Note, Who sees it.
Change a customer's name, email, phone or company
Fix a customer's billing company
TodayOpen the customer in WordPress and edit the billing details.
With DatapipeFix the company name after checking the current value.
Update a customer's email after they ask
TodayEdit the account email and hope it's the right person.
With DatapipeChange the email from Datapipe. Staff accounts are refused, so only customer accounts change.
Exactly what this can change
Changes contact details on one customer account. A new email becomes the address the customer signs in with and receives store emails at. Only accounts with the customer role can be changed; staff accounts are refused. Addresses, orders and passwords are unchanged.
Supported fields: First name, Last name, Email, Billing phone, Billing company.
Create a coupon
Create a code for a newsletter offer
TodayAdd a coupon by hand, set the type, amount, end date and limits.
With DatapipeCreate the code, discount and end date. Datapipe checks the code isn't taken.
Make a single-use code for a customer
TodayCreate a coupon and set the usage limit to one.
With DatapipeCreate the coupon with a use limit of one, then share it.
Exactly what this can change
Creates one coupon code that takes a percentage off the cart, a fixed amount off the cart, or a fixed amount off each product, in the store's currency. Anyone with the code can use it at checkout, so set an end date or a use limit if needed. Existing orders are unchanged.
Supported fields: Code customers type, Discount, Amount (percent or currency, for example 10), Last day it works (optional), Maximum number of uses (optional), Maximum uses per customer (optional).
Move a coupon to the trash
Remove a code that was shared publicly
TodayFind the coupon and move it to the trash as soon as you notice.
With DatapipeMove the coupon to the trash. It can be restored from the trash if needed.
Tidy up expired coupons
TodayGo through the coupon list and trash old ones by hand.
With DatapipeSpot expired coupons in the coupon report and trash each one from Datapipe.
Exactly what this can change
Moves one coupon to the trash, so customers can no longer use its code. Orders that already used it keep the discount. It can be restored from the coupon trash in WooCommerce, where WordPress deletes it for good after 30 days by default.
Supported fields: Trash.
Refund part or all of an order
Refund a late delivery
TodayOpen the order, start a refund, type the amount and pick the gateway refund.
With DatapipeRefund the amount from the order report. Datapipe shows what's still refundable first. Refunds can be set to need approval before money moves.
Record a refund you paid by bank transfer
TodayAdd a manual refund to the order so the reports match.
With DatapipeEnter the amount with Record the refund only. WooCommerce marks it without sending money through the gateway.
Exactly what this can change
Refunds one processing, on-hold or completed order, in part or in full, up to the amount not yet refunded. Through the payment gateway, money goes back to the customer straight away if the gateway supports refunds. Recording only marks the refund in WooCommerce, for money you return yourself. Items are not restocked. A refund can't be undone here.
Supported fields: Amount to refund (for example 12.50), Reason (optional, shown on the order), How.
Refund part or all of an orderOrder · 4163 · made by Jordan Blake
| Field | Before | After |
|---|---|---|
| Refund (record only) | — | $142.50, refunded in Stripe on Nov 3 |
You control who can change what
- A change is allowed for this data source
- A teammate or AI tool makes it
- It applies right away, or waits for approval if you set that
- Recorded with the values before and after
Source changes are managed on the Changes page in Datapipe. Approval is optional: set it for risky changes, for every change, or for one person. AI tools such as ChatGPT can never widen their own access. Who can turn this on?
Provider rules and limits
Provider permissions still apply, and automations in WooCommerce may react to changes.
Only fields supported by an allowed action can be changed; for some actions the owner, an admin or a project manager also picks the individual writable fields.
Before you connect
What you need
Connect your public HTTPS store from Data sources using its read-only consumer key and secret.
Read and write
Read access for reports. The 11 change actions need edit access in WooCommerce and stay off until the owner, an admin or a project manager allows them.
Limits and exclusions
Inventory is current state and ignores report dates; registered customers do not include every guest purchaser. Parent currency can be unavailable when an order cannot be read.
Full details and limits
Sixteen additional reports join the original order report. Inventory is current state and ignores report dates; registered customers do not include every guest purchaser. Global refund events require WooCommerce 9.0 or later and use refund creation dates, while selected-order refunds ignore report dates. Parent currency can be unavailable when an order cannot be read. Native sales reports use WooCommerce's own accounting, status and refund rules; their totals are not simply the sum of current orders or a certified ledger. Tax configuration is separate from collected tax. The top-seller report is limited to twelve products. Extensions, store permissions and versions affect availability. Optional product-content changes remain separate: they stay off until the action is allowed for this data source, and every change is recorded in history.
Reports you can build
17 reporting datasets, each with its own fields. Pick one in the app, then choose your columns.
- WooCommerce orders
- Product inventory
- Variations for a product
- Customers
- Coupons
- Refund events by date
- Refunds for an order
- Product categories
- Product tags
- Product attribute definitions
- Terms for an attribute
- Tax rate configuration
- Tax classes
- Sales and tax summary
- Sales and tax over time
- Top 12 selling products
- Store currency metadata
What each dataset reports
- WooCommerce orders
Orders and sales from the store.
- Product inventory
Current accessible store inventory, independent of report dates; it does not reconstruct past prices, stock or customer state. Store permissions, extensions and WooCommerce version affect availability. Missing measurements stay null, IDs remain strings and collections stay JSON. Native monetary amounts retain their currency context; no conversion or cross-currency summation is performed. Total sales is the provider's lifetime units-sold counter, not sales within report dates. Product variation IDs are not a substitute for the dedicated variation report.
- Variations for a product
Current accessible store inventory, independent of report dates; it does not reconstruct past prices, stock or customer state. Store permissions, extensions and WooCommerce version affect availability. Missing measurements stay null, IDs remain strings and collections stay JSON. Native monetary amounts retain their currency context; no conversion or cross-currency summation is performed. Choose one existing product. Variation attributes, prices and stock stay at variation grain; manage stock can inherit from the parent.
- Customers
Current accessible store inventory, independent of report dates; it does not reconstruct past prices, stock or customer state. Store permissions, extensions and WooCommerce version affect availability. Missing measurements stay null, IDs remain strings and collections stay JSON. Registered customer records are not a complete list of guest purchasers. Billing/shipping addresses remain JSON; passwords and payment details are excluded.
- Coupons
Current accessible store inventory, independent of report dates; it does not reconstruct past prices, stock or customer state. Store permissions, extensions and WooCommerce version affect availability. Missing measurements stay null, IDs remain strings and collections stay JSON. Coupon amount is a percentage for percent discounts and a store-currency amount for fixed discounts; always retain discount type. Usage counts are current provider totals. This read does not create or apply a coupon.
- Refund events by date
Native monetary amounts retain their currency context; no conversion or cross-currency summation is performed. Refunds are selected by refund creation dates in store time, including refunds for orders created before the selected range. Requires WooCommerce 9.0+ with the global refunds endpoint. Parent order currency is resolved without applying order-date filters; inaccessible/deleted parents can leave currency null. Refund amount is positive native refund value; line-item values can be negative. Gateway flags do not prove external settlement.
- Refunds for an order
Native monetary amounts retain their currency context; no conversion or cross-currency summation is performed. Current available refund records for one explicitly selected order, independent of report dates. Parent currency is read from that order, not inferred from the store default. Refund records are separate from the original order snapshot. This does not issue a refund.
- Product categories
Current accessible store inventory, independent of report dates; it does not reconstruct past prices, stock or customer state. Store permissions, extensions and WooCommerce version affect availability. Missing measurements stay null, IDs remain strings and collections stay JSON. Taxonomy counts are current product associations, not sales quantities. Empty categories are included.
- Product tags
Current accessible store inventory, independent of report dates; it does not reconstruct past prices, stock or customer state. Store permissions, extensions and WooCommerce version affect availability. Missing measurements stay null, IDs remain strings and collections stay JSON. Empty tags are included; association counts are not sales measurements.
- Product attribute definitions
Current accessible store inventory, independent of report dates; it does not reconstruct past prices, stock or customer state. Store permissions, extensions and WooCommerce version affect availability. Missing measurements stay null, IDs remain strings and collections stay JSON. Definitions describe shared product attributes; the separate terms report pages values for one selected definition.
- Terms for an attribute
Current accessible store inventory, independent of report dates; it does not reconstruct past prices, stock or customer state. Store permissions, extensions and WooCommerce version affect availability. Missing measurements stay null, IDs remain strings and collections stay JSON. Choose one attribute ID. Empty terms are included; counts reflect current product associations.
- Tax rate configuration
Current accessible store inventory, independent of report dates; it does not reconstruct past prices, stock or customer state. Store permissions, extensions and WooCommerce version affect availability. Missing measurements stay null, IDs remain strings and collections stay JSON. Configured rates and geographic rules are separate from collected tax. Rates retain percentage points; cities/postcodes remain native lists.
- Tax classes
Current accessible store inventory, independent of report dates; it does not reconstruct past prices, stock or customer state. Store permissions, extensions and WooCommerce version affect availability. Missing measurements stay null, IDs remain strings and collections stay JSON. Lists configured tax classes. It is not a tax collection report.
- Sales and tax summary
Native WooCommerce legacy sales report for the requested store-calendar dates. Its accounting/status/refund rules differ from summing current order snapshots or cash receipts. Values reflect the core report and installed extensions, not a certified financial ledger. Store currency is reporting context; multi-currency extensions can alter results. Native tax combines order and shipping tax. One row per native report. Refund and discount fields are native monetary amounts, not counts of refunded orders or coupon uses; these semantics are verified against the controller's underlying report data.
- Sales and tax over time
Native WooCommerce legacy sales report for the requested store-calendar dates. Its accounting/status/refund rules differ from summing current order snapshots or cash receipts. Values reflect the core report and installed extensions, not a certified financial ledger. Store currency is reporting context; multi-currency extensions can alter results. Native tax combines order and shipping tax. One row per native day or month bucket returned by WooCommerce; bucket granularity is selected by the provider. No daily buckets are invented when monthly data is returned.
- Top 12 selling products
Native WooCommerce legacy sales report for the requested store-calendar dates. Its accounting/status/refund rules differ from summing current order snapshots or cash receipts. Values reflect the core report and installed extensions, not a certified financial ledger. Store currency is reporting context; multi-currency extensions can alter results. Native tax combines order and shipping tax. An intentionally bounded native ranking, not a complete product-sales export. The core endpoint returns up to twelve available products; deleted products can be absent. Quantity is the native units-sold measure, not revenue.
- Store currency metadata
Current accessible store inventory, independent of report dates; it does not reconstruct past prices, stock or customer state. Store permissions, extensions and WooCommerce version affect availability. Missing measurements stay null, IDs remain strings and collections stay JSON. The configured reporting currency does not convert order/refund amounts or certify multi-currency extension behavior.
Metrics and dimensions
188 report fields across 17 datasets.
Hover or tap a field to see what it means. Custom fields from your own account appear after you connect.
No fields match. Try another search or choose All.
Send WooCommerce data anywhere
Google SheetsA sheet that refreshes every morning.
Data StudioCharts that read the same numbers.
BigQueryA warehouse table for the same columns.
ClickHousePush rows into ClickHouse over HTTPS with an API key.
AWS S3Write report files to your S3 bucket with IAM access keys.
Amazon RedshiftLoad rows into Redshift via the Data API with IAM keys.
FireboltPush rows into Firebolt over HTTPS with a Service Account.
PostgreSQLWrite report rows into PostgreSQL with database credentials.MySQLWrite report rows into MySQL with database credentials.
SnowflakePush rows into Snowflake over HTTPS with a PAT token.
Databricks SQLLoad rows into Databricks SQL with a Personal Access Token.
Cloudflare R2Write report files to your R2 bucket with access keys.
Excel / CSVA Drive file you can open in Excel.
ClaudeAsk Claude about these numbers in a sentence.
ChatGPTAsk ChatGPT about these numbers in a sentence.
APIRead the same rows from your own tool.Don't see yours? Use CSV or APIDownload the rows, or read them from your own tool.Ask AI about your data
Claude or ChatGPT can read the same numbers. You ask in a normal sentence, and the answer stays with your report.
AI tools can also make allowed WooCommerce changes. They can never widen their own access.
Which of the top 20 products by units sold in WooCommerce have fewer than 25 units in stock?
Four top sellers are under 25 units, led by the ceramic mug set with 9 left and 1,240 units sold to date.
Better than exporting by hand
- It refreshes on its own, so nobody pastes in a new export.
- Spend sits next to results, so a costly campaign is obvious.
- The same numbers can be split by who they came from.
- You can keep a row per day instead of one lump sum.
- Orders and sales stay in the report, ready each morning.
- People and the way you reach them can be their own rows.
What can you do with this data?
Explore all use cases →Start from a goal
WooCommerce sales and refunds dashboard
Daily store sales, refunds by the day they were issued and the top-selling products in a prepared dashboard.
Use this template →Product inventory
Current accessible store inventory, independent of report dates; it does not reconstruct past prices, stock or customer state.
Use this template →Variations for a product
Current accessible store inventory, independent of report dates; it does not reconstruct past prices, stock or customer state.
Use this template →Customers
Current accessible store inventory, independent of report dates; it does not reconstruct past prices, stock or customer state.
Use this template →How it works
Connect your public HTTPS store from Data sources using its read-only consumer key and secret.
Pick where it goes. This one sends the numbers to MySQL.
Choose a report and the fields you need, then refresh on a schedule.
Sample report
Sample product-inventory report. Each row is one product at the time of the read. A dash represents a null stock quantity when stock is not managed.
| Product ID | Product name | SKU | Current price | Store currency | Stock quantity | Stock status |
|---|---|---|---|---|---|---|
| 101 | Wool coat | COAT-01 | 80.00 | USD | 24 | instock |
| 102 | Canvas tote | TOTE-01 | 25.50 | USD | 8 | instock |
| 103 | Gift card | GIFT-01 | 50.00 | USD | — | instock |
Sample numbers, so you can see the shape. Your report uses your accounts.
Works well with WooCommerce
Add both to the same project. Each keeps its own report, so you can check them side by side or ask ChatGPT or Claude a question that needs both.
WooCommerce + Google Analytics“Did more visits mean more orders this week?”See Google Analytics →
WooCommerce + Klaviyo“Did orders rise in the days after each email?”See Klaviyo →
WooCommerce + Mailchimp“Did orders rise in the days after each campaign?”See Mailchimp →
WooCommerce + Stripe“Do store orders match the payments you received?”See Stripe →Questions
Free to start. Paid plans add more data sources and refresh faster.
Free and Starter refresh once a day. Pro refreshes every hour. Agency refreshes every 15 minutes on the first 50 data sources.
No. Name a project, add a data source, then choose a report and destination.
OAuth means you sign in with the service and grant access, without pasting an API key. Datapipe works with multiple partners to provide that sign-in. Some partners already provide it. Some integrations are API-only at present, so you paste a key or token. OAuth is coming soon for some. Some partners do not provide OAuth at all. The setup steps on each integration page say how that source connects. Signing in is only how the connection is made. It is not permission to change records. Where a source supports changes, those writes stay off until the workspace owner turns specific actions on and approves each one. We do not promise OAuth on every source, and we do not share dates.
The workspace owner, workspace admins and project managers. Changes start off. They choose which changes are allowed for each data source and who can make them: project operators and managers, selected teammates, and the AI tools those people connect. They can change this at any time.
No. Teammates make allowed changes in Datapipe, and Datapipe applies them through the connected WooCommerce account. Nobody else gets a WooCommerce login from this.
Yes, if that change is allowed for them. They work through Datapipe the same way a teammate does, within the same allowed changes and fields, and every change is recorded in the Changes history. AI tools can switch changes off, but they can never widen their own access. Asking for more waits for a person.
Yes, if you want. For each data source, approval can cover risky changes only (deleting, sending, publishing, refunds and price changes) or every change. You can also switch it on for one person, such as an intern. Those changes wait on the Changes page until the owner, an admin or a project manager approves them. Nobody but the owner approves their own change.
Datapipe sends each change once and records the result in the Changes history. If it cannot confirm that WooCommerce received it, the request is marked Uncertain and is never retried automatically, so you can check WooCommerce first.
Yes. Datapipe reads the reports on this page and can make 11 kinds of change: update product name or descriptions; change a product's regular or sale price; set a product's stock quantity or stock status; publish a product, or make it draft, pending or private; replace a product's categories or tags; change an order's status; add a note to an order; change a customer's name, email, phone or company; create a coupon; move a coupon to the trash; refund part or all of an order. Each one stays off until the owner, an admin or a project manager allows it for this data source. Allowed changes apply right away and are recorded in the Changes history. Provider permissions still apply.
This page lists 188 report fields across 17 datasets. You pick the columns when you build the report.
Available rows depend on the connected account, selected report type, its date rules and provider limits. Current-inventory reports show current records rather than earlier historical states.
One for each WooCommerce account you add to a project. Adding the same account to another project counts again. Reports and destinations do not use extra data sources.
Yes. The same numbers can go to a sheet, a chart, a warehouse, or an assistant.
Try WooCommerce with sample data first
Build the report first, then add WooCommerce when you are ready.