> ## 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).

# Transport

![Prestashop Mirakl Transport](https://storage.crisp.chat/users/helpdesk/website/-/3/f/a/8/3fa8ee645cd13200/screencapture-ps8-common-servi_m9jwfz.png)

On the **Transport** tab you configure **shipping delay**, **shipping fees for offer export**, which PrestaShop **carrier** is used by default, how **Mirakl carriers** map to PrestaShop on order import, and (optionally) **Mondial Relay** pickup points.

Configure the fields **from top to bottom**.

One configuration **per marketplace**: [Multi-marketplace](https://doc.common-services.com/en/article/multi-marketplace-720rdi/).
---

### Step 1 — Shipping Delay

**Delivery time** field.

Enter the usual shipping delay in **days** (e.g. `1` or `2`).

This value is sent with your **offers** to Mirakl (how long before you ship).

You can still set a different delay per profile (**Delay Preparing**) or per product (**Shipping Delay Override** on the product Mirakl tab).

---

### Step 2 — Shipping Fees

**Additional** field.

Enter an **extra shipping fee percentage** (e.g. `0` or `10`).

This % is added to the shipping amount calculated from the **Standard** carrier (step 3) when **exporting offers**.

* Example: if the carrier grid gives **5 €** shipping and **Additional** is `10`, the module sends about **5.50 €** shipping on the offer.
* Leave `0` if you do not want any extra %.
---

### Step 3 — Carriers → Standard

Choose **one** PrestaShop carrier (e.g. DPD, Colissimo…).

The module uses that carrier’s **shipping price grid** to calculate shipping when exporting offers.

It is also the **default** PrestaShop carrier on imported Mirakl orders, unless a more specific mapping is set in step 5.

---

### Step 4 — Mondial Relay integration (optional)

Section: **Pickup Point Integrations** → **Mondial Relay integration**.

#### When to enable

Enable **only** if:

1. Customers can choose a **Mondial Relay / PUDO / locker** pickup point on your Mirakl marketplace, **and**
2. You have a Mondial Relay PrestaShop module installed and enabled, for example:
   * `mondialrelay`
   * `mondialrelayadvanced`
   * `mondialrelayinpost` (Mondial Relay – InPost)

If you do **not** ship via Mondial Relay pickup points, leave the checkbox **unchecked** (default).

#### What it does

When **enabled**, for Mirakl orders that include a **relay / PUDO** (pickup point ID):

1. The Mirakl module imports the order into PrestaShop as usual.
2. It copies the **selected relay** (point ID + address from Mirakl) into the **Mondial Relay module tables**.
3. The order can then appear in the Mondial Relay back office (e.g. **Generating Labels**) so you can print labels.

Without this option, the order may still import, but the pickup point may be **missing** in Mondial Relay → labels often fail or the order does not show in “Generating Labels”.

#### What you must also configure

* Map Mirakl Mondial Relay / PUDO delivery modes to the correct PrestaShop Mondial Relay carrier in **Incoming order - carrier mapping** (step 5).
* Keep the Mondial Relay module configured (API / account / weight rules) as in that module’s documentation.
* After changing marketplace or carriers, use **Verify connection** (Authentication) so Mirakl carrier lists stay up to date.

#### Mondial Relay tools (shown when integration is enabled)

After you enable integration and **Save**, a **Mondial Relay tools** block can appear. These are **manual repair URLs** (open in a browser). They are **not** for crontab.

They need the module **Instant token** (`MIRAKL_INSTANT_TOKEN`) when your shop requires it (typical on PrestaShop 1.7; on PS 8+ the token may be optional depending on your setup).

| Tool | Use when |
| ---- | ---- |
| **Repair Mondial Relay all the failed orders** | Re-sync **every** Mirakl-imported order detected as failed. |
| **Repair by PrestaShop order ID(s)** | Fix one or more PS orders (e.g. `326358` or `326358,326359`). |
| **Repair by Mirakl order ID(s)** | Fix by Mirakl id (e.g. `1000182751-A`); the tool finds linked PrestaShop orders then repairs them. |

**Failed order** (for these tools) means roughly:

* the order is linked in Mirakl marketplace orders, **and**
* the shipping carrier is a Mondial Relay module carrier, **and**
* the Mondial Relay “selected relay” row is **missing** or has an **empty** relay number.

**Safety:** do **not** pass Mirakl order IDs and PrestaShop order IDs in the same request.

If the Mondial Relay module is **not** installed or not enabled, the tools show a warning and stay disabled.

There may also be a repair selector on the **Orders** area of the module for failed Mirakl orders (select orders or “all failed”).

#### Typical Mondial Relay checklist

1. Install / enable Mondial Relay (or InPost) module and configure it.
2. On **Transport**, enable **Mondial Relay integration** → **Save**.
3. Map Mirakl pickup carriers → PrestaShop Mondial Relay carrier (step 5).
4. Import a test relay order → check Mondial Relay **Generating Labels**.
5. If the relay is missing, use a **Repair** tool, then try the label again.

---

### Step 5 — Incoming order - carrier mapping

Link:

**Mirakl carrier / delivery mode** → **PrestaShop carrier**

Example: Mirakl “Standard” → PrestaShop “DPD”; Mirakl “Mondial Relay” → your PrestaShop Mondial Relay carrier.

Before mapping, use the link **Verify connection to update the list of Mirakl carriers** (Authentication tab) to refresh the Mirakl list.

Click **+**, choose the Mirakl carrier on the left and the PrestaShop carrier on the right. Add one row per Mirakl delivery mode you use.

Without mapping, order import often fails with a message asking you to configure **Transport → Carrier Mapping**.

---

### Step 6 — Resolve Unmapped Carrier

If an order arrives with a Mirakl carrier that is **not** in the mapping above:

* checkbox **off** → import may **fail** with an error;
* checkbox **on** → then choose:
  * **Use default carrier** — pick a fallback PrestaShop carrier for all unmapped cases, or
  * **Auto create carrier** — PrestaShop creates a new carrier from the Mirakl carrier name.

Prefer a complete mapping (step 5). Use this as a safety net only.

---

### Step 7 — Carrier Code Mapping

For each PrestaShop carrier, you can enter the marketplace **Mirakl carrier code**.

* **With code** → when you ship, tracking is sent to Mirakl with that official code.
* **Without code** → the module sends the PrestaShop carrier **name** + tracking URL.

Also check the tracking URL under **Shipping → Carriers** (`@` = parcel number).

Ask your Mirakl operator for the official carrier codes if you are unsure.

---

### Step 8 — Save

Click **Save** at the bottom of the tab (or module page). Nothing is stored until you save.

---

## Common mistakes

* Using **Additional %** thinking it raises product prices → use [Profiles](https://doc.common-services.com/en/article/profiles-16bb40d/) **Price Rule** instead.
* Enabling Mondial Relay without the Mondial Relay module installed.
* Enabling Mondial Relay but not mapping Mirakl PUDO carriers in step 5.
* Forgetting **Verify connection** so Mirakl carriers do not appear in the mapping list.
* Incomplete **Carrier Code Mapping** → tracking updates fail or use the wrong label on Mirakl.

---

## Next

[Orders](https://doc.common-services.com/en/article/orders-w2n36p/), [Export offers](https://doc.common-services.com/en/article/export-offers-7dacds/), [Scheduled tasks](https://doc.common-services.com/en/article/scheduled-tasks-2og48k/), [Get your Mirakl API keys](https://doc.common-services.com/en/article/get-your-mirakl-api-keys-1g54d55/), [Profiles](https://doc.common-services.com/en/article/profiles-16bb40d/).