A quote can meet its margin target and still become a bad order. The customer may hold the last payment until site acceptance, impose delay damages, extend the warranty, move freight and import risk to the supplier, or reserve a broad right to cancel. None of those terms appears in the unit price. Each one changes what the OEM must fund, perform or put at risk.
The review should produce a short exception schedule that sales can negotiate. It should not send a 40-page purchase agreement around the company with a request to “approve terms.” Show what the customer asked for, what the company normally offers, the dollars or work at stake, the proposed answer and the person who can accept the remaining exposure.
Build a terms comparison, not a tick-box form
Start with the customer RFQ, draft purchase agreement, portal terms and incorporated documents. Extract the clauses that apply to the proposed sale and compare them with the company’s approved position for that product, customer and country. A check mark beside “warranty reviewed” tells the approver nothing. The useful record shows that the customer requested 24 months from site acceptance, the offer includes 12 months from commissioning or 18 months from shipment, and the service director estimates the requested extension at $68,000.
Keep agreed terms in the record too. They prove what the team reviewed and prevent the same clause from returning as an exception when the customer issues a purchase order. Put the material differences at the top. Link each one to its source clause so legal, finance and operations can read the exact language when they need it.
| Field | What to record | Why it matters |
|---|---|---|
| Customer request | Exact clause, document, section and revision | Preserves the source and context |
| Company position | Approved term for this product and transaction | Creates a real comparison point |
| Difference | Plain-language change in obligation, timing or remedy | Lets a business owner understand the issue |
| Exposure | Cash, cost, schedule, legal right or operating work at risk | Supports a proportional decision |
| Proposed answer | Accept, reject, qualify, price or counter | Gives sales language it can use |
| Owner | Person with authority and decision date | Stops an exception from becoming an unowned comment |
Identify every document that could govern the sale
An industrial bid often sits inside several documents: the OEM proposal, customer RFQ, technical specification, purchasing terms, supplier code, data-security schedule and later purchase order. List every incorporated document and its revision. Then state which document controls when two provisions conflict.
Watch for incorporation by link. A portal may point to purchasing terms that change without the proposal revision changing. Download or otherwise preserve the version reviewed for the bid. If the customer asks the supplier to accept future policy updates automatically, route that request to legal. The team cannot price a duty that another party may change after award.
Resolve proposal exclusions and customer boilerplate before award. A line in the proposal that says “our terms apply” may not settle a conflict with the buyer’s purchase order. The sales record needs the negotiated order of precedence and the final set of incorporated documents. Counsel should approve the contract language; the commercial workflow should make the conflict visible early enough to negotiate it.
| Document | Revision or date | Role in the deal | Conflict to resolve |
|---|---|---|---|
| OEM proposal | Proposal revision | Scope, price, schedule and seller qualifications | Does the order incorporate it in full? |
| Customer RFQ | RFQ and amendment number | Requested scope and bid instructions | Which requirements survive into the order? |
| Technical specification | Document and revision | Performance, interfaces and tests | Does it conflict with the offered design? |
| Purchase terms | Dated copy or controlled version | Commercial and legal conditions | Which seller exceptions change them? |
| Purchase order | Order revision | Awarded price, quantity and delivery | Does it match the accepted proposal? |
| Referenced policies | Named version | Security, conduct, site or quality rules | Can the customer change them after award? |
Lock the scope, deliverables and customer dependencies
Describe the equipment, services, documentation, software, spares, installation, commissioning and training included in the price. State the quantities and site. List exclusions beside the related scope; a general note makes them easy to miss. If the customer supplies foundations, utilities, permits, process data or site access, state the date and condition in which the OEM needs each input.
Tie performance commitments to a defined operating envelope. A pump efficiency guarantee means little without the fluid, duty point, test method and tolerance. A line-throughput promise needs incoming material, staffing, utilities and acceptance method. Technical clarification should close those inputs before commercial approval turns them into a warranty or damage exposure.
Separate priced options from the base scope. Give each option its own validity, lead-time effect and acceptance rule. Do not let a proposal total imply that an optional service or spare package forms part of the base commitment.
| Scope check | Question to answer | Owner |
|---|---|---|
| Equipment boundary | What starts and stops at the OEM supply boundary? | Engineering and sales |
| Services | Which installation, supervision, commissioning and training days does the price include? | Field service |
| Documents | Which drawings, manuals, certificates and data formats are due? | Engineering and quality |
| Customer inputs | What must the customer provide, where and by when? | Project management |
| Performance basis | Which conditions, test method and tolerance govern? | Engineering and quality |
| Options | Which items can the customer add or remove without reopening the base? | Sales and estimating |
State the price basis in enough detail to administer it
Record currency, taxes, duties, freight, insurance, packaging, travel and commissioning assumptions. State whether the price covers one unit, a lot, a phased release or a forecast volume. If the customer can change quantity without changing unit price, estimate the effect at the lowest and highest permitted volume.
For long lead-time work, define how the price changes when material, labor or currency moves. The BLS price-adjustment guide says an escalation clause should identify the base selling price, exact index and code, source, adjustment frequency, index version, calculation and any floor or ceiling. BLS also warns that “the Producer Price Index” is not one index. Name the series that matches the cost exposure and state what happens if the series stops publishing.
A price-validity date needs an action after expiry. The proposal can require a refresh of supplier costs, exchange rates and delivery before acceptance. That is more useful than saying the price is “subject to change,” which gives the buyer no way to form a valid order.
| Price term | Minimum statement | Common failure |
|---|---|---|
| Currency | Quote, invoice and payment currency | Supplier costs move in another currency |
| Taxes and duties | Included, excluded and responsible party | Customer assumes a delivered tax-paid price |
| Quantity basis | Unit, lot, release and volume assumptions | Unit price survives a material volume reduction |
| Validity | Acceptance deadline and refresh action | Expired supplier and freight inputs remain hidden |
| Escalation | Base month, series, weights, timing and caps | No one can administer a vague index reference |
| Change pricing | Rates, markups or estimating method | Each change becomes a new commercial dispute |
Map payment to work, cash and acceptance
Show the amount, invoice event, evidence, due date and credit support for every milestone. “30 percent at shipment” needs a shipment definition. “20 percent after acceptance” needs an acceptance test and a deadline for the customer to respond. Avoid a final payment event that the customer can defer by delaying site readiness or withholding a signature.
Calculate the cash curve against material purchases, engineering, production and supplier payments. A 20 percent margin does not finance a project that reaches its peak cash need six months before the first meaningful customer payment. Finance should see the peak exposure, duration, credit limit and the days on the final invoice.
International sales may need a different payment instrument. The U.S. International Trade Administration’s guide to methods of payment explains the trade-off among cash in advance, letters of credit, documentary collections, open account and consignment. A letter of credit depends on compliant documents; it does not repair unclear shipment or acceptance terms. Credit, treasury and the bank should review the instrument before the proposal promises it.
| Milestone | Evidence | Due-date rule | Risk check |
|---|---|---|---|
| Order | Accepted order and any advance-payment security | Invoice at order; stated payment period | Credit approval and cancellation exposure |
| Design release | Approved drawing or elapsed review period | Invoice on release or deemed release | Customer review cannot suspend work indefinitely |
| Factory acceptance | Signed protocol or objective test record | Invoice on successful test | Retest and customer no-show rules |
| Shipment | Carrier receipt or named delivery document | Invoice on stated event | Matches the Incoterms rule |
| Site acceptance | Protocol against agreed criteria | Deadline and deemed acceptance | Site readiness sits with the correct party |
| Final retention | Closed punch list limited to material items | Fixed release deadline | Minor items do not hold unrelated payment |
Name the delivery point and the point where risk moves
Do not write “FOB customer site” or “freight included” and assume the parties understand the same thing. Choose the rule, exact place or port and edition. The ICC recommends the format “[rule] [named port, place or point] Incoterms 2020”. The named point matters because it helps define delivery, risk transfer and cost allocation.
Incoterms do not settle the entire contract. They do not define payment, title, product conformity, warranty, damages or dispute resolution. State those items elsewhere. Also check whether the chosen rule fits the mode of transport and whether the OEM can perform the import, export, insurance or unloading duties it accepts.
Tie the quoted lead time to a start event and customer dependencies. “40 weeks ARO” needs a definition of receipt of order: signed agreement, advance payment, approved drawings, export authorization or some combination. State how customer delay moves the schedule and how the team will document it.
| Delivery field | Required answer | Commercial effect |
|---|---|---|
| Lead-time start | Exact events that start the clock | Prevents an unready order from consuming schedule |
| Named delivery point | Precise facility, terminal or site point | Allocates carriage cost and risk |
| Incoterms rule and edition | Rule suited to transport mode and transaction | Defines stated seller and buyer duties |
| Title transfer | Separate contract event | Affects security, tax and recovery rights |
| Packaging and preservation | Standard, storage period and special requirements | Changes cost and warranty risk |
| Customer delay | Notice, storage, reschedule and cost rule | Protects capacity and finished equipment |
Define inspection and acceptance as an executable test
Acceptance should identify the item, test method, conditions, tolerance, witness rights, record, response time and remedy for a failed test. Split factory acceptance from site acceptance when they prove different things. Factory testing may prove equipment performance under simulated conditions; site testing may depend on the customer’s process, utilities and operators.
Set rules for customer no-shows and late responses. If the customer misses a witnessed factory test after proper notice, the OEM may run the test and issue the record. If the customer does not reject with a stated material failure within the review period, the contract can define deemed acceptance. Counsel must approve the language, but operations must confirm that the test can actually run as written.
The FAR inspection clause for fixed-price supplies offers a useful drafting lesson even for private work: it separates inspection, acceptance, correction, replacement and price reduction. Do the same in the bid. Do not let inspection rights silently become an unlimited right to delay acceptance or demand changes outside the agreed requirements.
| Acceptance item | Write this down | Do not leave open |
|---|---|---|
| Test basis | Procedure, inputs, load, duration and tolerance | “Customer satisfaction” |
| Witness | Notice period and result if customer does not attend | An indefinite wait for a witness |
| Result | Signed protocol or objective data set | Approval without a response deadline |
| Failure | Material failure, cure, retest and cost owner | Repeated new criteria after each test |
| Site dependency | Utilities, material, access and operators | OEM liability for customer readiness |
| Deemed acceptance | Use, elapsed review period or missed response | Final payment tied to an event with no end date |
Make the warranty operational
State when the warranty starts, how long it runs, what it covers, what it excludes, how the customer reports a claim and which remedies apply. For equipment that may sit in storage, use an outside date from shipment as well as a period from commissioning. Otherwise a delayed project can extend the supplier’s risk without limit.
Define the location and cost of repair. Large equipment can make removal, freight, travel, disassembly and reinstallation cost more than the failed part. State who bears those costs and when remote diagnosis, customer labor or a field visit applies. List maintenance, operating, consumable, wear, misuse, unauthorized modification and customer-supplied design conditions that affect coverage.
The FAR warranty clause for complex supplies distinguishes the warranty period, defect notice, repair or replacement, transport, data updates and the treatment of replaced parts. It is a good completeness check, not a clause to paste into a commercial offer. Service, engineering and counsel should set the terms that match the product and installed-base support model.
| Warranty field | Decision |
|---|---|
| Start and outside date | Commissioning event plus shipment cap |
| Covered promise | Conformity, materials, workmanship and stated performance |
| Exclusions | Wear, consumables, misuse, storage, maintenance and unauthorized changes |
| Claim process | Notice, evidence, access and response times |
| Remedy | Repair, replacement, parts, field labor or price adjustment |
| Logistics | Removal, freight, customs, travel, reinstallation and risk in transit |
| Replacement coverage | Remainder of original term or a stated new period |
Put delay damages beside the schedule they depend on
Record the triggering milestone, grace period, rate, cap, exclusions and sole-remedy position for liquidated damages. Then model the maximum amount against quote margin. A rate that looks small per week can consume the entire profit on a long delay.
The FAR policy on liquidated damages states that the rate should forecast probable harm and should not punish the supplier. It also recommends a maximum amount or period where that limit reflects the maximum probable damage. Private contracts follow their governing law, so counsel must assess enforceability. The commercial team still needs the same economic questions: what failure triggers the amount, which delays count, how the parties prove delay and where the exposure stops.
Link relief to events outside the OEM’s control: customer changes, late approvals, site access, force majeure, permit delay and agreed suspension. Require timely notice and a schedule update. Avoid accepting damages against a date that the customer can move without adjusting the delivery promise.
| Delay term | Question for approval |
|---|---|
| Milestone | Which delivery or performance event triggers damages? |
| Rate | What is the amount per day or week? |
| Cap | What is the maximum amount and percentage of affected scope? |
| Grace period | When does the calculation start? |
| Excusable delay | Which customer and external events extend time? |
| Concurrency | How should the parties treat simultaneous causes? |
| Remedy | Are damages the sole remedy for the covered delay? |
Route liability, indemnity and insurance to the right decision
Commercial review should summarize who bears each category of loss, the liability cap, exclusions from the cap and any waiver of indirect or consequential damages. Do not reduce this review to “legal approved.” Sales and the business sponsor need to know when the customer asks for exposure that exceeds the order value or the company’s insurance.
Match each indemnity to a defined event and control. Product injury, third-party intellectual-property claims, site work and customer-provided designs create different risks. State who controls the defense, who approves settlement and what notice the indemnified party must give. Compare the clause with insurance limits and exclusions; a contract obligation does not become insured because the certificate shows a large number.
Counsel owns the legal analysis. Finance and the executive sponsor own the business decision to accept residual exposure. The workflow should route them the clause, customer position, company counter, maximum modeled exposure and insurance response in one brief.
| Risk | Commercial record | Primary reviewer |
|---|---|---|
| Direct damages | Cap basis, amount and covered claims | Legal and finance |
| Consequential loss | Excluded categories and any carve-outs | Legal |
| IP infringement | Covered product, customer design and remedy | Legal and engineering |
| Personal injury or property damage | Fault standard and site responsibility | Legal and insurance |
| Customer indemnity | Protection for customer data, design and instructions | Legal |
| Insurance | Required limits, policies, duration and available coverage | Risk and finance |
Name the governing law and the path for disputes
State the governing law, court or arbitration forum, seat, language and notice method. Check where the customer, work, equipment and assets sit. A forum clause can change the cost and practical value of every other remedy in the agreement.
For cross-border sales, ask counsel whether the United Nations Convention on Contracts for the International Sale of Goods applies and whether the agreement should include or exclude it. The UNCITRAL sale-of-goods page explains that the CISG covers contract formation, buyer and seller obligations, and remedies for non-performance. A governing-law line may not answer the CISG question on its own.
Define the dispute path before formal proceedings: project managers, executives, mediation and then the chosen court or tribunal. Set response periods and preserve urgent relief where needed. Decide whether work continues during a dispute and how the customer pays undisputed amounts. An escalation ladder helps only when each step names a person with authority to settle.
| Dispute term | Decision to record |
|---|---|
| Governing law | Named jurisdiction and treatment of the CISG |
| Forum | Court or arbitration institution, seat and language |
| Notice | Addresses, permitted method and effective date |
| Escalation | Named roles, sequence and time at each level |
| Continued work | Which work proceeds and who funds it during the dispute |
| Undisputed payment | Customer pays amounts that the dispute does not affect |
| Urgent relief | Rights preserved for IP, confidentiality, safety or asset protection |
Price the customer’s rights to change, suspend or cancel
State that an authorized person must approve scope, price and schedule changes in writing. The contract should explain how the OEM handles urgent work when the parties have not yet agreed on the full adjustment. An email from a site contact should not quietly add engineering or field work that procurement later refuses to pay.
For suspension, define how the OEM secures work in progress, stores equipment, remobilizes people and moves the schedule. For cancellation, build a schedule that covers completed work, committed material, supplier cancellation, demobilization and reasonable closeout. A flat percentage may underrecover early long-lead commitments and overrecover late in the project; test the schedule against the actual cost curve.
The federal commercial-products clause at FAR 52.212-4 separates written changes, termination and payment. The exact public-contract mechanism will not fit every private sale, but the separation is sound: define how scope changes, how work stops and how the seller gets paid for each event.
| Event | Required mechanism | Cost to model |
|---|---|---|
| Customer change | Authorized request, impact quote and signed change | Engineering, material, labor, supplier and schedule |
| Urgent direction | Named interim authority and spending limit | At-risk work before final agreement |
| Suspension | Notice, protection, storage and restart | Idle labor, demobilization, storage and escalation |
| Cancellation for convenience | Termination schedule and payment date | Work done, commitments, unwind and closeout |
| Default | Notice, cure and remedy | Replacement, recovery and dispute cost |
| Force majeure | Notice, mitigation and time or cost relief | Unrecoverable delay and supplier effects |
Separate equipment ownership from IP, data and software rights
A customer buying equipment does not automatically need ownership of the OEM’s background designs, configurators, calculation methods or manufacturing know-how. List pre-existing intellectual property, project deliverables and any customer-funded development. State the license or ownership that applies to each group.
Define rights in drawings, models, manuals, source code, machine data, usage data and remote-service access. If the product contains third-party software, confirm that the proposed license, territory, users and transfer rights match the supplier terms. If cybersecurity obligations apply, route the specific controls and incident duties to the product and security teams before promising them.
Confidentiality needs a workable marking and handling rule, permitted recipients, exclusions and duration. Check whether the customer asks the OEM to receive export-controlled technical data or personal data. Those facts can change who may access the bid package and where the team may process it.
| Asset | Question to settle |
|---|---|
| Background IP | What existed before the project and stays with the OEM? |
| Project deliverables | What does the customer receive and in which format? |
| License | Who may use, copy, modify, transfer or sublicense the item? |
| Machine and service data | Who can collect, use, retain and disclose each data set? |
| Third-party software | Which supplier terms and renewal duties pass through? |
| Confidential information | How is it identified, shared, retained and returned? |
Clear compliance and export conditions before committing delivery
Identify the customer, end user, destination, end use, intermediaries and controlled technical content. Record which party obtains permits, licenses, certifications and customs documents. Do not promise a firm export delivery date before the team understands the authorization path.
The U.S. government’s Consolidated Screening List combines several restricted-party lists as a screening aid and tells users to check the official source when a possible match appears. BIS also publishes Know Your Customer red flags for unusual product, destination, routing and end-use facts. Screening is one control. The trade-compliance owner must resolve matches, classification, licensing and end-use concerns for the actual transaction.
Include anti-bribery, sanctions, local-content, origin, safety, environmental and industry-specific requirements only after the responsible function confirms that the company can meet them. State which certifications apply to the equipment and which apply to the customer’s site or finished system.
| Compliance check | Evidence before release |
|---|---|
| Parties | Customer, end user, consignee, freight party and intermediaries screened |
| Product | Classification, controlled content and license position |
| Destination and end use | Confirmed site, application and route |
| Certifications | Applicable product marks, code basis and issuing body |
| Origin and content | Supported country-of-origin and local-content statement |
| Permits and customs | Named party, document and schedule dependency |
Worked example: a compressor package with a risky final payment
An OEM plans to quote a $2.40 million compressor package with an estimated cost of $1.85 million. The draft gross margin is 22.9 percent. The customer’s purchase terms call for 10 percent at order, 60 percent at shipment and 30 percent after site acceptance, net 60. The customer controls site readiness and gives itself no deadline to run the acceptance test. That puts $720,000 of invoicing behind an event the OEM does not control.
The same terms require DDP delivery to the site, 24 months of warranty from site acceptance, delay damages of 0.5 percent of order value per week with no stated cap, broad cancellation for convenience and unlimited liability. The quoted estimate contains domestic freight, a 12-month warranty from commissioning with an 18-month shipment cap and no import duty. The 22.9 percent margin does not describe the requested deal.
The review prices the main differences. Finance calculates $46,000 of additional financing exposure. Logistics estimates $72,000 for the requested transport, brokerage and duty basis. Service adds an $84,000 reserve for the longer and open-ended warranty. Ten weeks of delay damages would equal $120,000, and the uncapped term could go further. Purchasing identifies $610,000 of noncancelable long-lead commitments before factory acceptance.
The team counters with 20 percent at order, 30 percent at design release, 40 percent after factory acceptance and 10 percent after site acceptance, each net 30. Site acceptance uses an agreed test, a 30-day customer window and deemed acceptance if the customer uses the equipment or misses the window for reasons unrelated to the OEM. Delivery becomes DAP at the named site, with import clearance and duty excluded. The OEM adds $58,000 of supported transport cost. The warranty runs 12 months from commissioning or 18 months from shipment, whichever occurs first.
Legal and operations approve delay damages at 0.25 percent per week after a two-week grace period, capped at 2.5 percent of the affected equipment price and serving as the customer’s sole remedy for the covered delay. Excusable customer delay moves the date. The liability cap equals the order value, with counsel-approved exceptions, and the parties waive stated categories of consequential loss. Cancellation payments follow the actual commitment curve.
The proposal price moves to $2.51 million against $1.908 million of supported cost, which produces 24.0 percent gross margin. If the OEM incurs the entire $60,000 delay-damage cap, margin falls to 21.6 percent. The approvers can see both results before release. The final exception schedule shows what changed, who approved it and which clauses must appear in the order.
| Term | Customer request | Approved offer | Result |
|---|---|---|---|
| Payment | 10% order / 60% shipment / 30% SAT, net 60 | 20% order / 30% design / 40% FAT / 10% SAT, net 30 | Peak cash and acceptance holdback reduced |
| Acceptance | Customer-controlled SAT with no deadline | Agreed test, 30-day window and deemed acceptance | Final milestone has an end date |
| Delivery | DDP site | DAP named site; duty and import clearance excluded | Responsibility matches estimate and capability |
| Warranty | 24 months from SAT | 12 months commissioning or 18 months shipment | Exposure has a supported outside date |
| Delay damages | 0.5% per week, no cap | 0.25% per week after grace, 2.5% cap on affected equipment | Maximum modeled exposure is $60,000 |
| Cancellation | Broad convenience right | Payment follows work and commitment schedule | $610,000 early commitment protected |
| Liability | Unlimited | Order-value cap, stated carve-outs and consequential-loss waiver | Residual exposure matches executive approval |
| Economics | $2.40M price / $1.85M cost / 22.9% margin | $2.51M price / $1.908M cost / 24.0% margin | 21.6% margin after the full $60K delay cap |
Give each exception one decision and one owner
Route the exception to the function that controls it. Credit approves customer exposure. Treasury approves currency and payment instruments. Operations approves schedule and delay recovery. Service approves warranty execution. Engineering approves performance conditions. Trade compliance clears restricted transactions. Legal approves rights, remedies and contract language. The business sponsor decides whether the commercial return justifies any residual risk.
Run independent decisions in parallel. A warranty question does not need to wait behind a currency question. Bring them together only when one answer changes another, such as a customer payment milestone tied to site acceptance or a liability cap tied to insurance.
Record approve, approve with conditions, counter, reject or escalate. A condition must state what evidence closes it and whether a later change reopens approval. “Legal to review at order” is not a bid decision when the customer expects acceptance of its terms in the proposal.
| Exception | Decision owner | Typical evidence |
|---|---|---|
| Payment and credit | Finance or credit | Cash curve, credit limit and security |
| Currency and escalation | Treasury and finance | Cost currency, rate basis and formula |
| Delivery and delay | Operations and project leadership | Schedule, dependencies and recovery plan |
| Acceptance and performance | Engineering and quality | Test method, conditions and tolerance |
| Warranty | Service and engineering | Installed-base data, reserve and service model |
| Liability and indemnity | Legal, finance and sponsor | Clause, cap, insurance and modeled exposure |
| Export and sanctions | Trade compliance | Parties, product, destination, end use and license |
Release a negotiation schedule sales can use
The final output should fit the negotiation. Put the material exceptions in priority order. For each one, give sales the requested clause, preferred answer, acceptable fallback, walk-away point and approver. Do not make the salesperson translate a chain of legal comments into customer language during a call.
Carry the schedule into every proposal revision. When the customer accepts a counterproposal, mark the clause agreed and preserve the evidence. When it rejects a position, route only the new exposure. Reopening the full contract on every turn wastes time and makes settled terms look uncertain.
Before submission, confirm that the proposal text, price, delivery, assumptions and exception schedule tell the same story. A price that assumes FCA cannot sit beside a proposal that promises DDP. A capped warranty reserve cannot sit beside an open-ended start date. Commercial approval ends when the complete offer matches the approved basis.
| Negotiation field | Example |
|---|---|
| Priority | 1: payment and site acceptance |
| Preferred position | 10% at SAT, net 30, with 30-day test window |
| Fallback | 15% at SAT with standby letter of credit |
| Walk-away point | No uncapped payment delay tied to customer site readiness |
| Reason for customer | Milestones match completed work and preserve project capacity |
| Approver | CFO for any fallback outside the approved credit band |
| Status | Counter sent in proposal Rev C; customer answer due Tuesday |
Check the purchase order against the approved bid
Do not assume the awarded order reflects the negotiation. Compare the purchase order, incorporated terms and technical attachments with the last approved proposal. Check price, quantity, delivery, payment, acceptance, warranty, damages, scope, revision and order of precedence. A buyer may restore standard terms or attach a new revision without calling attention to it.
Classify every difference as accepted, clerical, commercial or technical. Sales can correct a clerical reference. The original owner must review a material change. Stop order entry when the purchase order creates an obligation the bid team rejected or never priced.
After acknowledgment, carry the accepted terms into project execution. Billing needs the milestone evidence. Project management needs customer dependencies and notice dates. Service needs the warranty basis. Operations needs the delivery and damage triggers. The contract review has earned its value only when the people doing the work can act on it.
| PO comparison | Pass condition | Action on difference |
|---|---|---|
| Commercial values | Price, currency, tax and payment match | Finance and sales review |
| Technical baseline | Scope and document revisions match | Engineering review |
| Delivery | Date, point, rule and dependencies match | Operations review |
| Risk terms | Warranty, damages, liability and cancellation match | Original approvers review |
| Precedence | Accepted proposal and exceptions govern as agreed | Legal review |
| Handoff | Terms create named execution tasks and dates | Project owner accepts record |
How Bourne reviews commercial terms
Bourne reads the customer RFQ, draft agreement, purchasing terms and referenced documents. It compares each clause with the company’s approved positions and the current proposal. The review shows the requested term, source, difference, commercial exposure, proposed counter and decision owner.
Finance receives the cash and margin effect. Operations receives delivery, acceptance and delay terms. Service receives warranty duties. Engineering receives performance commitments. Legal receives the clause and negotiation history. Each owner decides its part in parallel, and sales receives one controlled exception schedule for the customer.
When the customer sends a revision, Bourne identifies the changed clauses and reopens the affected decisions. After award, it compares the purchase order with the approved bid and passes payment milestones, customer dependencies, warranty dates and notice duties into the customer PO review. The team can see exactly which promise produced each execution task.
Buğra Gündüz
Buğra Gündüz is the co-founder and CEO of Bourne and co-founder of HockeyStack. He built HockeyStack into an eight-figure AI business. At Bourne, he works with entrepreneurs and established companies to create AI products and services.