> For the complete documentation index, see [llms.txt](https://learn.moselle.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.moselle.io/mo/key-capabilities/ask-mo-about-your-supply-chain.md).

# Ask Mo About Your Supply Chain

Ask Mo about your supply chain in Moselle — lead times, stockout recovery, transfer versus reorder, and network gaps — with example prompts to copy and paste.

{% hint style="info" %}
**Quick Answer:** Once you've mapped your network on **Operations > Inventory > Supply Chain**, Mo can read it. Ask questions in plain language — "what feeds our East Coast warehouse?", "if we order today, when does stock land?", "is a transfer faster than a new PO?" — and Mo answers from your actual routes and lead times instead of general rules.
{% endhint %}

## What Does Mo Know About My Supply Chain?

**Mo reads the supply network you've mapped** — your warehouses, suppliers, factories and 3PLs, the lanes between them, and the terms attached to each route. That turns questions about *where stock comes from and how long it takes* from guesswork into arithmetic against your own setup.

Specifically, Mo can see:

* **Every location** and what supplies it — made there, bought from a named supplier, or transferred in from another site
* **Every lane**, in both directions, so it can trace a route forwards or backwards
* **Lead times** — production and transit, and the total time from placing an order to stock being available
* **Order terms** — minimum order quantities and order multiples
* **Stock policies** — the minimum and maximum inventory targets you've set
* **Channel fulfilment** — which location or region each sales channel ships from
* **Per-SKU exceptions** — when your question is about specific items rather than a whole location
* **Structural gaps** — the same problems the **Network problems** panel lists on the Supply Chain page

{% hint style="info" %}
**Mo knows your network exists before you ask.** It carries a running count of your locations, lanes, sources, stock policies and channels, so it looks your setup up rather than answering a routing question from sales history. If you haven't mapped anything yet, Mo tells you that instead of inventing a supply chain.
{% endhint %}

## Prerequisites

**Time Required:** Under a minute per question\
**Difficulty:** Beginner

* [ ] Your network is mapped on **Operations > Inventory > Supply Chain** — at minimum, the lanes and sources that matter to you
* [ ] Lead times are filled in on the routes you're asking about
* [ ] Mo credits available on your account

{% content-ref url="/pages/fjQL5Ho3uiOxopJxw9pB" %}
[Supply Chain Network](/operations/inventory/supply-chain-network.md)
{% endcontent-ref %}

## Example Prompts by Job

Copy these and swap in your own warehouse, supplier and SKU names. Exact names work best — they match what Mo sees in your network.

### Lead Times and Arrival Dates

* "What's the total lead time for `SKU-001` at our East Coast warehouse?"
* "If we place an order with `Acme Supply Co` today, when does stock become available?"

{% hint style="info" %}
Mo uses the total lead time recorded on the route, so production and transit time are already accounted for. If a number looks wrong, it's the network that needs correcting, not the question.
{% endhint %}

### Sourcing and Routing

* "What feeds our East Coast warehouse, and how long does each route take?"
* "Trace our Shopify channel back to where its stock is made."

### Stockout Recovery

* "How fast can we recover a stockout on `SKU-001` at our main warehouse?"
* "If we cancel the open order for `SKU-001` today, when does our DTC channel run dry?"

### Transfer vs. Reorder

* "Is transferring `SKU-001` from the West Coast faster than a new order from `Acme Supply Co`?"
* "Which of our warehouses could cover this shortfall soonest?"

### Risk and Exposure

* "Which channels ship from our East Coast warehouse?"
* "If our factory slips two weeks, which channels are exposed and by how much?"

### Auditing Your Setup

* "Are there any problems with how my supply network is mapped?"
* "What should I fill in next to make my network more useful?"
* "Why can't Mo see this lane I just added?"

{% hint style="success" %}
That last pair is the fastest way to finish a half-built map. Mo reads the gaps directly, so it can hand you a to-do list rather than making you hunt for what's missing.
{% endhint %}

## Two Things Mo Won't Do

**Mo doesn't build or edit your network.** It reads the map; you draw it. Adding a lane, changing a lead time, or grouping warehouses into a region all happen on the Supply Chain canvas. If you ask Mo to change a route, it can tell you where to go and what to change — it can't make the edit for you.

**Mo can only be as precise as your map.** A route with no lead time recorded can't produce an arrival date, and an unmapped warehouse looks independent of everything else. Answers get sharper as lanes, sources, lead times and order terms go in — which is the best argument there is for finishing the map.

## Tips for Better Answers

* **Use exact names.** Warehouse, supplier, region and channel names should match what's in Moselle.
* **Name the SKU when it matters.** Per-item lead times and order terms are pulled in when you ask about specific items, so "for `SKU-001`" is worth adding.
* **Ask "what would happen if…"** — delays, cancellations and slipped factory dates are all fair questions.
* **Stay in the conversation.** Follow up in the same thread rather than starting over; Mo keeps your network context.
* **Ask on the page you're looking at.** On a warehouse page, Mo already knows which location you mean, so "how would this site recover?" works without naming it.
* **Save the ones you reuse.** Recurring checks — weekly exposure, network gaps — are worth saving as prompts.

{% content-ref url="/pages/DAsnRIRTbbjM6bgR0RLM" %}
[Save Your Favourite Prompts](/mo/tips/save-favourite-prompts.md)
{% endcontent-ref %}

## Frequently Asked Questions

### Do I have to map my supply chain for Mo to be useful?

**Answer:** No — Mo answers plenty without it. But routing, lead time and arrival questions depend on the map, and Mo will tell you when no network is configured rather than guessing at one.

### Can Mo change my supply network for me?

**Answer:** No. Mo reads the network; edits are made by you on the Supply Chain canvas. Mo can tell you exactly what to change and where.

### Does Mo know about archived warehouses and channels?

**Answer:** Retired locations and channels aren't treated as live problems, but a live route still pointing at something archived does get flagged — so nothing dangles unnoticed.

### Will Mo use per-SKU lead times or just the location default?

**Answer:** Both. A route with no item attached applies to every item at that location, and Mo pulls the SKU-specific exceptions when you name the items you're asking about.

### Can Mo tell me how much stock is actually sitting somewhere?

**Answer:** Yes — Mo combines the network's structure with your live inventory, so "what's at this location and how quickly can we top it up?" is a single question.

### Why can't Mo see a lane or connection I can see on the canvas?

**Answer:** It's likely still showing a **red chip** — a work-in-progress connection that hasn't been filled in and confirmed, so it hasn't saved to your network yet. Mo only reads what's actually saved, so an unconfirmed connection stays invisible to it until you finish and confirm it on the canvas.

## Troubleshooting Common Issues

| Problem                                                   | Solution                                                                                                       | Time to Fix |
| --------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- | ----------- |
| Mo says no supply network is configured                   | Nothing has been mapped yet. Add your lanes and sources on **Operations > Inventory > Supply Chain**           | 10 minutes  |
| Mo can't give an arrival date                             | The route has no lead time recorded. Open the connection on the canvas and add production and transit days     | 2 minutes   |
| Mo's answer names the wrong warehouse                     | Warehouse names in your prompt didn't match Moselle. Use the exact names as they appear in your warehouse list | 1 minute    |
| Mo says a location can't be reached                       | There's no source or inbound lane for it. Add one, or check whether it should be archived                      | 5 minutes   |
| Mo's routing looks out of date                            | The map changed mid-conversation. Ask again — Mo re-reads the network for a new question                       | 1 minute    |
| Mo doesn't mention a connection you can see on the canvas | It's probably an unconfirmed connection showing a **red chip**. Finish and confirm its details to save it      | 2 minutes   |

## Related Guides

{% content-ref url="/pages/fjQL5Ho3uiOxopJxw9pB" %}
[Supply Chain Network](/operations/inventory/supply-chain-network.md)
{% endcontent-ref %}

{% content-ref url="/pages/kwz42KRZ3r6QG3PqvnnS" %}
[Update Inventory with Mo](/operations/inventory/update-inventory-with-mo.md)
{% endcontent-ref %}

{% content-ref url="/pages/HNe3qiLOPZnSe0stHRX3" %}
[Get Better Results with Mo](/mo/tips/tips-for-better-prompts.md)
{% endcontent-ref %}