Connection flow
OAuth 2.0 with provider account discovery. Customers choose from accounts returned by the provider rather than entering an unverified inventory endpoint.
Shopify connector for governed marketing data.
Connect Shopify orders, order lines, refunds, fulfillments, carts, catalog, inventory, and payment transactions to governed commerce datasets. This page is generated from the same customer catalog, source schemas, live-fetch classifier, semantic contracts, and export registry used by the product.
7Available, live-fetch-ready reports
324Verified report-field definitions
SemanticPublished semantic tier
Setup and fit
What the Shopify connection proves.
Registration alone is not enough for this page. The connector must be customer-discoverable, OAuth based, connectable at runtime, and backed by non-placeholder fetch implementations.
Best for
Commerce teams that need revenue, refund, fulfillment, inventory, and payment evidence at declared business grains.
Semantic coverage
6 declared base entities across the published reports: Checkout, Fulfillment, Order Line, Payment Transaction, Product Variant, Refund.
ConnectableConnection provider and at least one live fetcher are registered.
7 availableHidden, planned, deferred, and catalog-unlisted reports are excluded.
3 eligible datasetsEvery listed report passes the query and export registry contract checks; customer rollout is still gated.
Report contract
Supported Shopify reports, entities, and grains.
The grain column is the declared uniqueness contract for a report row. A semantic tier includes a base entity and full semantic contract; a basic tier defines a safe report grain and common mappings without promising complete relationships.
| Report | What it contains | Tier / entity | Declared grain | Field contract |
|---|---|---|---|---|
Cart and checkout eventscommerce_cart_events |
Abandoned checkout lifecycle events for cart and checkout exploration. These values are not completed order revenue. | Semantic Checkout |
event_idTime key: event_date |
28 schema fields 24 report fields export-visible |
Fulfillments and shipping operationscommerce_fulfillments |
Fulfillment orders, fulfillment status, carrier, tracking company, location, and fulfilled quantities. Raw tracking numbers are not exposed. | Semantic Fulfillment |
provider_account_id, fulfillment_date, fulfillment_id, fulfillment_event_idTime key: fulfillment_date |
33 schema fields 26 report fields export-visible |
Orders and product salescommerce_sales |
Orders, order lines, revenue, discounts, refunds, tax, shipping, products, variants, and attribution fields. | Semantic Order Line |
order_id, order_line_idTime key: Not part of the uniqueness grain; report date fields remain available |
152 schema fields 69 report fields export-visible |
Payment transactionspayment_transactions |
Shopify transaction and gateway fee facts used for Commerce Intelligence payment-fee readiness. | Semantic Payment Transaction |
provider_account_id, transaction_idTime key: date |
41 schema fields 40 report fields export-visible |
Product catalogproduct_catalog |
Latest product, variant, SKU, status, category, brand, price, and catalog metadata snapshots. | Semantic Product Variant |
snapshot_date, product_id, product_variant_idTime key: snapshot_date |
29 schema fields 28 report fields export-visible |
Product inventoryproduct_inventory |
Latest inventory quantities by product variant and location. | Semantic Product Variant |
snapshot_date, provider_account_id, product_variant_id, location_id, inventory_level_idTime key: snapshot_date |
25 schema fields 23 report fields export-visible |
Refunds and returnscommerce_refunds |
Refund and return event analytics for timing, status, reason, and operational refund amounts. These event amounts do not redefine net sales. | Semantic Refund |
refund_date, refund_idTime key: refund_date |
16 schema fields 15 report fields export-visible |
Export contract
Modeled outputs, with blocked fields kept blocked.
Export eligibility is not inferred from a connector page. The generator resolves each report through the query catalog and requires a registry contract with allowlisted default columns and modes. Eligibility does not mean a destination or production export is enabled for a customer.
commerce
Public dataset contract covering 4 supported reports on this connector.
Eligibility134 report-field definitions are marked export-visible; 30 default columns pass the dataset registry policy.
ModesSource Replication, Source Replication With Semantic Views are contract-eligible, subject to destination support and rollout gates.
ReportsCart and checkout events, Fulfillments and shipping operations, Orders and product sales, Refunds and returns
payment
Public dataset contract covering 1 supported report on this connector.
Eligibility40 report-field definitions are marked export-visible; 48 default columns pass the dataset registry policy.
ModesSource Replication, Source Replication With Semantic Views are contract-eligible, subject to destination support and rollout gates.
ReportsPayment transactions
product_catalog
Public dataset contract covering 2 supported reports on this connector.
Eligibility51 report-field definitions are marked export-visible; 36 default columns pass the dataset registry policy.
ModesSource Replication, Source Replication With Semantic Views are contract-eligible, subject to destination support and rollout gates.
ReportsProduct catalog, Product inventory
Truthful limitations
What this page does not promise.
A static contract page documents implemented product boundaries. It is not evidence that a specific tenant credential has permission to every provider account, that an upstream API is currently healthy, or that every provider field is publishable.
Provider-specific boundary
Refund events do not redefine net sales, abandoned checkout values are not completed-order revenue, and raw tracking numbers are not exposed. Payment payouts are omitted because live fetching is deferred.
Export rollout remains gated
Registry eligibility is not customer enablement. Destination support, deployment rollout, plan entitlement, tenant and account scope, date behavior, selected-field validation, PII policies, provider-native restrictions, and raw-payload blocks still apply.
Runtime evidence, not a blanket SLA
“Live-fetch ready” means the implementation is not a detected placeholder. It does not replace provider permissions, production smoke evidence, upstream API limits, or plan entitlement checks.
Related diagnostics
Use the contract to explain the numbers.
Connector availability is only the first question. These guides show how definitions, identifiers, attribution, time, currency, and report grain can still create different answers.
Shopify vs. GA4 revenue
Match order and transaction IDs before comparing a deliberately shared revenue basis.
Meta conversions vs. Shopify orders
Keep observed orders and platform-attributed purchase events as separate facts.
Connector FAQ
Common Shopify connector questions.
These answers use the same verified contract data as the report table and the page’s structured data.
What Shopify data can Metric Hive load?
Metric Hive exposes 7 reviewed, live-fetch-ready Shopify reports. The exact reports, entities, grains, fields, and semantic tiers are listed on this page.
Does the Shopify connector use a semantic layer?
The published reports use the semantic tier. Semantic reports declare a base entity and complete semantic contract; basic reports declare a safe grain and common mappings without claiming complete relationship metadata.
Can I export modeled Shopify data?
Each report on this page passes the query and export registry eligibility checks. That does not prove a destination is enabled for a customer: plan entitlement, destination support, rollout gates, tenant scope, and field policies still apply.
Inspect the contract, then connect your account.
Browse the full connector catalog, review canonical semantic definitions, or check pricing before starting an OAuth connection. Provider setup guidance is presented during the connection flow.