Help

Help›Commitments›Re-assign a commitment

Re-assign a commitment

Reviewed Oct 29, 2026

View as Markdown
Words
TierPro

The question this page answers ​

What should this Commitment cover, and what would bringing something in or taking it out arm?

What you see ​

The page is titled Change what it covers. It changes which products an armed Commitment applies to, and nothing else. It is reached from the room's On this commitment menu. When it is opened to add products to a range, the page is titled Add products and keeps what is already covered.

Four cards make up the page.

  • The picker. Bring in or Take out, then a grain: Category, Collection, Lifecycle, Product or Variant. Search with Find a and the grain's name. A category row also shows Held by another commitment, and an On the set column says Named once a row is on the set. Set dates reveals Joins from and Leaves after (or Excepted from and Lapses after for Take out).
  • What it would be applied to. Each entry is listed with Entry, Grain, Named and Nearness, a Remove button, a count, and, when 40 or fewer of the 200 allowed are left, "N of 200 entries left". Reset scope discards the draft.
  • Say why. Why is this changing? is required; Note · optional is free text.
  • What that arms. Tightly compiles the old and the new membership against your book and shows each engine's In force now against Would be in force, with a Compiled or Refused badge and "v1 → v2". It writes nothing.

Two statements stand before the button. The first is what the change moves. The second is:

The five numbers do not move.

An empty set returns the Commitment to covering its own scope in full, and the page says so: "Nothing is named: recording this returns the Commitment to covering its own scope in full."

What to do ​

  1. Open the Commitment's room, choose On this commitment, then Change what it covers.
  2. Choose Bring in or Take out, choose the grain, tick the rows and press the button over the table (for example Bring in the 3 chosen).
  3. Optionally choose Set dates and give the entry dates.
  4. Wait for What that arms to read Compiled. If the page asks you to review selling dates, do that first: "Review selling dates before confirming."
  5. Pick a reason under Why is this changing?. The reasons include "Demand ran ahead", "New products or assortment change" and "My judgement".
  6. Press Change what it covers in the head.

The receipt reads "v2 recorded beside v1" with an Entries table and the facts Covers now, Declared by, Reason, Note, Recorded by and Recorded. The way back is another re-assignment, or an empty set. Numbers themselves are moved by Amend a commitment; Buy plan shows the result.

Who can: the page says "Re-assigning a Commitment needs org-admin access." An admin can, as can a user whose access level can write and who has been given approval rights on Commitments. Only a live Commitment can be re-assigned.

When it is empty or failed ​

No commitment at this address.

The declaration did not come back.

A Commitment that has not been signed off reads "Sign this declaration before reassigning it." with a Read it for sign-off door. A closed one reads that it is closed and cannot be re-assigned.

Catalogue failed to load. Coverage is unchanged.

Your catalogue holds nothing at this grain to name here.

The button stays unavailable, and the page gives the reason, when nothing has changed from what it covers today, a target is named twice, the set takes products out and brings none in, more than 200 entries are named, or the engine has not accepted the membership:

The engine refuses this membership. Change what it names, then compile again.

This declaration does not carry all five numbers, so its membership cannot be compiled or re-assigned here.

A refused write shows The re-assignment was not recorded with Re-read this commitment; nothing was written. If the dates change before saving, the page reads them again and asks for review.