> For the complete documentation index, see [llms.txt](https://help.orderdesk.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.orderdesk.com/integration-setup-guides/sales-channels/sagemember-integration.md).

# SAGEMember Integration

Order Desk can import your orders from [SAGEMember](https://www.sagemember.com/) and send shipment information back as orders are fulfilled.

### Setup

To begin, click on **Manage Integrations** from the left sidebar in Order Desk. Under the **Shopping Carts** tab, find and enable SAGEMember.

![](https://251457507-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAQOLMUJWMYtrpQ7Oxxca%2Fuploads%2FJQyYm7OiOiyskq0SCjmu%2Flegacy-c5ebb9c3f82949e27a14.png?alt=media)

Enter your SAGEMember credentials to connect the integration.

![](https://251457507-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAQOLMUJWMYtrpQ7Oxxca%2Fuploads%2FrGl7Kwx4xXTSTRdC2xYl%2Flegacy-a4b5001058f0aef19625.png?alt=media)

These credentials can be found in your account at SAGEMember.

* Account ID is in the upper right corner next to your email address.
* Suppler Sage ID can be found at Account > Sage Supplier Logos. Find your ID in the Supplier Member section.
* Authentication Key can be found under Developer APIs. Click Settings to enable the SDK and create a key.

### Integration Settings

![](https://251457507-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAQOLMUJWMYtrpQ7Oxxca%2Fuploads%2FNlRRgXPEte076npSWNrR%2Flegacy-91b51ef8f19f4912e22a.png?alt=media)

Once connected, set your preferences in the SAGEMember settings.

#### Check For New Orders

Select how often you want Order Desk to look for and download new orders from SAGEMember.

By default, Order Desk will check for orders from the previous two days. If you would like to download from further back, you can do so with the [Manual Import](#manual-import) feature.

#### Folder for New Orders

Choose the folder where new orders should be placed as they come in from SAGEMember.

You can use the default New folder, or create your own custom folder from your [Store Settings](/start-here/getting-started-series/quick-start-overview.md#working-with-folders).

#### Sync Tracking Numbers

If enabled, shipment details will be passed back to the original order in SAGEMember as they are added to Order Desk.

#### Order Prefix

If you would like to set a prefix on all orders brought into Order Desk from SAGEMember, set that here.

#### Manual Import

![](https://251457507-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAQOLMUJWMYtrpQ7Oxxca%2Fuploads%2F0z9yYHFFCO5SbExozMZ8%2Flegacy-6015e9d61a17ee397910.png?alt=media)

If you would rather manually import orders, you can do so by setting the date from which orders should be imported and clicking the Import Orders button.

### Order Import Log

If an order from your cart hasn't come into Order Desk, the **Order Import Log** is a good place to start. It shows recent import attempts, including which orders were imported or skipped and any skip reasons.

Learn how to use the log in the [How to Troubleshoot Missing Shopping Cart Orders](/guided-walkthroughs/integration-specific-walkthroughs/how-to-troubleshoot-missing-shopping-cart-orders.md) guide.


---

# 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://help.orderdesk.com/integration-setup-guides/sales-channels/sagemember-integration.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.