Advanced Analytica Advanced Analytica: IBOM
← All connectors
Shopify logo

Source connector

Shopify

Set up Shopify as a source and move its data into your chosen destination.

Version 4.3.6 certified generally available

Shopify

Use this page to set up and reference the Shopify source connector.

Prerequisites

Set up the connector

You can authenticate this connector using OAuth2.0 or API Password for private applications.

:::warning Shopify’s API can’t retrieve only the most recently updated discount codes. The connector instead fetches every code associated with each recently updated discount. This approach syncs every updated code but may re-sync codes that haven’t changed. Discounts with many codes may therefore consume more credits than expected. :::

Set up Shopify

:::note Existing Airbyte Cloud customers using API Password authentication should switch to OAuth2.0. The API Password will be deprecated shortly. This change doesn’t affect Airbyte Open Source connections. :::

Airbyte Cloud

  1. Log into your Airbyte Cloud account.
  2. Click Sources, then click + New source.
  3. On the Set up the source page, select Shopify from the Source type dropdown.
  4. Enter a name for the Shopify connector.

Connect using OAuth2.0

  1. Choose a Source name.
  2. Click Authenticate your Shopify account.
  3. Click Install to install the Airbyte application. Log in if needed, then select the store you want to sync. Review the consent form, then click Install app to finish the installation.
  4. After authentication, the Shopify Store field is automatically filled using your selected store. Confirm that the populated value is correct.
5. (Optional) Set a **Replication Start Date** as the starting point for data replication. Data created before this date won't sync. The default is January 1st, 2020. 6. Click **Set up source** and wait for the connection test to finish.

Airbyte Open Source

  1. Go to the Airbyte Open Source dashboard.
  2. Click Sources, then click + New source.
  3. On the Set up the source page, select Shopify from the Source type dropdown.
  4. Enter a name for the Shopify connector.

Create a custom app

Shopify API authentication requires a custom application. Follow these steps to create a custom app and find your Admin API Access Token.

  1. Log in to your Shopify account.
  2. In the dashboard, go to Settings > App and sales channels > Develop apps > Create an app.
  3. Choose a name for your new app.
  4. Select Configure Admin API scopes.
  5. Grant access to the following list of scopes. Select only scopes prefixed with read_, not write_, such as read_locations and read_price_rules.
  6. Click Install app to give the app access to your data.
  7. After installation, go to API Credentials and copy the Admin API Access Token. You can now set up the source in Airbyte.

Connect using API Password

  1. Enter a Source name.
  2. Enter your Shopify Store name. Find it in your Shopify URL or the Store details section of Settings.
  3. For API Password, enter your custom application’s Admin API access token.
  4. (Optional) Set a Replication Start Date as the starting point for data replication. Data created before this date won’t sync. The default is January 1st, 2020.
  5. Click Set up source and wait for the connection test to finish.

Custom app scopes

Add these scopes to your custom app so Airbyte can sync all available data. For details about access scopes, see the Shopify docs.

  • read_analytics
  • read_assigned_fulfillment_orders
  • read_content
  • read_customers
  • read_discounts
  • read_draft_orders
  • read_fulfillments
  • read_gdpr_data_request
  • read_gift_cards
  • read_inventory
  • read_legal_policies
  • read_locations
  • read_locales
  • read_marketing_events
  • read_markets
  • read_merchant_managed_fulfillment_orders
  • read_online_store_pages
  • read_order_edits
  • read_orders
  • read_price_rules
  • read_product_listings
  • read_products
  • read_publications
  • read_reports
  • read_resource_feedbacks
  • read_script_tags
  • read_shipping
  • read_shopify_payments_accounts
  • read_shopify_payments_bank_accounts
  • read_shopify_payments_disputes
  • read_shopify_payments_payouts
  • read_themes
  • read_third_party_fulfillment_orders
  • read_translations

Supported sync modes

The Shopify source connector supports these sync modes:

  • Full Refresh
  • Incremental

This source syncs data through the Shopify REST API, Shopify GraphQL API, and Shopify GraphQL BULK API. Listed streams marked “(GraphQL)” use the GraphQL or BULK API. Unmarked streams use the REST API.

Supported streams

Entity-relationship diagram

Customer fields in Orders

The Orders stream includes top-level copies of customer attributes, including customer_id, customer_email, and customer_default_address. Enable Populate top-level customer fields in Orders (populate_top_level_orders_customer_fields) in the source configuration to populate them from the nested customer object.

This setting defaults to false. When disabled or omitted, every new customer field contains null. When enabled, each field contains its corresponding customer value. Missing attributes and orders without customers still produce null. The fields remain selectable in the schema in both modes. This setting doesn’t affect the existing customer_locale field.

The original customer object remains available in both modes. To sync only selected or hashed attributes, deselect customer and select the required customer_* fields. Then configure hashing on those fields. Hashing or deselecting customer_email alone doesn’t remove its original value from customer.email while customer remains selected.

If population is disabled and you select any new top-level customer field, the connector logs one warning per sync attempt. It logs the warning when it reads an order. The warning says these fields are redacted to null, but the nested customer object isn’t redacted. Enable the setting to populate selected fields, or deselect them.

After enabling population on an existing incremental connection, refresh the Orders stream. This populates historical orders that wouldn’t otherwise be read again. Disabling population affects subsequently read orders. It doesn’t clear existing destination values by itself.

Countries and market-driven shipping

Shopify is moving merchant shipping configuration from delivery profiles to Markets. After migration, the deliveryProfiles API behind the Countries stream returns a frozen snapshot. That snapshot no longer reflects the merchant’s changes.

The connector checks shop.features.marketDrivenShipping when the Countries or Market Countries stream starts syncing:

  • Shops using legacy shipping: Countries syncs as before, while Market Countries emits no records.
  • Shops using market-driven shipping: Countries continues emitting the shipping configuration snapshot captured at migration and logs a warning. This prevents previously synced data from being wiped. Market Countries emits one record for each market region. A region can be a whole country or a subdivision, such as a US state. Each record contains the market’s current shipping options.

Market Countries and Countries have different shapes. A country belonging to several markets appears once for each market. Whole-country regions don’t include a province list. shipping_enabled and shipping_options are null when a market inherits shipping configuration from its parent. Every market type and status is included. Filter by market_type = REGION and market_status = ACTIVE to find buyer-facing shipping countries.

Shopify’s rollout starts on October 1, 2026. It covers merchants who opt in and shops Shopify moves after confirming their installed apps are compatible. Shopify plans to cover all shops by July 1, 2027. Both stream behaviours will coexist during this period. Your connection doesn’t change automatically, and you don’t need a global switch. Keep Countries for the legacy snapshot. Enable Market Countries for shops that have migrated.

Enable Market Countries after migration

  1. Confirm that the connector has the read_markets scope. With OAuth2.0, re-authenticate the source from its Settings page. With API password, add read_markets to your custom app’s Admin API scopes and save the source again. Without this scope, the stream won’t appear in the catalogue. The source also logs a warning during schema discovery.
  2. Refresh the source schema on the connection so Market Countries appears in the stream list.
  3. Enable the Market Countries stream. You can keep Countries enabled because it retains the final legacy snapshot.
  4. Run a sync and confirm that market_countries contains one record per market region: market_handle, code, subdivision_code, shipping_options. For an unmigrated shop, the stream remains empty until Shopify migrates it. You don’t need to take any action.

Capture deleted records

The connector captures deleted records from the Articles, Blogs, CustomCollections, Orders, Pages, and PriceRules streams. For each deletion, it outputs the record’s ID. It also populates the deleted_at, deleted_message, and deleted_description fields. All other fields remain empty.

For deleted products, use the dedicated Deleted Products stream. It queries the Shopify GraphQL Events API for product deletion events. Records include id, the product ID, with the deleted_at, deleted_message, and shop_url fields.

For more information about retrieving deleted records, see the Shopify documentation.

Sync discount codes

The connector provides two discount code streams:

StreamMethodBest for
Discount CodesBulk Operations (async)Stores where every discount has fewer than ~100 redeem codes. High throughput, low API cost.
Discount Codes SyncSynchronous cursor-paginated GraphQLStores that have one or more discounts with more than ~100 redeem codes. Guarantees every code is returned.

Shopify’s Bulk Operations API silently truncates the nested codes connection at about 100 records per parent discount, even with groupObjects: true. For example, the bulk stream returns only ~100 codes from a discount containing 500. It doesn’t return an error or warning.

Discount Codes Sync avoids this limit by querying parent discounts with cursor pagination. It then pages through each parent’s child codes, with up to 250 per page. This approach has a higher per-record API cost and lower throughput than the bulk stream.

Recommendation: Enable the Discount Codes Sync stream if any discount has more than ~100 redeem codes. You can run both streams together. They produce the same schema, so you can deduplicate downstream using id.

Both discount code streams re-sync every code when its discount is updated. See the warning in the setup guide.

Discounts in Shopify Rollouts: Connector versions before 4.2.3 omit a discount while a serving Rollout activates or expires it for some or all buyers. Version 4.2.3 and later return these discounts. However, incremental syncs don’t backfill previously omitted codes because their updated_at predates the saved cursor. If your store has placed discounts into Rollouts, refresh and retain records for incrementally synced discount code streams after upgrading. During a Rollout, a discount’s status reflects its own dates, not what buyers receive.

Marketing attribution data

You can find data related to marketing attribution across several streams. Sync these streams to understand marketing performance:

  • Customer Journey Summary (firstVisit.source, firstVisit.sourcetype)
  • Orders (referring_site, source_name)
  • Abandoned Checkouts (referring_site, source_name)

Features

FeatureSupported?(Yes/No)
Full Refresh SyncYes
Incremental - Append SyncYes
NamespacesNo

IP allow list

Airbyte’s Shopify app accepts Admin API requests only from the IP addresses below. With OAuth2.0 authentication, the connector only works in Airbyte Cloud or Airbyte Agents. To run it elsewhere, including Airbyte Open Source, authenticate using API Password and your own custom app.

If your organisation restricts access by IP address, add these addresses to your allow list. They’re the Airbyte Cloud IP addresses plus the Airbyte Agents IP addresses.

ProductCloud providerRegionIP addresses
Airbyte CloudGCPus-west334.106.109.131, 34.106.196.165, 34.106.60.246, 34.106.229.69, 34.106.127.139, 34.106.218.58, 34.106.115.240, 34.106.225.141
Airbyte CloudGCPus-central134.33.7.0/29
Airbyte CloudAWSeu-west-313.37.4.46, 13.37.142.60, 35.181.124.238
Airbyte AgentsAWSus-west-244.226.44.242, 35.163.106.179, 44.227.212.246

Data type map

Integration TypeAirbyte Type
stringstring
numbernumber
arrayarray
objectobject
booleanboolean

Limitations and troubleshooting

View Shopify connector limitations and troubleshooting details

Connector limitations

Rate limits

Shopify applies several rate limit restrictions. Throttling and exceeded limits aren’t typical, but you may see this warning in some edge cases:

"Caught retryable error '<some_error> or null' after <some_number> tries.
Waiting <some_number> seconds then retrying..."

This warning is expected when the connector receives a 429 - Rate Limit Exceeded HTTP Error. The sync continues after a short backoff period.

Shopify’s bulk operation limitations apply to every Shopify GraphQL Bulk API request. Different request types can have different limits.

Missing records after bulk checkpoints

Version 3.3.3 fixes an issue affecting incremental GraphQL Bulk streams. Some streams could skip parent records after a bulk job checkpointed during output. The issue affected these streams:

  • metafield_customers
  • metafield_products
  • metafield_product_images
  • product_images
  • customer_address

If an earlier connector version may have missed historical records, clear the affected stream and run a backfill sync. Clearing a stream deletes the data Airbyte wrote for it in your destination. For more information, see Clearing your data.

Transactions created before orders

Some payment methods create transactions a few minutes before Shopify creates the order. These include offsite or redirect gateways such as Klarna. From version 4.2.6, the connector emits these transactions when their order first syncs. It may emit the transaction again until a newer transaction moves the cursor beyond the order’s creation time. Destinations without deduplication, such as Incremental | Append, may therefore contain duplicate rows. Upgrading doesn’t backfill transactions skipped by earlier versions. Refresh the transactions stream or clear its state to recover them.

Transaction status changes

Shopify transactions don’t have an updated_at field, so the transactions stream uses created_at as its cursor. From version 4.3.4, incremental syncs also emit every transaction from orders updated since the saved cursor. The saved cursor is the latest synced transaction created_at, minus the Lookback Window when configured. This allows status changes to reach the destination, such as refunds moving from PENDING to SUCCESS. Any order edit, including tag or fulfilment changes, re-emits every transaction for that order. Without new transactions, the cursor doesn’t move, so each sync may emit the same transactions. Use Incremental | Append + Deduped to retain one row per transaction. Upgrading doesn’t correct rows left stale by earlier versions. Refresh the transactions stream to correct them.

This behaviour applies to the default GraphQL transactions stream. The REST transactions stream doesn’t yet capture status changes incrementally. This REST stream is used when Add user_id to Transactions (slower) is enabled. The order_refunds stream also doesn’t capture them incrementally. Refresh these streams to correct stale rows.

Product category values

The category field in the products stream comes from Shopify’s Standard Product Taxonomy. Shopify updates this taxonomy several times each year. It can rename or move a category without changing its ID. Because products syncs incrementally using updated_at, it only reads a product again after that product changes. Its category values may therefore fall behind the current taxonomy. Use category.id as the stable identifier. Refresh the products stream to retrieve current values.

BULK job checkpoint collisions

Incremental GraphQL Bulk streams checkpoint a bulk job after collecting BULK Job checkpoint (rows collected) lines. They then start the next job from the newest cursor value found. If one cursor value contains more lines than this threshold, the next job can’t advance beyond it. The sync then fails with:

The stream: `<stream_name>` checkpoint collision is detected. Try to increase the
`BULK Job checkpoint (rows collected)` to the bigger value. The stream will be
synced again during the next sync attempt.

This issue usually affects metafield streams and discount_codes, where one parent record has many child rows. It often follows a bulk store change that assigns the same updated_at value to many records.

First, check whether it cleared itself. Check whether any sync has succeeded since the collision:

  • A later sync succeeded. The next attempt passed the cluster without intervention. You don’t need to act, but failed attempts still count towards your usage.
  • No sync has succeeded since. The stream is blocked and won’t recover without a configuration change. Recent records aren’t reaching your destination, so address this urgently.

To unblock a stream that is not recovering, raise BULK Job checkpoint (rows collected) in your source configuration. Set it above the number of lines sharing that cursor value. The maximum is 1,000,000. Increase the value gradually instead of moving directly to the maximum. Larger bulk jobs cover more data, take longer, and need more temporary disk space for sorting.

These two actions don’t help:

  • Lowering GraphQL BULK Date Range in Days. A collision prevents the sync from passing one cursor value. A date range can’t divide that single value.
  • Clearing the stream. The cluster exists in your source data, so a fresh sync encounters it again.

If the stream still collides at 1,000,000, or raising the value doesn’t change its behaviour, contact Airbyte Support. Find the affected cursor value in the sync logs on the line containing Stream <stream_name>, continue from checkpoint:.

Troubleshooting

  • Connection test returns 401: The Shopify access token is invalid or revoked. Re-authenticate the source for OAuth, or regenerate the custom app’s Admin API access token.

  • Connection test returns 403: Grant the app the required access scopes. Then re-authorise the source or regenerate its Admin API access token. When Shopify names a scope in its response, the connection test includes it in the error message. For example, products require read_products, while orders require read_orders. The connection test reads shop metadata but doesn’t validate access to every stream.

  • Invalid Shopify Store: Enter mystore, mystore.myshopify.com, or https://mystore.myshopify.com. These values normalise to mystore. Remove paths such as /admin, credentials, query strings, and fragments from pasted URLs.

  • If OAuth2.0 authentication returns access errors, follow this Shopify Article to request access to the client’s store. After receiving access, you can continue with OAuth2.0 authentication.

  • If you receive “The BULK job couldn’t be created at this time, since another job is running.”, check your operation’s progress using the Shopify GraphQL BULK api.

  • For a “checkpoint collision is detected” stream error, see BULK job checkpoint collisions above. It explains how to distinguish self-clearing failures from blocked streams.

  • To cancel a Shopify GraphQL BULKjob, follow these steps. You need the current in-progress job ID.

  • For common Shopify source connector issues, visit this Airbyte Forum here.

Changelog

Expand to review
VersionDatePull RequestSubject
4.3.62026-11-1091709Update dependencies
4.3.52026-11-0390900Require Python 3.11 or newer, retaining support through Python 3.13
4.3.42026-11-0389704Emit transactions of orders updated since the saved state so transaction status changes, such as refunds going from PENDING to SUCCESS, are captured by incremental syncs; refresh transactions to correct stale rows
4.3.32026-11-0390723Update dependencies
4.3.22026-10-3090254Explain connection test authentication and access scope failures, and improve invalid store name guidance.
4.3.12026-10-2689760Fix deleted_products incremental syncs skipping product deletions recorded in the same second as the saved cursor on Shopify API 2026-10
4.3.02026-10-2088902Add the Shopify product taxonomy category field to the products stream; refresh the products stream to populate it for existing products
4.2.72026-10-2078958Update dependencies
4.2.62026-10-1687638Emit transactions of newly created orders even when the transaction created_at predates the saved state (offsite/redirect payment methods); refresh transactions to recover previously skipped records
4.2.52026-10-1589009Upgrade to Python 3.13 and pendulum 3
4.2.42026-10-1388385Re-run the slice instead of rewinding to a stale cursor from an earlier slice when a checkpointed BULK job has no records within the current slice
4.2.32026-10-1388469Upgrade Shopify Admin API to 2026-10 so discount_codes and discount_codes_sync no longer leave out discounts affected by a serving Shopify Rollout; see Syncing discount codes to backfill them. Retry GraphQL pages that Shopify fails with a throttling or INTERNAL_SERVER_ERROR code in deleted_products, countries, market_countries and discount_codes_sync, fail deleted_products on other GraphQL errors instead of completing silently, skip discounts deleted mid-sync in discount_codes_sync, and stop the product_images query from growing with every slice
4.2.22026-10-0988405Fix countries returning no records when a second Countries stream is read in the same process: keep the dedup list per stream instance instead of on the class
4.2.12026-09-2887001Re-run the slice with checkpointing disabled instead of silently skipping it when a checkpointed BULK job is canceled and returns no result URL
4.2.02026-09-2587007Add selectable top-level customer_* fields to orders, populated by the optional populate_top_level_orders_customer_fields setting (default: false); fields remain null when disabled
4.1.12026-09-2886966Fail the stream instead of silently skipping the slice when a failed BULK job returns no partial result or no records to resume from; retry failed BULK jobs as system errors (ACCESS_DENIED is a config error); show BULK error details to the user
4.1.02026-09-2186493Add market_countries stream for shops on market-driven shipping (requires read_markets); countries logs a warning for such shops since deliveryProfiles returns a frozen snapshot; countries and market_countries retry throttled pages and fail on other Shopify GraphQL errors responses instead of completing a partial snapshot
4.0.32026-09-1686371Fix ValueError: year 0 is out of range when the lookback window is applied to an empty stream state
4.0.22026-09-1583335Upgrade Shopify API version to 2026-07
4.0.12026-09-1481363Classify Shopify authentication errors as config errors instead of system errors during bulk job creation
4.0.02026-08-1181339Add missing format: date-time annotations to datetime fields in orders and order_refunds. orders.processed_at and order_refunds.processed_at change column type in typed destinations and require a schema refresh and resync. See the migration guide.
3.5.12026-06-2480787Validate and normalize the shop config value: accept a bare subdomain or full myshopify URL, and reject malformed input with a clear config error. The normalized handle is also written to the shop_url record field, so previously-malformed configs now emit a clean value.
3.5.02026-06-1179624Add new synchronous cursor-paginated discount_codes_sync stream with support for >100 redeem codes per discount
3.4.12026-06-1078513Enable groupObjects: true on the discount_codes bulk query to preserve grouped output for stores with many redeem codes per discount.
3.4.02026-05-1976192Add lookback_window_in_days config option to re-fetch recent records during incremental syncs, preventing missing data from race conditions or late-arriving updates.
3.3.32026-05-1177005Fix some incremental GraphQL Bulk streams silently skipping parent records when a bulk job checkpoints mid-output. Use the parent cursor tracked by the bulk record producer to advance the next slice, not the child record’s cursor.
3.3.22026-04-2476969Replace in-memory sort of bulk GraphQL records with a disk-backed external merge sort to fix OOM failures on large metafield syncs
3.3.12026-04-2276920Fix AttributeError from null logger in LimitReducingErrorHandler when handling non-500 HTTP errors
3.3.02026-04-1576327Upgrade airbyte-cdk dependency from v6 to v7
3.2.32026-03-2075255Upgrade Shopify API version from 2025-01 to 2025-10
3.2.22026-03-0972849Fix missing fulfillment orders by querying fulfillmentOrders endpoint directly; add configurable fulfillment_orders_include_closed option (default: false)
3.2.12026-02-0472810feat(source-shopify): Add id and position fields to product_variants.options schema (AI-Triage PR)
3.2.02026-01-2072209Add CollectionProducts stream for all product-collection associations
3.1.22026-01-1571188Handle CDK exceptions in connection check
3.1.12026-01-0671035Fix IndexError in countries stream when profile_location_groups is empty
3.1.02026-01-0571005Add deleted_products stream using GraphQL Events API
3.0.132025-10-2168245Update dependencies
3.0.122025-10-1467805Update dependencies
3.0.112025-10-0767448Update dependencies
3.0.102025-09-3066904Update dependencies
3.0.92025-09-1666291Promoting release candidate 3.0.9-rc.1 to a main version.
3.0.9-rc.12025-09-0965987Use filter field value to adjust slice for streams with ID cursor field.
3.0.82025-09-0465552Fix Incremental Syncs for Metafield child streams.
3.0.72025-06-0259015🐙 source-shopify: Update dependencies [2025-05-17]
3.0.62025-05-2860797Fix 500s on orders & order_refunds streams by adding dynamic page limit.
3.0.52025-04-2358598Fix AttributeError with Null measurement_weight fields for product_variants streams
3.0.42025-04-1958431Update dependencies
3.0.32025-04-1257984Update dependencies
3.0.22025-04-0557449Update dependencies
3.0.12025-03-2956861Update dependencies
3.0.02025-03-2755823Update API version
2.6.72025-03-2256316Update dependencies
2.6.62025-03-0855621Update dependencies
2.6.52025-03-0155126Update dependencies
2.6.42025-02-2254477Update dependencies
2.6.32025-02-1551983Update dependencies
2.6.22025-01-1450976Retry requests that return HTTP 500
2.6.12025-02-1651602Updated the UpgradeDeadline for the deprecation notice about this change
2.6.02025-01-1551037Deprecated the ProductsGraphQL and CustomerSavedSearch stream from the stream catalog
2.5.182025-01-1151326Update dependencies
2.5.172025-01-0650884Add moments field Customer Journey Summary stream
2.5.162025-01-0450938Update dependencies
2.5.152024-12-2850779Update dependencies
2.5.142024-12-2149088Update dependencies
2.5.132024-12-1149134Added checkpointed value collision detection for BULK-supported streams
2.5.122024-11-2548661Starting with this version, the Docker image is now rootless. Please note that this and future versions will not be compatible with Airbyte versions earlier than 0.64
2.5.112024-11-0748402Add image_src, image_url, including options to Product Variants stream
2.5.102024-11-0548322Update dependencies
2.5.92024-10-2947814Update dependencies
2.5.82024-10-2847044Update dependencies
2.5.72024-10-1446552Add parent state tracking for BULK sub-streams
2.5.62024-10-1246844Update dependencies
2.5.52024-10-0546578Raise exception on missing stream
2.5.42024-10-0545759Update dependencies
2.5.32024-09-2746095Fixed duplicates for Product Images, Metafield Product Images and Metafield Products streams for Incremental syncs
2.5.22024-09-1745633Adds read_inventory as a required scope for product_variants stream
2.5.12024-09-1445255Update dependencies
2.5.02024-09-0645190Migrate to CDK v5
2.4.242024-09-0345116Have message and description be nullable for custom_collections deleted events
2.4.232024-08-3144971Update dependencies
2.4.222024-08-2444723Update dependencies
2.4.212024-08-1744318Update dependencies
2.4.202024-08-1243834Update dependencies
2.4.192024-08-1043194Update dependencies
2.4.182024-08-0643326Added missing type type for customer_journey_summary field for Customer Journey Summary stream schema
2.4.172024-08-0242973Fixed FAILED Job handling for no-checkpointing BULK Streams, fixed STATE collision for REST Streams with Deleted Events
2.4.162024-07-2142095Added the Checkpointing for the BULK streams, fixed the store redirection
2.4.152024-07-2742806Update dependencies
2.4.142024-07-2042150Update dependencies
2.4.132024-07-1341809Update dependencies
2.4.122024-07-1041103Update dependencies
2.4.112024-07-0941068Added options field to Product Variants stream
2.4.102024-07-0941042Use latest CDK: 3.0.0
2.4.92024-07-0640768Update dependencies
2.4.82024-07-0340707Fixed the bug when product_images stream emitted records with no primary_key
2.4.72024-06-2740593Use latest CDK version possible
2.4.62024-06-2640526Made BULK Job termination threshold limit adjustable from input configuration, increased the default value to 1 hour.
2.4.52024-06-2540484Update dependencies
2.4.42024-06-1939594Extended the Discount Codes, Fulfillment Orders, Inventory Items, Inventory Levels, Products, Product Variants and Transactions stream schemas
2.4.32024-06-0638084add resiliency on some transient errors using the HttpClient
2.4.12024-06-2039651Update dependencies
2.4.02024-06-1739527Added new stream Order Agreements
2.3.02024-06-1439487Added new stream Customer Journey Summary
2.2.32024-06-0638084add resiliency on some transient errors using the HttpClient
2.2.22024-06-0439019[autopull] Upgrade base image to v1.2.1
2.2.12024-05-3038769Have products stream return all the tags comma separated
2.2.02024-05-2938746Updated countries schema
2.1.42024-05-2438610Updated the source API Version to 2024-04
2.1.32024-05-2338464Added missing fields to Products stream
2.1.22024-05-2338352Migrated Order Risks stream to GraphQL BULK
2.1.12024-05-2038251Replace AirbyteLogger with logging.Logger
2.1.02024-05-0237767Migrated Products, Product Images and Product Variants to GraphQL BULK
2.0.82024-05-0237589Added retry for known HTTP Errors for BULK streams
2.0.72024-04-2436660Schema descriptions
2.0.62024-04-2237468Fixed one time retry for Internal Server Error for BULK streams
2.0.52024-04-0336788Added ability to dynamically adjust the size of the slice
2.0.42024-03-2236355Update CDK version to ensure Per-Stream Error Messaging and Record Counts In State (features were already there so just upping the version)
2.0.32024-03-1536170Fixed the STATE messages emittion frequency for the nested sub-streams
2.0.22024-03-1236000Fix and issue where invalid shop name causes index out of bounds error
2.0.12024-03-1135952Fixed the issue when start date is missing but the stream required it
2.0.02024-02-1232345Fixed the issue with state causing the substreams to skip the records, made metafield_*: collections, customers, draft_orders, locations, orders, product_images, product_variants, products, and fulfillment_orders, collections, discount_codes, inventory_levels, inventory_items, transactions_graphql, customer_address streams to use BULK Operations instead of REST
1.1.82024-02-1235166Manage dependencies with Poetry.
1.1.72024-01-1933804Updated documentation with list of all supported streams
1.1.62024-01-0433414Prepare for airbyte-lib
1.1.52023-12-2833827Fix GraphQL query
1.1.42023-10-1931599Base image migration: remove Dockerfile and use the python-connector-base image
1.1.32023-10-1731500Fixed the issue caused by the missing access token while setup the new source and not yet authenticated
1.1.22023-10-1331381Fixed the issue caused by the state presence while fetching the deleted events with pagination
1.1.12023-09-1830560Performance testing - include socat binary in docker image
1.1.02023-09-0730246Added ability to fetch destroyed records for Articles, Blogs, CustomCollections, Orders, Pages, PriceRules, Products
1.0.02023-08-1129361Migrate to the 2023-07 Shopify API Version
0.6.22023-08-0929302Handle the Internal Server Error when entity could be fetched
0.6.12023-08-0828291Allow shop field to accept *.myshopify.com shop names, updated OAuth Spec
0.6.02023-08-0228770Added Disputes stream
0.5.12023-07-1328700Improved error messages with more user-friendly description, refactored code
0.5.02023-06-1327732License Update: Elv2
0.4.02023-06-1327083Added CustomerSavedSearch, CustomerAddress and Countries streams
0.3.42023-05-1025961Added validation for shop in input configuration (accepts non-url-like inputs)
0.3.32023-04-1225110Fixed issue when cursor_field is "None", added missing properties to stream schemas, fixed access_scopes validation error
0.3.22023-02-2723473Fixed OOM / Memory leak issue for Airbyte Cloud
0.3.12023-01-1621461Added discount_applications to orders stream
0.3.02022-11-1619492Added support for graphql and add a graphql products stream
0.2.02022-10-2118298Updated API version to the 2022-10, make stream schemas backward cpmpatible
0.1.392022-10-1317962Added metafield streams; support for nested list streams
0.1.382022-10-1017777Fixed 404 for configured streams, fix missing cursor error for old records
0.1.372022-04-3012500Improve input configuration copy
0.1.362022-03-229850Added BalanceTransactions stream
0.1.352022-03-0710915Fixed a bug which caused full-refresh syncs of child REST entities configured for incremental
0.1.342022-03-0210794Minor specification re-order, fixed links in documentation
0.1.332022-02-1710419Fixed wrong field type for tax_exemptions for Abandoned_checkouts stream
0.1.322022-02-1810449Added tender_transactions stream
0.1.312022-02-0810175Fixed compatibility issues for legacy user config
0.1.302022-01-249648Added permission validation before sync
0.1.292022-01-209248Added shop_url to the record for all streams
0.1.282022-01-199591Implemented OAuth2.0 authentication method for Airbyte Cloud
0.1.272021-12-229049Updated connector fields title/description
0.1.262021-12-148597Fixed mismatched number of tables for base-normalization, increased performance of order_refunds stream
0.1.252021-12-028297Added Shop stream
0.1.242021-11-307783Reviewed and corrected schemas for all streams
0.1.232021-11-157973Added InventoryItems
0.1.222021-10-187107Added FulfillmentOrders, Fulfillments streams
0.1.212021-10-147382Fixed InventoryLevels primary key
0.1.202021-10-147063Added Location and InventoryLevels as streams
0.1.192021-10-116951Added support of OAuth 2.0 authorisation option
0.1.182021-09-216056Added pre_tax_price to the orders/line_items schema
0.1.172021-09-175244Created data type enforcer for converting prices into numbers
0.1.162021-09-095945Fixed the connector’s performance for Incremental refresh
0.1.152021-09-025853Fixed amount type in order_refund schema
0.1.142021-09-025801Fixed line_items/discount allocations & duties parts of orders schema
0.1.132021-08-175470Fixed rate limits throttling
0.1.122021-08-095276Added status property to product schema
0.1.112021-07-234943Fixed products schema up to API 2021-07
0.1.102021-07-194830Fixed for streams json schemas, upgrade to API version 2021-07
0.1.92021-07-044472Incremental sync is now using updated_at instead of since_id by default
0.1.82021-06-294121Added draft orders stream
0.1.72021-06-264290Fixed the bug when limiting output records to 1 caused infinity loop
0.1.62021-06-244009Added pages, price rules and discount codes streams
0.1.52021-06-103973Added AIRBYTE_ENTRYPOINT for Kubernetes support
0.1.42021-06-093926New attributes to Orders schema
0.1.32021-06-083787Added Native Shopify Source Connector
Advanced Analytica

Most businesses are sitting on information they can’t use at speed. The people who hold it are busy, and when they leave, the knowledge goes with them. The documents are static, and the processes around them weren’t designed for AI.

Advanced Analytica works with these businesses to turn that information into structured data assets. Once they're integrated, AI systems can govern it, and the business can use it. We bring in the strategy, the specification and the AI skills to rework how the business operates.

MOVE FAST. STAY SAFE.