vietnamese mud crabsoft-shell crabdifferent species of crab
6
10 Comments

Update: shipped a bunch since my last post — safety buffers, sync previews, and real billing

A few weeks ago I posted about Inventory Sync, a small tool for Shopify sellers who also sell in-store, on Etsy, or at markets. Wanted to share what's changed since, mostly thanks to feedback from this community:

Safety buffer: hold back 1-2 units on your riskiest SKUs so a sync delay can't cause an oversell in the first place
Sync preview: see exactly what's about to change before it syncs, instead of finding out after
Billing now runs through Shopify's own subscription system — no third-party checkout
Rebuilt the whole landing page around the actual pain (a refund + an apology email), not just "inventory sync" as a feature

Still small, still validating, but genuinely working end to end now. 14-day free trial, no card required, $29/month after:
👉 https://inventory-sync-starter.onrender.com
If you sell on more than one channel and this sounds familiar, I'd love for you to try it — and if it's not for you, I'll still take the harsh feedback.

on July 18, 2026
  1. 1

    Rebuilding the landing page around the refund and the apology email is the smartest thing on this list. You're not selling sync, you're selling insurance against one specific painful moment, which also means $29 is probably underpriced for stores doing real volume. Test a tier priced against the cost of a single oversell per month and see who takes it.

  2. 1

    One thing that helped me: define the weekly number before the feature list. Most of my ideas die there, which is the point.

  3. 1

    Great progress! I especially like the shift from selling features to solving a real business pain. The safety buffer and sync preview build trust, which is just as important as automation for merchants.

    1. 1

      Thanks — that trust-over-automation point keeps coming up from different people in different ways, which makes me think it's the actual core insight here, not just a nice-to-have angle. Appreciate you reinforcing it; it's shaping what I build next more than any single feature request has.

  4. 1

    Safety buffer + sync preview is the right duo — one prevents the oversell, the other rebuilds trust before the scary button. Billing going live is the real milestone. Curious whether merchants care more about the buffer defaults or the preview clarity when they first try the trial.

    1. 1

      Appreciate that read — and honestly, still don't know the answer to your actual question yet, since I don't have real trial users to observe. My guess going in was buffer defaults would matter more (it's the "protects me" feature), but now I'm not so sure — the preview might actually be the thing that gets someone to trust clicking Sync at all in the first place, before they even get to caring about buffer numbers.
      Billing's been fully live and tested for a bit now, but real merchants haven't picked it up yet — still working on that part. Once someone's actually in the trial, I'll actually be able to answer this instead of guessing. Good question to hold onto for when that happens.

  5. 1

    The interesting opportunity isn't synchronizing inventory across channels—it's giving merchants confidence that selling everywhere won't create costly customer mistakes. I'd keep validating whether customers adopt Inventory Sync because it automates updates or because it removes the uncertainty that comes with multi-channel selling.

    1. 1

      That's a really useful way to split it, and honestly I don't know the answer yet — I don't have enough real users to have tested it. My instinct after all the feedback so far is it's the confidence/uncertainty angle, not the automation itself — nobody's asked me for faster syncing, but almost everyone who's commented has asked about trust, permissions, what happens if something fails silently. That's confidence-seeking behavior, not "save me time" behavior.
      If that's right, it probably means I should keep leaning into things like the sync preview and the FAQ answering "what if this breaks" — reassurance features — rather than chasing speed or more integrations. Appreciate you naming this explicitly; going to actually pay attention to which parts of the product people engage with once real users show up, instead of assuming.

      1. 1

        Glad it was useful. I actually shared a few thoughts by email as well since I didn't want to derail the thread. No rush at all—just mentioning it in case it landed in spam. I'm interested to see what you learn once real customer behavior starts coming in.

  6. 1

    ttps://inventory-sync-starter.onrender.com

Trending on Indie Hackers
I sent 43 cold emails with my own tool. 17 replied. 1 paid. Here’s the unofficial launch. User Avatar 219 comments I built a web-based vector editor from scratch and integrated an AI Agent. Need just ONE beta tester! User Avatar 54 comments Why Your Users are Leaving in Silence (and How to Fix the "Leaky Bucket" with AI) User Avatar 21 comments Launched 580 landing pages in 1 week. Solo. No team. User Avatar 15 comments How Better T-Shirt Fit Reduced Product Returns by 25% User Avatar 10 comments I spent 2.5 years building a marketing engine nobody can see without installing it. So I built a free distortion calculator. User Avatar 9 comments