Guide

When the spreadsheet stops being enough

Keep the restock sheet until it starts costing you stockouts. That's usually around fifty SKUs, or the day Amazon sits next to Shopify or WooCommerce.

Keep the spreadsheet until it starts costing you money. A few dozen SKUs, one channel, supplier you could call this afternoon — a sheet can still hold the whole cycle: plan, forecast, replenish, monitor, learn. Skuvelo is for the week the sheet and Seller Central disagree, or you add a second place you sell and now you're reconciling two restock stories by hand. The sheet is also how you start inside Skuvelo. You do not have to connect a store first.

Most people don't switch at a round number. They switch after a stockout on the ASIN that was "fine in the sheet," or after sending in a pile of something that then sits in FBA.

What actually goes wrong

The columns are still there. You are the glue:

  • On-hand in the sheet is not on-hand in FBA, and not what's on the Shopify or WooCommerce shelf.
  • Lead time lives in your head, so you and a VA order different quantities of the same SKU.
  • Amazon's restock report never saw the store. The store never saw FBA inbound.
  • Handing the file to someone else is how you "add a user."

inFlow will track the counts. Amazon will tell you what Amazon wants sent in. Neither one writes a single PO that covers FBA and the store. That's the hole.

Skuvelo takes demand, on-hand, inbound, lead time, and what the next PO costs in cash, and puts them on one list. You still approve it. The sheet can retire without you throwing away how you think.

Start from the exports you already have. Import guide has the columns. Connecting Seller Central can wait.

If you're not there

A few dozen SKUs, one channel, no real lead time — wait. When Skuvelo is not the right fit. If you've already eaten a stockout or an overbuy, you're past that line even if the catalog still looks small.

Who Skuvelo is for. Pricing.