Store owners
See yesterday's orders, sales and refunds every morning.
Understand ecommerce orders, product catalog inventory and customer accounts with catalog adjustments from Datapipe.
Updated November 2026
| Order number | Order date | Status |
|---|---|---|
| 860 | Oct 27 | Enabled |
| 410 | Oct 28 | Pending |
| 155 | Oct 29 | Refunded |
See yesterday's orders, sales and refunds every morning.
Catch low stock and messy product data before customers do.
Report store results next to ad spend for each client.
Read products, order histories and customer accounts through Magento's REST API with your integration token.
Changes stay off until you allow them. Allowed changes apply to Magento right away, and history keeps the values before and after.
Product prices retain store currency and order statuses stay explicit.
Refresh order creation dates, billing and shipping totals, and customer details.
Limit: Order statuses retain native Magento lifecycle codes without artificial aggregation.
A teammate sets an updated price or cleaner product title for an existing SKU, and Magento publishes the change.
Limit: Price changes can be set to need approval first.
See the problem in your report, then make the fix in Datapipe instead of opening Magento, finding the record and retyping it.
Teammates and AI tools you allow can make changes without getting edit access to Magento.
Changes stay off until you allow them. Every change is recorded with who made it and the values before and after.
TodayLog into Magento Admin Panel, go to Catalog > Products, search SKU, click edit, enter new special price, and save product.
With DatapipeSpot margin opportunities or flash sale items in your inventory report and set the new price. Price changes can be set to need approval first.
TodayOpen product in Magento backend, rewrite title field, and clear Magento cache.
With DatapipeIdentify low-CTR catalog items in your sales report and update the title copy from Datapipe.
Changes the name or price of one product, found by its SKU, at the store's default (all store views) level. A name or price set for a single store view in Magento stays as it is. Stock, categories and images are unchanged.
Supported fields: Product name, Price.
TodayLog into Magento Admin, navigate to Sales > Orders, find order ID, scroll to Comments History, write comment, and submit.
With DatapipeIdentify shipping exceptions in your daily fulfillment report and add the carrier resolution note to the order.
TodayOpen order in Magento Sales dashboard, add manual audit verification note to history log.
With DatapipeAdd the verified payment risk review to the order history from Datapipe. The Changes history records who added it and when.
Adds a comment to one order's history and keeps its current status. Choosing to notify the customer emails them the comment. Nothing is refunded, invoiced or shipped.
Supported fields: Order comment, Customer notification.
| Field | Before | After |
|---|---|---|
| Price | $110.00 | $80.00 |
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 permissions still apply, and automations in Magento 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.
An API key or token from your Magento account.
Read access for reports. The 2 change actions need edit access in Magento and stay off until the owner, an admin or a project manager allows them.
Anything your connected account cannot see in Magento.
Current product catalog inventory, customer profiles, and orders with order line items for your connected Magento store.
Reporting reads catalog and orders. Optional product name, price or order comment updates are off until allowed for this data source, and every change is recorded in history. Order totals and payment transactions cannot be altered.
3 reporting datasets, each with its own fields. Pick one in the app, then choose your columns.
Orders created during the selected UTC dates. Amounts are in each order's currency; status, state and customer names are reported.
Store product catalog, not filtered by report dates. Standard SKUs, product names, price and status flags.
Registered store customers, not filtered by report dates. Names, customer group ID and creation timestamps.
28 report fields across 3 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.
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 Magento changes. They can never widen their own access.
Which Magento orders this month were refunded, and what was our total order value?
182 orders totalled $24,310; 6 were refunded for $642, mostly in the last week.
Create a project and choose Magento in Data sources.
Pick where it goes. This one sends the numbers to Databricks SQL.
Pick where it goes. Choose orders, products or customers and a destination.
| Order number | Order date | Status | Grand total | Total refunded | SKU | Product name | Price |
|---|---|---|---|---|---|---|---|
| 860 | Oct 27 | Enabled | 1,240 | 1,240 | COAT-BLK-M | Wool coat | $180.00 |
| 410 | Oct 28 | Pending | 640 | 640 | 640 | Canvas tote | $125.50 |
| 155 | Oct 29 | Refunded | 210 | 210 | 210 | Gift card | $42.00 |
Sample numbers, so you can see the shape. Your report uses your accounts.
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.
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 Magento account. Nobody else gets a Magento 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 Magento received it, the request is marked Uncertain and is never retried automatically, so you can check Magento first.
Yes. Datapipe reads the reports on this page and can make 2 kinds of change: update product name or price; add comment to 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 28 report fields across 3 datasets. You pick the columns when you build the report.
Current product catalog inventory, customer profiles, and orders with order line items for your connected Magento store. Account permissions and the records available from the provider determine which rows can be read.
One for each Magento 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.
Build the report first, then add Magento when you are ready.