> For the complete documentation index, see [llms.txt](https://docs.b2b-sellers.com/b2b-platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.b2b-sellers.com/b2b-platform/developer-guide/how-to/integration-of-erp-orders-to-shopware-6.md).

# Import Orders and Offers

Centralizing order data is a core requirement for B2B platforms. To ensure all transactions, whether they originate from an ERP system or other external sources, are visible within Shopware, a reliable integration is essential.

While the standard Shopware Admin API allows for order creation, it often requires complex workflows and deep platform knowledge. To solve this, the B2Bsellers Suite provides a Simplified Admin API Endpoint designed for high-performance data synchronization with minimal overhead.

## Key Advantages

* Identifier Flexibility: Unlike standard endpoints that require UUIDs, our API allows you to use familiar identifiers such as Product Numbers (SKUs), Order Numbers, and Customer Numbers.
* Support for External Products: By specifying a "custom" product type, you can include line items that do not exist in the Shopware database. This is ideal for one-off services or legacy ERP items.
* High Performance: The endpoint is optimized for batch processing, enabling you to create large volumes of orders or offers in a single request.
* Simplified Logic: Create fully functional orders and offers with significantly less payload data than the standard core API.

## Implementation Example

This endpoint is typically used by middleware or ERP connectors to push historical or external order data into the B2B Platform, ensuring the customer has a "Single Point of Truth" for their order history.

{% hint style="info" %}
This endpoint is particularly useful for Offer Migration, allowing you to sync open quotes from an external CRM directly into the B2Bsellers Offers section.
{% endhint %}

{% content-ref url="/pages/QkaxxjDzezXDDd9UWs2m" %}
[Broken mention](broken://pages/QkaxxjDzezXDDd9UWs2m)
{% endcontent-ref %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.b2b-sellers.com/b2b-platform/developer-guide/how-to/integration-of-erp-orders-to-shopware-6.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.