> For the complete documentation index, see [llms.txt](https://wiki.packstack.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.packstack.de/packstack-connect/einstellungen/pdf-templates.md).

# PDF-Templates

So kommst du dahin:

***

Auf dieser Seite findest du viele verschiedene Vorlagen, unter anderem die Rechnungsvorlagen. Einige Vorlagen sollten angepasst werden, da sie an deine Kunden geschickt werden. Dazu gehören:

* Zollerklärung
* Lieferschein
* Rücksendescheine

![](/files/N0DF7WS49EJPbOazluxe)

In der linken Spalte steht der Name des Templates. In der Spalte rechts daneben siehst du, wann das Template zuletzt bearbeitet wurde.

👁️ Klickst du auf das Auge, dann kannst du dir die Vorschau anzeigen lassen

✏️ Klickst du auf den Stift, dann kannst du das Template bearbeiten.

### **Rechnungstemplates** <a href="#fekzkc4ojjc5" id="fekzkc4ojjc5"></a>

Wenn du eine neue Version deines Rechnungstemplates erzeugen möchtest, klicke auf das + Symbol. Anschließend hast du die Möglichkeit den neuen (oder angepassten) Template-Code hochzuladend bzw. einzugeben. Danach steht das Template revisionssicher bereit. Vergiss nicht, das Template zu aktivieren, in dem du es als aktives Rechnungstemplate auswählst.

<div align="left"><img src="/files/x9DIremJmxIMUI5Jne6M" alt=""></div>

#### **Verfügbare Variablen** <a href="#ls8bem49pw0n" id="ls8bem49pw0n"></a>

Folgende Variablen kannst du in einem Rechnungstemplate verwenden. Bitte beachte, dass Variablen innerhalb doppelt geschweifter Klammern geschrieben werden müssen {{ variable }}

{% hint style="warning" %}
Diese Variablen sind für Leute mit Programmierwissen und sollte nur von diesen genutzt und eingebaut werden. Wenn du dieses Wissen nicht hast, suche dir bitte jemanden der diese Variablen für dich anwenden kann.
{% endhint %}

* invoice
  * id *<mark style="color:purple;">integer</mark>*
    * An internal unique identifier for the invoice
  * invoiceNr *<mark style="color:purple;">string</mark>*
    * the invoice assigned number with prefix and suffix
  * invoiceDate *<mark style="color:purple;">datetime</mark>*
    * the date on which the invoice has been created
  * ref *<mark style="color:purple;">string</mark>*
    * the payment reference number for the transaction
  * paymentGateway *<mark style="color:purple;">string</mark>*
    * the used payment method for the transaction
  * headline *<mark style="color:purple;">string</mark>*
    * A headline indicating that the document is an invoice, voucher or an order confirmation, cancellation with the order number
  * remark *<mark style="color:purple;">string</mark>*
    * An additional remark from the Shopify Order Remark Property
  * name *<mark style="color:purple;">string</mark>*
    * Customer billing address name
  * company *<mark style="color:purple;">string</mark>*
    * Customer billing address company name
  * address *<mark style="color:purple;">string</mark>*
    * Customer billing address address
  * address2 *<mark style="color:purple;">string</mark>*
    * Customer billing address addition
  * city *<mark style="color:purple;">string</mark>*
    * Customer billing address city
  * country *<mark style="color:purple;">string</mark>*
    * Customer billing address country
  * zip *<mark style="color:purple;">string</mark>*
    * Customer billing address zip code
  * totalNetto *<mark style="color:purple;">decimal</mark>*
    * The total invoice amount without VAT
  * totalBrutto *<mark style="color:purple;">decimal</mark>*
    * the total invoice amount including VAT
  * shopifyRefundId *<mark style="color:purple;">integer</mark>*
    * if the document is a voucher, the associated shopify refund id is included, otherwise null
  * isConfirmation *<mark style="color:purple;">bool</mark>*
    * Whether the document is tax invoice or an order confirmation
  * shopOrder *<mark style="color:purple;">array</mark>*
    * shopifyOrderId *<mark style="color:purple;">integer</mark>*
      * the shopify order identifier for the order
    * checkoutId *<mark style="color:purple;">integer</mark>*
      * a checkout identifier if the order was created with a checkout (e.g. from the online store sales channel)
    * orderName *<mark style="color:purple;">string</mark>*
      * Name of the order in Shopify
    * orderDate *<mark style="color:purple;">datetime</mark>*
      * The date of the order placement
    * name *<mark style="color:purple;">string</mark>*
      * Customer shipping address name
    * companyName *<mark style="color:purple;">string</mark>*
      * Customer shipping address company name
    * address *<mark style="color:purple;">string</mark>*
      * Customer shipping address street
    * address2 *<mark style="color:purple;">string</mark>*
      * Customer shipping address addition
    * housenumber *<mark style="color:purple;">string</mark>*
      * Customer shipping address housenumber
    * city *<mark style="color:purple;">string</mark>*
      * Customer shipping address city
    * plz *<mark style="color:purple;">string</mark>*
      * Customer shipping address zip code
    * country *<mark style="color:purple;">string</mark>*
      * Customer shipping address country
    * email *<mark style="color:purple;">string</mark>*
      * Customer’s email address
    * phone *<mark style="color:purple;">string</mark>*
      * Customer phone number
    * carrier *<mark style="color:purple;">array</mark>*
      * id *<mark style="color:purple;">integer</mark>*
        * An internal unique id for the used carrier
      * name *<mark style="color:purple;">string</mark>*
        * The name of the used carrier
    * prio *<mark style="color:purple;">integer</mark>*
      * Whether the order is a priority order (1) or a normal one (0)
  * positions *<mark style="color:purple;">array</mark>*
    * pos *<mark style="color:purple;">integer</mark>*
      * the position number on the invoice of the invoice line
    * description *<mark style="color:purple;">string</mark>*
      * A description (e.g. product name) of the invoice line
    * amount *<mark style="color:purple;">integer</mark>*
      * a purchased amount of the description
    * price *<mark style="color:purple;">decimal</mark>*
      * the single unit price of the invoice line including VAT
    * tax *<mark style="color:purple;">decimal</mark>*
      * the tax rate applied to the invoice line
    * totalPrice *<mark style="color:purple;">decimal</mark>*
      * the total amount of the invoice line including VAT
    * sku *<mark style="color:purple;">string</mark>*
      * the associated SKU number of the invoice line
  * taxes *<mark style="color:purple;">array</mark>*
    * rate *<mark style="color:purple;">decimal</mark>*
      * the rate of the VAT tax line
    * value *<mark style="color:purple;">decimal</mark>*
      * the tax amount of the tax line

{% hint style="info" %}
Bsp.: {{ invoice.ref }}
{% 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 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://wiki.packstack.de/packstack-connect/einstellungen/pdf-templates.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.
