Skip to main content

Loading Data from Shopify to AlloyDB Using dlt in Python


We will be using the dlt PostgreSQL destination to connect to AlloyDB. You can get the connection string for AlloyDB from the GCP AlloyDB Console.

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.

Loading data from Shopify to AlloyDB is a crucial task for businesses looking to leverage their e-commerce data for advanced analytics and decision-making. Shopify is a comprehensive commerce platform that allows anyone to start, grow, manage, and scale a business. On the other hand, AlloyDB for PostgreSQL is a fully managed, PostgreSQL-compatible database service designed for demanding workloads, including hybrid transactional and analytical processing. Using the open-source Python library dlt, you can seamlessly extract data from Shopify, transform it as needed, and load it into AlloyDB. This process ensures that your business data is readily available in a high-performance, reliable, and scalable database environment. For more information about Shopify, visit Shopify.

dlt Key Features

  • Easy to get started: dlt is a Python library that is easy to use and understand. It is designed to be simple to use and easy to understand. Type pip install dlt and you are ready to go.
  • Scalability via iterators, chunking, and parallelization: dlt offers scalable data extraction by leveraging iterators, chunking, and parallelization techniques. Learn more.
  • Implicit extraction DAGs: Automatically handle dependencies between data sources and transformations with dlt's extraction DAGs. Learn more.
  • Automated maintenance: With schema inference, evolution, and alerts, dlt simplifies maintenance with short declarative code. Learn more.
  • Configurable normalization engine: dlt recursively unpacks nested structures into relational tables, creating a schema that evolves with source data changes. Learn more.

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 AlloyDB:

pip install "dlt[postgres]"

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 AlloyDB. You can run the following commands to create a starting point for loading data from Shopify to AlloyDB:

# 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 postgres
# 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:


You now have the following folder structure in your project:

├── .dlt/
│ ├── config.toml # configs for your pipeline
│ └── secrets.toml # secrets for your pipeline
├── shopify_dlt/ # folder with source specific files
│ └── ...
├── # 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

log_level="WARNING" # the system log level of dlt
# use the dlthub_telemetry setting to enable/disable anonymous usage data reporting, see
dlthub_telemetry = true

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

private_app_password = "private_app_password" # please set me up!
access_token = "access_token" # please set me up!

dataset_name = "dataset_name" # please set me up!

database = "database" # please set me up!
password = "password" # please set me up!
username = "username" # please set me up!
host = "host" # please set me up!
port = 5432
connect_timeout = 15

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 AlloyDB destination in our docs.

3. Running your pipeline for the first time

The dlt cli has also created a main pipeline script for you at, 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='postgres', dataset_name="shopify_data"
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='postgres', 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 =

# 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

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 =
start_date=max_end_date, created_at_min=min_start_date

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(

# 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 {
node {

# Configure the resource with the query and json paths to extract the data and pagination cursor
resource = shopify_partner_query(
# JSON path pointing to the data item in the results
# JSON path pointing to the highest page cursor in the results
# The variable name used for pagination

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:


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 AlloyDB 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: Learn how to deploy a pipeline using GitHub Actions with step-by-step instructions. Read more
  • Deploy with Airflow and Google Composer: Follow this guide to deploy your pipeline using Airflow and Google Composer. Read more
  • Deploy with Google Cloud Functions: Discover how to deploy a pipeline using Google Cloud Functions. Read more
  • Explore other deployment options: Check out various other methods to deploy your pipeline. Read more

The running in production section will teach you about:

  • How to Monitor your pipeline: Learn how to keep an eye on your pipeline's performance and health by following this monitoring guide.
  • Set up alerts: Ensure you're promptly notified of any issues or important events in your pipeline by setting up alerts.
  • Set up tracing: Gain insights into your pipeline's execution and troubleshoot issues effectively by setting 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!


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.