# Meet Mo Mo is the AI built into Moselle. Before getting into what Mo can do, it helps to understand how Mo and Moselle relate to each other — because they're not the same thing. {% embed url="" %} Meet Mo | The Demand Planner {% endembed %} *** ### Moselle vs. Mo **Moselle** is the platform. It connects to your data sources, manages your inventory lifecycle, generates forecasts, tracks orders, and gives you a live view of your operations. It's the system of record for your inventory. **Mo** is the intelligence layer inside Moselle. Mo reads your data, identifies patterns, surfaces insights, and gives you recommendations — in plain language, in response to plain questions. Mo makes Moselle useful without requiring you to become an analyst. Think of it this way: Moselle holds the data. Mo knows what to do with it. You can use Moselle without talking to Mo — run reports, review forecasts, manage orders. But Mo is how you get the most out of what Moselle knows. *** ### What Mo can do Mo operates across three roles depending on what you need. *** **Demand analyst** Mo delivers on-demand reports on sales performance, demand projections, and trend analysis. Ask it about any SKU, category, channel, or time period and it will pull the relevant data, identify what's notable, and tell you what it means. > *"How has sell-through for our core collection trended over the last 90 days?"*\ > \&#xNAN;*"Which SKUs are tracking ahead of forecast this month?"* *** **Inventory planner** Mo connects directly to your inventory levels, bill of materials, and stock positions across locations. It can build replenishment recommendations, flag at-risk SKUs, suggest allocation strategies, and generate production schedules — grounded in your actual data, not assumptions. > *"What should my next purchase order look like for Q3?"*\ > \&#xNAN;*"Which products are at risk of stocking out before my next production run?"* *** **Growth partner** This is where Mo goes beyond operations and into revenue. Most inventory tools focus on avoiding problems — stockouts, overstock, delays. Mo does that too. But it also looks at your inventory position as a growth lever. **Overstocked on something?** Mo can identify which products have excess inventory and suggest where to deploy them — a promotional push, a bundle, a channel shift — to move stock and recover margin before it becomes a write-off. **Running a promotion?** Mo can model how a planned discount or campaign is likely to affect sell-through, and whether your current inventory position can support the uplift. No surprises mid-campaign. **Scaling a marketing channel?** Mo connects your inventory position to your revenue goals. If you're planning to increase spend on a channel, Mo can flag whether your stock levels support the demand that would generate — and what to order if they don't. > *"We're running a 20% off promotion on our top three SKUs next month. Do we have enough inventory to support it?"*\ > \&#xNAN;*"Which overstocked products should we promote this quarter?"*\ > \&#xNAN;*"If our Shopify revenue grows 30% in Q4, what does that mean for our replenishment plan?"* The goal is to make sure your inventory strategy and your growth strategy are the same conversation — not two separate ones that only meet when something goes wrong. {% embed url="" %} Vibe Demand Planning with Mo | Edit Your Forecast {% endembed %} *** ## What's Next? Learn how to use Mo to build forecasts: {% content-ref url="" %} {% endcontent-ref %} Or jump right into creating your first forecast: {% content-ref url="" %} {% endcontent-ref %} --- # 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/mo/meet-mo.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.