> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://doc.common-services.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Error: Octopia order state not mapped (order import)

When importing orders, you may see:

> The Octopia order state 'XXX' for order YYY (Standard (Seller)) is not mapped to a PrestaShop status. Please configure 'XXX' in the module Orders settings.

or, for fulfillment:

> The Octopia order state 'XXX' for order YYY (C Logistique (Fulfillment)) is not mapped to a PrestaShop status. Please configure 'XXX' in the module Orders settings.

*(*_`XXX`_ *= Octopia status,* *`YYY`* *= order reference / id.)*

Sometimes a **warning** (import still proceeds):

> Note: default order state was used for order … because the Octopia order state was not mapped (…)

### Cause

Each marketplace (Octopia) status must be linked to a **PrestaShop order state** in the module **Orders** tab. Without a mapping (and without a default state), the order is **rejected** to avoid a PrestaShop “Invalid new order status” error.

Two separate blocks:

- **Orders States** — seller (Standard) orders
- **Orders States (C Logistique)** — fulfillment orders

### What to do

1. Open the module configuration → **Orders** tab.
2. For each Octopia status you receive, choose a PrestaShop order state.
3. Save the configuration.
4. Optional: **Default PrestaShop order state for unmapped Octopia statuses** — if a status is not mapped yet, import can use that default (`Disabled — require mapping` = mapping required for every status).

Then retry import: [Orders import](https://doc.common-services.com/en/article/orders-import-gddlqn/)

For **shipment / tracking notification** (after import), see: [Orders Statuses](https://doc.common-services.com/en/article/orders-statuses-jjk3p0/) — a different topic from import mapping.