Skip to main content

Python Guide: Loading Shopify Data to Google Cloud with dlt Library

Need help deploying these pipelines, or figuring out how to run them in your data stack?

Join our Slack community or book a call with our support engineer Violetta.

This page provides a technical guide on how to load data from shopify, a comprehensive commerce platform, into Google Cloud Storage, a filesystem destination on the Google Cloud Platform. This process is facilitated by the open-source Python library, dlt. Shopify allows anyone to start, manage, and scale a business, while Google Cloud Storage offers the ability to create datalakes and upload data in various formats such as JSONL, Parquet or CSV. With dlt, you can easily bridge these two platforms, transferring data seamlessly from shopify to Google Cloud Storage. For more details about shopify, visit Shopify.

dlt Key Features​

  • Google Storage: dlt allows you to store your data in Google Storage. You will need to install the gcfs package and provide your Google Cloud credentials. Detailed instructions can be found here.

  • Azure Blob Storage: dlt supports Azure Blob Storage as a destination. You will need to install the adlfs package and provide your Azure credentials. More information can be found here.

  • Local File System: dlt can also store data in your local file system. You can specify the path to your local directory in the bucket_url configuration. More details can be found here.

  • Scalability and Efficiency: dlt leverages iterators, chunking, and parallelization techniques to provide scalable data extraction. It also utilizes implicit extraction DAGs to handle dependencies between data sources and transformations automatically. More about this can be found here.

  • Staging Support: dlt supports staging destinations like S3, Google Storage, and Azure Blob Storage for Snowflake. It uploads files in the parquet or jsonl format to the bucket provider and asks Snowflake to copy their data directly into the database. More information can be found here.

Getting started with your pipeline locally​

0. Prerequisites​

dlt requires Python 3.8 or higher. Additionally, you need to have the pip package manager installed, and we recommend using a virtual environment to manage your dependencies. You can learn more about preparing your computer for dlt in our installation reference.

1. Install dlt​

First you need to install the dlt library with the correct extras for Google Cloud Storage:

pip install "dlt[filesystem]"

The dlt cli has a useful command to get you started with any combination of source and destination. For this example, we want to load data from Shopify to Google Cloud Storage. You can run the following commands to create a starting point for loading data from Shopify to Google Cloud Storage:

# create a new directory
mkdir shopify_dlt_pipeline
cd shopify_dlt_pipeline
# initialize a new pipeline with your source and destination
dlt init shopify_dlt filesystem
# install the required dependencies
pip install -r requirements.txt

The last command will install the required dependencies for your pipeline. The dependencies are listed in the requirements.txt:

dlt[filesystem]>=0.3.8

You now have the following folder structure in your project:

shopify_dlt_pipeline/
├── .dlt/
│   ├── config.toml          # configs for your pipeline
│   └── secrets.toml         # secrets for your pipeline
├── shopify_dlt/                   # folder with source specific files
│   └── ...
├── shopify_dlt_pipeline.py        # your main pipeline script
├── requirements.txt         # dependencies for your pipeline
└── .gitignore               # ignore files for git (not required)

2. Configuring your source and destination credentials​

The dlt cli will have created a .dlt directory in your project folder. This directory contains a config.toml file and a secrets.toml file that you can use to configure your pipeline. The automatically created version of these files look like this:

generated config.toml​

# put your configuration values here

[runtime]
log_level="WARNING"  # the system log level of dlt
# use the dlthub_telemetry setting to enable/disable anonymous usage data reporting, see https://dlthub.com/docs/telemetry
dlthub_telemetry = true

[sources.shopify_dlt]
shop_url = "shop_url" # please set me up!
organization_id = "organization_id" # please set me up!

generated secrets.toml​

# put your secret values and credentials here. do not share this file and do not push it to github

[sources.shopify_dlt]
private_app_password = "private_app_password" # please set me up!
access_token = "access_token" # please set me up!

[destination.filesystem]
dataset_name = "dataset_name" # please set me up!
bucket_url = "bucket_url" # please set me up!

[destination.filesystem.credentials]
aws_access_key_id = "aws_access_key_id" # please set me up!
aws_secret_access_key = "aws_secret_access_key" # please set me up!

2.1. Adjust the generated code to your usecase​

Further help setting up your source and destinations
  • Read more about setting up the Shopify source in our docs.
  • Read more about setting up the Google Cloud Storage destination in our docs.

The default filesystem destination is configured to connect to AWS S3. To load to Google Cloud Storage, update the [destination.filesystem.credentials] section in your secrets.toml.

[destination.filesystem.credentials]
client_email="Please set me up!"
private_key="Please set me up!"
project_id="Please set me up!"

By default, the filesystem destination will store your files as JSONL. You can tell your pipeline to choose a different format with the loader_file_format property that you can set directly on the pipeline or via your config.toml. Available values are jsonl, parquet and csv:

[pipeline] # in ./dlt/config.toml
loader_file_format="parquet"

3. Running your pipeline for the first time​

The dlt cli has also created a main pipeline script for you at shopify_dlt_pipeline.py, as well as a folder shopify_dlt that contains additional python files for your source. These files are your local copies which you can modify to fit your needs. In some cases you may find that you only need to do small changes to your pipelines or add some configurations, in other cases these files can serve as a working starting point for your code, but will need to be adjusted to do what you need them to do.

The main pipeline script will look something like this:


"""Pipeline to load shopify data into BigQuery.
"""

import dlt
from dlt.common import pendulum
from typing import List, Tuple
from shopify_dlt import shopify_source, TAnyDateTime, shopify_partner_query


def load_all_resources(resources: List[str], start_date: TAnyDateTime) -> None:
    """Execute a pipeline that will load the given Shopify resources incrementally beginning at the given start date.
    Subsequent runs will load only items updated since the previous run.
    """

    pipeline = dlt.pipeline(
        pipeline_name="shopify", destination='filesystem', dataset_name="shopify_data"
    )
    load_info = pipeline.run(
        shopify_source(start_date=start_date).with_resources(*resources),
    )
    print(load_info)


def incremental_load_with_backloading() -> None:
    """Load past orders from Shopify in chunks of 1 week each using the start_date and end_date parameters.
    This can useful to reduce the potiential failure window when loading large amounts of historic data.
    Chunks and incremental load can also be run in parallel to speed up the initial load.
    """

    pipeline = dlt.pipeline(
        pipeline_name="shopify", destination='filesystem', dataset_name="shopify_data"
    )

    # Load all orders from 2023-01-01 to now
    min_start_date = current_start_date = pendulum.datetime(2023, 1, 1)
    max_end_date = pendulum.now()

    # Create a list of time ranges of 1 week each, we'll use this to load the data in chunks
    ranges: List[Tuple[pendulum.DateTime, pendulum.DateTime]] = []
    while current_start_date < max_end_date:
        end_date = min(current_start_date.add(weeks=1), max_end_date)
        ranges.append((current_start_date, end_date))
        current_start_date = end_date

    # Run the pipeline for each time range created above
    for start_date, end_date in ranges:
        print(f"Load orders between {start_date} and {end_date}")
        # Create the source with start and end date set according to the current time range to filter
        # created_at_min lets us set a cutoff to exclude orders created before the initial date of (2023-01-01)
        # even if they were updated after that date
        data = shopify_source(
            start_date=start_date, end_date=end_date, created_at_min=min_start_date
        ).with_resources("orders")

        load_info = pipeline.run(data)
        print(load_info)

    # Continue loading new data incrementally starting at the end of the last range
    # created_at_min still filters out items created before 2023-01-01
    load_info = pipeline.run(
        shopify_source(
            start_date=max_end_date, created_at_min=min_start_date
        ).with_resources("orders")
    )
    print(load_info)


def load_partner_api_transactions() -> None:
    """Load transactions from the Shopify Partner API.
    The partner API uses GraphQL and this example loads all transactions from the beginning paginated.

    The `shopify_partner_query` resource can be used to run custom GraphQL queries to load paginated data.
    """

    pipeline = dlt.pipeline(
        pipeline_name="shopify_partner",
        destination='filesystem',
        dataset_name="shopify_partner_data",
    )

    # Construct query to load transactions 100 per page, the `$after` variable is used to paginate
    query = """query Transactions($after: String, first: 100) {
        transactions(after: $after) {
            edges {
                cursor
                node {
                    id
                }
            }
        }
    }
    """

    # Configure the resource with the query and json paths to extract the data and pagination cursor
    resource = shopify_partner_query(
        query,
        # JSON path pointing to the data item in the results
        data_items_path="data.transactions.edges[*].node",
        # JSON path pointing to the highest page cursor in the results
        pagination_cursor_path="data.transactions.edges[-1].cursor",
        # The variable name used for pagination
        pagination_variable_name="after",
    )

    load_info = pipeline.run(resource)
    print(load_info)


if __name__ == "__main__":
    # Add your desired resources to the list...
    resources = ["products", "orders", "customers"]
    load_all_resources(resources, start_date="2000-01-01")

    # incremental_load_with_backloading()

    # load_partner_api_transactions()

Provided you have set up your credentials, you can run your pipeline like a regular python script with the following command:

python shopify_dlt_pipeline.py

4. Inspecting your load result​

You can now inspect the state of your pipeline with the dlt cli:

dlt pipeline shopify info

You can also use streamlit to inspect the contents of your Google Cloud Storage destination for this:

# install streamlit
pip install streamlit
# run the streamlit app for your pipeline with the dlt cli:
dlt pipeline shopify show

5. Next steps to get your pipeline running in production​

One of the beauties of dlt is, that we are just a plain Python library, so you can run your pipeline in any environment that supports Python >= 3.8. We have a couple of helpers and guides in our docs to get you there:

The Deploy section will show you how to deploy your pipeline to​

  • Deploy with GitHub Actions: Automate your deployment process using GitHub Actions. Follow the detailed guide to set up and schedule your pipeline efficiently. Learn more.

  • Deploy with Airflow and Google Composer: Utilize Google Composer, a managed Airflow environment, to deploy your pipeline. The guide provides step-by-step instructions for setting up and customizing your Airflow DAG. Learn more.

  • Deploy with Google Cloud Functions: Leverage Google Cloud Functions for a serverless deployment of your pipeline. This guide walks you through the process of setting up your pipeline to run on Google Cloud's serverless environment. Learn more.

  • Explore other deployment options: Discover various other methods to deploy your dlt pipeline, including different cloud services and CI/CD tools. Learn more.

The running in production section will teach you about:​

  • Monitor your pipeline: Learn how to effectively monitor your dlt pipeline to ensure smooth operation and quick identification of issues. How to Monitor your pipeline
  • Set up alerts: Configure alerts to get notified about any issues or important events in your dlt pipeline. Set up alerts
  • Set up tracing: Implement tracing to get detailed insights into the execution of your dlt pipeline. And set up tracing

Available Sources and Resources​

For this verified source the following sources and resources are available

Source shopify​

"Shopify is an e-commerce platform offering data on customer accounts, transactions, and product listings."

Resource NameWrite DispositionDescription
customersmergeIndividuals or entities who have created accounts on a Shopify-powered online store
ordersmergeTransactions made by customers on an online store
productsmergeThe individual items or goods that are available for sale

Additional pipeline guides​

This demo works on codespaces. Codespaces is a development environment available for free to anyone with a Github account. You'll be asked to fork the demo repository and from there the README guides you with further steps.
The demo uses the Continue VSCode extension.

Off to codespaces!

DHelp

Ask a question

Welcome to "Codex Central", your next-gen help center, driven by OpenAI's GPT-4 model. It's more than just a forum or a FAQ hub – it's a dynamic knowledge base where coders can find AI-assisted solutions to their pressing problems. With GPT-4's powerful comprehension and predictive abilities, Codex Central provides instantaneous issue resolution, insightful debugging, and personalized guidance. Get your code running smoothly with the unparalleled support at Codex Central - coding help reimagined with AI prowess.