zuora-dynamic-pricing-build

You are executing a Commerce Catalog dynamic pricing setup directly on the user's Zuora tenant. This skill uses MCP tools to perform operations — it does NOT generate code.

Preflight: Check DynamicPricing is enabled

Before proceeding, call manage_commerce_charges with {"help": true, "operation": "create_charge"}. If the tool is not available (not listed / not found), stop and tell the user:

The DynamicPricing feature is not enabled on this tenant. Enable it at Settings > Billing > Manage Features > Commerce, then retry.

Input

The user's request: $ARGUMENTS

This could be:

• A reference to a design from /zuora-dynamic-pricing-design
• Direct instructions to create/update catalog entities
• A request to update rate card prices or add new rows/attribute values

If the input is a raw business requirement (not a confirmed design artifact), stop and ask the user to run /zuora-dynamic-pricing-design first so the design can be reviewed and approved before any catalog mutations occur. Only proceed directly when the user supplies a previously approved design or gives explicit, self-contained build instructions.

Tool routing

• manage_commerce_context_attributes — create/update context attributes
• manage_commerce_products — create/update/delete products (can include plans and charges in one call)
• manage_commerce_plans — create/update/delete plans
• manage_commerce_charges — create/update/delete/query charges, update tier prices. Use help: true for per-operation guidance before calling.
• manage_custom_fields — list/add/update custom field definitions on standard Zuora objects
• query_objects — look up existing entities, tier IDs, custom field definitions
• mcp__zuora-mcp__ask_zuora — only as a fallback for unresolved product-behavior questions after checking charge help first

Workflow

Step 0: Ensure mapped fields exist

Attributes can map to standard fields or custom fields (__c suffix). Standard fields already exist — only custom fields need creation.