FAQ

Eight questions Cin7 users ask before switching

Plain answers on cost, migration, multi-warehouse coverage, the threshold engine, Shopify sync, lead times, support, and the full switch playbook — drawn from the same pricing and Cin7-exit material as the rest of the site.

Frequently asked questions

How does ReconcileIQ's cost compare to Cin7?

ReconcileIQ prices by warehouse count and SKU volume — the two variables that actually drive reconciliation cost. Starter is $499 per month for one warehouse and up to 500 SKUs; Growth is $1,200 per month for up to 3 warehouses and 5,000 SKUs; Scale is custom for teams past 5 warehouses or 25,000 SKUs. Cin7 layers capabilities behind module add-ons and seat tiers, so the published number rarely matches what lands on the renewal — the roughly 30% post-acquisition renewal jump ops teams report pushes the real cost well past the headline. See the full breakdown on the pricing page.

How long does the migration from Cin7 take?

Weeks, not quarters. A Starter team is usually live in a single sprint — the CSV PO download plus the real warehouse-aware feed selector cover the day-to-day without a migration engineer. Growth follows the same path with multi-warehouse routing switched on. Scale teams get a dedicated migration engineer through cut-over and bespoke onboarding around the warehouse graph, not a SaaS grid. Start with the 90-second Cin7 alternatives diagnostic to scope the work before any commitment.

Does it support multi-warehouse inventory?

Yes — multi-warehouse routing is the Growth tier. Stock is routed by source-of-truth per warehouse, the alert list carries a Warehouse column, and the CSV PO download writes the warehouse into the PO header so the supplier sees exactly which site is short. Growth supports up to 3 warehouses and 5,000 SKUs; Scale covers teams running past 5 warehouses or 25,000 SKUs with bespoke onboarding around the warehouse graph.

What is the threshold engine?

The threshold engine is the per-SKU reorder rule system that drives the alert list. Every SKU gets its own reorder threshold, the engine reads it on every reconciliation pass, and the alert list surfaces every row that has crossed the line — with status badges so on-call ops can scan the backlog in one view. The same engine runs in every tier: Starter ships it for single-warehouse, Growth adds the Warehouse column, and Scale layers the bespoke rules on top. Replaces the weekly spreadsheet workaround Cin7 leaves you to maintain by hand.

Does it sync stock levels with Shopify?

Yes. Shopify is one of the supported channels ReconcileIQ reconciles against, and the real warehouse-aware feed selector is in every tier. DTC apparel teams commonly reconcile Shopify against DrumWave and a 3PL in one view; consumer-electronics teams reconcile FBA, Shopify, and TikTok Shop in the same pass. Reconciliation drift between channels — the unit-economics leak that shows up on the P&L before it shows up on the dashboard — is exactly what the engine is built to surface.

Can I set lead times per supplier?

Yes — and it is the per-warehouse reorder-point blindspot that Cin7 leaves you to patch by hand. ReconcileIQ reads per-SKU reorder rules and per-3PL lead times on every reconciliation pass, so the alert list reflects the math your buyer is currently doing in a spreadsheet on Sunday night. Growth adds the Warehouse column to every alert and writes the warehouse into the CSV PO header so the supplier sees the correct site and lead time on each line.

What does support look like?

Support scales with the tier. Starter ships standard email support. Growth adds email plus chat. Scale ships a named support contact plus a quarterly review, dedicated support, and custom SLAs around reconciliation windows — the same model teams used to get from Cin7 before the 2024 acquisition. The point is that the support tier you pay for is the support tier that picks up the ticket.

What's the full switch playbook from Cin7?

The Cin7 → switch playbook is a three-step path. Step one is the 90-second Cin7 alternatives diagnostic — an 8–10 question form that scopes where the reconciliation work is breaking. Step two is the 20-min demo in your sandbox with your data, so the routing rules and the alert list are real before any commitment. Step three is the cut-over, with Growth teams self-onboarding and Scale teams getting a dedicated migration engineer through go-live. Open the playbook to start.

Still evaluating

Run the Cin7 alternatives diagnostic

90 seconds, eight to ten questions, and a result that lands in an internal-ops inbox — your answers do not end up on a marketing list.