Most commercial deals today are not one contract. They are a stack: a master services agreement, an order form, a data processing addendum, a service level agreement, and sometimes a statement of work, a security exhibit, and a support policy hosted on the vendor's website.
Each document has a job. Problems start when nobody knows which job belongs to which document, or when two documents try to do the same job differently. A pricing promise buried in the SLA. A liability cap in the order form that quietly overrides the MSA. A DPA that references a security standard the MSA never mentions.
This article walks through what each document in the stack is supposed to do, how they fit together, and what to check before anyone signs.
The Four Core Documents
The master services agreement (MSA). The MSA is the relationship contract. It sets the legal terms that apply to every purchase under it: warranties, indemnification, limitation of liability, confidentiality, intellectual property, term and termination, governing law, and dispute resolution. A well-built MSA is negotiated once and amended only when the relationship or the law changes. It should say almost nothing about price, quantity, or a specific product configuration, because those change from deal to deal.
The order form. The order form is the commercial deal. It identifies what is being purchased, how many seats or units, the fees, the subscription term, the billing schedule, and renewal mechanics. It is usually the document sales actually reads. Some vendors call it an order, a quote, a schedule, or a statement of work. The name matters less than the function: it is the document that changes every time the customer buys something new.
The data processing addendum (DPA). The DPA governs how the vendor handles personal data on the customer's behalf. It typically covers the scope and purpose of processing, confidentiality of personnel, security measures, subprocessors, breach notification, assistance with individual rights requests, audits, international transfers, and deletion or return of data at the end of the relationship. Privacy laws such as the GDPR, the CCPA, and other U.S. state comprehensive privacy laws require specific contract terms between businesses and their processors or service providers. The DPA is usually where those terms live. Where health information is involved, a HIPAA business associate agreement may also be part of the stack.
The service level agreement (SLA). The SLA defines the performance the vendor commits to: availability, support response times, and sometimes resolution targets. It also defines what happens when the vendor misses, usually service credits. We cover SLAs in more detail in a separate article.
How the Documents Talk to Each Other
The documents only work as a system if they reference each other correctly. Three provisions do most of that work.
Incorporation by reference. The MSA should state that each order form, the DPA, and the SLA are part of the agreement. Each order form should state that it is governed by the MSA. If a document is not clearly incorporated, a court may decline to treat its terms as part of the agreement. Incorporation standards vary by state, and terms hosted at a URL raise a further question: which version applies.
Order of precedence. This is the tiebreaker clause. It tells a reader which document controls when two documents conflict. A common structure is: the DPA controls on data protection matters, then the order form controls on commercial terms, then the MSA controls everything else, then the SLA and other exhibits. Customers often want the negotiated MSA to control over everything. Vendors often want the most recent order form to control. A middle ground that works well in practice: the order form controls only where it expressly identifies the MSA section it is modifying.
One caveat: precedence clauses do not always have the last word. If a DPA incorporates the EU Standard Contractual Clauses, the SCCs themselves provide that they prevail over any conflicting term in related agreements between the parties.
Definitions. Use one set of defined terms across the stack. If the MSA defines "Customer Data" and the DPA defines "Personal Data," check that the two definitions fit together and that the security and confidentiality obligations cover both. Mismatched definitions are one of the most common sources of gaps in these stacks.
Where Conflicts Usually Hide
A few places produce most of the friction we see in practice:
- Liability caps in two places. The MSA sets a general cap. The DPA sets a separate, higher cap for data breaches, or says it is "subject to" the MSA cap. Both versions exist in the market. What should not exist is a stack where nobody can tell which applies, or whether data protection indemnities sit inside or outside the cap.
- Online terms that change. Many vendors incorporate a support policy, acceptable use policy, or security page by URL. If the vendor can update that page unilaterally, the customer is agreeing to a moving target. Customers can ask that updates not materially reduce protections during the current term.
- Termination that does not line up. The MSA permits termination for material breach. The SLA permits termination for chronic failure. The order form says the subscription is non-cancellable. Make sure the exit rights in each document actually function together, and that a termination of the MSA addresses what happens to open order forms.
- Purchase orders and click-through terms. A customer's purchase order often comes with its own boilerplate on the back. A vendor's product may present click-through terms the first time a user logs in. Neither should quietly join the stack. The MSA should say that preprinted PO terms and click-through terms do not apply.
- Special terms in the order form. Sales teams sometimes solve a customer request by typing it into the order form's "special terms" box. Those terms may then override carefully negotiated MSA language through the order of precedence clause. A short internal rule helps: anything that changes a legal term goes through legal, even if it lives on the order form.
Why the Structure Is Worth the Trouble
A layered stack is not paperwork for its own sake. Done right, it lets a company negotiate the hard legal terms once, then close follow-on purchases with a one-page order form. That is faster for sales, easier for finance, and cleaner for anyone reviewing the contracts later, whether that is an auditor, an acquirer conducting diligence, or a new general counsel trying to figure out what the company has promised.
The structure also helps with privacy compliance. When the DPA stands on its own, it can be amended as laws change without renegotiating the commercial terms. Any amendment still needs both parties' signatures, unless the contract gives one party the right to make changes alone.
Questions to Ask Before Signing
- Every document in the stack is listed and incorporated by reference.
- The order of precedence clause is present and matches how the parties actually expect the documents to work.
- Defined terms are consistent across documents.
- There is one clear answer to "what is the liability cap for a data breach?"
- Any URL-based terms are identified, and the right to change them is addressed.
- Preprinted purchase order terms and click-through terms are expressly excluded.
- If the SLA makes service credits the "sole and exclusive remedy," everyone understands what that cuts off.
- Amendments to any document follow the MSA's amendment formalities.
- Termination rights in the MSA, SLA, and order form work together.
- Special terms on the order form have been reviewed by someone who knows what they override.
If the stack passes that list, it is probably doing its job. If it does not, better to find out now than in the middle of a dispute, when everyone suddenly reads the order of precedence clause for the first time.
This article is general information as of November 2026. It is not legal advice and does not create an attorney-client relationship.