> 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/gls-connector/gls-connector_en_us/daily-work/returns-and-pickup.md).

# Returns and Pickup

Use ShopReturn, Pick\&Ship and Pick\&Return with package details, create return packages from purchase return orders, and select parcelshops.

This page shows how to control GLS return and pickup services through the package. Which services you can use depends on your GLS account.

## Prerequisites

* In **GLS Configuration** → **Enabled Features**, **Enable Returns** and/or **Enable Pickup** are turned on. Turning them on does not book anything by itself.
* The required service is available in your GLS account.

## Fields on the package

| Field                       | Purpose                                     |
| --------------------------- | ------------------------------------------- |
| **Pickup Date**             | Required for Pick\&Ship and Pick\&Return    |
| **Number of Return Labels** | Transmitted for ShopReturn                  |
| **Parcelshop ID**           | Delivery to a GLS parcelshop                |
| **Place of Deposit**        | Preferred place of deposit at the recipient |

## Services at a glance

| Service      | What is transmitted     | Check before upload              |
| ------------ | ----------------------- | -------------------------------- |
| ShopReturn   | Number of return labels | –                                |
| Pick\&Ship   | Pickup date             | A missing pickup date is flagged |
| Pick\&Return | Pickup date             | A missing pickup date is flagged |

## Return package from a purchase return order

To send goods back to a vendor:

1. Open the purchase return order.
2. Choose **Create GLS Return Package**. By default, the package gets the Pick\&Return service.
3. Open the package and set the **Pickup Date**.
4. Upload the pending packages of this document with the upload action on the purchase return order.
5. Check the track ID on the package card.

The recipient address comes from the vendor or the document. Check it before uploading. This does not create a credit memo or a complete customer return process.

## ShopReturn for customer returns

1. Create the packages on the sales order.
2. On the package card, select the ShopReturn service.
3. Enter the **Number of Return Labels**.
4. Upload the packages as usual.
5. Check the GLS response and the provided return labels before passing them on.

## Delivery to a parcelshop

1. On the sales order, choose **Find GLS Parcelshop**, or use the parcelshop finder in the Role Center.
2. Open the package that has not yet been uploaded. Select **Service = ShopDelivery** and enter the **Parcelshop ID**. The search from the order does not copy the shop to the package automatically.
3. Check the service and ID, and upload the package. ShopDelivery without a parcelshop ID is flagged before the upload.

A parcelshop ID alone does not book ShopDelivery. Likewise, **Enable ShopDelivery** in the configuration does not replace selecting the service on the package.

## What is not included

* A separate pickup order without a shipment cannot be triggered from the app.
* Standalone returns management through additional GLS interfaces is not included.

## Troubleshooting

| Message or situation                | Solution                                                                      |
| ----------------------------------- | ----------------------------------------------------------------------------- |
| Upload flags a missing pickup date  | Set the **Pickup Date** on the package                                        |
| GLS rejects the service             | Clarify whether the service is available in your GLS account                  |
| Wrong address on the return package | Correct the vendor or document address and check the package before uploading |


---

# 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/gls-connector/gls-connector_en_us/daily-work/returns-and-pickup.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.