> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/ecommerce/adobe-commerce-magento/data-overview.md). # 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 {% tabs %} {% tab title="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 {% endtab %} {% tab title="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 {% endtab %} {% tab title="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 {% endtab %} {% tab title="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 {% endtab %} {% endtabs %} ## 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 --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.coupler.io/sources/category/ecommerce/adobe-commerce-magento/data-overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.