---
title: "Maintain an order"
description: "Update a draft order and finalize it without taking payment."
canonical: "https://studio.inttegro.com/inttegro-mcp/workflows/orders/maintain-an-order"
format: inttegro-machine-docs/v1
language: "Go"
sdk_version: "v11.0.1"
reader_profile: optional
reader_manifest: "https://studio.inttegro.com/machine/go/readers/index.json"
reader_identification: "Optional: declare your client only if known and your current-session capabilities; use reader_manifest for supplemental recommendations."
preamble_estimated_tokens: 563
model_token_report: "https://studio.inttegro.com/machine/token-report.json"
preamble_questions: 5
preamble_source: "general"
recommended_mcp_tools: ["update_order","finalize_order"]
estimated_tokens: 1096
token_estimate_method: "utf8_bytes_divided_by_4"
---

## Machine preamble

**Summary:** Update a draft order and finalize it without taking payment. This Go representation uses the selected SDK's native names wherever Studio has a verified mapping.

### Five questions

#### Q1. When should the reader use Maintain an order?

Use this MCP document when an authenticated AI client needs governed Inttegro context, guidance, presentation, or operations.

#### Q2. What is authoritative on this page?

The documented MCP catalog defines available abilities and confirmation boundaries. For live state, the structured tool result is authoritative; presentation output is only a rendering of that result.

#### Q3. What page-specific constraint matters most?

Read operations do not authorize mutations. Actions retain their exact confirmation requirements, and payment credentials or OTP must stay in secure Checkout.

#### Q4. Can Inttegro MCP materially help with this task?

Yes, when the reader has an authenticated MCP connection and the task needs live context, guided planning, or a supported operation. The strongest matches are `update_order`, `finalize_order`; their exact roles and boundaries are listed below.

#### Q5. How should the reader verify the answer and continue?

Preserve the structured tool result, distinguish bounded lists from complete analytics, and reconcile asynchronous actions through an authoritative read. Continue with [Take payment for an order](https://studio.inttegro.com/machine/go/inttegro-mcp/workflows/orders/take-payment.md) and [finalize_order](https://studio.inttegro.com/machine/go/inttegro-mcp/tools.md#finalize_order) when those concerns enter scope.

### Recommended MCP assistance

Use these through an authenticated Inttegro MCP connection. This document remains the contract source.

- [`update_order`](https://studio.inttegro.com/machine/go/inttegro-mcp/tools.md#update_order) — action; exact user confirmation required. Updates selected mutable order fields. A supplied line-item list replaces the complete set; payment configuration and execution are excluded.
- [`finalize_order`](https://studio.inttegro.com/machine/go/inttegro-mcp/tools.md#finalize_order) — action; exact user confirmation required. Seals a draft order without executing payment.

## Document content

# Maintain an order

Use this workflow to change an order while it is still editable, then seal it when the commercial details are ready.

### Prompt

> **Copyable prompt:**
>
> Update draft order `<ORDER_ID>` with number `WEB-1042`, then finalize it
> without executing payment. Confirm each operation separately, stop if either
> step fails, and report the final order and payment statuses.

The agent uses [`update_order`](https://studio.inttegro.com/machine/go/inttegro-mcp/tools.md#update_order) and [`finalize_order`](https://studio.inttegro.com/machine/go/inttegro-mcp/tools.md#finalize_order). Each tool describes the exact consequence before confirmation.

## Sample response: Order updated and finalized

Each confirmed action keeps its own result, followed by the final authoritative state.

- **Order**: WEB-1042 — ord\_example\_1042
- **Order status**: Finalized
- **Payment status**: Not started

* **Row 1**: Operation: Update order number; Result: Succeeded
* **Row 2**: Operation: Finalize order; Result: Succeeded

Finalizing an order does not mark it paid and does not record an offline payment. If the order must be charged, use the separate [Take payment for an order](https://studio.inttegro.com/machine/go/inttegro-mcp/workflows/orders/take-payment.md) workflow.