> For the complete documentation index, see [llms.txt](https://developer.esw.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.esw.com/returns-api/grp-returns-api/core-concepts/return-methods.md).

# Return Methods

Before creating a return order, you must discover which return methods are available for the shopper's location and the items being returned. GRP supports three method types.

Each return can be shipped back using one of several methods, depending on the carrier routes configured for the origin and destination country pair.

Use `POST /{id}/return-methods/{orderRef}` to discover which methods are available for a specific order. The response includes carrier service route details, whether the route supports paperless returns, and whether the route requires a drop-off location to be selected.

<table data-view="cards"><thead><tr><th>Method</th><th>What it is</th></tr></thead><tbody><tr><td><strong>Postal</strong></td><td>Shopper prints a label and drops the parcel at any post office or letterbox. Best for lightweight items.</td></tr><tr><td><strong>PUDO</strong></td><td>Pick-Up / Drop-Off. Shopper drops the parcel at a third-party location, such as a convenience store or parcel locker.</td></tr><tr><td><strong>Collections</strong></td><td>Carrier collects from the shopper's address. Typically used for bulky items or markets with limited postal infrastructure.</td></tr></tbody></table>

The `SearchReturnMethods` response also indicates whether a method is a *paperless route* (the shopper takes the parcel to the drop-off and the carrier scans it — no label required), and whether a drop-off location must be specified at time of return creation.


---

# 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://developer.esw.com/returns-api/grp-returns-api/core-concepts/return-methods.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.