This guide explains how to connect Shopify to Sanka, what the integration can update, and what to check before importing orders, syncing items, or updating inventory across stores.
What the integration supports
Use the Shopify integration when Shopify is the storefront and Sanka manages the back-office records behind sales, inventory, fulfillment, and operations. Depending on your workspace setup, the integration can help with:
Importing Shopify orders into Sanka orders
Importing or exporting Shopify products as Sanka items
Syncing inventory quantities between Sanka locations and Shopify locations
Importing or exporting customer and contact data
Running Sanka actions or workflows after Shopify orders, items, or inventory records meet your team's conditions
Keeping multiple Shopify stores or sales channels aligned through SKU, platform ID, and location mapping
Connecting Shopify does not automatically sync every product, order, customer, or inventory level. Confirm the selected store, object, mapping, sync direction, SKU or platform ID matching rule, and workflow conditions before treating a missing update as a product bug.
Sample prompt
/sanka Review this Shopify and Sanka record before making any changes. Confirm the store, matching item or order, SKU, platform ID, Shopify location, Sanka location, sync direction, required fields, and any action or workflow that should run. Do not import, export, update inventory, or create downstream records until I approve the plan.
Expected behavior
After the connection succeeds, Shopify appears on the Sanka integrations page. Orders, items, contacts, and inventory update only when the relevant import, export, sync, webhook, action, or workflow is configured and run.For a healthy Shopify setup:
Sanka records keep source details back to the Shopify store and record
Shopify products match Sanka items by the configured platform ID, SKU, or mapping rule
Inventory updates use the correct Sanka location and Shopify location
Imported orders include customer, line item, amount, currency, status, and source information
Downstream records such as inventory transactions, picking work, invoices, or tasks are created only when the relevant action or workflow runs
Import, export, action, workflow, and audit histories show what changed and when
If your team expects automatic order import, product sync, or inventory updates, check the workflow or integration action that should perform that step. The Shopify connection alone does not bypass missing SKU mappings, location mappings, disabled workflows, required fields, or store permissions.
Connect Shopify
Log in to Sanka and confirm you are in the workspace that should connect to the Shopify store.
In Sanka, open Workspace > Integrations.
Click Create Integration.
In the integration drawer, search for or select Shopify.
Select Standard, then click Create Integration.
When prompted, connect the Shopify store and approve access.
After authorization, Sanka redirects you back to the integrations page. Confirm the Shopify store appears in the list.
Open the Shopify integration drawer to review connection details and available actions.
Prepare item and inventory mapping
Before syncing products or inventory, confirm the item and location rules:
Use a stable SKU or Shopify platform ID to match Shopify products to Sanka items
Confirm each Shopify location maps to the correct Sanka location
Decide whether Sanka or Shopify is the source of truth for product names, variants, prices, and stock quantities
Review required item fields before exporting new products from Sanka to Shopify
Run a small test sync before syncing all items or all stores
For multi-store operations, use one store as the reference source first, then map the other stores through SKU, platform ID, and location rules. Do not run a broad multi-store inventory sync until duplicate SKUs, missing variants, and location differences have been reviewed.
Troubleshooting
Shopify is connected but orders or items are missing
Check the selected store, import or sync action, date range, object type, store permissions, and import history. If the records came from a workflow or webhook, confirm the workflow is enabled and the triggering event occurred.
Inventory quantity is wrong
Compare the Shopify location, Sanka location, SKU, platform ID, and the latest inventory transaction history. A product can exist in both systems but still update the wrong quantity if the location mapping or SKU matching rule is wrong.
Duplicate products or customers were created
Review the matching rule before rerunning import or export. Duplicates often happen when SKU, platform ID, email, or another matching field is missing or inconsistent across stores.
Product updates did not reach Shopify
Confirm whether the action was import, export, or sync. Then check required Shopify product fields, variant data, inventory tracking settings, store permissions, and action history.
A downstream order, picking task, invoice, or inventory transaction was not created
Check whether the required Sanka action or workflow is enabled and whether the Shopify order matched its conditions. Treat this as a configuration issue until the order, workflow history, and action history show that the step should have run.
Checkpoints
Use Sanka records, import history, action history, workflow history, inventory transactions, and audit logs to confirm what happened before replying to a customer or asking AI to make a code change.
2Imported Shopify order2026/05/10 13:15Green Salon Group orderCreated draft order from Shopify order after mapping reviewSanka integration
1Checked inventory workflow2026/05/10 13:25Inventory allocation workflowConfirmed inventory transaction conditions before reserving stockSanka user
A safe review should include the Shopify store, Sanka record, SKU or platform ID, location mapping, sync direction, import/export history, and any downstream inventory or order workflow.
Sanka and Shopify work best when the store, SKU or platform ID, location mapping, sync direction, and downstream workflow are explicit. Before changing production data, review the mapping and history so support replies and AI-assisted fixes match the expected behavior.
