> For the complete documentation index, see [llms.txt](https://subscriptions-docs.tech-arms.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://subscriptions-docs.tech-arms.io/features/subscriptions/past-orders.md).

# Past orders

Review every billing cycle of a subscription and charge a cycle again after a failed payment.

The **Past orders** tab of a subscription lists its billing cycles, newest first. Use it to check whether each order was paid and to charge a cycle again.

## What the list shows

Each billing cycle has a header with its number and dates, and a status such as **Unbilled**. Under it, each payment attempt shows:

* **Order No**: the Shopify order, if the payment succeeded. The order placed at checkout is **Billing Cycle 0** and is marked **First Order**.
* **Order date**: when the payment was attempted.
* **Payment status**: **Paid**, or the reason the payment failed, such as **INSUFFICIENT\_INVENTORY**.
* **Fulfillment status**: the Shopify fulfillment status of the order.

## Charge a cycle again

Use **Recharge Cycle** to collect a payment that failed, or an order that fell due while the subscription was paused.

{% stepper %}
{% step %}

### Choose the cycle

Open the subscription, click the **Past orders** tab, then click **…** on the billing cycle and choose **Recharge Cycle**.

![The Past orders tab with the Recharge Cycle option highlighted](https://3752025337-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F479XnzvtVA5dDE3Rt2Uh%2Fuploads%2FCiWz6DjjMMdOJIJlB6ed%2Fsubscription-past-orders-recharge.png?alt=media)
{% endstep %}

{% step %}

### Confirm

In **Create billing attempt**, click **Submit**. The charge can take up to 5 minutes. The result appears in the cycle's **Payment status**.
{% endstep %}
{% endstepper %}

**Recharge Cycle** is not available for cancelled subscriptions or for cycles that are already paid.

## If the charge fails

A failed charge, whether automatic or manual, works the same way:

* The subscription status changes to **Failed**.
* By default, the customer gets the **Payment failed (retrying)** email and you get the **Payment failed** email.
* The app retries according to your dunning settings in **Settings > Renewal & Dunning**. After the last retry, the app does not pause or cancel the subscription, and the next cycle is still charged on schedule.
* When a later payment succeeds, the subscription returns to **Active**.

See [Renewal & Dunning Settings](https://subscriptions-docs.tech-arms.io/features/email-notifications/renewal-and-dunning-settings.md) to change the number and timing of retries.

*If you need help, feel free to reach out to us via in-app* [***Live chat***](https://go.crisp.chat/chat/embed/?website_id=c4ae10a3-f762-4968-b35a-c931caf62a96)***,*** [***Book a call***](https://calendly.com/ta-subscription-app-support/30min) *or at* [***support@tech-arms.io***](mailto:support@tech-arms.io)***.***


---

# 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://subscriptions-docs.tech-arms.io/features/subscriptions/past-orders.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.
