How to Set Up Inventory Tracking That Actually Works

How to Set Up Inventory Tracking That Actually Works

Last updated: July 2026. This guide reflects our work with e-commerce brands using Shopify, Square, and custom stacks. No affiliate links.

---

What This Guide Covers

• A decision framework for picking your first inventory system
• The exact setup we use for Shopify brands doing $500K–$5M/year
• A worked example: configuring reorder points for a 200-SKU store
• When to migrate from spreadsheets to a dedicated platform
• The integration decisions that matter (and the ones that don't)

Who this is for: E-commerce operators who have outgrown spreadsheets but aren't sure what comes next. If you're doing $10M+ or have 5+ warehouses, you need an ERP consultant, not a blog post.

---

The Framework We Use

We evaluate inventory setups on three axes. Pick two to optimize; the third will suffer.

Axis	Cheap & Fast	Cheap & Good	Fast & Good
Setup cost	Under $500	$5K–$15K	$15K+
Time to live	1–2 days	2–4 weeks	6–10 weeks
Accuracy	80–85%	95–98%	99%+
Best for	Proof of concept	Most businesses	High-volume or regulated
Tools	Sheet + Shopify native	TradeGecko / Cin7	NetSuite / custom

Our default recommendation: Start at "Cheap & Good." Most businesses we work with outgrow "Cheap & Fast" within 90 days and end up paying twice.

---

Phase 1: Map Your Current State (Before You Buy Anything)

Don't pick software until you know where data breaks. Here's the audit we run in week 1:

Step 1: Count Your Data Latency Points

Walk through your order flow and note where inventory data sits idle:

Step	Where Data Lives	How Long It Sits	Who Updates It
Order placed	Shopify	Real-time	Automatic
Order picked	Warehouse floor	2–24 hours	Warehouse staff
Stock updated	Spreadsheet	1–3 days	Operations manager
Reorder triggered	Owner's head	When they remember	Owner

The rule: If any step sits longer than 4 hours without a good reason, that's your bottleneck.

Step 2: Identify Your "Ghost SKUs"

Ghost SKUs = products showing as available online but physically out of stock. They're your #1 source of customer service tickets.

To find them:

1. Export your Shopify inventory report
2. Sort by "available" quantity
3. Cross-reference with a physical count of your top 20 movers
4. Flag any SKU where Shopify says "available" but the shelf is empty

In our experience: Most stores doing $1M+ have 5–15 ghost SKUs at any given time. One client had 23 ghost SKUs driving 40% of their customer service volume.

Step 3: Document Your Reorder Process

Write down, step by step, how you decide to restock:

• Who checks stock levels? How often?
• What triggers a reorder? (Visual inspection? Spreadsheet alert? Gut feeling?)
• Who places the order? How?
• How long from "we need this" to "it's in the warehouse"?

If the answer to any of these is "it depends" or "whoever notices first," you have a process gap, not a tool gap.

---

Phase 2: Pick Your Tool (Decision Tree)

Option A: Spreadsheet + Shopify Native (Under $500)

When to use: Under 100 SKUs, under 500 orders/month, single warehouse, no wholesale.

Setup:

1. Export Shopify product CSV
2. Add columns: Physical count, reorder point, reorder quantity, supplier lead time
3. Set conditional formatting: red when available < reorder point
4. Schedule 30-minute weekly review

The spreadsheet template we use:

SKU	Product	Physical Count	Shopify Available	Reorder Point	Reorder Qty	Supplier Lead Time	Status
TSH-001	Black Tee	45	42	20	100	14 days	OK
TSH-002	White Tee	12	12	20	100	14 days	REORDER

Reorder point formula we use:

Reorder Point = (Average Daily Sales × Lead Time in Days) + Safety Stock

Safety stock rule of thumb: 7 days of average sales for stable products, 14 days for seasonal or supplier-unreliable products.

Worked example:

• SKU: TSH-002 (White Tee)
• Average daily sales: 3 units/day
• Lead time: 14 days
• Safety stock: 14 days × 3 = 42 units
• Reorder point: (3 × 14) + 42 = 84 units

Wait — the table shows reorder point at 20, not 84. Why?

Because this store has cash flow constraints. They can't afford to tie up $2,800 in white tee inventory (100 units × $28 cost). So they accept a higher stockout risk and reorder more frequently. The math is situational. That's why "best practice" posts that give you one number are useless.

Option B: TradeGecko / Cin7 ($5K–$15K setup)

When to use: 100–1,000 SKUs, 500–5,000 orders/month, multiple channels (DTC + wholesale + Amazon), or growth trajectory that will hit these numbers in 12 months.

Why we default to Cin7 for this bracket:

• Native Shopify integration (2-hour setup, not 2-week custom build)
• Multi-location support out of the box
• B2B portal for wholesale orders (separate from DTC inventory)
• API access for custom automation

What TradeGecko does better:

• Stronger QuickBooks integration
• Simpler UI for non-technical teams
• Better mobile app for warehouse staff

Our decision rule: If you're already on QuickBooks Online, start with TradeGecko. If you're on Xero or no accounting integration yet, start with Cin7.

Option C: NetSuite / Custom ($50K+)

When to use: 5,000+ orders/month, 3+ warehouses, international fulfillment, or regulatory requirements (FDA, lot tracking, etc.).

When NOT to use: If you're reading this guide to decide. At this level, you hire a consultant.

---

Phase 3: The Setup We Run for Shopify + Cin7

This is the exact sequence we use for clients in the $500K–$5M range.

Week 1: Data Prep

1. Clean your Shopify catalog

   • Remove discontinued SKUs
   • Standardize variant names ("Black / Large" not "Blk-Lrg")
   • Ensure every SKU has a unique identifier

2. Export and audit

   • Shopify product CSV
   • Current stock levels (physical count, not system count)
   • Supplier list with lead times

3. Set your reorder logic

   • For each SKU: reorder point, reorder quantity, primary supplier
   • We use a simple scoring matrix:

Factor	Score 1	Score 2	Score 3
Sales velocity	< 1/week	1–5/week	> 5/week
Margin	< 30%	30–50%	> 50%
Supplier reliability	Unpredictable	Usually on time	Always on time
Total score	Reorder conservatively	Standard reorder	Aggressive reorder

Week 2: Platform Configuration

1. Connect Shopify

   • Cin7 admin → Integrations → Shopify
   • Map locations (Shopify location → Cin7 warehouse)
   • Set sync frequency: every 15 minutes for active SKUs, daily for slow movers

2. Import SKUs

   • Use Cin7's bulk import template
   • Map fields: SKU, name, cost, reorder point, reorder quantity
   • Verify 10 SKUs manually before importing the full catalog

3. Configure alerts

   • Low stock: email to purchasing manager
   • Out of stock: email + Slack notification
   • Reorder point: daily digest (not individual alerts — too noisy)

Week 3: Integration & Testing

1. Test order flow

   • Place test order in Shopify
   • Verify it appears in Cin7 within 15 minutes
   • Pick and fulfill in Cin7
   • Verify Shopify shows as fulfilled

2. Test reorder alert

   • Manually set a test SKU's stock to 1 unit below reorder point
   • Verify alert fires
   • Place test purchase order
   • Verify stock updates when PO is received

3. Train the team

   • Warehouse staff: scanning, picking, receiving
   • Operations manager: dashboards, reports, reorder workflow
   • Owner: exception handling (what to do when alerts fire)

Week 4: Go Live + Monitoring

1. Run parallel for 1 week

   • Old process continues
   • New process runs alongside
   • Compare daily: stock accuracy, order fulfillment time, error rate

2. Daily standup questions:

   • Any orders we couldn't fulfill due to stock discrepancy?
   • Any alerts that fired but shouldn't have?
   • Any manual workarounds the team had to use?

3. Kill the old process when:

   • 3 consecutive days with zero stock discrepancies
   • Team can complete core tasks without referencing old system
   • Owner feels confident in exception handling

---

The Mistakes We See (And How to Avoid Them)

Mistake 1: Perfect Data Migration

What happens: Client insists on migrating 3 years of sales history. Adds 4 weeks to timeline. Data is messy. Team loses confidence.

What we do instead: Migrate 90 days of sales data. Archive the rest. If you need historical analysis later, export from Shopify directly.

Mistake 2: Over-Engineering Phase 1

What happens: Client wants demand forecasting, automated purchasing, and multi-currency on day 1. Never launches because scope keeps growing.

What we do instead: Launch with stock tracking + reorder alerts only. Add forecasting in month 3, after the team trusts the base system.

Mistake 3: No Rollback Plan

What happens: New system crashes during Black Friday. No way to process orders. Client loses $50K+ in sales.

What we do instead: Keep Shopify's native inventory active as backup for first 30 days. If Cin7 fails, revert to manual updates in Shopify. It's tedious but functional.

Mistake 4: Skipping the Weekly Review

What happens: System runs fine for 3 months. Then a supplier misses a delivery, safety stock is wrong, and the client stockouts their #1 SKU.

What we do instead: 30-minute weekly review, non-negotiable. Review: stock levels, upcoming reorders, supplier performance, any discrepancies.

---

When to Upgrade (And When Not To)

Upgrade when:

• You're manually updating more than 10 SKUs per week
• You have stockouts on products that should be in stock
• You're using more than 3 spreadsheets to track inventory
• Your team spends more than 2 hours/week on inventory admin

Don't upgrade yet when:

• You're still validating product-market fit
• Your SKU count changes weekly (too early to systematize)
• You have cash flow constraints (manual process is cheaper than stockouts, but software costs money)

---

FAQ

Q: Can I use this same process for Square instead of Shopify?

Yes, with one change: Square's inventory API is less robust than Shopify's. For Square + Cin7, we typically use a middleware layer (Zapier for simple setups, custom API for complex ones). Budget an extra $2K–$5K for the integration.

Q: What if I have products with variants (size, color)?

Track at the variant level, not the product level. "Black Tee" is useless for reordering. "Black Tee / Large" is what you actually stock. Cin7 handles this natively; in spreadsheets, each variant gets its own row.

Q: How do I handle seasonal products?

Two approaches:

1. Separate seasonal SKUs with their own reorder logic (higher safety stock pre-season, zero reorder post-season)
2. Dynamic reorder points using Cin7's demand forecasting module (available on Pro plan)

We typically recommend #1 for businesses under $2M, #2 for businesses above $2M where the Pro plan cost ($200/month) is justified by inventory carrying cost savings.

Q: What's the real cost of a stockout?

We can't give you a universal number, but here's how to calculate yours:

1. Average order value × stockout frequency = lost revenue
2. Customer service time per stockout × hourly rate = labor cost
3. Customer lifetime value × stockout-driven churn rate = long-term cost

For a client doing $2M/year with $85 AOV: one stockout per week on a top-20 SKU cost them ~$18K/year in lost revenue + labor. That's what justified the Cin7 investment.

Q: Do I need a barcode system?

Not at first. We typically add barcodes when:

• SKU count exceeds 200
• Warehouse staff exceeds 3 people
• Error rate exceeds 2%

Until then, printed pick lists with checkboxes work fine.

---

The Decision Checklist

Before you buy anything, answer these:

• I know my top 20 SKUs by sales volume
• I've counted physical stock for those 20 SKUs in the last 30 days
• I can articulate my reorder process in 5 steps or fewer
• I know my average supplier lead time (within 3 days)
• I've identified my biggest inventory pain point (stockouts, overstocks, or data accuracy)
• I have $5K–$15K budgeted for setup (not just software cost)
• I can dedicate 2–4 hours/week for the first month to system management

If you can't check at least 5 of these, fix the gaps first. Software won't solve process problems.

---

What We Do at TkTurners

We set up inventory systems for e-commerce brands. Not theory — the actual configuration, integration, and training.

Integration Foundation Sprint: 4-week implementation of Shopify/Square + Cin7/TradeGecko, including:

• Week 1: Data audit and cleanup
• Week 2: Platform configuration
• Week 3: Integration and testing
• Week 4: Training and go-live

Who it's for: Brands doing $500K–$5M/year who have outgrown spreadsheets but don't have in-house technical ops.

Who it's not for: Businesses looking for a $500 quick fix (use the spreadsheet method above), or enterprises needing custom ERP development.

Contact us if you want to discuss whether your business is ready for this level of systematization. No pitch — we'll tell you if you're not.