E-commerce
August 13, 2026
How to import QuickBooks multi level into Shopify is not the same job as posting Shopify sales into QuickBooks. Multi-level means parent items, sub-items, category trees, assemblies, price levels, and inventory sites that already live in QuickBooks Online or QuickBooks Desktop. Shopify does not store this tree like Intuit. You flatten it into products, variants, collections, locations, and metafields, then you keep the SKUs stable so that subsequent accounting syncs do not invent duplicates.
The Shopify-QuickBooks conversation of most blogs is primarily accounting: orders, payouts, fees, refunds, sales taxes, Shopify Payments, PayPal. This still counts. This is the second loop. The first, if QuickBooks is your item master, is the catalog import. Intuit's rebuilt e-commerce connectors (migration documented in 2026) still match products by SKU and by name, and do not yet offer bi-directional inventory sync. If you skip the hierarchy work, you get a Shopify store full of flat SKUs, broken kits, and accounting that never reconciles with the shelf.
This guide shows a practical path for Shopify QuickBooks integration for import: what multi-level data is, how to map it, when a CSV is enough, when a Shopify app is needed (Webgility, Connex, or a Partner build), and how to avoid mixing up catalog import and payout accounting. Shopify's POS migration docs are clear: inventory can move, but an inventory-style grid does not migrate as a grid. That is the multi-level problem in one sentence. (The Shopify Help Center often responds with an anti-bot challenge; the facts below use the already published official matrix, with no dead Help links.)
What you will clarify: the difference between importing the QuickBooks structure into Shopify and syncing sales to QuickBooks.
What you will be able to do: choose CSV vs app vs Desktop Connector, map sub-items to variants, and test inventory before enabling order posting.
To connect: Shopify integration, the e-commerce product catalog and Shopify inventory management.
Useful rule: QuickBooks remains the financial system of record. Shopify remains the sales system of record. Multi-level import is the translation layer between the two.
Summary
Is importing multi-level QuickBooks considered accounting synchronization?
Most merchants search for "connect Shopify QuickBooks" and land on an accounting setup. The query how to import QuickBooks multi level into Shopify goes the other way. You already have items in QuickBooks. You want these items, and their children, on the Shopify store so customers can buy them.
Two integrations, two owners
Catalog import (this guide): QuickBooks items, sub-items, quantities, prices, and locations become Shopify products, variants, and locations.
Accounting sync: Shopify orders, refunds, fees, taxes, and payouts become QuickBooks sales receipts, invoices, journal entries, or deposits.
If you only install the Shopify Connector by QuickBooks by Intuit, you are mostly pulling transactions into QuickBooks Online. Intuit documents product tracking (matching by SKU and name) and customer tracking, plus sales, refunds, fees, and payouts. This is not an ERP PIM that publishes a multi-level catalog. Treat the free connector as accounting automation, not as a product information manager.
When QuickBooks is the item master
Distributors, manufacturers, and multi-channel operators often create items first in QuickBooks Desktop or QuickBooks Online, then list them on Shopify, Amazon, eBay, Walmart marketplace, or Etsy. Webgility and similar tools describe this as pushing item, price, and description from QuickBooks to sales channels. If this is your model, Shopify should not become a second hand-typed list of items. Import once, map the SKUs, then let the app align descriptions and quantities.
When Shopify must remain the item master
If the Shopify store is where you add photos, SEO copy, and variants every week, keep Shopify as the catalog owner and only post sales to QuickBooks. Importing a dirty QuickBooks list into Shopify will overwrite a better storefront. Decide on the master before clicking Sync now. A sync running in the wrong direction recreates sub-items as orphan products, breaks handles, and forces support to explain two SKUs for the same hoodie.
In practice, write the rule on an internal page: who creates the item, who can change the web price, who can adjust stock. Without this, the app will do what it is designed to do, and you will pay for the cleanup in tickets and inventory discrepancies.
Convert over 2,000 customers on average per month with Qstomy.
The world’s 1st Shopify AI dedicated to customer conversion
Empowering 200+ e-commerce merchants
What does multi-level mean in QuickBooks?
“Multi-level” is not a Shopify field name. In QuickBooks, it refers to several different trees. You must name the tree you are importing; otherwise, the mapping will fail.
1. Categories and sub-categories
Intuit's import help for QuickBooks Online uses colon-separated paths like Category:Sub-category:Product, supporting up to four category levels. This is a merchandising tree. In Shopify, this usually translates to collections, tags, or a product type combined with metafields, rather than nested SKUs.
2. Items and sub-items
Desktop and many Online lists use parent items with sub-items for size, color, or finish, written as T-shirt:Large:Blue. Intuit's spreadsheet examples use one line per variation. As of June 1, 2026, QuickBooks Online no longer supports product variants on this import path; existing variants become standard products or services. The hierarchy often survives only as colon-separated names. Your Shopify import must parse these names into Option1 / Option2, rather than creating a product for each colon-separated string, unless you want a thousand near-duplicate URLs.
3. Assemblies, kits, and grouped items
QuickBooks assemblies (especially Desktop / Enterprise) break down into components for COGS. Shopify sells a finished SKU, a bundle app, or a kit. If you import the assembly as a simple inventory item, you will oversell components or hide the kit from the catalog. Webgility documents support for sub-items and assemblies on Desktop and Enterprise Advanced Inventory. Native Intuit connectors do not rebuild a bill of materials on the Shopify product page.
4. Inventory sites, classes, and warehouses
Enterprise Advanced Inventory and Desktop sites use multi-level inventory. Shopify uses locations. Shopify's QuickBooks Desktop POS migration maps stores or classes to locations, with a documented maximum of 20 locations on this connector path. Excess warehouses will require another app or a Plus location model.
5. Price levels and B2B
QuickBooks customer price levels (common in Desktop / Enterprise) do not map 1:1 to a standard Shopify retail price. Shopify Plus catalogs and company locations can carry B2B prices. On Basic, you publish a web price or use an app. Do not flatten five wholesale tiers into a single compared price.
How does Shopify store this hierarchy?
The Shopify catalog consists of products, variants, options, media, and inventory per location. A product can have up to three options. Shopify raised the variant limit from 100 to 2,048 variants per product in 2025 (GraphQL Admin API). This helps dense matrices. It does not provide a fourth option, unlimited nested categories, or native bundling. See the Shopify 2,048 variants announcement (2025).
Translation Table
QuickBooks Parent + sub-items: one Shopify product + variants (maximum of three option names).
Deep category path: product type, tags, collections, or metafields. See the e-commerce product catalog.
SKU / item number / UPC: Shopify SKU and barcode. This is the join key for all subsequent syncs.
Site / class / store: Shopify location. Inventory quantity is per location, not a single store-wide figure.
Assembly: one sellable SKU plus a bundle or BOM app, not five "required" products at checkout.
Inactive item: draft product or product excluded from the sales channel, not a live 404.
Why the SKU is Non-Negotiable
The new Intuit connectors match products by SKU and by name. Third-party apps do the same. If QuickBooks sub-items share an empty SKU, Shopify will create duplicates on every sync. Assign a unique SKU on each sheet before importing. Parent headers that are not sellable should not become a Shopify product, unless you need them as a collection landing page.
Style Grids vs. Variants
Shopify's QuickBooks Desktop POS migration documents list inventory as migratable and style grid inventory as non-migratable. A style grid is classic multi-level retail (size x color matrix). You rebuild this as Shopify options. Plan time for this rebuild. It is not a checkbox in the Desktop Connector. To create or update many variants afterwards, the 2025+ path is GraphQL: productVariantsBulkCreate and the new product model.
How to import QuickBooks items with a Shopify CSV?
A one-shot import is often the right first move: clean the list in a spreadsheet, then load Shopify. The Help Center documents the native product CSV, but this Help page often returns a 403 error. In practice, you export / import from Products in the admin, or you use the APIs. For high volume, Shopify documents GraphQL bulk imports and productCreate. Use an app later for real-time inventory, not for the messy first load.
Step-by-Step CSV Path
Export the item list from QuickBooks: Online: export products and services. Desktop: Item List report or IIF / Excel export that your accountant already uses. Include name, SKU, barcode, description, price, cost, quantity, location, tax code, and active flag.
Separate parent lines from sellable lines: Parents that only group children do not become Shopify products. Children become variant rows that share a Handle.
Parse colon names: Transform
Tee:M:Navyinto Option1 Name = Size, Option1 Value = M, Option2 Name = Color, Option2 Value = Navy. If there are four levels, fold the extra level into the title, a tag, or a metafield. Shopify only allows three options.Build the Shopify CSV: Handle, Title, Body HTML, Vendor, Type, Tags, Published, Option columns, SKU, Grams, Inventory Tracker, Inventory Qty, Inventory Policy, Price, Compare At, Taxable, Image Src, Status. One row per variant. Same Handle on each product row.
Quantities and locations: A simple CSV quantity applies to a single-location store. QuickBooks multi-site stock requires a location-aware app, or an inventory / admin import after the products exist.
Dry run on 20 SKUs: Import a small file, check the product page, the POS, and a test order. Only then import the rest in batches. Shopify enforces a daily variant upload limit (10,000 new variants per day) except on Plus.
What the CSV won't do
The CSV will not keep QuickBooks and Shopify synced in real time. It won't post payouts, Shopify transaction fees, or bank deposits. It won't explode assemblies into component deductions. It won't create B2B price lists. These are jobs for an app or Plus. The CSV is simply the translation of multi-level names into a catalog you can sell.
Which Shopify QuickBooks apps actually import a catalog?
Choose your tool by QuickBooks' direction and flavor. The Shopify App Store is full of "QuickBooks" tiles that only push orders to accounting. For a broader overview of apps, see the Shopify app ecosystem.
Intuit Shopify Connector (QuickBooks Online)
The Intuit article "Connect Shopify to QuickBooks Online" describes importing transactions into QuickBooks: sales, refunds, fees, payouts, optional product and customer tracking, start date up to one year ago, initial import taking about 10 minutes to 3 hours. Migration notes for the new e-commerce connectors add: no two-way inventory sync yet, sync occurs every few hours, imports individual transactions rather than a summary sales receipt per payout, and product matching by SKU and name. Shopify inventory sync is listed as under development. For a multi-level import to Shopify, this connector is the wrong primary tool. The App Store listing remains Shopify Connector by QuickBooks.
Shopify QuickBooks Desktop Connector
The Shopify Help path for QuickBooks Desktop integration is oriented toward POS and Stocky: tax preferences, app token, account mapping (e.g., COGS), summary vs. detailed sync for customer, inventory, and supplier, Stocky API key, same Desktop machine. POS data migration can bring customers, suppliers, inventory items, and locations into Shopify POS. Use this when you are leaving QuickBooks POS, not when you only want a cloud catalog push from QuickBooks Online Global. (No Help link here: these pages return 403 errors behind a WAF.)
Webgility
Webgility is positioned for QuickBooks Desktop / Enterprise, Advanced Inventory, sub-items, assemblies, multi-level inventory categorization, serial/lot tracking, and multi-channel (Amazon, Walmart, eBay, Etsy) plus Shopify. This matches "how to import QuickBooks multi level into Shopify" if QuickBooks Desktop is the hub. Confirm current plan limits and whether Shopify is a listing destination or just an order source. Seller claims are not Intuit documentation; test a portion of the item list.
Connex and other Shopify apps
Connex for QuickBooks (Shopify App Store) is built around rules: mapping customers, products, and orders, multi-channel including Walmart, payout matching, B2B. MyWorks and similar apps emphasize order-level posting, two-way inventory, and QuickBooks Online or Desktop. Use them when you need continuous sync after the catalog exists. Tools like A2X reconcile Shopify Payments deposits with the bank. They do not import a category tree.
Custom API
If assemblies, five pricing levels, and bin tracking must hit Shopify Plus catalogs, a Partner writes middleware: flattening matrices into variants, mapping attributes to metafields, mapping warehouses to location IDs. GraphQL product APIs are the 2025+ path for high variant counts. REST-era apps that still assume 100 variants will truncate a multi-level import. productVariantsBulkCreate and bulk operations exist for this.
How to map sub-items, assemblies, and tax codes?
Mapping is where multi-level imports succeed or create duplicate SKUs. Do it in a spreadsheet before an app runs.
Parent / Child Rules
One Handle per parent: all sub-items that customers see as options of the same product share it.
Leaf SKU only: never reuse the parent item number on a variant.
Three options budget: size, color, material: this is already the limit. A fourth QuickBooks level becomes a separate product or a metafield filter.
Images: Shopify allows up to 250 media per product. A matrix of 2,000 variants cannot have a unique photo for each variant.
Bundles and kits
Decide on the sellable unit. If QuickBooks builds "Gift Box" from SKUs A+B+C, Shopify must sell Gift Box as a product with its own SKU. The inventory deduction of A, B, and C belongs to QuickBooks or a BOM app, not as three extra lines at checkout, unless you want customers to unbundle the kit. If you import A, B, C, and Gift Box as four separate Shopify products with independent quantities, you will oversell.
Tax codes
QuickBooks tax items and Shopify tax settings are different engines, especially US vs Canada vs QuickBooks Online Global. Map the taxable flags on the product during import so the store doesn't sell exempt parts as taxable finished goods. Detailed jurisdictional posting is a later accounting sync issue, not a reason to skip the taxable box in the CSV.
Example: apparel sub-items
QuickBooks list: Hoodie, Hoodie:S:Black, Hoodie:M:Black, Hoodie:S:Grey. Shopify product title Hoodie, Option1 Size, Option2 Color, four variant lines, four SKUs. "Sweatshirts" collection from the QuickBooks category. This is a correct multi-level import. Four separate Shopify products named Hoodie S Black, no.
How to manage multi-site stock after the import?
Inventory is the reason why merchants ask for real-time sync. After the Intuit 2026 connector rebuild, official help states that you must manually update inventory levels in QuickBooks and in the e-commerce platform until bidirectional inventory is delivered. If QuickBooks sites are the warehouse truth, you need a third-party inventory sync, not hope.
Choosing a single quantity master
QuickBooks master: receiving, assemblies, and vendor bills live in Intuit. The app pushes available qty to Shopify locations. Shopify must not allow random admin stock edits.
Shopify master: DTC fulfillment and POS live in Shopify / Stocky. QuickBooks only receives COGS and sales. Do not import quantities from Desktop sites on a schedule, otherwise you will fight with the warehouse.
Location Mapping
List each QuickBooks site next to a Shopify location ID. Unmapped sites spill over into a default location and look like "doubled inventory". The Shopify POS migration allows up to 20 locations on this connector. More sites mean another integration. Transfers between sites in QuickBooks must have a corresponding Shopify transfer if Shopify sells from those locations. See efficient inventory management in Shopify and managing Shopify inventory.
Serial, Lot, and Bins
Enterprise Advanced Inventory can track serials, lots, and bins. The core Shopify catalog cannot. If you need a lot expiration date on the storefront, that is an app, not a CSV column. For most DTC brands, finished goods quantity at the location level is enough. Do not block the import waiting for bin-level storefronts that you will never show to customers.
High-Volume Stores
High-volume stores should not sync every inventory movement as a full catalog rewrite. Delta updates (SKU + location + qty) are cheaper and safer. Full item re-imports belong in the night or during real PIM changes (new sub-item, new price list).
What do Amazon, Walmart, or Etsy charge in addition to Shopify?
Multi-channel e-commerce is in the semantic neighborhood of this query for a reason. Many QuickBooks files already feed Amazon, eBay, Walmart, and Etsy. Importing this file into Shopify without channel rules will publish SKUs that you only sell on Amazon, or will create pricing conflicts.
Filter Before Publishing
Channel Flag: A QuickBooks custom field or class that means "web", "wholesale", or "Amazon only".
Shopify Sales Channel: Online Store vs POS vs unpublished. Import as draft, then publish the web subset.
Pricing per Channel: Tools like Webgility display pricing and quantity rules per channel. The native CSV only has one price column.
If Amazon is already the volume channel, read Shopify integrations with Amazon before making Shopify a second listing brain. One master item. Multiple listings. QuickBooks can be this master only if SKUs and kits remain consistent.
Desktop vs Online vs Global
QuickBooks Desktop (US and some Canada editions) still possesses the deepest inventory features: assemblies, sites, price levels. QuickBooks Online is the Intuit cloud product targeted by most App Store connectors. QuickBooks Online Global uses a different tax structure and sometimes different item features. Do not assume that a US Webgility Desktop playbook applies as-is to a Global Online company file. Confirm the app's country matrix.
When should order-level accounting synchronization be turned on?
Once the catalog is in Shopify, you still need accounting. Do not let the accounting app recreate products and destroy the hierarchy you have just built.
Order Level vs. Summary
Shopify Help for Desktop asks you to choose Summary or Detailed sync for customer, stock, and vendor. Third-party apps let high-volume stores post a daily summary while wholesale orders remain detailed at the order level. The new Intuit connectors import individual transactions rather than a sales receipt summarized by payout period. If your accountant wants bank matching at the payout level (Shopify Payments deposit vs. fees vs. refunds), that requires a payout tool plus the bank feed, not another product import.
Fees, Refunds, Taxes, Payouts
Map Shopify sales, refunds, fees, and payouts to product, contra-revenue, expense, and clearing accounts. PayPal and Shopify Payments are different clearing accounts. Mixing them is how "the integration works" but the bank never reconciles. Product tracking must match existing SKUs, not Add all unmatched Shopify titles as new QuickBooks items. That Add button is how you undo a multi-level import.
Do Not Enable Accounting Until SKU QA is Done
Catalog imported and published as draft: spot-check variants and locations.
Test order: one variant, one bundle, one taxed item, one discount.
Confirm order line SKU: matches the QuickBooks item.
Enable auto-post or a review queue: depending on volume and current connector behavior.
Manual entry is what you are trying to kill. A connector that creates a new item named "Hoodie - M / Black" next to your existing "Hoodie:M:Black" is worse than typing. Lock matching rules on the SKU.
What breaks a QuickBooks to Shopify import?
Here are the breakdowns that appear after a successful "Shopify QuickBooks setup".
Import and Mapping
Every sub-item became its own product: colon-separated names were not parsed into options.
Missing style grid: expected: Shopify Help says the grid does not migrate. Rebuild the variants.
Duplicate SKUs: empty QuickBooks SKUs or the accounting app auto-creating items.
Doubled quantity: two locations mapped to one, or CSV qty plus app qty.
Assembly overselling: components and finished goods both sellable with independent stock.
More than three options: QuickBooks matrix wider than the Shopify option limit.
App still on the 100-variant REST limit: truncated import. A GraphQL-capable connector is required.
Sync and Accounting
Drifting stock after January 2026: Intuit documents the absence of two-way stock on new connectors. Use a dedicated stock app or accept double entry.
Queue / review required: some merchants report that rebuilt connectors require transaction review. Check the Integration transactions screen in QuickBooks Online before assuming auto-post.
Missing PayPal orders: some native setups are more robust on Shopify Payments. Confirm gateway coverage.
Sales tax collapsed into one line: jurisdictional detail is often limited. Talk to the accountant before promising Avalara-level splits.
Desktop token on the wrong PC: Shopify requires the Desktop Connector workflow on the machine running QuickBooks.
How to fix without another full import
Export Shopify products, join to QuickBooks on the SKU, fix Handles and option columns, reimport with "overwrite products with matching handles" only on the SKUs you want to fix. Do not trigger a blind full sync from QuickBooks again, otherwise you will recreate duplicates. For ongoing errors, open the app's unmatched-product report, not the Shopify admin search.
How to support buyers after a multi-level catalog?
A clean multi-level import still leaves customers asking operational questions that the catalog cannot answer in a banner: which warehouse is shipping, whether a kit includes the charger, if the B2B SKU matches the invoice. These questions hit support while finance is still mapping payouts. An assistant on the Shopify store must read the same SKUs that you imported, not a second unofficial list.
To be answered before checkout, not in QuickBooks
Availability by location: especially after mapping sites to Shopify locations.
Kit contents: the assembly that the buyer does not see in a variant selector.
Lead time: when the QuickBooks quantity is on order, not in stock.
SKU identity: wholesale buyers citing the QuickBooks item number.
Example: wholesale hardware brand
A US brand kept QuickBooks Desktop as their item master, with sub-items for size and finish and assemblies for parts kits. They flattened the sub-items into Shopify variants via Webgility, kept kits as single SKUs, and left the accounting to an app detailed at the order level. The storefront chat was still receiving "is the 14 mm in the kit?" because the BOM never belonged to the PDP. Qstomy answered from product metafields (kit contents, location, SKU) so support wouldn't have to open QuickBooks during the sales conversation. It is complementary to Shopify integration, an AI sales assistant and AI customer support, not an Intuit replacement.
If catalog questions are still leaking into tickets after the import, book a Qstomy demo. Don't ask a chatbot to be your ledger.
Checklist, sources and FAQ
Pre-Live Checklist
Name the master: QuickBooks or Shopify for items. Only one.
Inventory the trees: categories, sub-items, assemblies, sites, price levels.
SKU every leaf: no blanks, no reused parent SKU.
Map to a maximum of three options: extra levels to metafields or split products.
Choose the pipeline: CSV one-shot, Desktop Connector / Stocky for POS, Webgility / Connex / custom for continuous multi-level Desktop, Intuit connector for QBO accounting.
Dry-run 20 SKUs: including one kit and two locations if you have them.
Lock product matching to SKU: disable auto-creation in the accounting app.
Turn on order posting last: fees, refunds, taxes, payouts mapped with the accountant.
Document the quantity master: who has the right to edit stock where.
Train support on SKUs: same identifiers on PDP, packing slip, and QuickBooks.
In brief
How to import QuickBooks multi level into Shopify: flatten Intuit trees into products, variants, collections, and locations.
Style grids and deep sub-items: not a native 1:1 migration. Rebuild options. Shopify Help states that the POS style grid does not migrate.
Intuit 2026 Connector: powerful for pulling Shopify sales into QuickBooks Online, not for bi-directional inventory or publishing a hierarchy.
CSV then app: clean the catalog once, then automate inventory and orders.
Never let the accounting software auto-create items: otherwise you undo the import.
External sources
Shopify: announces 2,048 product variants (2025).
Shopify Dev: productCreate ; productVariantsBulkCreate ; imports bulk ; new GraphQL product model.
Apps and tools: Shopify Connector by QuickBooks ; Connex for QuickBooks ; Webgility.
Intuit and Help Center: facts detailed in prose (SKU matching, no bi-directional stock yet, QBO variants retired by June 1, 2026, non-migratable POS style grid, limit of 20 locations on this connector). Intuit learn-support pages timeout; Shopify Help returns 403. No dead hrefs.
FAQ
How do I import multi-level QuickBooks data into Shopify accurately?
Export items, keep unique SKUs on each sub-item, parse parent/child names into Shopify options (three max), map sites to locations, import via CSV or a Desktop/Enterprise capable app, then test before enabling order sync.
What are the best tools for integrating QuickBooks with Shopify?
For accounting to QuickBooks Online: the Intuit connector, then a specialist app if you need inventory, PayPal, or custom posting. For multi-level Desktop catalogs: Webgility, Connex, or a custom API, plus the Shopify Desktop Connector when you are on POS and Stocky. For payouts: a payout reconciler, not a catalog tool.
Can the integration handle complex accounting structures or multi-level data?
The accounting structure (sub-accounts, classes) remains in QuickBooks. Multi-level items become Shopify variants and metafields. Assemblies and price levels typically require Desktop/Enterprise apps or Plus catalogs. The free Online connector does not rebuild a style grid.
How do I automate syncing and reconciliation between Shopify and QuickBooks?
After SKU matching, turn on order or summary-level posting, map fees, refunds, taxes, and payouts, and choose an inventory master. Intuit 2026 Notes: no bi-directional inventory yet, sync occurs every few hours. Use a third party if you need near real-time inventory.
What are common issues during integration and how can I fix them?
Duplicate auto-created items, unparsed sub-items, doubled quantities, kits sold as single parts, and style grids never migrated. Correct this with SKU matching, a mapping sheet, and a small re-import. See also the Shopify app ecosystem.
Going further
Catalog model: What is an e-commerce product catalog
Inventory ops: Managing inventory in Shopify
Amazon channel: Shopify and Amazon inventory
Import the hierarchy once, lock the SKUs, then automate. If buyers still cannot distinguish a kit from a single part, fix the PDP and helper text, not the general ledger. See Qstomy on a Shopify catalog.
Enzo
August 13, 2026
