Preparing report
Preparing report
Study setup · Onboarding & Activation
“I want to find out why new StockFlow Inventory users abandon setup before seeing first useful inventory value.”
Across all 10 qualified interviews, users tied value to an early visible result, such as a Mapping preview, valid-row import, repair queue, sample dashboard, stock-risk view, or location preview. The CSV importer lost momentum when full cleanup came first.
Executive summary
StockFlow Inventory has a sequencing problem in the CSV importer. Users come in with inventory pain, but the first session can ask them to finish CSV import, SKU cleanup, and catalog cleanup before they see value. Across all 10 qualified interviews, value was tied to an early visible result: a Mapping preview, valid-row import, repair queue, sample dashboard, stock-risk view, or location preview. The strongest next move is to make the first useful inventory view appear as early as the data allows. Then use staged validation, partial import, repair states, and row examples to keep cleanup inside StockFlow. Overall confidence is medium. Treat weaker secondary findings as directional until conflicting evidence is resolved.
The clearest patterns in this study, supported across most interviews.
Users arrive with inventory pain, but the first session asks them to prove data perfection before value is visible. That reframes activation as spreadsheet cleanup and delays trust.
How to apply itRemove perfect csv gating blocks normal retailers before first useful inventory value from the onboarding path, then make the activation moment easier to reach and easier to recognize.
Heard in 5 of 10 interviews
“Support answered, but the problem was that StockFlow made me fix duplicate SKUs before I understood the payoff. That is the moment I would want the team to study, because it shows what was happening before the surface metric or form answer simplified the story. I came to StockFlow with real inventory pain, but the first session made me clean my data before I saw the value.”
Leo Park · Trail Supply Co.Transcript
When clean items move forward and messy rows are isolated, cleanup feels finite. Without that, users rename, delete, or invent rules outside StockFlow.
How to apply itRemove partial import and row-level repair make cleanup finite and measurable from the onboarding path, then make the activation moment easier to reach and easier to recognize.
Heard in 4 of 10 interviews
“StockFlow made inactive products block the activation path. By then the fallback behavior made sense to the person doing the work. It was faster, safer, or less embarrassing than staying with the official path, even though it created cleanup and confusion later. I came to StockFlow with real inventory pain, but the first session made me clean my data before I saw the value.”
Alyssa Grant · Garden PorchTranscript
Patterns with good support — apply these with a bit more judgment.
All interviews point to the need for a visible win before full cleanup. Early output explains the payoff and keeps users working inside the product.
How to apply itRemove the first useful output creates activation from the onboarding path, then make the activation moment easier to reach and easier to recognize.
Heard in 10 of 10 interviews
“Let me import the active spring collection first and I would have seen value the same day. My workaround was to open the CSV, rename fields, invent SKU rules, or delete rows outside StockFlow. That may solve a few rows, but it also means the product is not carrying the user toward activation. The better path would show useful inventory value from partial data: a mapping preview, valid-row import, repair queue, and sample dashboard that shows why cleanup is worth finishing.”
Alyssa Grant · Garden PorchTranscript
A dashboard gives users and their teams evidence of the payoff. Without it, repeated CSV failures leave no visible reason to continue.
How to apply itRemove a sample or partial dashboard must show payoff before full cleanup from the onboarding path, then make the activation moment easier to reach and easier to recognize.
Heard in 4 of 10 interviews
“I reached value because our CSV already had clean SKU, name, cost, price, and variant columns. That is the moment I would want the team to study, because it shows what was happening before the surface metric or form answer simplified the story. I came to StockFlow with real inventory pain, but the first session made me clean my data before I saw the value.”
Grace Liu · Modern PantryTranscript
Examples turn ambiguous cleanup into specific repair work. Without them, users guess whether the problem is SKU, color, size, bundle, or variant naming.
How to apply itRemove mapping preview turns sku and variant cleanup from guessing into visible progress from the onboarding path, then make the activation moment easier to reach and easier to recognize.
Heard in 3 of 10 interviews
“A mapping preview with examples would have turned the import from a guessing game into cleanup work. My workaround was to open the CSV, rename fields, invent SKU rules, or delete rows outside StockFlow. That may solve a few rows, but it also means the product is not carrying the user toward activation. The better path would show useful inventory value from partial data: a mapping preview, valid-row import, repair queue, and sample dashboard that shows why cleanup is worth finishing.”
Ibrahim Khan · Harbor GoodsTranscript
Open questions for a follow-up study