Google described three travel planning and booking features in Search on August 27. AI Mode can track flight prices after user confirmation, including options using points or miles, and a hotel experience can continue from discovery into room selection and booking. Google also states that the participating provider remains the merchant of record and continues to handle the transaction and customer service. The travel category is specific, but the design lesson applies to B2B sites: when an AI interface compresses the journey, commercial responsibility needs to become more visible, not less.
Identify the responsible party at every step
A buyer can move across an AI answer, supplier page, payment service and fulfillment system during one task. Each state should identify who supplies the information, who receives money or a request, who issues the confirmation and who handles changes. A legal entity mentioned only in a footer is not enough for a consequential action.
In B2B purchasing, distinguish platform discovery, supplier information, a quotation and a binding agreement. An AI-generated comparison may support selection, but it is not a commercial commitment from a manufacturer. Before an inquiry, sample request or order moves forward, restate the supplier entity, currency, destination, applicable version and validity period.
Partner-operated steps need the same clarity. If logistics, payment or local service is provided by another company, describe the role before the buyer transfers information or confirms an action. The user should not discover the operating entity only after an exception occurs.
Produce a confirmation that systems and people can read
After a user acts, they need evidence that the system accepted the intended request. The confirmation should contain a durable ID, object, commercial or technical condition summary, timestamp, responsible provider and next step. If the action merely creates a request, label it as pending rather than presenting it as completed.
A buyer agent benefits from structured status fields, while procurement and finance need plain language. Provide both. A record can expose machine-readable identifiers and a concise human summary on the same page. When the request changes, retain the prior version, change reason and actor instead of overwriting the evidence.
Confirmation should also reveal missing steps. A sample request may be received but still require technical review or shipping information. Naming that state prevents the agent from reporting an outcome that the business has not accepted.
Put change and service paths next to the transaction
After a booking or B2B request, the next need is often a change, cancellation, supplementary document or service question. Place those paths on the confirmation page, notification and account view. The buyer should see the applicable time window, identity requirement and responsible provider.
Where several providers participate, state which issue belongs to the platform, supplier, payment service or logistics operator. An AI assistant can guide the user to the correct route, but it should not promise a refund, delivery date or contract change without authority from the responsible entity.
This responsibility map should survive channel changes. A buyer who moves from the site to email or messaging should retain the same request ID and status. Otherwise, every channel creates a separate version of the commercial truth.
Treat tracking consent separately from execution
Google says price tracking begins after confirmation. That distinction helps other businesses separate monitoring from action. A buyer may authorize alerts for price, availability or document updates without authorizing an order or change to existing conditions.
Every subscription should name the object, frequency, channel and method for stopping it. When a tracked condition changes, show the source and difference, then ask for a new decision. Do not extend an earlier approval to a different model, quantity, market or commercial state.
For long-running procurement work, authorization scope is more important than the number of reminders. A precise monitoring record helps an agent know what it may watch and where it must stop.
What this means for Chinese exporters
AI search is moving supplier websites closer to transaction support. Chinese exporters need a consistent responsibility model across product facts, quotation, payment, fulfillment and after-sales service before delegating more of the journey to agents.
The most practical starting point is the inquiry and sample flow. State what record each action creates, who receives it, when a person must confirm it and where the buyer goes if something is wrong. These facts increase buyer confidence and give AI systems a reliable next-step description.
Action checklist
- Display the responsible entity and service route at inquiry, payment, confirmation and after-sales states.
- Separate suggested, requested, pending, accepted and completed statuses.
- Generate a durable ID, object, version, timestamp and condition summary for every submission.
- Put change, cancellation, document and human-service links beside the confirmation.
- Obtain separate authorization for price or availability tracking and provide a clear stop control.
- Test entity names, statuses and service links across every platform handoff.
Sources
- Google, 3 new ways to plan and book travel in Search, August 27, 2026: https://blog.google/products-and-platforms/products/search/book-travel-ai-mode/

