← Articles

UCP Order Currency Field: Multi-Currency Agentic Commerce Gets Cleaner

UCP Schema Commerce

March 3, 2026 · deinck6 + Ilya Grigorik · Commit 294ce8d

A small schema change landed today that has outsized implications for global agentic commerce: the UCP Order schema now includes a top-level currency field.

The Change

The commit adds a single field to source/schemas/shopping/order.json:

{
  "currency": {
    "type": "string",
    "description": "ISO 4217 currency code for this order (e.g., USD, EUR, JPY)"
  }
}

Four lines of schema. Co-authored with Ilya Grigorik, indicating this had core team review.

Why This Matters

Previously, currency information was embedded within individual price objects throughout the order. Line items had currency. Totals had currency. Shipping had currency. This meant:

Redundancy — every monetary value repeated the same currency code
Validation complexity — ensuring all currencies matched required checking every price object
No single source of truth — which currency was the "order currency" if they differed?

The top-level field provides a single, authoritative answer: "This order is in EUR." Period.

Implications for AI Agents

For AI agents handling international commerce, this simplifies several scenarios:

Currency Detection

An agent no longer needs to parse nested price objects to determine what currency an order uses. One field lookup gives the answer immediately.

Multi-Currency Comparison

When an agent is comparing offers from different merchants (potentially in different currencies), having a consistent top-level field makes aggregation cleaner.

Display and Formatting

Presenting order information to users requires knowing the currency upfront for proper formatting. The top-level field provides this without object traversal.

Backward Compatibility

The field is additive — existing implementations that rely on currency within price objects continue to work. But new implementations can use the top-level field as the authoritative source.

This follows UCP's pattern of evolution: additive changes that improve the protocol without breaking existing integrations.

The Bigger Picture

Google's UCP continues to mature through small, deliberate improvements. The currency field joins recent additions like:

Ancillaries Extension for add-ons and upgrades
Payment instrument qualifiers for BNPL and installments
Status discriminators for semantic error handling

Each addition makes agentic commerce more robust for real-world scenarios. Multi-currency is one of those scenarios — inevitable when AI agents start shopping across borders on behalf of users.

Author Context

Daniel Einck (deinck6) has been contributing to UCP's schema work, focusing on practical improvements that address implementation friction. The co-authorship with Ilya Grigorik signals this aligns with the protocol's strategic direction.