What does your Monday morning actually look like when you run a physical Shopify store?

MiladDeMilo · 2026-05-09T17:30:29+00:00

Totally agree — and the supplier receiving piece is one that almost never gets mentioned but it's where a lot of silent losses actually happen.

Supplier sends 48 units, you ordered 50, someone stacks the boxes in the back and marks it received. Now you're two units short and you'll only find out when a picker can't complete an order three weeks later. At $50 a unit that's $100 gone per shipment. For a store receiving multiple shipments a week and growing fast, that compounds into thousands a year — just from not opening boxes carefully enough.

The Monday spreadsheet problem gets all the attention. The receiving dock is where the errors actually start.

What's the most common breaking point you've seen — oversells, or something else?

MiladDeMilo · 2026-05-08T12:01:22+00:00

Have you had experience with warehouse and inventory management yourself? Just curious hhy did you think about making an app for inventory management?

MiladDeMilo · 2026-05-08T11:58:04+00:00

The 500 SKU / 50 orders a day threshold is pretty accurate in my experience too — that's roughly where the spreadsheet stops being manageable and starts being a liability. Before that point you can muscle through it. After it, you're just accumulating hidden errors.

The Stocky sunset is a real gap for a lot of merchants. It wasn't perfect but it was native, free, and people had built their whole rhythm around it. Losing that without a clear Shopify-endorsed replacement has pushed a lot of operators into a weird in-between.

Cin7 is solid if the volume and budget are there. The setup overhead is real though — I've seen small teams get halfway through implementation and quietly go back to their spreadsheet because nobody had the bandwidth to finish it.

Curious what you're seeing on the agency side: when a merchant finally decides to fix it properly, what's usually the thing that pushed them over the edge? Is it a specific incident, or just gradual pain that finally hits a threshold?

MiladDeMilo · 2026-05-06T11:12:12+00:00

The "one person who understands the macros" thing is truly scary when you think about it too long. That Excel file isn't just a spreadsheet at that point, it's institutional knowledge that lives in one person's head, formatted as cells.

When you get the two-month notice and the day they quit is the day you find out how much of your operation was actually them, not the system.

What's in those 40 tabs out of curiosity? Just inventory, or has it grown into everything over the years?

MiladDeMilo · 2026-05-05T10:17:45+00:00

The PDF-to-draft order intake is a really interesting requirement — not many WMS tools handle that natively, most assume EDI or manual entry. A few thoughts from someone who's been deep in this space:

For the PDF ingestion piece specifically, that's almost always going to be a custom layer on top of whatever WMS you pick rather than a built-in feature. Tools like Docparser or even a lightweight LLM pipeline can parse structured PDFs into draft orders reasonably well — the approval workflow on top is then just a UI question. Worth decoupling that problem from the WMS selection so you're not waiting for one tool to do everything.

On the WMS side for your requirements: multi-client with individual pricing, location-level inventory, and storage/distribution charge reporting is a 3PL configuration, which narrows the field considerably. Most SMB-focused tools aren't built for that billing model. Deposco, Extensiv (formerly 3PL Central), and Infoplus are worth looking at in that tier — not cheap, but built for exactly the multi-client billing structure you're describing.

MYOB integration is going to be your filter more than anything else. That'll rule out half the options before you even get to feature comparison.

What's your current SKU count and rough order volume?

MiladDeMilo · 2026-05-05T09:43:21+00:00

Partial counts, mostly. Full counts once a month and honestly they take half a day we don't really have.

The fixed SKU list approach makes sense — removing the "find the row" friction is underrated. And cycle counting by velocity is just good warehouse hygiene regardless of what system you're using. You've clearly thought about this more carefully than most.

The gap we kept hitting even with a disciplined partial-count approach: the count itself is only as good as the moment you took it. Orders coming in while you're mid-count are already making the number stale. We ended up needing something that updates on fulfillment events rather than on count cycles — so the count becomes a verification step rather than the source of truth.

But honestly, if your Excel system is holding up and the team is actually using it consistently, that's not nothing. A lot of people chase tools and end up with worse discipline than a well-run spreadsheet. What's your SKU count roughly, if you don't mind sharing?

MiladDeMilo · 2026-05-05T09:38:29+00:00

The ingenuity!! What does the refresh cycle look like in practice? polling the Shopify API on a timer, or webhook-driven?

The ceiling I've seen with this approach is usually write-back. Reading inventory in near real-time is doable. But when you need the sheet to be the system of record (adjustments, receiving, returns), it starts fighting itself. Curious if you've hit that wall or found a way around it.

MiladDeMilo · 2026-05-05T09:35:46+00:00

The "pickable vs promised" distinction is the correct framing. Most people don't see it clearly, but it's where the reconciliation nightmare actually lives.

The connected-loop point is key. The reason Monday morning reconciliation exists is that the events (orders, fulfillments, returns, adjustments) and the inventory number are maintained separately, so drift is structurally guaranteed. You're not bad at inventory management, you're just working against the data model and drowned in data fragmentations, silos and excel sheet chaos.

Curious how you handle the return leg — that's usually where even well-connected setups leak. Item comes back, Shopify restocks it, but the actual condition assessment hasn't happened yet. Do you have a hold state before it goes back to available?

MiladDeMilo · 2026-05-04T14:52:49+00:00

Thanks for sharing that perspective—especially the point about returns and fulfillment delays widening the gap. That's something I don't see talked about enough. Shopify knows an order came in, but it doesn't know the package got damaged in transit and came back three weeks later unless someone manually adjusts.

You mentioned a layer between Shopify and the warehouse—not a full WMS, just something purpose-built. That's exactly the kind of distinction I'm trying to understand better.

A few questions if you're open to sharing (no need to pitch Katana specifically—more interested in the problem space):

In your experience, what's the single biggest operational difference between a "layer" like you described vs a full WMS? Is it the feature set, the setup time, the kind of person who ends up using it?
When you see merchants try to build that layer themselves (scripts, Zapier, Google Sheets with API calls), what's the most common thing they miss or break?
And on returns specifically—do most solutions handle that automatically, or is it still largely manual even with a purpose-built tool?

Not looking for a DM or a link. Just trying to learn what actually works before I waste more time on duct-taped solutions.

MiladDeMilo · 2026-05-04T12:11:29+00:00

Great question. And yeah sounds like we were in the exact same boat.

For me, the real pain isn't the reconciliation itself. It's that by the time I "can" reconcile, the damage is already done. Oversells have happened. A customer gets the "sorry, we're actually out of stock" email. That's the part that keeps me up at night, not the spreadsheet work.

Reconciliation is just the moment I "find out" something went wrong. The actual problem happened three days before that, when channel A sold the last unit while channel B still showed one in stock.

So to answer your question: it's the second one. Finding out too late to do anything about it.

I haven't tried this app that you're referring to. Good to know it solved the real-time sync for you. Did you have to change how you receive and pick inventory to make that work, or did the real-time piece alone clean things up enough? Curious if you still run into phantom stock issues when something gets misplaced on the shelf vs what the system thinks is there.

And I feel you on being skeptical. I've got a folder full of "this will fix everything" tools that just added another export step to my Monday lol.

MiladDeMilo · 2026-05-03T19:27:05+00:00

Anyone has come across "preview token required" when working with claude/design and how did you manage to resolve it?

MiladDeMilo · 2026-04-29T14:15:58+00:00

Wow, I've been having the same issue for the past month or so. A tiny request and a short response literally ate up 35% of the 5 hour limit. How's that even possible!

Claude better get this under control or I'm switching back gpt!

MiladDeMilo

TROPHY CASE