Order form

An order form is the short document that records the commercial specifics of a software deal: the plan, the number of seats, the price, the term length and when it renews. It sits on top of a much longer master agreement (the terms and conditions the order form references by URL), which sets out the legal framework the same for every customer.

The split matters because the two documents can disagree, and the order form is usually written to win where they do. The renewal clause, the notice period and any price-increase cap are the terms most often changed on the order form, so reading only the master agreement can tell you the wrong deadline.

Most master agreements contain an order of precedence clause, and it almost always puts the order form first on anything it covers: price, term, seat count, renewal and notice. So where the master agreement says one thing about renewal and the order form says another, the order form governs. Check it before you rely on a deadline worked out from the standard terms alone.

The practical trap is that the order form is short and easy to skim, while the renewal mechanics are the one part worth reading twice. A clause buried in it can shorten the notice window, cap or uncap a price rise, or move the renewal date off the anniversary you assumed.

The order form is where the fields that drive a renewal decision actually live. Copy the term start and end dates, the notice period, whether it auto-renews, the seat count and any agreed price or uplift cap into one place, so the deadline is computed from the document rather than from memory. Keep the order form itself with the record: it is the evidence if a renewal charge is ever disputed.

In StackTrackr a tool records the renewal date, the notice period and whether it auto-renews, and those produce the cancellation deadline, so the order form's renewal terms become a dated reminder rather than a clause nobody re-reads until the invoice arrives.