> For the complete documentation index, see [llms.txt](https://docs.roadmap.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roadmap.so/subscriptions/managing-subscriptions/adjusting-an-upcoming-subscription-order.md).

# Adjusting an upcoming subscription order

Change a single upcoming subscription order without affecting the contract or the schedule, from the admin or from the customer's own account.

Most changes to a subscription apply from that point onward: swap a product, change the frequency, move the address, and every future order follows. Occasionally you need to change **one delivery only**.

Both you and the customer can do this. The steps below are the admin route, and customers have their own equivalent from their account dashboard.

### Where upcoming orders live

Open the contract from **Subscriptions**, then find the upcoming orders in the **Orders** list. Each order has a `•••` menu holding the actions that affect that order alone.

The **Upcoming** tab lists every scheduled order, not only the next one, and each has its own `•••` menu. You can change a delivery several cycles out and leave every order before it alone.

{% hint style="info" %}
This is the part customers cannot do. From their dashboard they can only change their **next** order. Anything further ahead has to come from you.
{% endhint %}

{% hint style="warning" %}
The contract's own **Products** card, higher up the page, has an identical looking `•••` menu that changes **every future order**. The modal heading tells you which one you opened: **Edit upcoming order product** is this page, **Edit subscription product** is the contract. See [Changing the products on a subscription contract](/subscriptions/managing-subscriptions/changing-the-products-on-a-subscription-contract.md).
{% endhint %}

### Add a product to one order

From the upcoming order's `•••` menu, choose **Add product to this order**.

{% hint style="info" %}
This applies to one order only. It does not become part of the contract, so the delivery after it goes back to the contract's usual products. If the customer wants the item every time, change the contract instead.
{% endhint %}

#### Which products the picker offers

The picker does not offer your whole catalogue. Three rules decide what appears:

* **Only what the plan's One-off products setting allows.** Each plan controls its own adds.
* **Bundled products never appear**, whichever plan the subscription is on.
* **Sold-out products are marked**, so you can see at a glance what you cannot add.

The same rules apply to the customer's own picker, so you and they see the same list.

{% hint style="info" %}
If a product you expect is missing, open the plan settings that subscription belongs to and check **One-off products** rather than the product itself. A product can be available on subscription and still be left out of the one-off list, because the two are configured separately. If the product is deliberately not published to your online store, **Include unlisted products** is what lets it through. See [How to set up a subscription plan](/subscriptions/getting-started/how-to-set-up-a-subscription-plan.md).
{% endhint %}

### Change or drop a product on one order

Each product line inside an upcoming order has its own `•••` menu with **Edit** and **Remove**.

<figure><img src="https://393112916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ8asLD4FVCFagK40xEr4%2Fuploads%2FVTdFbWv4vlH2L083WguD%2FScreenshot%202026-09-30%20at%202.07.04%E2%80%AFPM.png?alt=media&amp;token=b4852e81-f9c3-4e8d-bda9-1fcff61be087" alt="" width="563"><figcaption></figcaption></figure>

**Edit** opens **Edit upcoming order product**, which states at the top: *This will update the product ONLY for this upcoming order. The subscription itself will remain unchanged.* Change the **Select Product / Variant** or the **Quantity**, then click **Update order**.

**Remove** drops the product from that delivery. It stays on the contract and returns on the next cycle.

Both are scoped to that one order, so the contract keeps billing as it always did. An order showing `2 × Brain Wave` while the contract's Products card reads `2 × Happy Gut` is a swap applied to that delivery alone, and the orders after it go back to Happy Gut.

Use these when a customer wants a one-time change, for example doubling a quantity for one month, sending a substitute while something is out of stock, or skipping one item without skipping the whole delivery.

<figure><img src="https://393112916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ8asLD4FVCFagK40xEr4%2Fuploads%2FksjYsQIdPdMB1oA22AXu%2FScreenshot%202026-09-30%20at%202.34.29%E2%80%AFPM.png?alt=media&amp;token=acbc8e80-203a-4172-a2b6-60ccc3f22784" alt="" width="563"><figcaption></figcaption></figure>

### How customers do it themselves

Customers reach the same thing from their account dashboard, so it is worth knowing the flow before doing it on their behalf.

{% stepper %}
{% step %}

#### Add product to order

Under **Products** on the subscription card, the customer clicks **+ Add product to order**.

<figure><img src="https://393112916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ8asLD4FVCFagK40xEr4%2Fuploads%2FOKnxxPEfMpWp4aAYYtdf%2FScreenshot%202026-09-30%20at%202.11.15%E2%80%AFPM.png?alt=media&amp;token=c280f918-4512-497f-b573-c5edb9367406" alt="" width="563"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Choose how to add it

The **Add product** modal asks how they want it added:

* **Add to subscription**: *ships every future order*. Only the plan's products are offered.
* **Next order only**: *ships once with your next order*.

They pick one and click **Next**.

<figure><img src="https://393112916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ8asLD4FVCFagK40xEr4%2Fuploads%2FPgeurEs6WVtB04lSaUb7%2FScreenshot%202026-09-30%20at%202.12.07%E2%80%AFPM.png?alt=media&amp;token=d960a58b-c090-48de-8397-bf44b299fe37" alt="" width="563"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Pick the product

**Next order only** opens **Add to next order only**, with a search field and the products they can choose from. Sold-out items are listed but greyed out and marked `(sold out)`, so they cannot be picked.

They select a product and click **Add to next order**.
{% endstep %}
{% endstepper %}

The item then sits on the card with a **One-off · Next order only** badge, and the card total updates to include it.

<figure><img src="https://393112916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ8asLD4FVCFagK40xEr4%2Fuploads%2FKIOEryXZwbkqRYC5fudz%2FScreenshot%202026-09-30%20at%202.13.32%E2%80%AFPM.png?alt=media&amp;token=92b04bf6-ddb8-4531-bacb-2106525fe96f" alt="" width="375"><figcaption></figcaption></figure>

Those two options are the whole distinction in miniature: **Add to subscription** changes the contract and is limited to plan products, while **Next order only** touches a single delivery.

### What customers can do themselves

From their account dashboard they can:

* **Add a one-off product to an upcoming cycle**, the same as you can here, drawn from the same **One-off products** list.
* **Add and remove subscription products** on their own subscription.

Alongside those, an Active contract offers **Order now**, **Skip next delivery**, **Reschedule**, **Change delivery frequency**, **Edit shipping address**, **Swap Products**, **Redeem loyalty points**, **Update payment method**, **Pause** and **Cancel**. The menu narrows when a contract is Paused or Failed.

[The customer subscription dashboard: a tour](/subscriptions/storefront-and-accounts/the-customer-subscription-dashboard-a-tour.md) covers each action, which ones appear in which status, and the address and swap restrictions that catch customers out.

Because a customer can make these changes without telling you, the contract's Timeline is the quickest way to see who changed what.

<figure><img src="https://393112916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ8asLD4FVCFagK40xEr4%2Fuploads%2F7SdrcSMaSVeh3eN21SLK%2FScreenshot%202026-09-30%20at%202.15.30%E2%80%AFPM.png?alt=media&amp;token=ff59ae48-8ccc-4c89-8f10-a06a7d08f292" alt="" width="337"><figcaption></figcaption></figure>

### Using Order now with a one-off addition

A one-off addition sits on a specific upcoming order, so **Order now** brings it forward along with everything else on that order. Add a product to the next order, run Order now, and the customer is billed for the subscription items and any one-off additions together, and receives them in the same delivery.

Once that order has been processed the contract refreshes for the next cycle. The one-off additions have been used, so the following delivery goes back to the contract's usual products.

This is worth knowing before running Order now to recover a contract or to send an early refill: check the upcoming order first, because anything staged on it will be charged now rather than later. See [Manually charging a subscription (Order Now)](/subscriptions/managing-subscriptions/manually-charging-a-subscription-order-now.md).

#### Related guides

* [Changing the products on a subscription contract](/subscriptions/managing-subscriptions/changing-the-products-on-a-subscription-contract.md): changing every future order instead of one
* [The customer subscription dashboard: a tour](/subscriptions/storefront-and-accounts/the-customer-subscription-dashboard-a-tour.md): every action customers can take themselves
* [Manually charging a subscription (Order Now)](/subscriptions/managing-subscriptions/manually-charging-a-subscription-order-now.md)
* [How to set up a subscription plan](/subscriptions/getting-started/how-to-set-up-a-subscription-plan.md): the **One-off products** setting that controls this list
* [Changing shipping on a subscription contract](/subscriptions/managing-subscriptions/changing-shipping-on-a-subscription-contract.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.roadmap.so/subscriptions/managing-subscriptions/adjusting-an-upcoming-subscription-order.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.