> For the complete documentation index, see [llms.txt](https://docs.solutioo.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solutioo.de/shopware/shopware6_en_us/master-data-management/product-data-sheet-as-pdf.md).

# Product Data Sheet as PDF

{% hint style="info" %}
This function is provided as an extension. Contact us to find out whether it is available for your installation.
{% endhint %}

Directly from the Item Card, you can create a **product data sheet** as a PDF in A4 landscape format – ideal for sales, catalogs, and customer inquiries.

**Contents of the data sheet**

* **Cover image** and **image gallery** from the item pictures stored in Shopware.
* **Marketing text** of the item.
* Optional origin statement **“Made in …”** including the country flag (DE, ENG, and FRA are integrated; further countries can be configured).
* **Freely configurable attribute data blocks** for a flexible presentation of the product information.
* **Fixed details** such as Item No., EAN/GTIN, packaging unit, and recommended sales price.

**Configuration**

A dedicated setup page lets you individually configure the attributes used, the section headings, the logo, and the footer.

{% hint style="success" %}
When you download the file, the **item name is automatically used as the file name** of the PDF.
{% endhint %}


---

# 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.solutioo.de/shopware/shopware6_en_us/master-data-management/product-data-sheet-as-pdf.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.