> ## Documentation Index
> Fetch the complete documentation index at: https://help.localflow.travel/llms.txt
> Use this file to discover all available pages before exploring further.

# Issue a new version after a change, and why you need to

> In Localflow an issued version never changes. Learn why a change after sending needs V2, how to issue it, what blocks it, and how to see what changed.

Once you issue a version, for example V1, Localflow keeps it exactly as it was. The customer's link shows that version. When the customer asks for a change, you make it and issue a new version: V2, then V3, and so on.

## Why a new version

* The customer must see the same prices and days that you sent. A sent version never changes behind their back.
* You keep a record of every version you sent.
* Each link opens one version. Make a new link, or email the new version, after you issue it.

## What you see after a change

When the costing matches a sent version, Costing stops saving by itself. Instead you see **Save costing** at the top, with **Undo**.

![The trip header after a change to a sent costing, with the Save costing and Undo buttons](https://mintcdn.com/localflow-help/-7jmDiPwUk5YVCM5/images/shots/sent-costing-save.png?fit=max\&auto=format\&n=-7jmDiPwUk5YVCM5\&q=85\&s=3786679c2aff66e939f1d91a691ef6ae)

Press **Save costing** to keep your change. Saving a sent costing makes a new version.

## Issue V2

**1. Open Review & issue**

The status line says **The trip changed since V1. Ready to send V2.**

**2. Click Issue V2**

A box opens. It shows the options, the price, and **Replaces: V1, which stays as it was**.

**3. Choose the price shown**

Under **Price shown to the customer**, pick **Total only**, **Section totals** or **Every line**.

**4. Write the reason**

Type the **Reason for the new version**, for example "One more night in Colombo, as you asked."

**5. Issue**

Click **Issue V2**. Then email it or make a link, as for V1.

![Review & issue showing The trip changed since V1. Ready to send V2, with the Issue V2 button](https://mintcdn.com/localflow-help/-7jmDiPwUk5YVCM5/images/shots/ready-v2.png?fit=max\&auto=format\&n=-7jmDiPwUk5YVCM5\&q=85\&s=7e9cf4f0baf143ea2f792d54db2cfccc)

![The Issue V2 box with Options, Route, Check, Replaces, the price choices and the reason box](https://mintcdn.com/localflow-help/7Qq3JWkrIOx0-Zam/images/shots/issue-v2-dialog.png?fit=max\&auto=format\&n=7Qq3JWkrIOx0-Zam\&q=85\&s=5ed107a6aca19f1ab0811aa05797b839)

> [!WARNING]
>
> Always type a reason. If you leave it empty, Localflow sends a short fixed sentence, for example "The trip changed. The new prices are below." It does not say what changed.

## See what changed

In the **Sent** list, open the **⋯** next to V2 and choose **What changed in V2**. Each change shows the new value and what it **Was**.

![What changed in V2: Standard price USD 1,179, up USD 73, was USD 1,106](https://mintcdn.com/localflow-help/-7jmDiPwUk5YVCM5/images/shots/what-changed-v2.png?fit=max\&auto=format\&n=-7jmDiPwUk5YVCM5\&q=85\&s=31de4fbb4c67c8a702204ac461c7bd08)

## What stops you issuing

Only one thing blocks a new version: a hotel whose price-list dates changed under its rate. It shows as, for example, "Galle · new dates". Choose **Use the new price** or **Keep the old price**.

Everything under **Notes** (for example "km to check") does not stop you issuing.

> [!NOTE]
>
> An older version issued before 12 November has no price per person by room sharing. Issue a new version to show it. See [Prices per person](https://help.localflow.travel/tasks/prices-per-person.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.