> For the complete documentation index, see [llms.txt](https://docs.hubyte.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hubyte.de/dropshipping-bestellung-an-lieferanten-herstelle/english-documentation/plugin-configuration.md).

# Plugin configuration

The global plugin configuration can be found in the Shopware administration under:\
**Settings > System > Plugins > Huebert Dropshipping > Configure**

***

## Test mode

Test mode allows you to safely test the plugin without sending real emails to suppliers.

| Setting                | Description                                                                                   |
| ---------------------- | --------------------------------------------------------------------------------------------- |
| **Test email address** | All dropshipping emails are sent to this address instead of the configured supplier addresses |
| **Activate test mode** | Enables test mode. All supplier and manufacturer emails are redirected to the test address    |

> **Note:** Enable test mode during initial setup to verify your configuration before real emails are sent.

***

## Trigger status (payment & order status)

Defines which **payment status** or **order status** triggers the sending of dropshipping emails. The trigger fires as soon as one of the configured statuses is set.

| Setting                      | Description                                |
| ---------------------------- | ------------------------------------------ |
| **Trigger status (payment)** | Payment status that triggers email sending |
| **Trigger status (order)**   | Order status that triggers email sending   |

**Available payment statuses:**

* Disabled
* Authorized
* Cancelled
* Chargeback
* Failed
* In progress
* Open
* **Paid** *(default)*
* Partially paid
* Refunded
* Partially refunded
* Reminded

**Available order statuses:**

* Disabled *(default)*
* Open
* In progress
* Completed
* Cancelled

> **Tip:** In most cases, "Paid" is a sensible trigger for the payment status, as it ensures that the order is only forwarded to the supplier after payment has been received.

***

## Additional trigger status

You can configure a **second trigger status** to send emails on two different status transitions. The trigger still fires as soon as any one of the configured statuses is met.

| Setting                        | Description                                                                                      |
| ------------------------------ | ------------------------------------------------------------------------------------------------ |
| **Trigger status 2 (payment)** | Second payment status as trigger                                                                 |
| **Trigger status 2 (order)**   | Second order status as trigger                                                                   |
| **Resend email on trigger**    | Email is resent when the trigger status is set, even if an email was already sent for this order |

***

## General email options

| Setting                           | Description                                                                   |
| --------------------------------- | ----------------------------------------------------------------------------- |
| **BCC email**                     | This address receives a blind copy (BCC) of all dropshipping emails           |
| **Send email on order placement** | Email is sent immediately after order placement, regardless of trigger status |
| **Add attachments**               | CSV or XML file is attached to the email *(default: active)*                  |
| **Email template**                | Select the email template to use                                              |
| **No email if in stock**          | Does not send an email if the product is still in stock                       |

### Email templates

The following templates are available:

| Template                                           | Description                               |
| -------------------------------------------------- | ----------------------------------------- |
| `Dropshipping Partner Delivery Note`               | Older version (V1)                        |
| `Dropshipping Partner Delivery Note v2`            | Current default version *(recommended)*   |
| `Dropshipping Partner Delivery Note mpXgastronomy` | Specifically for the mpXgastronomy plugin |

> For more details on email templates, see [Email templates](/dropshipping-bestellung-an-lieferanten-herstelle/english-documentation/email-templates.md).

***

## DHL shipping labels

> These features require the free extension **DHL Versand by Pickware**.

| Setting                            | Description                                                      |
| ---------------------------------- | ---------------------------------------------------------------- |
| **Activate DHL shipping labels**   | Enables automatic DHL label creation                             |
| **Send label as email attachment** | The DHL label is attached to the supplier email as a PDF         |
| **Reuse existing label**           | Does not create a new label if one already exists for this order |

> For more details on the DHL integration, see [DHL integration](/dropshipping-bestellung-an-lieferanten-herstelle/english-documentation/dhl-integration.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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://docs.hubyte.de/dropshipping-bestellung-an-lieferanten-herstelle/english-documentation/plugin-configuration.md?ask=<question>
```

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.
