ATIS Purchase Order Changes: Keep Configuration, Price and Acceptance on the Same Revision
An ATIS purchase order change should update the technical configuration, commercial scope and acceptance records together before the revised order is released. Identify what changed, which vehicles are affected and who must accept the revision. A corrected price or quantity on its own does not establish that the supplier, installer and fleet are working to the same requirement.
This guide is for fleet procurement teams, engineers, distributors and installers managing a revised order. It offers a practical document-control workflow, not a universal contract clause or a claim that a particular change is legally binding. The actual agreement and authorized approval process govern the transaction.

Start with a specific change request
Record the current order reference, revision and proposed change. State whether the trigger is a different vehicle, quantity, component reference, installation location, service scope or delivery requirement. Avoid a vague instruction such as “update the kits” because different teams may interpret it differently.
Explain why the request exists and what decision is needed. A fleet adding trailers to an order needs an application review for the added assets. A buyer correcting a billing detail may need a different review. Classify the actual effect rather than treating every amendment as either trivial administration or a complete redesign.
Freeze the baseline before comparing revisions
Preserve the accepted order and its referenced documents. Create a revision list showing the configuration, quotation, application register and acceptance requirements that formed the baseline. Do not overwrite those files and leave the team unable to establish what was originally agreed.
Use the procurement acceptance-document checklist to identify the relevant records. The checklist is a planning aid; it does not decide whether a proposed contractual amendment is accepted. Keep the technical review and commercial authorization explicit.
Use a change-impact table
| Change | Technical question | Commercial question |
|---|---|---|
| Additional vehicles | Are their configurations within the accepted application scope? | What quantities, price and delivery dates are proposed? |
| Different component reference | Is the replacement supported for the identified application? | What documentation and cost changes follow? |
| Installation location | Can the proposed workshop deliver the approved scope? | Which labor, travel and local costs change? |
| Shipment arrangement | Does packaging or identification affect receiving controls? | Which delivery responsibilities and named place apply? |
| Acceptance scope | Which checks and records are required? | Who accepts completion and under what agreed terms? |
Assign an owner for every affected row. If a change has no effect on a topic, record the reason rather than leaving the cell blank. An explicit “reviewed, no change” can be distinguished from a subject that nobody considered.
Resolve configuration before confirming supply
List the asset groups affected by the amendment and identify the proposed equipment for each. Keep confirmed applications separate from applications awaiting review. A larger quantity does not necessarily mean a larger order of the same configuration.
NACFE describes different inflation arrangements. A broad product category is not a sufficient purchase specification. The order should point to the actual configuration decision and relevant documents rather than relying on the abbreviation ATIS to communicate technical scope.
If the change involves a substitute item, obtain the appropriate written application decision. Do not let an amended commercial line silently authorize a technical substitution. The buyer can record an approved replacement, but purchasing convenience should not determine compatibility.
Reconcile the complete cost scope
Compare the revised order with the previous scope line by line. Identify equipment, documents, installation, training, travel, service stock and other agreed elements. Show which items are included, excluded or still provisional. Avoid describing a kit-price reduction as a lower installed cost if associated services have moved outside the quotation.
The ATIS quotation exclusions guide can help identify questions that often sit outside the equipment line. Use it to make the commercial conversation explicit, not to assume that every listed service is available or required for every transaction.
Specify delivery terms without treating them as the whole agreement
The International Trade Administration’s Incoterms overview explains their role in allocating delivery tasks, costs and risks. Where relevant, identify the agreed rule, version and named place. Have the appropriate commercial or logistics specialists review the proposed arrangement.
Delivery terms alone do not define the goods, full contract price, payment arrangements or every acceptance obligation. Keep these subjects in the actual agreement and order documents. If a shipment date changes, ask whether installation bookings, receiving arrangements and pilot plans also need revision.
Do not state a customs, tax or import outcome from a generic delivery term. Responsibilities and requirements need review for the actual transaction. Record which party will obtain any required specialist advice instead of implying that a short purchase-order note resolves every cross-border question.
Match claims and acceptance evidence
A change request may introduce new expectations, such as a different operating application or a numerical performance target. Treat a new expectation as a question to resolve, not an outcome already promised. Ask what evidence supports the statement and whether the revised scope actually includes the work needed to assess it.
The U.S. FTC advertising-substantiation policy concerns evidence for objective advertising claims. It is U.S. legal context, not an ATIS acceptance standard. The practical commercial discipline is to avoid unsupported savings, approval or performance statements in the revised offer.
Write acceptance requirements in terms of the agreed configuration, documents and applicable verification. If a performance study is proposed, specify its separate method, responsibilities and limitations. Do not turn a normal installation handover into evidence of an unmeasured operating result.
Control release to the people doing the work
After authorization, distribute the revised order and relevant documents through the agreed route. Identify which previous revision is superseded for active work. Ask the receiving, installation and fleet teams to confirm the version they will use, especially if goods or documents have already been prepared.
Reconcile work in progress. Establish whether an existing shipment, installed item or workshop booking is affected and who will decide its disposition. A revision notice sent after dispatch does not automatically change what was packed. Keep the physical status and document status aligned.
Handle a disagreement without losing the baseline
If a proposed change is not accepted, preserve the current agreed baseline and record the unresolved issue. Do not issue competing revisions that each appear final. Escalate through the authorized commercial and technical roles, stating the decision required and the operational consequence of delay.
When the decision is complete, retain the request, impact review, authorization and final revision together. This makes later invoice, receiving and service questions easier to reconcile. A short but complete change history is more useful than a long message chain with no clear accepted version.
Purchase-order revision checklist
- Identify the accepted baseline and exact proposed change.
- List affected vehicles, configurations and documents.
- Resolve technical substitutions through the proper authority.
- Reconcile included costs, delivery and acceptance scope.
- Record authorization and communicate the released revision.
- Align work in progress and retain the change history.
Record approval by role
Identify who accepted the technical scope and who authorized the commercial amendment. They may be different people. Recording both decisions helps prevent a price approval from being mistaken for configuration acceptance.
Frequently asked questions
Does a quantity change always need a new application review?
Check which vehicles are being added. Identical quantities and product names do not prove identical configurations. Review any application outside the documented scope.
Can a revised quotation replace the technical approval?
No. A commercial document can reference the technical decision, but it should not silently create one. Keep the responsible technical authorization traceable.
Should the old order revision be deleted?
No. Preserve it as history while making the currently released revision clear to those performing the work.
Review a proposed order change
Ask IntelliSafeAir about fitment, a fleet pilot or distributor cooperation. Include the affected vehicle types, current order scope and proposed amendment. Request aligned technical and commercial documents before treating a revised configuration as confirmed.