# Onboarding
Welcome to Moselle. This section walks you through everything that happens from the moment your engagement begins to the moment you're fully live and operating independently on the platform.
Onboarding is structured as a five-week program designed to be hands-on, high-touch, and built around your business — not a generic walkthrough. By the end, you'll have a live forecast, a configured production plan, and a clear understanding of how to use Mo, your AI inventory planning assistant, every day.
***
## Before Week 1 — Setup & Preparation
Before your first onboarding call, the Moselle team works in the background to make sure Week 1 starts clean and productive.
**The CX team will:**
* Review your integration landscape and identify which connectors apply to your business (Shopify, Amazon, SPS Commerce, QuickBooks Online, Fulfil, NetSuite, and others)
* Pre-configure your channels and add any known warehouses based on intake information
* Complete a backfill of your historical sales data — clean historical data is critical for accurate forecasting from day one
{% hint style="info" %}
This prep work is completed 1–2 business days before your first onboarding call.
{% endhint %}
***
## Week 1 — Admin Setup & Team Introduction
Week 1 is about foundations: get the team connected, understand the business, and activate the account.
**Team & Account Setup**
* Meet your CSM and establish points of contact
* Discovery session to understand your business, key SKUs, channels, and pain points
* Enable and configure integrations: Shopify, Amazon, SPS Commerce, QBO, Fulfil, NetSuite, and any additional ERPs
* Invite your team members to the platform and configure accounts and permissions
* Define KPIs for onboarding completion and align on 3, 6, and 12-month goals
**Reporting & Communication**
* Learn how to send retail sell-through reports to your dedicated `@[yourcompany].moselle.io` inbox (if applicable)
* Configure your channels and warehouses within the platform
* Set a recurring cadence call schedule
### Introducing Mo
Mo is Moselle's AI inventory planning assistant. Think of it as having a dedicated supply chain analyst available 24/7 who knows your entire business inside and out.
{% hint style="warning" %}
**Note:** At this stage, live inventory and SKU data from integrations will not yet be loaded. Historical sales data may have been backfilled during pre-onboarding prep, but real-time data requires integrations to be activated first (done later in Week 1). The prompts below are designed to show you how Mo thinks and communicates — so you're ready to hit the ground running the moment your data goes live.
{% endhint %}
**First Call Demo Prompts — No Data Required**
| Prompt | Why It Works |
| --------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| `What data do you need from me to build an accurate demand forecast?` | Mo explains the inputs it uses — sales history, inventory, POs, and more — setting clear expectations and building confidence. |
| `What does a healthy inventory coverage report look like, and what should I be watching for?` | Mo walks through what "good" looks like, teaching you the framework and language you'll use in Moselle from day one. |
| `Once my data is loaded, what's the first report I should run?` | Mo builds anticipation and gives you a concrete next step — a natural bridge to what comes after Week 1. |
**Day-After Prompts — Once Live Integration Data is Loaded**
These prompts are sent to you after Week 1 integrations are configured, as a starting point to explore on your own.
| Prompt | What Mo Returns |
| ---------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| `Which of my SKUs are at risk of stockout in the next 60 days based on my current inventory and sales velocity?` | Mo cross-references live inventory against recent sales velocity to surface which SKUs need attention, ranked by urgency. |
| `Based on my last 90 days of sales, which SKUs should I prioritize for my next purchase order?` | Mo analyzes 90-day sell-through, factors in current stock and lead times, and returns a prioritized reorder list. |
***
## Week 2 — Platform Training & First Forecast
Week 2 shifts from setup to empowerment. Your CSM leads a live guided walkthrough of the platform while you follow along on your own account in real time.
**Forecasting Fundamentals**
* Walk through building your first forecast end-to-end
* Learn key features: duplicating a forecast, locking a forecast, adjusting time frames, and grouping by channels, SKUs, product line, and product type
* View projections for past months and current sales by unit
* Review 30 / 60 / 90-day sales velocity reporting
* Interpret your first real forecast results against actuals
### Mo Guidelines — What Your Demand Planner Needs to Know
Before Mo can produce a truly accurate forecast, it needs context that lives in your head — not just your data. Your CSM will walk through the following with you and show how each input can be fed directly into Mo to sharpen accuracy.
| Business Context | Example Mo Prompt |
| -------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Marketing Calendar** — Upcoming promotions, campaigns, or seasonal pushes | `"We have a 20% off sitewide sale running in 3 weeks. Adjust my 60-day forecast for SKUs in the [category] collection to reflect a 30% demand lift."` |
| **Seasonality** — Predictable seasonal patterns, peaks, and troughs | `"Based on last year's data, which SKUs have the strongest seasonal demand in Q4 and by how much does velocity typically increase?"` |
| **Out-of-Stock Events** — Periods where a SKU couldn't sell and shows artificially low demand | `"SKU [X] was out of stock from [date] to [date]. Exclude that period from the baseline and use surrounding weeks to fill the gap."` |
| **Phased-Out SKUs** — Products being discontinued or wound down | `"Mark SKU [X] as end-of-life. Stop generating reorder recommendations for it and flag when remaining inventory is projected to clear."` |
| **New Launches** — New SKUs with no sales history | `"We're launching [new SKU] next month. Use [existing SKU] as a comparable and build a launch forecast based on its first 90-day sell-through."` |
| **Promotional History** — Past discounts or bundles that caused demand spikes | `"SKU [X] had a BOGO promotion in [month] that inflated sales by roughly 40%. Remove that spike from the baseline so it doesn't skew the forecast."` |
| **Macro & External Factors** — Competitor stockouts, supply chain disruptions, or one-time demand shifts | `"In [month], a competitor went out of stock and we saw a 50% demand spike on SKU [X]. Flag that as a one-time event and exclude it from the forward forecast."` |
| **Replenishment Lead Time Changes** — Supplier lead times that have shifted | `"Our lead time for [supplier] has increased from 6 weeks to 10 weeks. Update all reorder point calculations for affected SKUs."` |
| **Price Changes Affecting Velocity** — Significant price increases or decreases | `"We increased the price of SKU [X] by 25% in [month]. Treat pre- and post-change velocity as separate demand periods and forecast using post-change data only."` |
### Critical Next Step — Validation
Before moving forward, you should:
1. Create your first forecast and verify that sales data, inventory levels, and projections are accurate across your channels
2. Explore the platform independently using what was covered in the Week 2 call
3. Confirm everything reflects reality — does the data match what you know about your business?
{% hint style="warning" %}
Ideally, validation takes one week. If inconsistencies are found, onboarding will be paused until they are resolved. Accurate sales data is the foundation everything else is built on.
{% endhint %}
**If something looks off**, notify the Moselle team. During validation:
* The CX team will meet with you to address issues immediately once identified, or
* You can send supporting documentation for the team to investigate — note this may take additional time
The CX team may request a raw sales data export to dig deeper.
***
## Week 3 — First Review & Validation
Week 3 flips the dynamic. You present your forecast back to your CSM — validating your understanding and surfacing any gaps before you go independent.
**Client-Led Forecast Review**
* You walk your CSM through your first completed forecast
* CSM reviews for accuracy, methodology, and any misconfigurations
* Identify and resolve any gaps before you move to self-serve
* Confirm all integrations are syncing correctly and data looks as expected
**Optimization & Next Steps**
* Walk through any adjustments or refinements to the forecast together
* Review Mo usage — confirm you're asking the right questions and interpreting outputs correctly
* Set expectations for ongoing cadence calls and self-serve workflows post-onboarding
***
## Week 4 — Production Planning: Signal to Execution
By Week 4, your forecast should be solid. Now it's time to act on it.
The forecast tells you what demand looks like. Mo helps you interpret it and catch issues. The Production Plan is the bridge from signal to execution — this is where you take action.
### Before the Call — Client Prep Required
{% hint style="info" %}
Send your MOQ (Minimum Order Quantities) and lead time data to your CSM ahead of this call. Having this ready allows the CSM to layer your real constraints into the demo, making it immediately relevant to your actual business.
{% endhint %}
**Production Planning Demo**
Your CSM will walk you through the Production Plan module:
* How the forecast feeds directly into the production plan — demand signal drives the production schedule
* How Moselle flags in real time whether there are enough components to fulfill a production run
* Exactly what you're short on and when the shortage will hit — the moment to take action
* How MOQ and lead time constraints shape what's actually executable
* How to add and manage Purchase Orders (POs) directly within the platform
* How open POs factor into available inventory and component coverage calculations
At the end of this call, you will have been through the full Moselle platform — forecasting, inventory, Mo, and production planning.
***
## Week 5 — Final Sign-Off & Onboarding Close-Out
Week 5 is the formal close of your onboarding engagement. A focused session to confirm you're fully set up, confident, and ready to operate independently.
**Final Review**
* Confirm all platform modules are configured and functioning: forecast, inventory, production plan, POs, and integrations
* Verify your team has the correct permissions and knows who to contact for support
* Final Mo check-in — are you using it confidently? Any outstanding questions?
**Onboarding Sign-Off**
* Formally close out the onboarding engagement
* Recap everything covered across the five-week program
* Transition to the ongoing CS cadence: recurring calls, Slack support, and QBR schedule
{% hint style="success" %}
You're now live and fully operational on Moselle.
{% endhint %}
***
## FAQ — Evaluating & Getting Started with Moselle
Answers to the questions prospects and new customers ask most.
Is there a dedicated Customer Success Manager for onboarding?
Yes. Every Moselle client is assigned a dedicated CSM from day one. Your CSM is your primary point of contact throughout the entire onboarding program and beyond.
Do you have a native integration with my ERP and sales channels?
Moselle has native integrations with the platforms most commonly used by consumer brands, including Shopify, Amazon, QuickBooks Online (QBO), and NetSuite — each with self-service setup guides. Integrations such as SPS Commerce and Fulfil are also supported but require CSM-assisted configuration rather than self-service setup. If you're running a different ERP or channel stack, your CSM will review your integration landscape during pre-onboarding prep and confirm what's supported before your first call.
How is historical sales data loaded — automatically or via import?
For supported integrations, historical sales data is backfilled automatically as part of the pre-onboarding setup — completed before your first call so the platform is ready to work from day one. In cases where a direct integration isn't available, your CSM will guide you through a structured data import process to ensure your history is loaded accurately.
What does "going live" look like — what's the first meaningful output?
Going live means having a validated forecast that reflects your real business. By Week 2, you'll have built your first forecast end-to-end with your CSM. By Week 3, you'll have reviewed and validated it against actuals. By Week 4, that forecast is driving your production plan — surfacing component shortages, shaping PO decisions, and giving you a clear line from demand signal to execution. The first meaningful output is a forecast you trust, built on your data, that you can act on.
What support is available after onboarding closes?
Onboarding graduation isn't the end — it's the beginning of your ongoing relationship with Moselle. After onboarding, you transition to a regular CS cadence that includes recurring check-in calls, dedicated Slack support for day-to-day questions, and a QBR (Quarterly Business Review) schedule to align on performance and platform evolution. Mo is also available 24/7 as your always-on planning assistant for anything that comes up between calls.
***
## What's Next?
Explore the platform setup guides to get your integrations and data connected:
{% content-ref url="onboarding/setup-integrations" %}
[setup-integrations](https://learn.moselle.io/getting-started/onboarding/setup-integrations)
{% endcontent-ref %}
{% content-ref url="onboarding/manual-data-uploads" %}
[manual-data-uploads](https://learn.moselle.io/getting-started/onboarding/manual-data-uploads)
{% endcontent-ref %}
Or jump straight into learning about Mo:
{% content-ref url="../mo/who-is-mo" %}
[who-is-mo](https://learn.moselle.io/mo/who-is-mo)
{% 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/getting-started/onboarding.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.