> For the complete documentation index, see [llms.txt](https://docs.parcellab.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parcellab.com/docs/developers/returns/connect-order-data.md).

# Connect Order Data

Send your customers' order data via file or API when creating a tracking or let us retrieve the order data using a real-time API connection.

To initiate the returns process, parcelLab will need to receive all the necessary order-related information. With the order data, we can display the purchased articles for each order, so your customers can select the items they want to return.

There are two ways you can provide the order data required for the Returns Portal to work.

{% stepper %}
{% step %}

### Using outbound order data

Using this method, we reference order data that is sent to parcelLab via a file or API connection for outbound trackings. We store the data for up to 90 days and reference this database whenever your customers use your Returns Portal.

For more information on using this method of data transmission, please refer to the following documentation pages:

{% content-ref url="/pages/U7MQ07RqCyYjsccBgGn0" %}
[Create Orders/Trackings](/docs/developers/orders/create-orders-trackings.md)
{% endcontent-ref %}
{% endstep %}

{% step %}

### Using real-time API connection

Using this method, we call an API endpoint the moment a customer logs into your Returns Portal. This real-time API connection ensures that the order data is up to date and stored only when necessary.

This integration enables the handling of use cases that require the returns window to be longer than 90 days.

For information on using this method of data transmission, please refer to the order data required section below.

For details on the Real-time API see:

{% content-ref url="/pages/xRoeFG5VSPCQLCjgB0IB" %}
[Real-time API Connection for Returns](/docs/developers/returns/connect-order-data/real-time-api-connection-for-returns.md)
{% endcontent-ref %}
{% endstep %}
{% endstepper %}


---

# 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.parcellab.com/docs/developers/returns/connect-order-data.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.