---
title: "Maintain catalog availability"
description: "Publish a product and deactivate a price as separately confirmed catalog changes."
canonical: "https://studio.inttegro.com/inttegro-mcp/workflows/catalog/maintain-catalog"
format: inttegro-machine-docs/v1
language: "cURL"
reader_profile: optional
reader_manifest: "https://studio.inttegro.com/machine/curl/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: 553
model_token_report: "https://studio.inttegro.com/machine/token-report.json"
preamble_questions: 5
preamble_source: "general"
recommended_mcp_tools: ["publish_product","deactivate_price"]
estimated_tokens: 1073
token_estimate_method: "utf8_bytes_divided_by_4"
---

## Machine preamble

**Summary:** Publish a product and deactivate a price as separately confirmed catalog changes. This cURL representation preserves HTTP paths and JSON wire names.

### Five questions

#### Q1. When should the reader use Maintain catalog availability?

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 `publish_product`, `deactivate_price`; 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 [deactivate_price](https://studio.inttegro.com/machine/curl/inttegro-mcp/tools.md#deactivate_price) and [publish_product](https://studio.inttegro.com/machine/curl/inttegro-mcp/tools.md#publish_product) when those concerns enter scope.

### Recommended MCP assistance

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

- [`publish_product`](https://studio.inttegro.com/machine/curl/inttegro-mcp/tools.md#publish_product) — action; exact user confirmation required. Publishes a product to customer-facing catalog and checkout flows.
- [`deactivate_price`](https://studio.inttegro.com/machine/curl/inttegro-mcp/tools.md#deactivate_price) — action; exact user confirmation required. Deactivates a price so it cannot be selected in new active catalog flows.

## Document content

# Maintain catalog availability

Use this workflow when product visibility or price availability must change without altering historical commercial records.

### Prompt

> **Copyable prompt:**
>
> Publish product `<PRODUCT_ID>`, then deactivate price `<PRICE_ID>`. Confirm each
> operation separately, stop if either step fails, and report the resulting
> product and price statuses.

The agent uses [`publish_product`](https://studio.inttegro.com/machine/curl/inttegro-mcp/tools.md#publish_product) and [`deactivate_price`](https://studio.inttegro.com/machine/curl/inttegro-mcp/tools.md#deactivate_price). Each tool presents its consequence before confirmation.

## Sample response: Catalog availability updated

The product and price retain separate lifecycle states.

- **Product**: Published — prod\_example\_kit
- **Price**: Inactive — price\_example\_launch

* **Row 1**: Operation: Publish product; Result: Succeeded; Effect: Product is available
* **Row 2**: Operation: Deactivate price; Result: Succeeded; Effect: Price cannot be used for new orders

Deactivating a price prevents new use; it does not rewrite existing orders. Price updates cannot change the amount, currency, or product association.