GateTrue

What each generator documents about marking its output

List price: the figure a crossing point is quoted at

A list price is what a plan ordinarily costs. It is the figure this register quotes beside a crossing point, because a promotional rate describes one billing period rather than the boundary. As of 2026-09-22.

Which figure gets recorded, and whyA promotional rate describes one billing period, so a reader who lets it lapse is back to marked output. An annual figure and a monthly figure are both ordinary prices for the same boundary. A price that is not present as text cannot be recorded at all.What kind of figure is printed beside this planAn ordinary priceRecordedMonthly or annual,whichever the page printsas the plan's headlinefigure.A first-period offerNoted, not recordedIt describes a billingperiod rather than theboundary the column isabout.Not present as textCannot be recordedOne entry here. Theboundary is named and nofigure can be cited fromthe page.Why the cell sometimes has a tier and no number
Fig. 1 Recording an offer would make the register's values expire faster than the behaviour they describe.
How this register uses the term, and what it excludes. Written 2026-09-22.
The termList price
What it namesThe ordinary published price of a plan
What it is notA first-period offer, or a negotiated rate
Where the register uses itBeside the tier in every priced paid-tier value

Inclusion rule. Words this site uses in a narrow sense, where the ordinary sense would lead a reader to misread a cell. No vendor statement appears on this page. Order. Fixed order: what the word names, what it excludes, then where it is used here.

1Why the offer is not the boundary

Some pages print a first-month price beside the list price. A reader who pays it once and lapses is back to marked output, so the promotional figure describes a billing period rather than the state a subscription puts files in. The boundary is where the mark stops for as long as somebody keeps paying.

Recording the offer would also make the register's own values expire faster than the vendor's behaviour does. Promotions rotate; list prices move rarely. A cell built on the first is out of date within weeks and looks like a product change.

2Two list prices for one plan

Several pages print both a monthly figure and a lower one for an annual commitment, and both are list prices. The register keeps whichever the page prints as the plan's headline figure in the cell and the alternative in the prose of the reading.

Averaging them would produce a number no vendor publishes, and normalising everything onto one basis would put this register's arithmetic into cells meant to hold vendor statements. The cost is that comparing two crossing points requires saying which basis each uses.

3When a price cannot be recorded at all

A figure rendered as an image, or assembled after a page loads, is not readable from the document. One entry here is in that position: the boundary is named and the prices are not present as text, so the crossing point can be cited and not quoted.

Taking the number off a screenshot would put something in a cell that no later reader could verify the same way, which is the kind of unverifiable precision this site exists to avoid. The cell records that the price is not published as text.

Nothing on this page is a vendor statement; the values it helps read are on the support table, with the page and the date each one was read from. See also the paid tier column, reading a plan table. Nearby terms: annual basis, promotional rate, plan inheritance.