Original Summary

For the last few years I’ve worked in ecommerce and one of the biggest headaches was always inventory. We had thousands of SKUs, different suppliers, different lead times and constantly had to answer the same questions. What are we going to run out of? What needs ordering now? How much should we actually buy? And probably the most important one, what can wait? We actually used Inventory Planner at work, so this hasn’t come from me thinking inventory planning software doesn’t exist. I’ve used this type of software with thousands of SKUs and real money being spent based on the numbers. Over time I started forming my own ideas about how I’d want an inventory planning tool to work. So I started building Replenn. The bit I’m most interested in isn’t just forecasting demand. I want Replenn to make the actual purchasing decision easier. Say you’ve got 420 units of something in stock. At first glance, that sounds healthy. But Replenn knows how quickly that product has been selling, whether demand has recently changed, whether there was an unusual spike that shouldn’t distort the forecast, how much stock you’ve already got coming and how long that particular supplier normally takes to get more stock to you. Suddenly 420 units might not actually be healthy. If you’re likely to run out before another order could physically arrive, that SKU needs attention now. Another product might only have 80 units left and look far more worrying, but if it sells slowly and the supplier can replenish it in a few days, it might not need ordering at all. That’s the problem I’m trying to solve. Stock level on its own doesn’t tell you whether you need to buy something. Sales velocity on its own doesn’t either. Lead time doesn’t. Incoming stock doesn’t. It’s the relationship between all of them that actually matters. Replenn continuously brings those pieces together and turns them into something actionable: This needs ordering. This doesn’t. This is when you’ll need it. This is how much you should consider buying. And this is why. That last part is important to me. I don’t want Replenn to be a black box that spits out “Order 600” and expects someone to blindly spend thousands of pounds because a piece of software told them to. The merchant should be able to understand what drove the recommendation. I’m also building the purchasing workflow around it. Recommendations can become purchase orders, stock can be received against them, and Replenn knows what’s already on order so you don’t end up buying stock twice because one system doesn’t know what another system is doing. The eventual goal is pretty simple. Someone managing hundreds or thousands of Shopify SKUs should be able to open Replenn in the morning and answer: “What actually needs my attention today?” I’ve been building it for the last couple of months and I’m getting close to putting the first real merchants through it. I’m deliberately not linking anything yet because neither the product nor website is ready for that. I

  • 情报分类：商业与市场研究
  • 分类依据：内容涉及商业、投资或市场动态
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/9/29 07:09:00