# A size split that does not total

Source: https://docs.tightly.io/help/commitments/a-size-split-that-does-not-total
Reviewed: 2026-09-07

## The sentence

Where the shares of a size split do not add up to the whole buy:

> A size curve must add up to the whole buy: 10000 basis points, which is 100%. This one adds up to {total} ({percent}%). It has not been saved and has not been adjusted: rounding a curve to fit would store a split you did not choose. Sizes you leave out keep no reading at all, and a size you want to buy none of is entered as 0.

Where the split names a size the style does not come in:

> This style is not offered in {sizes}, so no part of its buy can go there. The sizes it is offered in are: {sizes}.

Where the style has no sizes at all:

> This style is not offered in sizes, so there is no size run to spread its buy across.

## What it means

A size split spreads one style's worked depth across the sizes it is offered in, in basis points: ten thousand is the whole buy. Tightly checks the split as a distribution before it stores anything. A split that totals more or less than the whole is refused with what it actually totalled, and it is never normalised: rounding thirty, thirty and thirty to fit would store a curve you did not type, and the next planner to read it could not tell. Refusing puts the rounding where the decision belongs, with the person making it.

Two things that look alike mean different things, and both are kept. A size at zero is a cut: buy none of that size. A size left out has no reading. A split that is all zeros totals nothing and is refused; buying none of a style is a depth of zero, a different act on the same row. A share on a size the style is not offered in is a share of the buy assigned to nothing, so it is refused with the sizes named and the sizes the style does come in listed beside them. A style with no size run has nothing to spread across, and Tightly will not invent a run to hold a curve.

The refusal is the server's, printed on [Buy plan](../commitments/the-desk) against the style where you typed, and the depth on record is untouched. It is not a failed read, and it is not a locked style: the same row takes the corrected split once its current record has been reviewed. If another person has changed the saved split since you opened it, saving is refused separately. Reload the current decision, compare it with your intended shares, and review the correction before saving again. A total of 100% does not override that conflict.

## What to do next

Open the product's **Buy** tab. If **Initial store plan** is shown, find **Buy quantity & size split**, then open **Size mix & packs**. Enter a percentage for each offered size, using 0 where you want none, and make the total 100%. **Save size curve** stays unavailable while the total is invalid. Closing the size editor or changing product tabs keeps your draft. Review the corrected split and save it.

Where the refusal lists the sizes the style is offered in, use those labels exactly. Ask Tightly can set the split with the same checks; an omitted size remains unknown, not zero.

## Who to ask

Ask Tightly on the desk answers from this article and from [Set a size split](../commitments/act-set-a-size-split).