You're on Shopify, you ship physical products, and you probably rebuilt your inventory picture in Excel this morning. We built something for exactly that

Shopify Apps
1

Yeah, that headline is basically my life for the past 18 months.

I run a small-medium operation—110 SKUs, 75 bins, several part-time pickers. And somehow I was still spending every Monday morning reconciling Shopify stock vs what was actually on the shelf. You know the dance: export orders, cross-check pick lists, find three units of something that Shopify said was zero, realize you oversold a bundle two weeks ago.

So we built LaSyncro.

Not a “warehouse management system” with a six-figure implementation fee. Not another dashboard that looks pretty but can’t tell you why the count is off.

Just a WMS that works the way a 1–10 person operation actually works:

  • Camera-scan receiving & picking – no $3k handheld scanners. Your phone works. (Though if you already have USB barcode scanners lying around, plug them in. They just work. We didn’t even advertise that until last week.)

  • Morning Brief – every day at 8am, a plain-text summary of what’s low, what’s late, and what’s about to stock out. No logging in.

  • An actual event ledger – every stock movement is recorded, immutable. When something goes wrong, you don’t guess. You replay the timeline.

We’re not live on the Shopify App Store yet—deliberately. We’re running a small pilot with 10 merchants to get the unit economics right (yes, we nerded out on CAC, churn, and support hours) and to seed real reviews.

But the product is shipped. 11+ modules. Mobile-first (owners spend more time on the phone than the web app, so we designed the web app for planning, the mobile app for action).

If you’re tired of Excel reconciliation and you want to talk actual warehouse workflows—not buzzwords—I’d genuinely love your take. What’s the one inventory headache that makes you want to throw your laptop?

We are looking for several SMBs who are willing to try our service and help us validate all aspects before we actually go to the market. You’d be the pioneers, free of charge.

If interested please do get in touch and very much looking forward to hearing from you.

-– Milad (co-founder, LaSyncro)

2

This is a fantastic story and a very relatable pain point! Most WMS tools are definitely built for enterprise-level operations, leaving SMBs stuck in spreadsheet hell.

You’re specifically targeting operations with 1-10 people, have you considered how you’ll handle bundled inventory synchronization? That’s often the one inventory headache that breaks a workflow Shopify subtracts the bundle, but the individual shelf counts don’t update until a manual reconciliation happens.

If you’ve solved that via your event ledger, you’ve got a killer feature there.

3

Pretty nice idea and potential to solve pain points. Most inventory solution are thinking for large enterprises but you’re targetting real small ones. Many small merchants don’t even realize the problems until they get to look further into it. I’m curious to see how this evolves once more merchants get their hands on it :+1:

4

Bundles, yeah, this one keeps coming up and honestly it should, because it’s where most lightweight WMS tools silently fail.

The way we handle it right now → every fulfillment event decomposes the bundle at the component level before it hits the ledger. So when an order ships, it’s not “1x Bundle A subtracted” — it’s “2x SKU-103, 1x SKU-217, 1x SKU-441 subtracted,” each as its own ledger entry, timestamped and immutable. Shopify fires the webhook, we decompose, we write. No reconciliation loop needed because the shelf count and the Shopify count are derived from the same source of truth.

The place it gets interesting is mid-fulfillment substitutions — picker grabs a component that’s already allocated to another bundle. That’s where the event ledger earns its keep. You can actually replay exactly what happened and when with full traceability.

Happy to walk you through it in more detail if you’re curious — or if you’re running bundles yourself and want to stress-test it.

5

You nailed something we talk about internally a lot — the “don’t know what you don’t know” problem.

A lot of the merchants we’ve spoken to during initial phases weren’t actively looking for a WMS. They were just… living through the pain. Monday morning reconciliation was just part of the job. Then we asked them “what if you didn’t have to do that?” and the look of uncertainty on their faces.

That’s actually why we’re doing a small pilot before any public launch. Not just to validate the product, but to understand how merchants describe the problem once they’ve had a tool that removes it. That language matters a lot for how we build and communicate going forward.

Would love to hear your take as we grow — always valuable to hear from people who see this space clearly.

6

The immutable event ledger is the right foundation - that’s the piece most lightweight inventory tools skip and it’s exactly what makes root cause analysis possible when something goes wrong mid-fulfillment.

Bundle decomposition into component SKUs is the correct call too. Treating bundles as a presentation layer rather than a separate inventory unit avoids the phantom stock problem that catches out a lot of Shopify merchants running kits or multipacks.

A couple of things worth validating early in the pilot:

Morning Brief thresholds - static low-stock alerts become noise quickly for merchants with seasonal SKUs. Worth exploring whether thresholds that adapt to sales velocity get better adoption than fixed ones.

Shopify’s own inventory adjustments - when Shopify auto-adjusts stock for a return or fulfillment correction, does that write to your ledger or only events flowing through your system? That gap, if it exists, is where discrepancies will surface.

The 1-10 person segment is smart. Would be interested to hear how the pilot shapes things over the next few months.

7

Reply:

This is exactly the kind of feedback we were hoping the pilot would surface. Greatly appreciate you thinking through it carefully.

On the Morning Brief thresholds: you’re right that the static thresholds become noise fast, especially for anyone with seasonal SKUs or irregular velocity patterns. The current implementation lets merchants set their own thresholds per SKU, which is better than a global default but still manual. Velocity-adaptive thresholds are on the roadmap — the pilot is actually the right moment to test whether merchants engage with that level of configurability or whether they’d rather we just calculate it for them. My instinct is the latter, but we’ll find out.

On Shopify-initiated adjustments: this is the gap worth being honest about. Events that flow through LaSyncro — fulfillments, receives, returns processed through our WMS — write to the ledger cleanly. Shopify-side adjustments made directly in the admin (manual stock edits, Shopify’s own return restocking) come in via webhook and are recorded, but they’re flagged differently in the ledger because we can’t decompose the intent behind them the way we can with our own events. So the audit trail exists, but the granularity is lower. It’s a known constraint and something we’re actively working on closing — ideally surfacing those as a distinct event type with a prompt to document the reason.

The pilot is really about stress-testing exactly these edges. Happy to keep you posted on what we learn if that’s useful.