Skip to main content
Shopify is a leading e-commerce platform for creating and managing online stores. Connecting Shopify to Nekt lets you centralize core commerce data—orders, products, customers, inventory, collections, and locations—sourced from the Shopify Admin API. With near real-time incremental syncs and consistent schemas, you can join Shopify with marketing, finance, and operations data to drive end-to-end analytics like revenue performance, cohort behavior, merchandising impact, inventory health, and fulfillment efficiency.

​
Configuring Shopify as a Source

In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Shopify option from the list of connectors. Click Next and you’ll be prompted to add your access.

​
1. Add account access

You’ll need a Shopify Admin API access token and your store identifier.
  • Access Token: The private app access token for authenticating API requests.
  • Store ID: The name of your Shopify store extracted from your store admin URL. Use only the store subdomain: https://[store].myshopify.com/admin → Store ID = [store].
  • Start Date: The earliest record date to sync.
To generate your Shopify token:
  1. Go to your Shopify admin panel
  2. Navigate to Settings → Apps and sales channels
  3. Click on “Develop apps” (or “Manage private apps” for older stores)
  4. Create a new app or select an existing one
  5. Grant the following API permissions as needed for these streams:
    • read_customers
    • read_inventory
    • read_locations
    • read_orders
    • read_products
  6. Go to API Credentials and generate an access token

​
2. Select streams

Choose which data streams you want to sync - you can select all streams or pick specific ones that matter most to you.
Tip: The stream can be found more easily by typing its name.
Select the streams and click Next.

​
3. Configure data streams

Customize how you want your data to appear in your catalog. Select a name for each table (which will contain the fetched data) and the type of sync.
  • Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix and make this process faster!
  • Sync Type: you can choose between INCREMENTAL and FULL_TABLE.
    • Incremental: every time the extraction happens, we’ll get only the new data - which is good if, for example, you want to keep every record ever fetched.
    • Full table: every time the extraction happens, we’ll get the current state of the data - which is good if, for example, you don’t want to have deleted data in your catalog.
Once you are done configuring, click Next.

​
4. Configure data source

Describe your data source for easy identification within your organization, not exceeding 140 characters. To define your Trigger, consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times). Optionally, you can determine when to execute a full sync. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while. Once you are ready, click Next to finalize the setup.

​
5. Check your new source

You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.
For you to be able to see it on your Catalog, you need at least one successful source run.

​
Streams and Fields

Below you’ll find all available data streams from Shopify and their corresponding fields:
Stream containing abandoned checkouts.Key Fields:
  • id - Unique identifier for the abandoned checkout
  • abandonedCheckoutUrl - URL for the abandoned checkout
  • createdAt, updatedAt, completedAt - Timestamps
  • taxesIncluded - Whether taxes are included
Price Sets:
  • subtotalPriceSet.presentmentMoney.amount, subtotalPriceSet.presentmentMoney.currencyCode
  • totalPriceSet.presentmentMoney.amount, totalPriceSet.presentmentMoney.currencyCode
  • totalTaxSet.presentmentMoney.amount, totalTaxSet.presentmentMoney.currencyCode
  • totalDiscountSet.presentmentMoney.amount, totalDiscountSet.presentmentMoney.currencyCode
Customer:
  • customer.id, customer.firstName, customer.lastName, customer.email
  • customer.tags, customer.state, customer.note
  • customer.createdAt, customer.updatedAt
Addresses:
  • billingAddress.* - Address lines, city, province, country, zip, phone
  • shippingAddress.* - Address lines, city, province, country, zip, phone
Line Items:
  • lineItems[].id, title, sku, quantity
  • lineItems[].variant.id, lineItems[].variant.price
Taxes and Discounts:
  • discountCodes[]
  • taxLines[].rate, taxLines[].title, taxLines[].priceSet.presentmentMoney.amount, currencyCode
Stream containing product collections and included products.Key Fields:
  • id, title, handle, description
  • publishedAt, updatedAt
Image:
  • image.altText, image.originalSrc
Products:
  • products[].id, title, handle, createdAt, updatedAt
  • productType, vendor, tags, totalInventory, status, price, inventoryQuantity
  • variants[].id, title, sku, price, inventoryQuantity
Sorting and Template:
  • sortOrder, sortType, sortValue, templateSuffix, url
Metafields:
  • metafields[].id, namespace, key, value, type, description
Stream containing customer profiles.Key Fields:
  • id, firstName, lastName
  • createdAt, updatedAt
  • verifiedEmail, taxExempt, tags, state
  • numberOfOrders
Spend and Contacts:
  • amountSpent.amount, amountSpent.currencyCode
  • defaultEmailAddress.emailAddress, defaultEmailAddress.marketingState
  • defaultPhoneNumber.phoneNumber, defaultPhoneNumber.marketingState, defaultPhoneNumber.marketingCollectedFrom
Addresses:
  • addresses[].id, firstName, lastName, address1, city, province, country, zip, phone, name, provinceCode, countryCodeV2
  • defaultAddress.* - Same structure as addresses
Metafields:
  • metafields[].id, namespace, key, value, type, description
Stream containing inventory items, levels and costing information.Key Fields:
  • id, legacyResourceId, sku, tracked
  • countryCodeOfOrigin, provinceCodeOfOrigin, harmonizedSystemCode
  • duplicateSkuCount, inventoryHistoryUrl
Country HS Codes:
  • countryHarmonizedSystemCodes[].countryCode, harmonizedSystemCode
Inventory Levels:
  • inventoryLevels[].id
  • inventoryLevels[].location.id, inventoryLevels[].location.name
  • inventoryLevels[].item.id, inventoryLevels[].item.sku
  • inventoryLevels[].quantities[].id, name, quantity, updatedAt
Counts and Measurements:
  • locationsCount.count
  • measurement.weight.unit, measurement.weight.value
Cost and Variant:
  • unitCost.amount, unitCost.currencyCode
  • variant.id, variant.title, variant.sku
  • variant.product.id, variant.product.title
Timestamps:
  • createdAt, updatedAt
Stream containing store locations.Key Fields:
  • id, name, active, activatable, deactivatable, deletable
  • createdAt, updatedAt, deactivatedAt
  • addressVerified, isFulfillmentService
Fulfillment Service:
  • fulfillmentService.id, fulfillmentService.serviceName
Address:
  • address.address1, address.address2, city, country, countryCode, province, provinceCode, zip
Metafields:
  • metafields[].id, namespace, key, value, type, description
Stream containing orders, transactions and line items.Key Fields:
  • id, name, legacyResourceId, email, phone
  • processedAt, createdAt, updatedAt, cancelledAt, closedAt, confirmed
  • currencyCode, presentmentCurrencyCode
Transactions:
  • transactions[].id, kind, status, gateway, authorizationCode, test, paymentId, createdAt, processedAt
  • transactions[].amountSet.presentmentMoney.amount, currencyCode
  • transactions[].amountSet.shopMoney.amount, currencyCode
  • transactions[].parentTransaction.id
Totals:
  • totalPriceSet.shopMoney.amount, currencyCode
  • totalPriceSet.presentmentMoney.amount, currencyCode
  • subtotalPriceSet.*, totalShippingPriceSet.*, totalDiscountsSet.*, totalTaxSet.* (both shopMoney and presentmentMoney)
  • totalWeight, taxesIncluded, taxExempt
Statuses and Flags:
  • displayFinancialStatus, displayFulfillmentStatus
  • fullyPaid, fulfillable, restockable, test, customerAcceptsMarketing
  • sourceName, sourceIdentifier, currentSubtotalLineItemsQuantity
  • tags, note, clientIp
Customer and Addresses:
  • customer.id, firstName, lastName, email
  • shippingAddress.*, billingAddress.*
Discounts and Metafields:
  • discountCode, discountCodes[]
  • metafields[].id, namespace, key, value, type, description
Sales Channel:
  • channelInformation.channelDefinition.handle
Line Items:
  • lineItems[].id, title, quantity, sku, vendor, variantTitle
  • lineItems[].discountedTotalSet.*, originalTotalSet.*
  • lineItems[].discountAllocations[].allocatedAmount.amount, currencyCode
  • lineItems[].discountAllocations[].discountApplication.*
  • lineItems[].variant.id, title, sku, product.id, product.title
Stream containing products, variants, images and metafields.Key Fields:
  • id, title, descriptionHtml, vendor, productType
  • createdAt, updatedAt, publishedAt, status, tags, templateSuffix
Options:
  • options[].id, name, position, values[]
Variants:
  • variants[].id, title, sku, price, position, inventoryPolicy, compareAtPrice, createdAt, updatedAt, taxable, barcode
  • variants[].inventoryItem.id
Images:
  • images[].id, altText, originalSrc
  • featuredImage.id, featuredImage.altText, featuredImage.originalSrc
Metafields:
  • metafields[].id, namespace, key, value, type, description