Load Shopify data into Databricks
Send Shopify orders, customers, products and payments to Databricks with OWOX Data Marts: one table per endpoint in your catalog, a readable schema, a scheduled refresh. Join them with accounting data to see where revenue figures differ.
ShopifyConnectedAbandoned Checko…Article Metafiel…ArticlesBlog Metafields
DatabricksIdAband…Compl…Daily 09:00Shopify Endpoints
25 Shopify endpoints you can import. Each lands in its own table in your data warehouse.
Abandoned Checkouts
Checkout sessions that did not complete — customer info, items, and pricing for recovery campaigns.
20 fieldsTime seriesArticle Metafields
Custom metadata attached to articles — namespace, key, value, and type.
9 fieldsArticles
Blog articles — title, author, publication status, and timestamps.
15 fieldsBlog Metafields
Custom metadata attached to blogs — namespace, key, value, and type.
9 fieldsBlogs
Blogs in the store — title, handle, and template settings.
6 fieldsCollection Metafields
Custom metadata attached to collections — namespace, key, value, and type.
9 fieldsCollections
Product collections — title, sort order, product count, and last updated.
10 fieldsCustomer Metafields
Custom metadata attached to customers — namespace, key, value, and type.
9 fieldsCustomers
Customer accounts — contact info, marketing consent, order history, and lifetime spend.
22 fieldsTime seriesDiscount Codes
Discount codes — type, status, usage limits, and validity window.
12 fieldsFulfillment Orders
Fulfillment orders — items to ship, assigned location, delivery method, and status.
11 fieldsInventory Items
Inventory items (SKUs) — tracking status, shipping requirements, and country of origin.
9 fieldsLocation Metafields
Custom metadata attached to locations — namespace, key, value, and type.
9 fieldsLocations
Physical and virtual store locations — activity status, fulfillment capabilities, and address.
19 fieldsOrder Metafields
Custom metadata attached to orders — namespace, key, value, and type.
9 fieldsOrders
Orders placed in the store — financial and fulfillment status, customer info, totals, and timestamps.
96 fieldsTime seriesPage Metafields
Custom metadata attached to pages — namespace, key, value, and type.
9 fieldsPages
Static store pages — title, handle, publication status, and timestamps.
10 fieldsProduct Metafields
Custom metadata attached to products — namespace, key, value, and type.
9 fieldsProduct Variant Metafields
Custom metadata attached to product variants — namespace, key, value, and type.
9 fieldsProduct Variants
Product variants — SKU, price, inventory quantity, and availability.
18 fieldsProducts
Products in the store catalog — vendor, type, status, inventory, and price range.
21 fieldsTime seriesShop
Store settings — domain, currency, timezone, and plan details.
20 fieldsShop Metafields
Custom metadata attached to the shop — namespace, key, value, and type.
9 fieldsTender Transactions
Payment tender transactions — amount, currency, order reference, and processing time.
7 fields
Why join Shopify with accounting and ad data in Databricks
Ask what revenue was last month: Shopify gives one number and the accounting system another. Refunds, discounts, taxes, currencies and payment timing each move the figure. To see where they differ, load both into one warehouse.
- Reconcile Shopify orders with accounting records in SQL
- Split gross sales from discounts, refunds and cancellations
- Set daily orders beside daily ad spend
ShopifyOrders, refundsYour data warehouseShopifyAccountingAd spendJoined by idOrder placedRevenue reportedOne query shows where they differ.Step 1: Connect Shopify and choose what to load
Create a Data Mart, choose Shopify as the source, add your shop domain and Admin API access token, open an endpoint and tick only the fields you need.
- 25 endpoints and 337 fields to choose from
- Orders alone has 47 fields: totals, discounts, refunds, status, customer
Google AdsShopify
TikTok AdsAuthorizeConnectedEndpointOrdersAbandoned Checkou…Article MetafieldsArticlesOrderscreatedAttotalPricetotalDiscountstotalRefundedcurrencyCodedisplayFinancialStatusStep 2: Load Shopify into Databricks tables
The catalog defaults to main, and the schema and table are pre-filled; change any of them. Run it and the first load lands in your own Databricks workspace.
- Each endpoint gets its own table, not one table for the whole store
- Every run is logged in Run History
DestinationCatalogmainSchemashopifyTableordersRunTablemain.shopify.ordersStep 3: Open the output schema in plain words
The first run gives you the output schema: every field with an alias and a readable description, not an API identifier. Your quality checks can read it too.
- Descriptions say what a field holds, for example the total amount refunded
- Finance and marketing read the same column names
main.shopify.ordersOutput schemaFieldDescriptioncreatedAtThe date and time when the…totalPriceThe total price of the order.totalDiscountsThe total discounts applied.totalRefundedThe total amount refunded.currencyCodeThe currency of the order.displayFinancialStatusThe financial status of the…Step 4: Keep the Shopify tables linked
Customers, orders and payment transactions stay separate tables, joined by ids. In SQL they become one Shopify model, ready to join to accounting.
- Orders carry customerId; tender transactions carry orderId
- Add accounting, ad spend and web analytics tables to the same model
CustomersiddisplayNamenumberOfOrdersOrdersidcustomerIdtotalPriceTender Transactio…orderIdamountprocessedAtStep 5: Refresh on a schedule and backfill the history
Set it once. A scheduled refresh keeps the Databricks tables current, and a manual run loads a past period of your choice.
- Daily runs with no pipeline to maintain
- Backfill order history the first time you connect
Step 6: Reuse the Databricks tables in every tool
One set of tables feeds your model, , , assistants like Claude and ChatGPT and AI insights in Slack or email.
- Define revenue once
- Every report reads the same table
ShopifyData MartPublished
Google Sheets
Data Studio dashboards
Claude, ChatGPT
Slack, email
- 0.43.0Compare LinkedIn Ads results across markets: spend by country, region, and county
- 0.43.0The Sheet link of a Google Sheets source opens the imported tab, not the first one
- 0.43.0Connect a Google Sheets plan with one Google sign-in
- 0.41.0Rotating a warehouse key is one change: Storages share reusable Credentials
- 0.41.0Dates from Google Sheets arrive as dates, not text
Why OWOX for Shopify in Databricks
Notebooks over the Admin API and generic ETL tools get orders in. OWOX also keeps them in your tables, readable and ready to join to accounting.
- You own the data. It lands in your own Databricks workspace, in tables you control.
- An endpoint per table. Orders, customers and payment transactions each load on their own, not as one table for the whole store.
- Described columns. Fields say what they hold, for example the total amount refunded.
- Joined by customer and order ids. Ready to meet accounting, ad spend and web analytics.
- Maintained for you. No jobs to repair when Shopify changes its API.
- Free to self-host. The open-source OWOX Data Marts runs in your own infrastructure.
You are booked. The invitation is on its way to , with the calendar invite and the meeting link.