> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/chord-oms/chord-oms-overview/subscriptions/prepaid-subscriptions/prepaid-shipping-method-carryover.md).

# Prepaid Shipping Method Carryover

## Overview

By default, when a prepaid subscription generates its recurring installment orders, Chord OMS recalculates shipping rates from scratch and lets the standard rate-selection logic pick a shipping method. This can mean a customer who originally paid for expedited shipping on their prepaid bundle ends up receiving later installments via the cheapest available method instead.

When this feature is enabled, Chord OMS will **carry over the shipping method the customer selected on the original prepaid checkout** and apply it to every recurring installment order generated by that subscription.

## What it does

When a customer selects a shipping method on their initial prepaid purchase, that method is saved to the subscription and reused on every installment order — so each delivery goes out via the same carrier and service level they originally chose. Installments remain free; only the method carries over, not a new charge.

## What it does *not* do

* It does **not** change pricing — the customer is not re-charged for shipping on installments.
* It does **not** affect non-prepaid (standard recurring) subscriptions.
* It does **not** affect one-time orders.

## When to enable it

Enable this feature if any of the following apply to your store:

* You sell prepaid subscription bundles where customers can choose between shipping speeds (e.g. Standard vs. Expedited) at checkout.
* You want installment deliveries to match the cadence and speed the customer paid for up front.
* You've received customer-support tickets about installments arriving via a slower method than the original order.

Leave it disabled if:

* All of your prepaid subscriptions ship via a single shipping method anyway.
* You explicitly want installment orders to use whatever the cheapest available method is at the time of generation.

## How to enable it

Set the store-level config flag `USE_ORIGINAL_SHIPPING_METHOD_ON_PREPAID` to `enabled` (default: `disabled`). Once enabled, the change takes effect for ***new*** prepaid subscriptions created after the flag is turned on — existing subscriptions are unaffected.

## Example

Prepaid checkout showing the total shipping cost across the total installments.

![](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-ad17fe6ec0efe074bc388960573fa937ca5d7f31%2Fprepaid-shipping-method-carryover-1.png?alt=media)


---

# 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.chord.co/chord-oms/chord-oms-overview/subscriptions/prepaid-subscriptions/prepaid-shipping-method-carryover.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.