> 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/common-issues.md).
# 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](https://developer.adobe.com/commerce/webapi/rest/) 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.
{% hint style="warning" %}
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.
{% endhint %}
---
# 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/common-issues.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.