Inventory & Stock Quantities

Why Inventory & Stock Quantities needs Custom Migration

Inventory may involve warehouses, locations, or variant-level quantities the default migration does not mirror. Custom Migration for inventory & stock quantities adjusts stock export/import so on-hand counts and availability flags match operations on the target cart.

Who this customization is for

• Multi-location / multi-warehouse merchants
• Teams syncing stock from ERP or 3PL as system of record
• Catalogs with variant-level quantities and backorder rules
• Stores planning a stock freeze or delta remigration at go-live

Common use cases

• Multi-location inventory mapped from a single source quantity
• Variant-level stock tied to the correct option combination
• Backorder, continue-selling, or out-of-stock flag differences by platform
• Filtered stock updates when only part of the catalog should sync
• Pre-launch inventory freeze / delta update strategies around go-live

What Cart2Cart customizes

We define quantity sources, location mapping, and availability rules, then verify sample SKUs against your WMS or spreadsheet of truth before Full Migration.

Platform considerations

Shopify locations, Magento MSI, and Woo stock management expose different levers. Custom Migration maps your operational model onto what the target can store.

Note: The Target platform may require installing additional apps, plugins, or add-ons when a capability is not available by default. Custom Migration can map and import the data, but those Target-side apps/plugins often need to be installed and configured so the feature works in admin and on the storefront.

The best way to make sure everything is mapped correctly is to run a Demo Migration with your real Source platform data, then carefully check how entities look on the Target store before Full Migration.

Checklist for evaluating this customized migration

• Clarify the system of record for stock (cart, ERP, 3PL, spreadsheet).
• Map single vs multi-location quantities to the target model.
• Confirm backorder / continue-selling / out-of-stock flag behavior.
• Plan freeze or delta remigration around go-live.
• Reconcile sample SKU quantities against ops data after Demo.

How to apply for this customization

1. Visit Custom Migration or schedule a call.
2. Explain platforms and whether you use multi-location inventory.
3. Provide how stock is maintained today (cart only, ERP, 3PL).
4. We design stock rules, test on Demo products, then apply them at Full Migration / remigration.

Self-service Additional Options vs Custom Migration

Stock quantities usually travel with products/variants. One Wizard option adjusts quantities for testing. Custom Migration covers multi-location, ERP-of-record, and go-live freeze/delta strategies.

• Change products quantity to 100 on Target Store — Self-service: Set Target quantities to 100 (useful for storefront testing) via the Wizard. Choose Custom Migration when: Custom Migration for real multi-location inventory, backorder flags, and operational reconciliation—not test overrides.

Availability depends on your Source → Target pair—confirm checkboxes in the Migration Wizard Entities / Additional Options step. See the Additional Options guide and Additional Options FAQ for pair-specific details. If Wizard options are not enough, schedule a Custom Migration call.

Already ran a self-service migration?

Yes—you can still apply this Custom Migration after a Wizard (self-service) run. Cart2Cart can restart migration with the customized rules; the Target store typically needs Clear current data on Target Store before Migration (or an equivalent cleanup of the entities from the previous self-service migration) so customized results are not mixed with the old import. Share your Source/Target carts and what already moved—Migration Experts will confirm the safest clear-and-rerun plan before Full Migration. Schedule a call if you already completed a Demo or Full Wizard migration and need customization next.

Case studies from real Custom Migrations

Cart2Cart Migration Experts have delivered custom work related to Inventory & Stock Quantities across 70 recorded customization projects spanning 31 Source→Target platform pairs. Below are pairs we see most often, the entities typically involved, and sample data volumes when available.

Platform pairs already in focus

• WooCommerce → Shopify — 13 customization projects
• PrestaShop → Shopify — 10 customization projects
• Magento → Shopify — 6 customization projects
• Magento → WooCommerce — 5 customization projects
• Volusion → BigCommerce — 3 customization projects
• PrestaShop → WooCommerce — 3 customization projects

Entities commonly customized

• Products — seen in 45 related projects
• Customers — seen in 26 related projects
• Orders — seen in 23 related projects
• Categories — seen in 16 related projects
• Coupons — seen in 4 related projects

How much data was migrated

Among projects with recorded store size, median migration volume is about 6.4K records, with larger builds reaching roughly 144.4K at the 90th percentile and peaks near 389.1K. Exact counts depend on products, customers, orders, and related entities in scope.

Sample projects

• BigCommerce → Shopify — entities: Orders 85.6K, Customers 33K, Products 32.8K, Manufacturers 577 — total volume ~152.3K
• WooCommerce → Shopify — entities: Orders 110.8K, Products 18.2K, Customers 14.6K, Categories 147 — total volume ~144.4K
• Shift4Shop → Shopify — ~88.2K records migrated
• Magento → Shopify — entities: Orders 34.3K, Customers 25.1K, Coupons 16.1K, Products 1.9K — total volume ~78K

Every store is different—share your Source/Target carts and entity scope on a Migration Expert call and we will estimate a similar Custom Migration path.

What we need to scope inventory customization

Stock is often multi-location, backorder-aware, or split across warehouses and apps. Quantity rules that look standard in the Wizard can still be unique to your fulfillment model.

Best results come from staging or production access so we can inspect locations, buffers, and variant-level stock on real SKUs. When that is not possible, a DB dump of inventory tables supports offline analysis; expect a deposit for dump restore and stock-model review prior to scoping the Custom Migration.

Tip: Initial data-structure analysis is much more efficient when you prepare exact examples of the important attributes and fields on the Source, plus how each should be mapped on the Target store (sample products/customers/orders with field names, values, and desired Target destinations). Clear examples reduce discovery time and help Migration Experts quote and implement the customization accurately.

FAQs

Can you split one source qty into multiple Shopify locations?

Yes with explicit allocation rules you approve.

Should inventory migrate before or after products?

Products first, then quantities—especially when variants must exist before stock attaches.

What about reservations and open orders?

Open-order reservations are platform-specific; we plan cutover timing with ops.

Keep sellable quantities accurate after switching carts—talk to Cart2Cart.