---
title: "Create and invoice an order"
description: "Create a finalized order and send its invoice through available customer channels."
canonical: "https://studio.inttegro.com/inttegro-mcp/workflows/orders/create-and-invoice-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: 586
model_token_report: "https://studio.inttegro.com/machine/token-report.json"
preamble_questions: 5
preamble_source: "general"
recommended_mcp_tools: ["create_order","send_order_invoice"]
estimated_tokens: 1190
token_estimate_method: "utf8_bytes_divided_by_4"
---

## Machine preamble

**Summary:** Create a finalized order and send its invoice through available customer channels. This Go representation uses the selected SDK's native names wherever Studio has a verified mapping.

### Five questions

#### Q1. When should the reader use Create and invoice 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 `create_order`, `send_order_invoice`; 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 [send_order_invoice](https://studio.inttegro.com/machine/go/inttegro-mcp/tools.md#send_order_invoice) and [create_order](https://studio.inttegro.com/machine/go/inttegro-mcp/tools.md#create_order) when those concerns enter scope.

### Recommended MCP assistance

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

- [`create_order`](https://studio.inttegro.com/machine/go/inttegro-mcp/tools.md#create_order) — action; exact user confirmation required. Creates an order for an existing customer from catalog product and price IDs. This tool never executes payment; finalize defaults to false.
- [`send_order_invoice`](https://studio.inttegro.com/machine/go/inttegro-mcp/tools.md#send_order_invoice) — action; exact user confirmation required. Sends a finalized order invoice through the order customer’s available delivery channels after confirmation.

## Document content

# Create and invoice an order

Use existing customer, product, and price IDs. Finalizing seals the order so its invoice can be sent, but it does not charge the customer.

### Prompt

> **Copyable prompt:**
>
> Create and finalize an order for customer `<CUSTOMER_ID>` containing two units
> of product `<PRODUCT_ID>` at price `<PRICE_ID>`. Do not execute payment. After
> creation, send its invoice through the customer's available channels. Confirm
> the order and delivery separately, then report the order ID, calculated total,
> and channels that succeeded or failed.

The first confirmation covers [`create_order`](https://studio.inttegro.com/machine/go/inttegro-mcp/tools.md#create_order). The second covers [`send_order_invoice`](https://studio.inttegro.com/machine/go/inttegro-mcp/tools.md#send_order_invoice). Keeping them separate prevents a delivery failure from obscuring a successfully created order.

## Sample response: Order created and invoice sent

The order result and delivery result remain distinct, so a channel failure cannot hide a successful order.

- **Order**: WEB-1042 — ord\_example\_1042
- **Status**: Finalized
- **Payment**: Not started
- **Total**: GHS 700.00 — 2 products

Invoice delivery

- **Row 1**: Channel: Email; Result: Sent; Reference: chime\_example\_email
- **Row 2**: Channel: SMS; Result: Sent; Reference: chime\_example\_sms

Invoice delivery can partially succeed. The agent reports each channel's outcome instead of reducing the delivery attempt to one success or failure.