The order form is the most practical document in your contracting stack and the one that gets the least attention. It’s the document your customer actually reads and signs. It contains the deal terms that matter most to both sides: what they’re buying, what they’re paying, and for how long. Everything else, your Terms of Service, DPA, and SLA, is incorporated by reference.
Despite that, most B2B SaaS order forms are either too thin (missing key commercial terms) or too thick (cluttered with legal provisions that belong in the standard terms). Both create problems. A thin order form leaves gaps that surface mid-relationship with no contractual answer. An overloaded order form undermines the reusability of your standard terms and introduces inconsistencies across your customer base.
This post covers what belongs in the order form, what should stay in your standard agreements, how to handle document hierarchy when there’s a conflict, and the common mistakes that create deal friction or post-signing disputes.
What Belongs in the Order Form
The order form should contain deal-specific commercial variables. These are the terms that change from customer to customer and deal to deal.
Product and scope. Which service or tier the customer is purchasing. If your product has multiple plans, modules, or feature sets, the order form should specify exactly what the customer has access to. Ambiguity here leads to disputes about what’s included in the subscription.
This is one of the most important provisions in the order form and one of the most commonly underspecified. A vague product description (“access to the Platform”) creates confusion when you release a new module or feature and want to charge for it separately. The customer argues it’s included in their existing subscription because their order form says “access to the Platform” without limitation. You argue it’s a new product with separate pricing. Neither side has a clear contractual basis.
The fix is specificity. Name the plan or tier. List the modules or feature sets included. If your product has add-ons or premium features that are priced separately, state that the order form covers only the specified components and that additional modules are available under separate order forms at then-current pricing. If you anticipate releasing new features that may be separately priced, include language reserving the right to offer new products or features outside the scope of the current subscription. This protects your ability to monetize your roadmap without renegotiating every existing customer relationship.
This is particularly relevant for agentic AI capabilities. AI-powered features are increasingly released as premium add-ons with their own pricing models, often usage-based, that don’t fit neatly into a flat subscription. If your order form doesn’t clearly scope whether AI features are included or excluded, a customer whose subscription predates the AI release will argue it’s covered. Define it upfront: which AI capabilities are included in the base subscription (if any), which are available as separately priced add-ons, and how agent-driven usage is metered and billed.
Pricing. The fee structure for this specific customer: monthly or annual amount, per-seat or per-unit pricing, usage rates if applicable, and any negotiated discounts. If the customer’s pricing differs from your standard rate card, the order form is where that’s documented.
Payment terms. Payment frequency (monthly, quarterly, annual), payment method, and any customer-specific payment terms (net 30, net 60). If the customer negotiated extended payment terms beyond your standard, it belongs here.
Subscription term. The initial term length, the start date, and the renewal mechanics. If the deal includes a multi-year commitment with pricing locked for the initial term, that’s an order form provision.
Renewal pricing. How pricing changes on renewal. If you have an annual escalation mechanism (the greater of a fixed percentage or CPI, as covered in the termination post), state the applicable rate in the order form. If renewal pricing defaults to your then-current list price, state that. Silence on renewal pricing is one of the most common order form gaps and creates friction at every renewal cycle.
Usage limits and overages. If the deal includes usage thresholds, seat counts, storage limits, or API call allocations, define them here along with the overage rate if the customer exceeds those limits. For products with agentic AI features, include any spend caps or usage guardrails the customer has agreed to.
Support tier. Which level of support the customer is entitled to (standard, premium, enterprise) and any customer-specific support commitments (dedicated account manager, guaranteed response times beyond the standard SLA).
Customer-specific commitments. Any one-off commitments made during the sales process: a custom integration, a specific onboarding timeline, a pilot period with conversion terms. If you promised it to close the deal, it belongs in the order form.
What Stays Out of the Order Form
The order form should not contain legal terms that belong in your standard agreements. The purpose of separating the order form from the Terms of Service is to keep deal-specific variables in one document and reusable legal framework in another.
Limitation of liability. Your liability cap structure belongs in the Terms of Service. If it’s in the order form, every deal negotiation becomes a liability negotiation, and you end up with different caps across different customers.
Indemnification. Same principle. Indemnification obligations should be consistent across your customer base, governed by the Terms of Service, not renegotiated on every order form.
Data processing terms. These belong in the DPA. The order form can reference the DPA, but data handling commitments, security obligations, and breach notification timelines should not be restated or modified in the order form.
Termination provisions. The mechanics of how the relationship ends (cure periods, data export, survival clauses) belong in the Terms of Service. The order form specifies the term length. The ToS governs what happens when the term ends.
Confidentiality. Governed by the Terms of Service. Restating or modifying confidentiality terms in the order form creates the same cross-document contradiction risk we’ve covered throughout this series.
The principle: if a provision applies the same way to every customer, it belongs in the standard terms. If it varies deal to deal, it belongs in the order form. Your default order form template should contain no legal terms at all. When enterprise negotiations produce agreed deviations from your standard terms, those belong in a dedicated Special Terms section on that specific order form, covered below.
Incorporating Your Standard Terms by Reference
The order form is the document the customer signs. Your Terms of Service, DPA, SLA, and AUP are only binding on the customer if the order form explicitly incorporates them by reference. Without that incorporation, your standard terms exist as standalone documents with no contractual force behind them.
The order form should include a clear statement that by executing the order form, the customer agrees to be bound by the Terms of Service, DPA, SLA, and AUP, with links or URLs to each document. The language should be unambiguous: “This Order Form incorporates and is subject to the Terms of Service at [URL], the Data Processing Addendum at [URL], the Service Level Agreement at [URL], and the Acceptable Use Policy at [URL]. By signing this Order Form, Customer agrees to be bound by each of these documents.”
Include the URLs so there’s no dispute about which version of the document was in effect at the time of signing. If your terms are versioned with effective dates, reference the version date or specify that the then-current version at the time of execution applies.
This is a foundational requirement that gets overlooked. A beautifully drafted Terms of Service that isn’t incorporated into the document the customer actually signs is unenforceable.
Order of Precedence: Which Document Controls
Every order form should include an order of precedence clause that defines which document controls when there’s a conflict between the order form and the standard terms.
The standard approach: the order form prevails over the Terms of Service for deal-specific commercial terms (pricing, term, support tier). The Terms of Service prevail for all legal provisions (liability, indemnification, termination mechanics, governing law). The DPA prevails for data processing matters. The SLA prevails for service level commitments.
Without a clear precedence clause, a conflict between the order form and the ToS is ambiguous. If the order form states a different renewal mechanic than the Terms of Service, which one governs? If a customer-specific commitment in the order form contradicts a limitation in the ToS, which one applies? The precedence clause answers these questions before they become disputes.
A simple precedence clause might read: “In the event of a conflict between this Order Form and the Terms of Service, this Order Form will prevail with respect to the commercial terms specified herein. For all other matters, the Terms of Service will control.” Adapt this to include your DPA and SLA in the hierarchy.
Watch for Legal Terms Smuggled Into the Order Form
Enterprise procurement teams sometimes use the order form to introduce legal terms that should be negotiated in the main agreement. This happens because the order form feels like a less formal document, and one-off additions seem harmless in the context of a specific deal.
Common examples: a customer adds a line item granting themselves termination for convenience rights that don’t exist in the Terms of Service. A procurement team includes a sentence requiring the provider to maintain specific insurance coverage not mentioned in the standard terms. A customer adds a data residency requirement to the order form rather than negotiating it into the DPA.
Each of these is a legal commitment that, combined with a precedence clause that gives the order form priority, could override your standard terms. Review every customer edit to the order form with the same care you’d apply to a redline of your Terms of Service. The order form may look like a commercial document, but any provision in it is contractually binding.
Special Terms: When Deviations Are Intentional
Not every deviation from your standard terms is a problem. Enterprise deals sometimes require negotiated modifications that both parties agree to. A customer may need a specific data residency commitment, a shorter breach notification timeline, an extended termination cure period, or a different liability cap for a high-value deal.
The question is whether to accommodate these through a redline of your standard terms or through special terms on the order form. The answer comes down to the volume and scope of the requested changes.
If a customer is requesting a large number of changes across multiple sections of your terms, those need to be negotiated as a redline of the standard agreement. You can’t fit 15 modifications into a special terms section without creating a confusing document that’s hard to interpret and harder to enforce. When the scope of changes is extensive enough that it effectively rewrites the underlying agreement, the redline is the right vehicle.
If the customer has a handful of targeted changes, a different liability cap, a specific data residency requirement, a custom SLA tier, those fit cleanly in the special terms section of the order form. The deviations can be clearly understood as a short list of exceptions to the standard terms without creating ambiguity about what the overall agreement says.
The right way to handle these is a dedicated “Special Terms” or “Additional Terms” section in the order form. This section captures any agreed deviations from the standard Terms of Service, DPA, or SLA for that specific customer. It should state explicitly that the special terms apply only to this order form and that they prevail over the corresponding provisions in the standard terms to the extent of any conflict.
The advantage of this approach: your standard terms remain unchanged and reusable across your customer base. The customer-specific deviations are documented in one place, clearly identified as exceptions, and tied to the specific deal. When you’re reviewing your contract portfolio in diligence or for renewal purposes, you can see at a glance which customers have non-standard terms and what those deviations are.
The risk to watch for: special terms that accumulate over time and effectively hollow out your standard agreement. If half your customer base has negotiated exceptions to your liability cap, your “standard” cap isn’t really standard. Track your special terms across your customer portfolio. If the same deviation keeps appearing, consider whether your standard terms need to be updated to reflect what you’re actually agreeing to in practice.
One practical note: if a deal is standard and there are no special terms, remove the section from that customer’s order form entirely. Don’t present a blank “Special Terms” section. A blank section signals to the customer that there’s a place to put deviations, which invites requests for modifications that wouldn’t have come up otherwise. Only include the section when there are actual deviations to document.
The Problem of Missing Terms
The most common order form issue isn’t what’s in it. It’s what’s missing.
An order form that specifies pricing and term length but is silent on renewal pricing, overage rates, support tier, or usage limits creates gaps that surface mid-relationship. When the renewal comes up and the customer asks what the new pricing is, your order form doesn’t say. When the customer exceeds their usage allocation, there’s no defined overage rate. When the customer expects premium support but the order form doesn’t specify a tier, you’re negotiating from sales emails and verbal commitments rather than from a signed agreement.
Every material commercial term that was discussed during the sales process should be reflected in the order form. If it was important enough to discuss, it’s important enough to document. Silence on a commercial term doesn’t mean the default in your Terms of Service applies. It means there’s ambiguity, and ambiguity favors whichever party is unhappy at the moment the question arises.
Keeping the Order Form Clean
A clean order form does three things well.
First, it contains only deal-specific commercial variables. A customer should be able to read the order form and understand the commercial deal without wading through legal provisions. The buyer’s champion, the person who actually wants your product, reviews the order form. Make it readable for them.
Second, it incorporates your standard terms by reference with a clear precedence clause. The order form should state that by signing, the customer agrees to the Terms of Service, DPA, SLA, and AUP (with links to each). This creates the contractual hierarchy without restating any of those documents.
Third, it’s complete. Every commercial term that was negotiated or discussed is documented. No gaps, no assumptions, no reliance on email threads to fill in what the order form left out.
The order form is the front door to your contracting stack. Make it clean, complete, and commercial. Let the standard terms handle everything else.
No Boiler provides self-service legal document generation and educational content. This material and our service is not a substitute for legal advice. Please have a qualified attorney review any documents before relying on them. No Boiler is not a law firm, and communications with us do not create an attorney-client relationship or carry any expectation of confidentiality. Use of our platform and content is governed by our Terms of Service and Privacy Policy.
This is the final post in the Terms of Service pillar. Previously: IP Ownership in B2B SaaS. Related: Anatomy of B2B SaaS Terms of Service · Billing Terms That Don’t Create Disputes.