FAQ

How do I check if I'm using the new GraphQL source or a legacy REST source?

Look at the entity selector in your data flow settings:

• New GraphQL source: Entities are organized into groups (Basics, Order & product breakdowns) with a grouped dropdown.

• Legacy REST source: Entities appear as a flat, ungrouped list, and the source is labeled "Shopify (legacy)" on the data flow view page.

If you're unsure, contact support at [email protected] and they can verify which version your data flow uses.

Should I migrate from the legacy Shopify source to the new one?

Yes. Shopify has deprecated the REST API for third-party apps and recommends migrating to GraphQL. While there's no final shutdown date yet, the new source is faster, supports column selection, and includes customer journey data that the legacy version doesn't have.

Coupler.io will not migrate your data flows automatically to avoid data inconsistency (some field names differ). You can migrate at your own pace by creating new data flows with the GraphQL source and adjusting your destination/transformation settings.

Can I pull Shopify reports or analytics data?

No. Coupler.io pulls raw entity data (orders, products, customers, inventory) via the Shopify API. Shopify's built-in reports (Sales reports, Finance reports), analytics dashboards, conversion rates, and session/traffic data are not accessible through the API.

To build equivalent reports, export raw order data and calculate the metrics you need in your destination (Google Sheets, Looker Studio, BigQuery, etc.).

Can I export product metafields?

Not currently. The Shopify source exports standard product and variant fields but does not support custom metafields (e.g., wholesale price, product dimensions, custom attributes). This is one of the most requested features (7+ tickets).

If you need metafield data, contact support at [email protected] to register your interest — the team tracks feature requests by demand.

Why don't my order totals match Shopify's reports?

Shopify's reports use specific definitions for metrics like "Total sales," "Gross sales," and "Net sales" that include various adjustments. Coupler.io exports raw order totals from the API, which may not match these calculated metrics exactly.

Key column mappings:

• Current order total amount — The current total after all adjustments (refunds, edits)

• Net payment amount — Total minus refunds and pending amounts

• Current discounts amount — Total discount applied

For the closest match to Shopify's "Total sales," you may need to build a formula that combines multiple columns. Also check for test orders and timezone differences.

How do I filter orders by date?

Use the Created after and Created before parameters in your data flow settings. Select dates using the date picker:

• Last 30 days: set Created after to a date 30 days ago

• This month: set Created after to the first of the month, Created before to today

• Specific range: Created after = 2025-01-01, Created before = 2025-12-31

Note that date filters use your browser's timezone, not your Shopify store's timezone. If they differ, you may see orders appear in unexpected date ranges.

What's the difference between Orders and Orders with line items?

Orders gives you one row per order with order-level data — totals, status, customer info, tags.

Orders with line items splits each order into multiple rows — one row per product (line item) in the order. This includes SKU, quantity, line item price, and discount details.

Use Orders for revenue dashboards and daily sales summaries. Use Orders with line items for product-level analysis (top-selling SKUs, product mix, per-item revenue).

How do I handle test orders in my export?

Shopify test orders (created using the Bogus Gateway) are included in Coupler.io exports by default. To exclude them:

1. Add the "Is Test Order?" column to your export if it's not already included.

2. In your destination, filter out rows where this field is true.

3. Alternatively, use a Coupler.io transformation step to exclude test orders before they reach your destination.

My data flow keeps timing out — what can I do?

Timeout errors happen when the dataset is too large. Try these fixes in order:

1. Add date filters — Set Created after to limit the time range (e.g., last 90 days).

2. Use column selection — Remove columns you don't need.

3. Split by date range — Create multiple data flows covering different time periods.

4. Use Changed after — For ongoing syncs, pull only recently modified records (e.g., set Changed after to a date 7 days ago).

If none of these help, contact support — they can investigate your specific data flow.

Can I export data from multiple Shopify stores?

Yes, but each data flow connects to one Shopify store. To pull data from multiple stores:

1. Create a separate Shopify connection for each store.

2. Create data flows for each store using the appropriate connection.

3. Export all flows to the same destination.

4. Add a formula column or label to identify which store the data comes from.

5. Use Coupler.io's Append transformation to combine the datasets.

What happened to the Collection ID filter? [not sure]

The Collection ID filter (which let you export only products from a specific collection) was available in the legacy REST-based Shopify source but is not available in the current GraphQL-based source. The GraphQL source exports all products and you can filter by product status (Active, Archived, Draft) only.

If you need to filter by collection, contact support — they may be able to help with a workaround.

How do I export inventory data for specific locations?

The Inventory entity exports stock levels across all locations by default. To filter by specific locations, you'll need the Location ID from your Shopify store:

1. In Shopify Admin, go to Settings → Locations.

2. Select a location and copy the numeric ID from the URL (e.g., for site.myshopify.com/admin/settings/locations/51840778406, the ID is 51840778406).

3. Enter the Location ID in the data flow settings.

You can add multiple Location IDs, each on a separate line.

For step-by-step connection setup, see the Shopify data source guide. For information on migrating from the legacy source, see the GraphQL migration guide. For product field changes after GraphQL migration, see the Products changes article.