Context-aware pricing

Context-aware pricing lets Conversational agent show each shopper the prices that apply to them, such as a member price, a trade price, or a regional price. The shopper sees these prices on product cards, in the mini product detail page (PDP), and in the agent's replies.

Benefits of context-aware pricing

Accurate prices and answers: Shoppers see the price set for their group on product cards and in the mini PDP, and the agent quotes the same price and can explain why it applies.
Visible member savings: You can show a member or trade price next to the regular price, so eligible shoppers see what they save.

How it works

By default, Conversational agent shows the same catalog price to every shopper. With context-aware pricing, your website identifies the shopper's status before Conversational agent starts, for example, whether the shopper is logged in, is a member, or is in a certain region. That status determines which prices apply, and Conversational agent follows.

The feature supports two patterns:

One price per shopper: Each shopper sees the single price for their group, for example, trade or non-trade pricing, or regional pricing.
Several prices side by side: A shopper sees more than one price, for example, a member price next to the regular price.

For each shopper message:

Your website sends the prices that apply to the shopper and marks one as primary. It can also send a short shopper note, such as the shopper's member tier.
Conversational agent requests only the prices your website sent from your catalog. The agent and product cards work with those prices.
Conversational agent finds products and writes the reply based on those prices and the shopper note. Price filters and sorting, such as "under 100," use the primary price.
Conversational agent shows the shopper's prices on product cards, in the mini PDP, and in the chat.

For example, a member might get the member price as the primary price, plus the regular price for comparison. A non-member gets only the regular price.

How prices appear

Mini PDP: Each price appears in its own block with its label above it. Up to two prices sit side by side.
Product cards: A single price uses the regular price layout. When two prices apply, the card shows them as a range, from the lower to the higher price.
Reference prices: You can show a price struck through, for example, the regular price next to a member price. The struck-through price shows only when it's higher than the price it's linked to.

Fallback behavior

If your website sends no prices for a shopper, Conversational agent shows the regular catalog price. If your catalog has no regular price, no price appears.
If a product has no value for one of the shopper's prices, that price doesn't appear for that product. It doesn't fall back to the regular price unless a fallback is set up for that price field.
If your website sends a price name that isn't configured, or a new price field before the next catalog sync, Conversational agent skips it and logs a warning. The chat keeps working.
If the shopper's status changes during a chat, for example, they log out, the next message uses the new prices. Product cards shown earlier keep their original prices.
If you hide prices, the setting also hides all context-aware prices.

Data the agent uses

The agent receives only the current shopper's prices and the shopper note your website sends, and uses them to pick products and write its reply. The shopper note is part of the conversation, so limit it to pricing context such as member tier or region. Don't include personal data such as names, email addresses, or exact locations.

Known limitations

Catalog prices only: Contract prices that come from an API aren't supported. Use a custom product card instead.
Search catalogs: Each price group must be its own field. View-based pricing, where one view returns one price, isn't supported yet.
Number of prices: Up to four prices per message. Product cards and the mini PDP show at most two.
Discount percentage: The discount percentage badge doesn't appear in the mini PDP when context-aware prices are shown, or on a product card that shows two prices as a range.
New price fields: A new price field works only after the next catalog sync finishes. Until then, Conversational agent skips that price if your website sends it.

Learn how prices appear in the Conversational agent mini PDP.
Prepare price attributes in your product catalog data.
Adjust the look of prices when you customize the chat widget.
Use shopper data to personalize conversation.