Configure project settings

Ask about this Page
Copy for LLM
View as Markdown

Configure your Project environment within the Merchant Center to support US-based agentic commerce.

Do not add AgenticLift configuration to an existing production Project. Use a dedicated, isolated Project to avoid Channel, Store, and Product Type conflicts.

Project settings

Set the following values in Merchant Center > Settings > Project settings:
SettingRequired valueNotes
CurrencyUSDISO 4217 code. Required for US launch.
CountryUSISO 3166 alpha-2. Governs tax and shipping configuration.
Languageen-USIETF language tag. All Product Attributes must have at least one localized value.
ZonesDefine a US shipping zoneGroup states or regions as needed for Shipping Method configuration.
Tax CategoriesMinimum of one US Tax CategoryRequired for Agentic Checkout to function.

Channels

AgenticLift uses a distribution Channel (pricing) and a supply Channel (inventory) assigned to the Store. If you are adding AgenticLift to an existing Project (for example, launching a new region or brand), you can reuse existing Channels whose prices and inventory are appropriate for the agentic channel. For new Projects, create dedicated Channels as part of Project setup. If no Channels are configured, fallback global prices and inventory are used.

Common reasons to create dedicated AgenticLift Channels:

  • The agentic channel requires different pricing than other sales channels.
  • Inventory should be tracked or allocated separately.
  • You want to control the agentic product assortment independently.

Store setup

Create one dedicated Store per AI platform. Multiple Stores per platform feed are supported and recommended where country-specific behavior is needed, for example, separate Stores for ChatGPT US, ChatGPT France, and ChatGPT Japan.

Store Custom Fields

Each module requires specific Custom Fields on the Store. These carry merchant-level policy and URL information passed to the AI platform during product feed generation and checkout.

Fields required for all modules

FieldTypeDescription
storeUrlStringBase URL of the storefront, used for product deep links.

Fields for the OpenAI module

FieldTypeDescription
sellerTermsOfServiceUrlStringMerchant terms of service URL.
sellerPrivacyPolicyUrlStringPrivacy policy URL.
sellerShopPoliciesUrlStringShop policies URL.
returnPolicyUrlStringReturn policy URL.
returnWindowDaysNumberNumber of days in the return window.
sellerNameStringMerchant or brand name.
orderUrlStringOrder permalink URL for order confirmation.

Fields for the Google Gemini module

FieldTypeDescription
sellerTermsOfServiceUrlStringTerms of service URL.
sellerPrivacyPolicyUrlStringPrivacy policy URL.
sellerRefundPolicyUrlStringRefund policy URL.
sellerShippingPolicyUrlStringShipping policy URL.
sellerFaqUrlStringFAQ URL.
ucpCheckoutContinueUrlStringURL for checkout handoff and session recovery.
orderUrlStringOrder permalink URL appended with the Order ID.

Shipping Method Custom Fields

The OpenAI and Google Gemini modules use Custom Fields on Shipping Methods to communicate delivery estimates and carrier information to the AI platform.
FieldTypeDescription
earliestDeliveryInDaysNumberMinimum estimated transit time in days.
latestDeliveryInDaysNumberMaximum estimated transit time in days.
carrierStringShipping provider name (for example: FedEx, DHL).

Shipping Method Custom Fields are not required if you use external shipping methods. In that case, delivery estimates and carrier information are provided by the external shipping service.

Shipping Methods

Configure at least one Shipping Method with a US zone rate and assign it to the AgenticLift Store. Without a Shipping Method, Agentic Checkout sessions fail because the Universal Commerce Protocol (UCP) specifications both require fulfillment options in the checkout session response.

API Clients

API Clients for AgenticLift are automatically generated during Agentic Channel setup, with scopes restricted to what each integration requires. No manual API Client creation is needed.