> 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/upcoming-orders.md).

# Upcoming orders

Place the next order now, skip an order, or move an order to another date.

The **Upcoming orders** tab of a subscription lists the next scheduled orders, one row per billing cycle, with the order date and a status:

* **Queued**: the order will be charged on its date.
* **Skipped**: the order will not be charged.

The schedule is shown only for **Active** and **Failed** subscriptions. Other statuses show no schedule.

To act on an order, click **…** at the end of its row.

![The Upcoming orders tab with the actions menu open](https://3752025337-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F479XnzvtVA5dDE3Rt2Uh%2Fuploads%2FFz3w5kDgvdpy7UohfWtI%2Fsubscription-upcoming-orders-actions.png?alt=media)

## Place the next order now

Choose **Place Order** to charge the next order right away instead of waiting for its date, for example when a customer asks for an early delivery.

* Only the next order can be placed early. The option is greyed out on later orders.
* It is not available for paused or cancelled subscriptions.
* The charge can take up to 5 minutes. If it fails, the subscription becomes **Failed**, as with any failed payment.

## Skip an order

Choose **Skip cycle**, then confirm, to skip one order, for example while the customer is away. The row changes to **Skipped** and the next order goes ahead as planned. To undo it, choose **Resume cycle** on the same row.

* Only future orders can be skipped.
* By default, the customer gets the **Installment Skipped** email.

Skipping one order is different from pausing the subscription. Pausing stops every order until you activate the subscription again. See [Contract details](https://subscriptions-docs.tech-arms.io/features/subscriptions/contract-details.md).

## Reschedule an order

Choose **Reschedule** to move one order to another date and time, for example when you cannot ship on that day.

1. Pick the new **Date** and **Time**. You can move the order only within its billing cycle; dates outside it are greyed out.
2. To change the billing date of every later order as well, tick **Reschedule all upcoming orders?**. Otherwise, only this order moves.
3. Click **Reschedule**.

![The Reschedule Order window](https://3752025337-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F479XnzvtVA5dDE3Rt2Uh%2Fuploads%2FGaLuqzpfE9UidjSLJ4i1%2Fsubscription-reschedule-order.png?alt=media)

{% hint style="info" %}
Orders are charged at the scheduled time in the app's billing time zone, within the days and hours allowed in **Settings > Renewal & Dunning**. An order moved outside that window is charged when the window opens.
{% endhint %}

## Prepaid subscriptions

On a prepaid subscription, one payment covers several deliveries, so you cannot skip or reschedule its orders here. Hover over the info icon next to the option to see why.

*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/upcoming-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.
