Get Better Results with Mo
Mo is available throughout Moselle. Ask questions in natural language — no specific format required.
Understanding how Mo processes a question will help you get better answers faster and know when to give it more guidance.
How Mo works through a question
When you send Mo a message, it moves through a few stages before responding.
1. It identifies what you're asking Mo reads your question and determines the business concept — stockout risk, sell-through rate, reorder quantity, demand trend — along with the scope: which SKUs, which channel, which time period. If something is ambiguous, Mo will make a reasonable assumption and tell you what it assumed, or ask a clarifying question if it can't resolve it on its own.
2. It pulls from your connected data Mo works from the data Moselle has access to: your sales history, current inventory levels, SKU catalog, supplier lead times, and channel breakdown. It draws on whichever of these is relevant to your question and cross-references across them to build its answer.
3. It checks whether the answer makes sense Before responding, Mo evaluates whether the result is internally consistent — if a number looks anomalous, it will flag it rather than presenting it as fact. Mo will tell you when it's uncertain and explain why.
4. It responds and shows its reasoning Mo formats its answer based on what you asked for — a recommendation, a number, an analysis, a ranked list — and explains the logic behind it so you can decide whether to act on it or adjust it.
What Mo can see
Mo's answers are only as good as the data behind them. It can work with:
Sales history — order data synced from your connected channels (Shopify, Amazon, Walmart)
Inventory levels — current stock positions across locations, synced from your fulfillment integrations
SKU catalog — your products, variants, bundles, and bill of materials
Supplier data — lead times and supplier details you've added to Moselle
Forecasts — the 12-month projections Moselle has generated for your SKUs
Current conversation — everything you've said in this session, including context you've added along the way
What Mo can't see:
Information not in Moselle — if a supplier lead time hasn't been entered, or a channel isn't connected, Mo won't know. It may make a reasonable assumption, but it will say so.
Previous conversations — Mo starts fresh each session. Context you established in a past conversation doesn't carry over. If there's something Mo should always know — a planning assumption, a key definition — the best place for it is in your Moselle setup, not a previous chat.
External signals — Mo doesn't browse the web or pull in market data. Its view is your business, not the broader market.
When to give Mo more guidance
Mo works well with plain questions. But the more specific you are, the sharper the answer.
"What should I order?"
"What should I order for our wholesale channel, assuming a 10-week lead time from our main supplier?"
"Which SKUs are at risk?"
"Which SKUs are at risk of stocking out before the end of Q2, across our Shopify and Amazon channels?"
"How's our inventory looking?"
"How many months of cover do we have on our top 10 SKUs by revenue, based on current forecast?"
Give Mo more guidance when:
Your question involves a definition Mo might not share — if "slow mover" or "at-risk" means something specific to your business, say so. Mo will apply your definition rather than guessing.
You have context Mo doesn't — a promotion coming up, a supplier delay, a new product launch. Add it to the question and Mo will factor it in.
The answer doesn't look right — ask Mo to explain its reasoning. If there's a mismatch between what Mo assumed and what you intended, a follow-up question in the same session will correct it.
Mo will tell you when it needs more information. It will also tell you when it's made an assumption — which is usually the signal to either confirm it or add the missing context.
Last updated