Shopify connector FAQ
This feature is in Beta. To use it, a workspace admin must turn on Lakeflow Connect for Shopify from the Previews page. See Manage Databricks previews.
This page answers frequently asked questions about the managed Shopify ingestion connector in Lakeflow Connect. For FAQs that apply to all managed connectors, see Managed connector FAQs.
Which Shopify plans does the connector require?
The connector works with any Shopify plan, because the Shopify Admin API is available on all plans. To ingest the balance_transactions and disputes tables, the store must have Shopify Payments set up, and the disputes scope requires approval from Shopify.
Which tables does the connector support?
The connector supports 39 source tables: products, orders, customers, draft_orders, collections, custom_collections, smart_collections, articles, pages, product_variants, blogs, inventory_items, discount_codes, discount_automatic, locations, shop, tender_transactions, collects, disputes, abandoned_checkouts, fulfillment_orders, media_image, media, countries, balance_transactions, transactions, order_refunds, fulfillments, order_line_refund, order_adjustment, product_variant_media, order_shipping_line, order_agreements, order_risks, customer_address, fulfillment_order_line_item, discount_redeem_code, collection_product, and inventory_level. For the full schemas, see Destination table schemas.
How far back can the connector ingest data?
For incremental tables, the first sync ingests records from the previous 365 days, and each later sync ingests records modified after the last run. To ingest from a different start date, set the start_datetime option. See Connector options. Full-refresh tables reingest all available records on every run.
Which authentication methods does the connector support?
The connector supports the Shopify OAuth client credentials grant (OAuth M2M) only. OAuth U2M and basic authentication with a username and password aren't supported.