E-commerce
July 1, 2026
A private catalog can be useful for professional clients, resellers, members, internal teams, or confidential offers. But it also raises questions: why are some products not visible, how can one gain access, and are the displayed prices indeed reserved for the logged-in account?
The chatbot must verify the identity of the path without exposing sensitive information. It explains the conditions of access, helps the customer log into the correct account, and transfers requests for authorization or special pricing.
This guide shows how to support a private catalog with an AI chatbot, without creating confusion between the public catalog and the reserved area.
Summary
Why must a private catalog be well-defined?
The customer may think a product has disappeared when it is simply not visible with their access level. Conversely, a reserved price must not be displayed to someone who is not entitled to it.
The chatbot must therefore explain that visibility sometimes depends on the account, role, market, contract, or invitation received.
A private catalog is only reassuring if the customer understands why they see certain products and not others.
Convert over 2,000 customers on average per month with Qstomy.
The world’s 1st Shopify AI dedicated to customer conversion
Empowering 200+ e-commerce merchants
What information should be checked?
The bot must verify if the customer is logged in, with which account, which role is associated, which invitation was received, which market or country is concerned, and which product or rate is being searched.
It must avoid revealing information about other customers' access or unauthorized rates. The response must remain focused on the user's account.
How to explain an access denied?
Denied access may be due to an expired invitation, an unvalidated account, an incorrect email, an incomplete role, an inactive contract, or a catalog restricted to certain countries.
The chatbot must explain the confirmed cause if it is visible. If it cannot confirm it, it prepares an authorization request rather than concluding that the client is not eligible.
How to guide towards the right products?
Once access is verified, the bot can help filter products according to usage, volume, compatibility, budget, delivery times, or conditions reserved for the account.
It must remain cautious regarding contractual prices. If a discount, negotiated rate, or reserved stock depends on a contract, transferring to sales or support is preferable.
How to manage an invitation or a private link?
The customer may receive a link to a private catalog and not understand why it no longer works. The chatbot can check if the link is expired, already used, linked to a specific email, or incompatible with the logged-in account.
It can also advise logging in with the guest address. If the invitation needs to be reissued, it must be transferred with the context.
Which flow to follow?
The flow must verify access before talking about products or prices.
Identify the catalog, account, email, and searched product.
Verify connection, role, invitation, country, and authorization status.
Explain what is visible, limited, or pending validation.
Guide to accessible products or request authorization.
Forward denied accesses, private prices, contracts, and invitations to be reissued.
Which messages should be used?
To set expectations: "This catalog may depend on the connected account and associated permissions."
For an invisible product: "I am checking if this product is available in your space or if it requires specific access."
For an invitation: "Try logging in with the email that received the invitation. If the link has expired, I can forward the request."
When to transfer?
The transfer is necessary if the client requests access, a private rate, account validation, a renewed invitation, a quote, or visibility on reserved products.
The bot must transmit the account, email, catalog, searched product, error message, received invitation, and exact request.
Which KPIs should be monitored?
Track denied access, expired invitations, products not found, private price requests, account validations, and conversions after access is granted.
This data shows whether the private catalog is understood or if it generates too much friction before purchase.
Which mistakes should be avoided?
Avoid displaying restricted information, promising access, revealing pricing for another segment, or treating a private catalog as a simple search issue.
The chatbot should help without weakening the access rules.
How can Qstomy help?
Qstomy can connect the chatbot to the catalog, customer accounts, product sheets, manuals, orders, and support rules to answer clearly, then transfer sensitive cases with an actionable summary.
The chatbot helps the customer move forward without inventing compatibility, troubleshooting steps, or visual rendering that still needs to be confirmed by a reliable source.
Explore AI support, the AI sales agent, or request a demo.
Key takeaways
Key takeaways
A private catalog must be guided by account, role, invitation, and visible permissions.
What the client must understand
The client must understand why certain products or prices are only visible with the correct access rights.
The proper boundary for the chatbot
The chatbot can verify and guide, but it must hand over access, contracts, and private prices.
Enzo
July 1, 2026
