> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/user-guide/data/customers-and-orders-sample-data.md).

# Customers and Orders sample data

Use this small fictional dataset to check relationships, joins, and query inputs. It contains two customers and three orders.

## Customers

```csv
id,name
1,Ada
2,Grace
```

## Orders

```csv
id,customer_id,total
101,1,25
102,1,40
103,2,15
```

These identifiers describe the example. If Jet Tables generates its own primary keys during import, keep source identifiers in separate fields and use the corresponding field names when configuring the relationship. Do not assume imported source IDs become the Jet Tables primary keys.

## Expected results

| Check                      | Expected result                              |
| -------------------------- | -------------------------------------------- |
| Orders for customer 1      | Orders 101 and 102                           |
| Orders for customer 2      | Order 103                                    |
| Total for customer 1       | 65                                           |
| Orders joined to customers | Three rows; Ada appears twice and Grace once |
| Query for customer 3       | No rows                                      |

For matching tests, add an order with a missing customer identifier and inspect the result. Decide whether a join should keep unmatched orders or exclude them.

Use the dataset with [Relationships](/user-guide/data/relationships.md), [Use dynamic SQL inputs](/user-guide/sql-queries-and-api-requests/use-dynamic-sql-inputs.md), and [Join data from multiple sources](/user-guide/synced-tables/join-data-from-multiple-sources.md).


---

# 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.jetadmin.io/user-guide/data/customers-and-orders-sample-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.