Datapipe
Store owners
See yesterday's orders, sales and refunds every morning.
Read & reportOwner-approved writes
See your Shopify numbers in Claude.
Review orders, variants, location stock and refunds. Teammates or AI can propose product, price, stock, collection, order, customer, discount and refund changes, and each one waits for owner approval.
- Orders, products and stock by location, refreshed for you
- Refunds and sales over time in the sheet your team already uses
- Fix products, prices, stock, tags, discounts and refunds from Datapipe, approved by the owner
ClaudeUpdated November 2026
| Date | Orders | Sales |
|---|---|---|
| Oct 27 | 860 | $80.00 |
| Oct 28 | 410 | $125.50 |
| Oct 29 | 155 | $42.00 |
- SetupSign in, no key to copy
- Reads413 report fields across 11 datasets
- Changes16 owner-approved actions
- RefreshDaily to every 15 minutes
Who uses Datapipe with Shopify
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 Shopify
Read and report
Eight GraphQL reports add orders, products, variants, customer totals, inventory items, locations, stock at one location and refunds for one order.
- My customers
- My products
- My sales by day
- Orders (GraphQL)
- and 7 more
Change with owner approval
- Update product title, vendor or type
- Update product SEO title or description
- Change a product's description
- Replace a product's tags
- Set a product to active, draft or archived
- Set product metafields the owner picks
- Put a product in a collection or take it out
- Change a variant's price or compare-at price
- Set a variant's available stock at one location
- Change an order's tags or internal note
- Cancel an order without refunding it
- Refund part or all of an order's payment
- Change a customer's tags or internal note
- Record a customer's email marketing consent
- Create a discount code
- Turn a discount code off or back on
The owner reviews the exact values and approves every proposed change before it is applied to Shopify.
Full read details
Current inventory is separate from dated orders; currency and store permissions stay attached to the data.
Examples for your team
Check stock at a location
Choose a store location and compare available, on-hand, committed and incoming stock.
- Scheduled refresh
- Latest Shopify data
- Updated report
Limit: Product variants and inventory item IDs keep the rows identifiable.
Review an order's refunds
Choose one order and read its existing refunds with processed times and shop/presentment currencies.
- Scheduled refresh
- Latest Shopify data
- Updated report
Limit: This report does not create refunds or reconstruct past balances.
Build the weekly store update
Send orders and sales by day to your reporting destination.
- Scheduled refresh
- Latest Shopify data
- Updated report
Limit: Keep the product list beside the results when preparing the next client update.
Review a product's search description
A teammate proposes a clearer SEO title or description for an existing product.
- Proposed
- Owner approves
- Applied and logged
Limit: The owner reviews the exact replacement before it changes the storefront.
Fix things in Shopify without opening it
Spot it, fix it
See the problem in your report, then propose the fix in Datapipe instead of opening Shopify, finding the record and retyping it.
More people can help
Teammates and AI tools can suggest changes without getting edit access to Shopify.
Nothing changes without your yes
You see the current and proposed value side by side, and every change is logged.
Jobs you can stop doing by hand in Shopify
Update product title, vendor or type
Standardize vendor names
TodayFind every product listed as "NIKE", "Nike Inc" or "nike" and fix each one in the admin.
With DatapipeSort the product report by vendor to see every spelling. Propose the correct vendor for each product and approve.
Fix product types so reports group properly
TodayEdit products one by one in Shopify admin.
With DatapipeSpot blank or inconsistent types in the report and propose the right one. Prices, stock and variants stay as they are.
Exactly what this can change
Changes product content in the selected Shopify store. Storefront content and provider automations may change. Prices, inventory, publication status, handles and variants are unchanged.
Supported fields: Product title, Vendor, Product type.
Update product SEO title or description
Write missing SEO titles for new products
TodayOpen each new product and write its search title by hand.
With DatapipeChatGPT drafts titles from your product data, and you approve each one before it's saved.
Shorten meta descriptions that get cut off
TodayCheck each product's description length manually.
With DatapipeFilter the report for long descriptions and propose shorter ones. Search engines pick them up on their own schedule.
Exactly what this can change
Changes the selected product's SEO fields. Search engines choose when and whether to display them. Product URLs, publication status, prices and inventory are unchanged.
Supported fields: SEO title, SEO description.
Change a product's description
Rewrite thin descriptions on best sellers
TodayOpen each product in Shopify admin and write a fuller description in the editor.
With DatapipeSort the product report by units sold. ChatGPT drafts a fuller description for each top product, and you approve the exact text before it goes live.
Fix a wrong material or size note
TodaySearch products for the old wording and edit each description by hand.
With DatapipePropose the corrected description and compare the current and new text side by side before approving.
Exactly what this can change
Replaces the description of one product with the approved text. Basic HTML such as paragraphs, lists and links is kept; scripts, frames, forms and styles are refused. Customers see the new description on the product page straight away. Title, price, stock and status are unchanged.
Supported fields: Description (HTML allowed).
Replace a product's tags
Tag products for a seasonal collection
TodayOpen each product and type the new tag, hoping the spelling matches every time.
With DatapipePick the products from your report and propose the full tag list for each. Smart collections that use the tag pick them up once you approve.
Clean up duplicate tags
TodayFind tags like "Sale" and "sale " product by product and fix each one.
With DatapipeSpot the variants in the product report and propose a tidy tag list per product. Tags left out of the list are removed.
Exactly what this can change
Replaces the tags on one product with the approved list, so tags left out are removed. Smart collections, storefront filters, Shopify Flow and apps that use tags may react. Title, price, stock and status are unchanged.
Supported fields: Tags, separated by commas (empty removes all).
Set a product to active, draft or archived
Archive products you no longer sell
TodayFind discontinued products in admin and archive them one at a time.
With DatapipeFilter the stock report for items with no sales and no stock. Propose archiving each one and approve it; archived products can be restored later.
Put a restocked product back on sale
TodayRemember which drafts are ready and switch each one to active.
With DatapipeWhen the stock report shows the product back in stock, propose setting it to active and approve.
Exactly what this can change
Active products can be bought on the sales channels they're published to. Draft and archived products are hidden from customers and can't be bought. Archiving doesn't delete anything and can be reversed here. Prices, stock and variants are unchanged.
Supported fields: Status.
Set product metafields the owner picks
Fill in care instructions for a new range
TodayOpen each product and type the same metafield values by hand.
With DatapipeThe owner allows the care instructions metafield. A teammate proposes the value for each product, and you approve each before the theme shows it.
Correct a wrong fabric weight shown on product pages
TodayHunt for the metafield on each affected product.
With DatapipePropose the corrected value for each product and review the current and new value before approving.
Exactly what this can change
Sets owner-selected product metafields, using the store's own metafield definitions. Themes and apps that read those metafields may show the new values. Values can't be cleared here. If a metafield changed in Shopify after review, nothing is changed. Other metafields, price and stock are unchanged.
The owner selects supported writable fields for this action before teammates can propose changes.
Put a product in a collection or take it out
Add new arrivals to the New In collection
TodayOpen the collection and add each product by searching for it.
With DatapipeList this week's new products in the report, then propose adding each to the collection and approve.
Take sold-out products out of a featured collection
TodayCheck the collection against stock and remove items by hand.
With DatapipeThe stock report shows which featured products are sold out. Propose taking each out and approve.
Exactly what this can change
Adds one product to a manual collection, or takes it out. Customers see the collection change on the storefront. Smart collections pick products by their conditions, so they are refused. The product itself is unchanged.
Supported fields: Collection ID (numeric), Change.
Change a variant's price or compare-at price
Raise prices after a supplier increase
TodayEdit each variant's price in admin and double-check you didn't miss a size.
With DatapipeStart from the variant report. Propose the new price for each variant and approve each one after checking the current and new price.
Start or end a sale price
TodaySet compare-at prices variant by variant, then remember to remove them later.
With DatapipePropose the compare-at price to show the variant on sale, and later propose clearing it. Each change waits for your approval.
Exactly what this can change
Changes what customers pay for one variant, in the store's currency, from the moment it's saved. A compare-at price above the price shows the variant as on sale; leave it empty to remove it. Existing orders, other variants and stock are unchanged.
Supported fields: Price (for example 24.00), Compare-at price (empty removes it).
Set a variant's available stock at one location
Correct stock after a warehouse count
TodayOpen each variant's inventory at the location and type the counted number.
With DatapipeCompare the stock report with the count sheet. Propose the counted quantity per variant, and Shopify refuses it if stock moved since review.
Set opening stock at a new location
TodayEnter quantities for every variant at the new location by hand.
With DatapipePropose the quantity for each variant at that location and approve each change before customers can buy it.
Exactly what this can change
Sets the available quantity of one variant at one location to the approved number. If the stock changed in Shopify after review, nothing is changed. Customers can buy up to the new quantity, and apps that sync stock may react. Price and other locations are unchanged.
Supported fields: Location ID (numeric), Available quantity.
Change an order's tags or internal note
Tag orders that need a follow-up
TodayOpen each order and add the tag by hand so Flow picks it up.
With DatapipeSpot the orders in the order report and propose the tag. Shopify Flow reacts once you approve.
Leave an internal note for the warehouse
TodayCopy notes from email into each order's note field.
With DatapipeA teammate proposes the note for the order, and you approve it before it's saved. Customers don't see it.
Exactly what this can change
Replaces the tags or the internal note on one order. Customers don't see either. Shopify Flow and apps that use order tags may react. Items, amounts, payment and fulfillment are unchanged. Shopify may first need to review Datapipe's access to protected customer data before this works.
Supported fields: Tags, separated by commas (empty removes all), Internal note.
Cancel an order without refunding it
Cancel an order the customer asked to stop
TodayOpen the order, cancel it and pick the restock and email options each time.
With DatapipeA teammate proposes the cancellation with the reason and restock choice. You approve it, and the refund is a separate approval if money should go back.
Cancel an order flagged as fraud
TodayReview the order in admin, then cancel it and restock by hand.
With DatapipePropose cancelling with fraud as the reason and no customer email. Nothing is refunded until you approve a separate refund.
Exactly what this can change
Cancels one order. Nothing is refunded here; use the refund action separately if money should go back. Shopify voids payments that were authorized but not yet captured, restocks the items if you choose, and emails the customer only if you choose. A cancelled order can't be reopened. Shopify may first need to review Datapipe's access to protected customer data before this works.
Supported fields: Reason, Restock the items, Email the customer.
Refund part or all of an order's payment
Refund a late delivery
TodayOpen the order, start a refund and type the amount, checking it against what was paid.
With DatapipePropose the amount from the order report. Datapipe shows how much is still refundable, and you approve the exact amount before money moves.
Give a partial refund for a damaged item
TodayWork out the amount and refund it from the order page.
With DatapipeA teammate proposes the partial amount with a reason. You approve it, and the refund can't exceed what is left to refund.
Exactly what this can change
Sends money back to the customer through the order's original payment, up to the amount not yet refunded, in the store's currency. Items are not restocked and the order is not cancelled. Shopify emails the customer only if you choose. A refund can't be undone. Orders paid in another currency or through more than one payment are refused; refund those in Shopify. Shopify may first need to review Datapipe's access to protected customer data before this works.
Supported fields: Amount to refund (for example 12.50), Reason, kept on the refund (optional), Email the customer.
Change a customer's tags or internal note
Tag wholesale customers
TodayOpen each customer and add the wholesale tag so segments and pricing apps see it.
With DatapipeFind them in the customer report and propose the tag for each. You approve every change.
Record an account note after a support call
TodayPaste the note into the customer's profile by hand.
With DatapipeA teammate proposes the note, and you approve it before it's saved on the customer.
Exactly what this can change
Replaces the tags or the internal note on one customer. Customers don't see either. Customer segments, Shopify Flow and apps that use tags may react. Email, marketing consent and orders are unchanged. Shopify may first need to review Datapipe's access to protected customer data before this works.
Supported fields: Tags, separated by commas (empty removes all), Internal note.
Record a customer's email marketing consent
Record an opt-in collected at an event
TodayFind each customer and change their email marketing setting by hand.
With DatapipePropose subscribed with the opt-in level you collected, for each customer who signed the form. You approve each one.
Unsubscribe a customer who asked by email
TodaySearch for the customer and switch off email marketing.
With DatapipePropose unsubscribed for that customer and approve. Shopify stops marketing emails to them.
Exactly what this can change
Records that one customer subscribed to or unsubscribed from email marketing. A subscription needs the opt-in level you actually collected: single opt-in, or confirmed opt-in when the customer confirmed by email. Only record consent the customer gave. Shopify Email and marketing apps follow the new state. Shopify may first need to review Datapipe's access to protected customer data before this works.
Supported fields: Email marketing, How the customer opted in.
Create a discount code
Create a code for a newsletter offer
TodayOpen discounts, set the percentage, end date and limits, and check the code isn't taken.
With DatapipePropose the code, percentage and end date. Datapipe checks the code is free, and you approve before anyone can use it.
Make a thank-you code for an unhappy customer
TodayCreate a single-use code by hand and send it.
With DatapipePropose a fixed amount off with a use limit of one, and approve it before sharing the code.
Exactly what this can change
Creates one discount code that takes a percentage or a fixed amount, in the store's currency, off the whole order for any customer, starting now. Anyone with the code can use it at checkout, so set an end date or a use limit if needed. It doesn't combine with other discounts. Existing orders are unchanged.
Supported fields: Code customers type, Name shown in Shopify admin (optional), Percent off (1 to 100), Amount off the order (for example 10.00), Last day it works (UTC, optional), Maximum number of uses (optional), Uses per customer.
Turn a discount code off or back on
End a code that leaked online
TodayFind the discount and end it by hand as soon as you notice.
With DatapipePropose turning the code off and approve it. Orders that already used it keep their discount.
Bring back last season's code for a weekend
TodayFind the old discount and reactivate it.
With DatapipePropose turning the code back on, approve it, and propose turning it off again when the weekend ends.
Exactly what this can change
Turning a discount code off ends it now, so no one can use it at checkout. Orders that already used it keep the discount. Turning it back on lets anyone with the code use it again until its end date.
Supported fields: Discount code.
Update product title, vendor or typeProduct · Wool coat · proposed by Jordan Blake
| Field | Current value | Proposed value |
|---|---|---|
| Vendor | NORTHWIND inc | Northwind |
Every team member's change needs owner approval
- Owner turns on an action
- A teammate or AI tool proposes
- Check the current and proposed values, then approve that individual change
- Applied once and logged
Source changes use the separate Actions & approvals workflow in Datapipe. AI tools such as ChatGPT can propose changes but never approve them. Who can turn this on?
Provider rules and limits
Provider permissions still apply, and automations in Shopify may react to approved changes.
Only fields supported by an enabled action can be proposed; some actions also support individual owner-selected writable fields.
Before you connect
What you need
A Shopify login with access to the account you want to report on.
Read and write
Read access for reports. The 16 change actions need edit access in Shopify and stay off until the owner turns them on.
Limits and exclusions
Inventory, customer totals and refunds describe current provider state, not past snapshots. Shopify normally exposes only the last 60 days of orders unless older-order access is separately approved.
Full details and limits
Eight GraphQL datasets extend the original reports. Stock requires a location ID; refunds require an order ID. Inventory, customer totals and refunds describe current provider state, not past snapshots. Shopify normally exposes only the last 60 days of orders unless older-order access is separately approved. Customer reporting depends on Shopify permissions. For optional product edits, the owner separately authorizes access, enables specific actions and proposers, and approves every proposed change.
Reports you can build
11 reporting datasets, each with its own fields. Pick one in the app, then choose your columns.
- My customers
- My products
- My sales by day
- Orders (GraphQL)
- Products (GraphQL)
- Product variants (GraphQL)
- Customer totals (GraphQL)
- Inventory items
- Store locations
- Stock by location
- Refunds for an order
What each dataset reports
- My customers
People who have bought from you.
- My products
What you sell, and the price.
- My sales by day
Orders and sales from your Shopify store.
- Orders (GraphQL)
One order created in the selected UTC dates, with current financial/fulfillment status and original/current totals in explicit shop and presentment currencies. Shopify normally allows only the last 60 days of orders; older orders require separately approved read_all_orders access. Totals are current provider state, not historical sales snapshots.
- Products (GraphQL)
Current records from the connected store. Report dates do not reconstruct past inventory. GraphQL Admin API 2026-10; provider permissions apply. One row per product, with status, vendor, type and tags. Variants and their prices are a separate dataset.
- Product variants (GraphQL)
Current records from the connected store. Report dates do not reconstruct past inventory. GraphQL Admin API 2026-10; provider permissions apply. One row per variant with its parent product, SKU, tracked inventory and store-currency price. Currency accompanies prices; quantities can be negative. Location stock is a separate report.
- Customer totals (GraphQL)
Current records from the connected store. Report dates do not reconstruct past inventory. GraphQL Admin API 2026-10; provider permissions apply. One row per customer ID with lifetime order count/spend and currency. This dataset does not request names, email addresses or phone numbers. Customer access still depends on Shopify approval.
- Inventory items
Current records from the connected store. Report dates do not reconstruct past inventory. GraphQL Admin API 2026-10; provider permissions apply. One row per inventory item, preserving SKU, tracking and shipping/customs attributes. Item identities join explicitly to the stock-by-location report; no inventory quantities are inferred.
- Store locations
Current records from the connected store. Report dates do not reconstruct past inventory. GraphQL Admin API 2026-10; provider permissions apply. Active, inactive and legacy fulfillment-service locations are included. The location ID is the required input for the stock-by-location report.
- Stock by location
Current records from the connected store. Report dates do not reconstruct past inventory. GraphQL Admin API 2026-10; provider permissions apply. Choose one location ID from the connected store. One row per stocked inventory item at that location, with available, on-hand, committed and incoming quantities. Missing quantities stay null, not zero. Signed stock counts and item/location identities are retained.
- Refunds for an order
Choose one order ID from the connected store. One row per existing refund, with processed time and native shop/presentment amounts and currencies. This is current order refund history; the report date range does not filter it. Refund totals describe recorded transactions, not a separate successful-payment ledger. Shopify's order-access limits apply.
Metrics and dimensions
413 report fields across 11 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 Shopify data anywhere
Google SheetsA sheet that refreshes every morning.
Data StudioCharts that read the same numbers.
BigQueryA warehouse table for the same columns.
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 propose a Shopify change. Only the owner can approve it.
Which bestselling products in Shopify will run out of inventory within two weeks at current sales velocity?
Five high-margin inventory items identified with daily burn rate, current quantity, and recommended reorder date.
Better than exporting by hand
- It refreshes on its own, so nobody pastes in a new export.
- 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.
- Products can be listed with the price and the status.
What can you do with this data?
Explore all use cases →Ecommerce
Which product pages deserve more search attention?
Combine Search Console demand, GA4 engagement and Shopify stock before deciding which product pages to promote or improve.
See the example & prompts →Email marketingWhich email links get clicks but few purchases?
Read Mailchimp link clicks, GA4 campaign behavior and Shopify product availability to decide what to investigate before the next send.
See the example & prompts →Paid marketingWhy do Facebook ad clicks look stronger than purchases?
Compare Facebook Ads, tagged GA4 traffic and Shopify order context before deciding what needs a campaign or checkout investigation.
See the example & prompts →EcommerceCan our planned promotion be supported by available stock?
Match the SKUs and quantities in Google Sheets to Shopify stock at the fulfillment location you intend to use.
See the example & prompts →Customer supportWhich quiet support tickets need attention first?
Combine unresolved Zendesk tickets with the linked Shopify order before choosing the next support action.
See the example & prompts →EcommerceWhich paid orders need a warehouse check today?
Match Shopify’s unfulfilled orders to promised dispatch dates in Google Sheets, then put the warehouse check on the order.
See the example & prompts →EcommerceWhich products need attention before our next promotion?
Compare Shopify inventory with the SKUs and quantities in your Google Sheets promotion plan, then update the plan before launch.
See the example & prompts →Start from a goal
Top products
What is for sale, and the price.
Use this template →Orders (GraphQL)
One order created in the selected UTC dates, with current financial/fulfillment status and original/current totals in explicit shop and presentment currencies.
Use this template →Products (GraphQL)
Current records from the connected store.
Use this template →Product variants (GraphQL)
Current records from the connected store.
Use this template →How it works
Type your store name and click Connect Shopify.
Pick where it goes. This one sends the numbers to Claude.
You're done. It refreshes every day.
Sample report
| Date | Orders | Sales | Product | Status | Price |
|---|---|---|---|---|---|
| Oct 27 | 860 | $80.00 | Wool coat | Paid | $80.00 |
| Oct 28 | 410 | $125.50 | Canvas tote | Pending | $125.50 |
| Oct 29 | 155 | $42.00 | Gift card | Refunded | $42.00 |
Sample numbers, so you can see the shape. Your report uses your accounts.
Works well with Shopify
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.
Shopify + Google Analytics“Did more visits mean more orders this week?”See Google Analytics →
Shopify + Klaviyo“Did orders rise in the days after each email?”See Klaviyo →
Shopify + Mailchimp“Did orders rise in the days after each campaign?”See Mailchimp →
Shopify + 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.
Only the workspace owner. Writes start disabled. The owner enables permitted actions and eligible teammates: owner only, all project operators and managers, or selected teammates. The owner can change this at any time, and saving new settings cancels pending proposals.
No. Teammates propose in Datapipe, and approved changes are applied through the connected Shopify account. Nobody else gets a Shopify login from this.
They can propose a change through Datapipe, the same way a teammate can. They can never approve it. Only the owner approves, in Actions & approvals.
Datapipe sends each approved change once and logs the result. If it cannot confirm that Shopify received it, the request is marked Uncertain and is never retried automatically, so you can check Shopify first.
Yes. Datapipe reads the reports on this page and can make 16 kinds of change: update product title, vendor or type; update product seo title or description; change a product's description; replace a product's tags; set a product to active, draft or archived; set product metafields the owner picks; put a product in a collection or take it out; change a variant's price or compare-at price; set a variant's available stock at one location; change an order's tags or internal note; cancel an order without refunding it; refund part or all of an order's payment; change a customer's tags or internal note; record a customer's email marketing consent; create a discount code; turn a discount code off or back on. Each one stays off until the owner turns it on, and every proposed change needs the owner's approval. Provider permissions still apply.
This page lists 413 report fields across 11 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 Shopify 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 Shopify with sample data first
Build the report first, then add Shopify when you are ready.