The order document. Where the real terms hide.

The master agreement gets the legal review, but the ordering document carries the terms that actually govern your purchase, and frequently overrides the master. The buyer that reads the order with the same care as the contract negotiates from the document that matters.

The Oracle ordering document, the order form or the order schedule that accompanies the master agreement, is where the specific terms of each Oracle purchase live, and it is frequently the document the customer reads least carefully. The master agreement, the OLSA or the OMA, establishes the general terms, but the order document specifies the products, the quantities, the metrics, the prices, and frequently a set of order specific terms that can override the master. The customer that focuses its review on the master agreement and signs the order without the same scrutiny misses the document that actually governs the purchase.

This article walks through the Oracle order document negotiation. The relationship between the order and the master agreement. The product and metric definitions in the order. The order specific terms that override the master. The pricing and the price hold provisions. The negotiation strategy. The framework helps an organisation read and negotiate the order with the care it deserves.

The order and the master agreement.

The relationship between the order document and the master agreement determines which terms govern, and it is frequently misunderstood. The master agreement establishes the general framework, but the order document can incorporate, modify, or override the master terms for the specific purchase, and the order frequently contains provisions that change the customer's position relative to the master. The customer that assumes the master governs and the order merely lists the products misunderstands the structure, and it can sign an order that materially changes its rights.

The order document should be read against the master agreement to identify the terms the order adds or changes. The order frequently incorporates additional terms by reference, including product specific terms, cloud service terms, or program documentation, and these incorporated terms can materially affect the customer's rights. The customer should identify every term the order adds, modifies, or incorporates, and it should understand how those terms interact with the master agreement. The order and the master must be read together.

The structural response is to read the order document against the master agreement, identifying the terms the order adds, modifies, or incorporates. The buyer that reads the documents together understands which terms govern. See the contract terms pillar and the audit clause negotiation article.

The product and metric definitions.

The product and metric definitions in the order document determine exactly what the customer is licensing and on what basis, and the precision of these definitions determines the customer's compliance exposure. The order specifies the products, the license metrics, frequently processor or named user plus, and the quantities, and the definitions of these metrics determine how the customer's usage is measured against the license. The customer that signs an order with imprecise or unfavourable metric definitions accepts a compliance position that can produce gaps it did not anticipate.

The metric definitions should be examined for the measurement basis, the counting rules, and the treatment of the customer's actual deployment. The processor metric, for example, incorporates the core factor table and the counting rules that determine how many processor licenses a given deployment requires, and the named user plus metric incorporates the minimums and the counting rules for users and devices. The customer should ensure the metric definitions in the order match its actual deployment and produce a compliant position. The metric definitions are the foundation of the customer's compliance.

The structural response is to examine the product and metric definitions in the order, ensuring they match the actual deployment and produce a compliant position. The buyer that gets the metric definitions right limits its compliance exposure. See our contract review service and the Oracle Database product page.

The order specific terms that override the master.

The order specific terms are the provisions in the order document that apply only to that purchase, and they frequently override the master agreement in ways that affect the customer's position. The order can contain provisions on the deployment rights, the territory, the support terms, the assignment rights, and a range of other matters, and these order specific terms can be more or less favourable than the master. The customer that signs the order without examining the order specific terms can accept provisions that materially change its rights for the products in that order.

The order specific terms deserve particular scrutiny because they are frequently where Oracle inserts the provisions it wants for a specific deal, including restrictions on the deployment, limitations on the customer's rights, or terms that favour Oracle in a future audit or renewal. The customer should examine every order specific term, understand how it changes the customer's position relative to the master, and negotiate the terms that matter. The order specific terms are frequently the most negotiable and the least negotiated provisions in the transaction.

The structural response is to examine the order specific terms, understand how they override the master, and negotiate the terms that matter. The buyer that scrutinises the order specific terms negotiates from the document that governs. See the SLA service level clauses article and the perpetual licenses deal type page.

The pricing and the price hold provisions.

The pricing and price hold provisions in the order document determine not only the current price but the customer's protection against future increases, and they are frequently the most valuable terms to negotiate. The order specifies the price for the products purchased, but the price hold provisions, the caps on future increases, the protections for future purchases, and the renewal pricing, determine the customer's cost over the life of the relationship. The customer that negotiates the price but ignores the price hold provisions captures a one time saving but forfeits the protection against the future increase.

The price hold provisions should address the renewal pricing for support, frequently subject to an annual uplift that compounds over time, the pricing for future purchases of the same products, and the protection against the price increase. The customer that negotiates a cap on the support uplift, a price hold for future purchases, and protection against the renewal increase captures value that compounds over the life of the relationship. The price hold provisions are frequently more valuable than the initial discount.

The structural response is to negotiate the pricing and the price hold provisions in the order, capturing the protection against future increases. The buyer that negotiates the price holds captures value that compounds. See the Oracle Negotiation Playbook white paper and the list price vs street price article.

The negotiation strategy.

The order document negotiation strategy is to treat the order with the same care as the master agreement, reading and negotiating the order before signing rather than treating it as a formality. The customer that negotiates the master agreement carefully but signs the order without scrutiny negotiates the wrong document, because the order frequently carries the terms that govern the specific purchase. The customer that gives the order the attention it deserves negotiates from the document that matters.

The negotiation strategy should integrate the order document review with the broader deal negotiation, ensuring the product and metric definitions are correct, the order specific terms are favourable, and the pricing and price hold provisions are negotiated. The order is the point at which the negotiated terms become concrete, and the customer should ensure the order reflects the deal it negotiated. The customer that reviews the order against the negotiated terms captures the value of the negotiation. See the contract terms pillar for the broader framework.

The structural response is to treat the order document with the same care as the master agreement, integrating the order review with the broader negotiation. The buyer that negotiates the order captures the value of the deal. See the ULA deal type page and our contract review service.

Reading the document that governs.

The Oracle order document is the document that governs the specific purchase, and the customer that reads it with the care it deserves negotiates from the document that matters. The relationship with the master agreement, the product and metric definitions, the order specific terms, and the pricing and price hold provisions each affect the customer's position, and the customer that scrutinises the order captures the value and limits the exposure that the order otherwise carries. The order that is signed as a formality governs on Oracle's terms. The order that is read and negotiated governs on terms the customer chose.

For the broader framework see the contract terms pillar and the SLA service level clauses article.