> For the complete documentation index, see [llms.txt](https://docs.live-eo.com/tradeaware/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.live-eo.com/tradeaware/using-the-tradeaware-web-app/manage-your-transactions/mixed-origin-re-import-and-self-managed-supplier-transactions.md).

# Mixed-Origin, Re-Import, and Self-Managed Supplier Transactions

Some transactions cannot be described using only supplier plots *or* only upstream DDS references.

This page explains how to create a transaction when your final product:

* includes inputs from multiple suppliers (mixed origin), or
* needs both an upstream DDS reference and supplier plots (re-import / hybrid), or
* is managed under one account where you upload and manage supplier plots yourself (self-managed suppliers).

### Quick decision guide

Use this guide to identify which flow matches your business process:

```ps
Do you submit ONE DDS for ONE final product (one HS code)?
  |
  +-- Does the product include inputs from multiple suppliers?
  |      -> Mixed-Origin (multiple suppliers on one product)
  |
  +-- Do you have an upstream EU DDS reference, AND also need non-EU supplier plots?
  |      -> Re-Import / Hybrid (DDS reference + supplier plots)
  |
  +-- Do you manage supplier plots under your own TradeAware account
      (no supplier accounts / no supplier IDs)?
         -> Self-Managed Supplier (no supplier business selected)
```

#### Why TradeAware supports this

In mixed-origin and re-import scenarios, you still submit **one DDS for one final product**, but the traceability data can come from **multiple sources**:

* multiple suppliers (each with their own plots), and/or
* upstream DDS references (EU inputs already declared), and/or
* plots stored centrally under one business account (self-managed model).

TradeAware supports these flows to help you submit a compliant DDS without splitting a single final product into multiple “products” just to represent your upstream structure.

### Creating a Mixed-Origin transaction (multiple suppliers on one product)

Use this when one final product (one HS code) includes inputs from multiple suppliers.

**Diagram**:

```powershell
Supplier A (plots)     Supplier B (plots)     Supplier C (plots)
        \                    |                    /
         \                   |                   /
          ----------- ONE final product (HS code) ----------
                               |
                           ONE DDS
                               |
                           EU market
```

**Steps:**

1. Go to Manage your transactions.
2. Select the plus icon in the top right of the Transaction table to create a new transaction.
3. Select the relevant Activity.
4. Select Add product or commodity, choose your HS code, then select Save.
5. In the product row, select a supplier in the Supplier dropdown.
6. Select Manage plots and choose the plots that apply to that supplier.
7. Add the next supplier to the same product row and repeat steps 5–6 for each supplier.

💡 Why multiple suppliers on one product?\
This keeps the transaction as **one product / one DDS**, while still attaching the correct plots for each supplier.

### Creating a Re-Import / Hybrid transaction (DDS reference + supplier plots)

Use this when your final product includes:

* EU input already covered by an upstream DDS, and
* non-EU input that must include supplier + plots.

**Diagram**:

```powershell
Upstream EU DDS reference (EU input)
               +
Non-EU Supplier (plots)
               |
      ONE final product (HS code)
               |
             ONE DDS
```

**Steps**:

1. Create a new transaction and select the correct Activity.
2. Add an upstream DDS reference using the Add reference statement button (Reference Number + Verification Number).
3. Select Add product or commodity, choose your HS code, then select Save.
4. In the product row, select the supplier (for the non-EU input).
5. Select Manage plots and choose the plots linked to that supplier.
6. Select Submit when ready.

💡 In a re-import/hybrid scenario, you may need both the DDS reference and supplier plots because your final product includes mixed inputs.

⚠️ **Regulatory note (Re-Import / Hybrid)**\
The EU is discussing simplifications to EUDR processes, including how upstream DDS references may be reused. If these changes are implemented, you may no longer need to combine DDS references + supplier plots in the same product for some re-import scenarios. TradeAware will align with official guidance and this page will be updated accordingly.

***

### Creating a transaction with self-managed supplier plots (no supplier business)

Use this when you manage supplier plots under one account (e.g. you collect plot data in your own supplier portal and upload it into TradeAware), and you want to submit a transaction without selecting a supplier business.

**Diagram**:

```powershell
Your company collects supplier plots externally
               |
Uploads & manages plots under ONE TradeAware account
               |
Creates DDS using those plots (no supplier business selected)
```

**Steps:**

1. Create a new transaction and select the correct Activity.
2. Add your product/HS code as usual.
3. In the product row, do not select a supplier business.
4. Select Manage plots and choose the plots stored under your business account.
5. Select Submit when ready.

💡 When is this useful?\
This is common if you operate a centralized supplier onboarding process and store all supplier geolocation data under one TradeAware business account.

⚠️ Note\
Use this only if your business is responsible for maintaining the plot data and ensuring it reflects the correct upstream suppliers.w


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.live-eo.com/tradeaware/using-the-tradeaware-web-app/manage-your-transactions/mixed-origin-re-import-and-self-managed-supplier-transactions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.