# Moving off spreadsheets If your inventory planning lives in a spreadsheet right now, you're not alone. Most consumer brands start there. Spreadsheets are flexible, familiar, and free — until they become the bottleneck. This guide is for teams making the move to Moselle. Here's what to bring, what to leave behind, and how to build trust in the system quickly. *** ### Why this transition feels harder than it is The hesitation is usually one of two things: **"Our spreadsheet has years of logic in it."**\ It probably does. Formulas built over time, columns only one person fully understands, conditional formatting that nobody remembers creating. That logic exists because the data wasn't connected. Moselle connects the data — so most of that logic becomes unnecessary. **"I'm not sure I trust the system yet."**\ That's fair. Mo's recommendations are grounded in your actual sales data, but trust is earned. This guide will show you how to verify Mo's outputs against what you already know, so you can build confidence at your own pace. *** ### What to bring into Moselle **Historical sales data**\ The more history Moselle has, the better Mo's forecasts get. If you have clean sales data going back 12–24 months, import it. Even imperfect historical data is better than none. **Your product catalog**\ SKUs, variants, bundles, kits — all of it. If Moselle doesn't know what you sell, it can't plan for it. **Supplier lead times**\ How long it takes to get stock from each supplier is one of the most important inputs in replenishment planning. This is often locked in someone's memory or buried in email threads. Getting it into Moselle is worth the effort. **Channel breakdown**\ If you sell across Shopify, Amazon, wholesale, or retail, bring that structure in. Planning by channel lets Mo give you more accurate projections for each. *** ### What to leave behind **Manual override formulas**\ If your spreadsheet has cells that add 15% to certain SKUs "just in case," or subtract from slow movers based on a rule someone set years ago, those adjustments can go. Mo handles safety stock and risk buffers from the data. You can adjust from there — but start clean. **Copy-paste reporting**\ Weekly inventory snapshots that get pasted into a summary tab, then emailed. Moselle's reporting gives you live projections, so the manual compile step disappears. **The single-person dependency**\ Most inventory spreadsheets have one person who truly understands them. When that person is out, planning stalls. Moselle is built for team access — so institutional knowledge lives in the system, not in one person's head. *** ### How to build trust in Mo, step by step **Week 1–2: Verify the forecast**\ Ask Mo to show you projections for SKUs you know well. Compare them to what your gut says. Note where they're close and where they diverge. Ask Mo why — it can explain the signals driving any projection. **Week 3–4: Run a parallel plan**\ Keep your spreadsheet open but create your replenishment plan in Moselle. See how the two compare. You'll usually find Moselle catches something the spreadsheet missed — a stockout risk, a timing issue, an overorder. **Week 5+: Let Mo drive**\ Once you've seen the outputs hold up over a few cycles, start trusting Mo's recommendations as your starting point. Override where you have context Mo doesn't — a promotion coming, a supplier delay you know about. That's the right use of your judgment. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://learn.moselle.io/getting-started/onboarding/moving-off-spreadsheets.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.