When setting up the Shopify integration, all of the following scopes should be selected:
read_all_orders,read_analytics,write_app_proxy,read_apps,write_assigned_fulfillment_orders,read_audit_events,read_customer_events,write_cart_transforms,read_all_cart_transforms,write_validations,write_cash_tracking,write_channels,write_checkout_branding_settings,write_checkouts,write_companies,write_custom_fulfillment_services,write_custom_pixels,write_customers,write_customer_data_erasure,read_customer_payment_methods,write_customer_merge,write_delivery_customizations,write_price_rules,write_discounts,write_discounts_allocator_functions,write_discovery,write_draft_orders,write_files,write_fulfillment_constraint_rules,write_fulfillments,write_gift_card_transactions,write_gift_cards,write_inventory,write_inventory_shipments,write_inventory_shipments_received_items,write_inventory_transfers,write_legal_policies,write_delivery_option_generators,write_locales,write_locations,write_marketing_integrated_campaigns,write_marketing_events,write_markets,write_markets_home,write_merchant_managed_fulfillment_orders,write_metaobject_definitions,write_metaobjects,write_online_store_navigation,write_online_store_pages,write_order_edits,write_orders,write_packing_slip_templates,write_payment_mandate,write_payment_terms,write_payment_customizations,write_pixels,write_privacy_settings,write_product_feeds,write_product_listings,write_products,write_publications,write_purchase_options,write_reports,write_resource_feedbacks,write_returns,write_script_tags,read_shopify_payments_provider_accounts_sensitive,write_shipping,read_shopify_payments_accounts,read_shopify_payments_payouts,read_shopify_payments_bank_accounts,write_shopify_payments_disputes,write_content,write_store_credit_account_transactions,read_store_credit_accounts,write_own_subscription_contracts,write_theme_code,write_themes,write_third_party_fulfillment_orders,customer_write_customers,customer_read_metaobjects,unauthenticated_read_metaobjectsAssigning all scopes ensures the integration has everything it needs to function correctly, and avoids any access issues if the integration is expanded in the future.

