Adobe Commerce (Magento)

Adobe Commerce (formerly Magento) is a leading ecommerce platform for building and managing online stores. It powers everything from product catalogs and customer accounts to orders, shipments, and promotions — making it a rich source of operational and transactional data.

Connecting Adobe Commerce to Coupler.io lets you pull that data into your preferred destination automatically, without writing code or maintaining custom scripts.

Why connect Adobe Commerce to Coupler.io?

• Analyze orders, revenue, and refunds in Google Sheets, Excel, or Looker Studio

• Send product and inventory data to BigQuery or Redshift for warehouse-level reporting

• Combine orders with shipments and invoices using Join transformations for end-to-end fulfillment visibility

• Route customer or sales data to AI tools like ChatGPT, Claude, or Gemini for trend analysis and forecasting

• Append data from multiple store views or websites into a single dataset

Prerequisites

Before connecting, make sure you have:

• An active Adobe Commerce (Magento) instance with REST API access enabled

• An API access token or integration credentials with read permissions for the entities you want to export

• The base URL of your Magento store (e.g., https://yourstore.com)

• The API version your store is running (check under System > Web API)

Start with the Orders entity — it's usually the most valuable for revenue reporting and connects quickly with a single API token.

Quick start

1

Create a new data flow in Coupler.io. From your Coupler.io dashboard, click Add data flow and search for Adobe Commerce as the source.

2

Enter your API credentials. Provide your store's base URL and your API access token. You can generate an integration token in Magento under System > Integrations > Add New Integration — grant it read access to the resources you need.

3

Set your API version and start date. In the Basic settings, enter the API version your store uses (e.g., V1). Use the date picker to set a start date for how far back you want to pull historical data.

4

Select an entity. Choose the data you want to export — for example, Orders, Products, or Customers.

5

Choose your destination. Pick where you want the data to land — Google Sheets, Excel, BigQuery, Looker Studio, or an AI destination like ChatGPT or Claude.

6

Run the data flow. Click Run to execute your first manual sync and confirm data is coming through correctly.

Adobe Commerce (Magento) data overview

Adobe Commerce exposes a wide range of ecommerce entities through its REST API. In Coupler.io, each entity maps to a separate source in your data flow — you can pull one or combine several using Append or Join transformations.

Available entities

Entity	What it contains
Orders	Order IDs, status, totals, items, billing/shipping addresses, timestamps
Invoices	Invoice IDs, order references, amounts, status, created dates
Shipments	Shipment IDs, tracking numbers, carrier, items, order references
Creditmemos	Refund amounts, order references, items, status
Transactions	Payment gateway records, transaction type, amount, status
Carts	Cart IDs, customer references, items, totals, created/updated timestamps
Customers	Customer ID, name, email, group, addresses, created date
Customer groups	Group ID, name, tax class
Products	SKU, name, price, type, status, attributes, categories
Coupons	Coupon code, rule ID, usage count, expiry
Sales rules	Rule name, conditions, discount type, amount, active status
Inventory stocks	Stock ID, name, sales channels
Inventory sources	Source code, name, location, contact info, enabled status
Inventory source items	SKU, source code, quantity, status
Tax rates	Tax rate ID, code, rate, country, region, postcode
Tax classes	Class ID, name, class type
Store websites	Website ID, code, name, default group
Store views	Store view ID, code, name, website, locale
Store groups	Group ID, name, root category, default store
Directory countries	Country ID, ISO codes, name
Directory currencies	Base currency, allowed currencies, exchange rates

Key metrics and dimensions

Order metrics

Field	Description
grand_total	Final order value including tax and shipping
subtotal	Order value before tax and shipping
discount_amount	Total discount applied
tax_amount	Tax charged on the order
shipping_amount	Shipping cost
total_qty_ordered	Total quantity of items ordered
total_refunded	Amount refunded on the order

Order dimensions

Field	Description
status	Order status (pending, processing, complete, canceled, etc.)
state	Internal Magento order state
store_name	Store view where the order was placed
customer_group_id	Customer group at time of order
payment.method	Payment method used
created_at	Order creation timestamp
updated_at	Last update timestamp

Product fields

Field	Description
sku	Stock keeping unit identifier
name	Product name
price	Base price
type_id	Product type (simple, configurable, bundle, etc.)
status	Enabled or disabled
visibility	Catalog/search visibility setting
weight	Product weight

Inventory fields

Field	Description
quantity	Units available at a source location
status	In stock / out of stock
source_code	Identifies the warehouse or fulfillment location

Customer fields

Field	Description
email	Customer email address
group_id	Assigned customer group
created_at	Account creation date
gender	Customer gender (if collected)
dob	Date of birth (if collected)

Common entity combinations

• Orders + Invoices — Join on order_id to reconcile revenue against invoiced amounts

• Orders + Shipments — Join on order_id to track fulfillment rates and shipping lag

• Orders + Creditmemos — Join to calculate net revenue after refunds

• Inventory source items + Products — Join on sku to build a full inventory report with product names and prices

• Carts + Customers — Join on customer_id to analyze abandoned cart behavior by segment

• Multiple store views — Use Append to combine order data across stores into one unified dataset

Use cases by role

Ecommerce managers

• Track daily order volume, average order value, and revenue by store view

• Monitor abandoned cart rates using the Carts entity

• Measure coupon and promotional rule effectiveness using Coupons and Sales rules

• Build weekly sales dashboards in Looker Studio or Google Sheets

Operations & fulfillment

• Join Orders and Shipments to identify fulfillment bottlenecks

• Monitor inventory levels per source location using Inventory source items

• Flag out-of-stock SKUs by combining Products with Inventory source items

• Track refund volumes and patterns with Creditmemos

Finance teams

• Reconcile orders against invoices and transactions for accurate revenue recognition

• Calculate net revenue by subtracting Creditmemos from Orders

• Analyze tax collected by region using Tax rates and order data

• Export transaction records to BigQuery for audit-ready financial reporting

Marketing teams

• Segment customers by group or purchase history for targeted campaigns

• Evaluate discount code performance using the Coupons entity

• Identify high-value customer groups via Customer groups and order totals

• Send product performance data to ChatGPT or Claude for AI-assisted merchandising insights

Platform-specific notes

• Date filtering applies to entities that have created_at or updated_at fields — not all entities (e.g., Directory countries) support date-based filtering

• Multi-source inventory (MSI) data is available through Inventory stocks, Inventory sources, and Inventory source items — these are separate from the legacy single-source stock system

• Store views, store groups, and store websites reflect your Magento store hierarchy and are useful for filtering or segmenting order data by locale or region

• The customer_group_id on orders and customers maps to Customer groups — join these to get group names in your reports

• Configurable products appear as a single product record in the Products entity; child/variant details may require separate attribute handling

Adobe Commerce (Magento) common issues

Connection issues

Invalid API token or authentication failure

Make sure you're using an integration token created under System > Integrations in your Magento admin, not an admin user password. The integration must be activated and granted read access to the specific resources you're syncing.

Also confirm the base URL you entered matches your store's domain exactly, including https:// and no trailing slash.

Incorrect or unsupported API version

If you enter an API version that your store doesn't support, the connection will fail. Check your Magento version in System > About Magento and use the corresponding REST API version (most commonly V1). The Adobe Commerce REST API docs list supported versions.

Store URL not reachable or returns a 404

Coupler.io sends requests to https://yourstore.com/rest/V1/.... If your store has a custom API base path, IP allowlisting, or a Web Application Firewall (WAF) blocking external requests, the connection will fail. Whitelist Coupler.io's IP addresses or temporarily disable WAF rules to test the connection.

Missing data

No data returned even though orders exist

Check your start date setting. If you've set it too recently, older orders won't be included. Use the date picker to move the start date further back. Also confirm that the entity you selected (e.g., Orders) actually contains records in the date range you specified.

Inventory data is empty or incomplete

If your store uses Magento's legacy single-source inventory, the Inventory source items and Inventory stocks entities may return no data — these are specific to the Multi-Source Inventory (MSI) feature introduced in Magento 2.3. Check whether MSI is enabled in your store configuration.

Cart data doesn't include guest carts

The Carts entity typically returns carts associated with logged-in customers. Guest carts may require additional API permissions or may not be returned depending on your Magento version and REST API configuration.

Permission errors

403 Forbidden when accessing certain entities

Your integration token doesn't have read access to the requested resource. Go to System > Integrations in Magento, edit your integration, and expand the API section to grant access to the specific resources (e.g., Sales, Catalog, Customers, Inventory).

Access denied for customer or transaction data

Customer PII and payment transaction data require explicit permissions in the integration. Make sure Customers > All Customers and Sales > Transactions are checked in the integration's resource access settings.

Data discrepancies

Order totals in Coupler.io don't match the Magento admin

Magento stores several total fields per order (grand_total, subtotal, base_grand_total, etc.). The base_* fields use the store's base currency, while the non-prefixed fields use the order currency. If your store accepts multiple currencies, make sure you're using the correct field for your reporting currency.

Refund amounts don't reconcile with order totals

Refunds live in the Creditmemos entity, not on the order record itself. The total_refunded field on an order is a summary — for line-item refund details, pull the Creditmemos entity and join it to Orders on order_id.

Rate limits

Sync fails or slows down for large catalogs or order histories

Adobe Commerce REST API performance can degrade with very large datasets (e.g., hundreds of thousands of products or orders). If you're hitting timeouts, try narrowing the start date to reduce the volume of records per sync, or split large entities across multiple data flows with different date ranges.

Magento's default API rate limiting can vary by hosting environment. Managed cloud environments (Adobe Commerce Cloud) may have stricter limits than self-hosted instances.

Adobe Commerce (Magento) FAQ

Can I connect multiple Magento stores or store views to Coupler.io?

Yes. Each Magento store instance (with its own base URL) needs its own source in Coupler.io. You can then use the Append transformation to combine data from multiple stores into a single destination dataset. If you're working with store views within the same Magento instance, the data already includes a store_id or store_name field you can use to filter or segment.

Where do I find my Adobe Commerce API token?

Go to your Magento admin panel and navigate to System > Integrations > Add New Integration. Give it a name, set the resource access to the entities you need (e.g., Sales, Catalog, Customers), and save. Magento will display an Access Token — copy that and paste it into Coupler.io. Keep it secure and don't share it.

Which API version should I use?

Most Magento 2.x stores use V1. You can confirm this in your Magento admin under System > About Magento or by checking the Adobe Commerce REST API documentation. Enter the version exactly as shown (e.g., V1) in the API Version field in Coupler.io.

Does Coupler.io support incremental sync for Adobe Commerce?

Coupler.io uses the start date you configure to filter records — entities with created_at or updated_at fields (like Orders, Customers, and Invoices) support date-based filtering. Reference entities like Directory countries or Tax classes don't change often and are typically pulled in full each sync.

Can I pull abandoned cart data?

Yes — the Carts entity includes both active and abandoned carts. Abandoned carts are those that were created but never converted to an order. You can join Carts with Customers on customer_id to analyze which customer segments abandon most frequently.

How do I get a full inventory report with product names, not just SKUs?

Pull both the Inventory source items and Products entities, then use Coupler.io's Join transformation to combine them on the sku field. This gives you quantity and stock status alongside product names, prices, and categories.

Why does my order count in Coupler.io differ from the Magento admin?

The most common reasons are: (1) your start date excludes older orders, (2) you're filtering by a specific store view that doesn't include all orders, or (3) canceled or archived orders may be handled differently. Check your start date and confirm there are no status filters applied. See Common Issues for more detail on data discrepancies.

Can I send Adobe Commerce data to AI tools like ChatGPT or Claude?

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Perplexity, Cursor, and OpenClaw. You can route product performance data, customer segments, or order trends directly to these tools for analysis, forecasting, or generating merchandising recommendations.

Looking for details on which fields are available per entity? Check the Data Overview article. For connection errors or missing data, visit Common Issues. For setup tips and multi-store patterns, see Best Practices.