> For the complete documentation index, see [llms.txt](https://docs.digitalriver.com/digital-river-api/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitalriver.com/digital-river-api/general-resources/standards-and-certifications/test-and-use-cases.md).

# Test and use cases

Here you'll find a continually expanding list of use cases that you can use when developing and testing your commerce connector. You can also reference our [sequence diagram](/digital-river-api/general-resources/standards-and-certifications/integration-checklists.md#sequence-diagram) to understand better how these use cases fit into the lifecycle of a Digital River order.

## Create a physical SKU

The commerce connector uses the [SKUs API](https://docs.digitalriver.com/digital-river-api-reference/2021-12-13/skus) to create a [physical SKU](/digital-river-api/product-management/creating-and-updating-skus.md#how-products-are-specified-as-physical-or-digital). This allows Digital River to [compute taxes](/digital-river-api/integration-options/checkouts/creating-checkouts/tax-calculations.md) and return that information to customers during checkout.

## Create a digital SKU

The commerce connector uses the [SKUs API](https://docs.digitalriver.com/digital-river-api-reference/2021-12-13/skus) to create a [digital SKU](/digital-river-api/product-management/creating-and-updating-skus.md#how-products-are-specified-as-physical-or-digital). This allows Digital River to [compute taxes](/digital-river-api/integration-options/checkouts/creating-checkouts/tax-calculations.md) and return that information to customers during checkout.

## Create a checkout as a guest customer

The commerce connector uses the [Checkouts API](https://docs.digitalriver.com/digital-river-api-reference/2021-12-13/checkouts) to create a [guest checkout](/digital-river-api/integration-options/checkouts/creating-checkouts/using-the-checkout-identifier.md#guest-checkouts-or-invoices). This means the customer isn't required to create an account during checkout.

## Create a checkout as a registered customer

The commerce connector uses the [Checkouts API](https://docs.digitalriver.com/digital-river-api-reference/2021-12-13/checkouts) to create a [registered checkout](/digital-river-api/integration-options/checkouts/creating-checkouts/using-the-checkout-identifier.md#registered-checkouts-or-invoices). This means customers aren't required to reenter their shipping, billing, and payment details during checkout.


---

# 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://docs.digitalriver.com/digital-river-api/general-resources/standards-and-certifications/test-and-use-cases.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.