E-commerce
July 1, 2026
"The bot promises distributor access without verifying my account." "The AI cites a product that I don't see in the pro login." "Chatbot confuses 404 catalog and pricing error." Three failures where a miscalibrated private catalog bot invents access or B2BSEG route.
A private e-commerce catalog AI chatbot does not replace PRIVCAT agents (#811). It reads PRIVCAT-MAP, verifies Shopify B2B API company catalog, cites access_rule_copy catalog_id_copy, and hands off to sales without promising invented access.
This guide #812 covers bot_privcat_* intents, PRIVCATbot flow, and privcat_bot KPIs. Bot companion to the PRIVCAT playbook (#811). B2B AI use case: verify tier 1 catalog access.
Summary
Why automate private catalog access by bot?
"Distributor Catalog", "product not found", and "restricted range" issues are coming to the B2B portal PDP widget. A calibrated bot looks up PRIVCAT-MAP, verifies catalog assigned API, and cites SKU access without opening rights outside the map.
What the tier 1 private catalog bot resolves
Login required: login_required_copy ACCESS-CITE-BOT map
Catalog assigned: catalog_id_copy company API map
SKU visibility: sku_visibility_copy CATALOG-VERIFY-BOT map
Product guide: catalog-assigned links alternatives map
Commercial handoff: #811 payload company SKU access request
B2B distributors expect self-service on restricted catalogs (Shopify, B2B Catalogs 2026). Without a grounded bot, AI will mistakenly promise access or route segment prices incorrectly.
PRIVCATbot vs PRIVCAT #811, B2BSEGbot #810, country visibility, B2B lead and anti-hallucination #123
Six contents, six distinct catalog pathways.
Quick Matrix
#812 PRIVCATbot: tier 1 bot verify access guide private catalog products
#811 PRIVCAT: agents escalate commercial catalog assign
B2BSEGbot #810: distinct segment price invisible product
Country Visibility #814: distinct local market bot B2B account
Anti-hallucination #123: catalog access = whitelist only API map
Pipeline: #812 bot verify tier 1 access → #811 agents escalate commercial catalog assign.
Which bot_privcat_* intents should look for configuration?
Eight private catalog bot intents mapped to privcat_* typologies #811.
Eight bot_privcat intents
bot_privcat_login: login_required_copy portal URL map
bot_privcat_no_access: catalog_id missing ACCESS-CITE-BOT map
bot_privcat_pending: pending_account_copy status validation map
bot_privcat_location: company_location_copy catalog site map
bot_privcat_sku: sku_visibility_copy CATALOG-VERIFY-BOT API
bot_privcat_request: request_access_copy form map
bot_privcat_guide: assigned catalog product links alternatives map
bot_privcat_handoff: lost_access → PRIVCAT811-HANDOFF-BOT
Tier 1 auto: login no_access sku guide if PRIVCAT-MAP + ACCOUNT-API-GROUNDED-BOT.
Product visible wrong price → B2BSEG810-REROUTE-BOT distinct access.
How do I consume PRIVCAT-MAP #811?
The bot reads PRIVCAT-MAP #811: privcat_program_id, catalog_id_copy, access_rule_copy, login_required_copy, company_location_copy, eligible_accounts_copy, sku_visibility_copy, request_access_copy, b2bseg809_reroute_copy.
Lookup grounded PDP portal embed
ACCESS-CITE-BOT: access_rule_copy catalog_id_copy cite map verbatim
ACCOUNT-API-GROUNDED-BOT: company catalog assigned login Shopify B2B API only
CATALOG-VERIFY-BOT: SKU in assigned catalog products API compare
NO-ACCESS-PROMISE-BOT: access outside eligible_accounts_copy forbidden map
B2BSEG810-REROUTE-BOT: visible price → #810 distinct access
COUNTRY814-REROUTE-BOT: country hidden → #814 distinct B2B account
PRIVCAT811-HANDOFF-BOT: lost_access request escalate → #811 agents PC-7
Alignment anti-hallucination (#123): catalog access = PRIVCAT-MAP + company API whitelist only.
PRIVCATBOT-SUP policy in six rules
Six bot rules for private catalog PDP portal manager.
PRIVCAT-MAP-GROUNDED-BOT: response access from map only
ACCESS-CITE-BOT: access_rule catalog_id cite map
ACCOUNT-API-GROUNDED-BOT: company catalog before explaining visibility
CATALOG-VERIFY-BOT: SKU in catalog API before citing product
NO-ACCESS-PROMISE-BOT: do not promise access outside of eligible_accounts map
NO-GRANT-BOT: bot does not assign catalog or grant map access rights
Flow PRIVCATbot PCB-1 to PCB-8
Eight-step PDP portal embed private catalog bot flow.
PCB-1 Classify: bot_privcat_* intent detect keyword distributor private catalog product not found 404
PCB-2 Account collect: company_email session SKU product_url minimal
PCB-3 PRIVCAT-MAP: catalog access login eligible sku request b2bseg country handoff
PCB-4 Account verify: company catalog assigned CATALOG-VERIFY-BOT SKU API
PCB-5 Guardrail: ACCESS-CITE ACCOUNT-API CATALOG-VERIFY NO-PROMISE NO-GRANT B2BSEG COUNTRY HANDOFF
PCB-6 Respond: TPL-PRIVCATbot grounded access guide max 3 sentences
PCB-7 Handoff or close: request access #811 payload or close client understands access
PCB-8 Log: intent privcat_program_id tag privcat_bot access_cited handoff Y/N
TPL-PRIVCATbot-SKU Example
“Reference [SKU]: [sku_visibility_copy map.] Assigned catalog [catalog_id_copy API]. Status: [in / out of catalog verify API]. [If out: alternatives bot_privcat_guide map.] ACCESS-CITE-BOT.”
TPL-PRIVCATbot and touchpoints templates
Four short B2B portal PDP embed templates.
TPL-PRIVCATbot-LOGIN
[login_required_copy map.] Log in: [portal URL]. Catalog: [catalog_id_copy map.] ACCESS-CITE-BOT.
TPL-PRIVCATbot-NO-ACCESS
Account [company_name API]: catalog [assigned / none map]. [access_rule_copy map.] [request_access_copy map.] ACCESS-CITE-BOT.
TPL-PRIVCATbot-SKU
[SKU]: [sku_visibility_copy map.] Catalog [catalog_id_copy]. Verify API: [in_catalog Y/N]. CATALOG-VERIFY-BOT.
TPL-PRIVCATbot-GUIDE
Catalog [catalog_id_copy]: [alternative product links map.] Portal collection: [catalog_url map.] bot_privcat_guide.
B2B portal PDP touchpoints
Distributor catalog keyword: bot_privcat_login bot_privcat_no_access instant
Proactive 404 PDP: bot_privcat_sku bot_privcat_login trigger
Restricted range guest: bot_privcat_login proactive embed
Keyword access request: bot_privcat_request request_access_copy map
No embed catalog assign: PRIVCAT811-HANDOFF-BOT agents #811 only.
Edge cases and reroutes
Five cases outside tier 1 bot private standard catalog.
Visible price found product: B2BSEG810-REROUTE-BOT distinct segment access
Hidden by country: COUNTRY814-REROUTE-BOT distinct local market B2B
Prospect no account: lead qualification distinct catalog access
Wholesale MOQ: #144 bulk distinct catalog rights
Access removed post-order: PRIVCAT811-HANDOFF-BOT agents #811 commercial policy
Tier 1 access rule ACCESS-CITE. Assign catalog → handoff #811 NO-GRANT-BOT.
Essential privcat_bot KPIs
Five PRIVCATbot management metrics.
privcat_bot_access_resolve: access included post-bot without agent login redirect
privcat_bot_access_cite_rate: ACCESS-CITE-BOT / bot_privcat login no_access sku
privcat_bot_access_promise_violations: promised access outside map audit target 0
privcat_bot_misroute_rate: wrongly routed to b2bseg country / total
privcat_bot_handoff_rate: escalate #811 / total privcat bot
Target: privcat_bot_access_resolve greater than 40% and privcat_bot_access_promise_violations 0.
PRIVCATbot anti-patterns
Five common mistakes bot private catalog portal.
Promising chat access: NO-ACCESS-PROMISE-BOT eligible_accounts_copy only
Citing SKU without catalog API: CATALOG-VERIFY-BOT in_catalog mandatory
Assigning catalog bot: NO-GRANT-BOT handoff #811 agents only
Direct price route: B2BSEG810-REROUTE verify product visible access OK
Treating 404 as a bug: bot_privcat_sku sku_visibility_copy pedagogy
PRIVCATbot with Qstomy
Qstomy on Shopify: detect bot_privcat intent portal PDP, PRIVCAT-MAP RAG grounded, company catalog API lookup, ACCESS-CITE guardrail, handoff #811 tier 2.
Pipeline: #812 bot verify access tier 1 → #811 agents escalate commercial catalog assign.
Explore AI support and request a demo.
Checklist, FAQ and going further
PRIVCATbot Checklist (8 steps)
Sync PRIVCAT-MAP #811: RAG bot PDP portal private catalog embed
Policy PRIVCATBOT-SUP: 6 rules ACCESS-CITE ACCOUNT-API CATALOG-VERIFY NO-PROMISE NO-GRANT
8 intents bot_privcat_*: flow PCB-1 to PCB-8
4 templates TPL-PRIVCATbot-*: LOGIN NO-ACCESS SKU GUIDE
Shopify B2B catalog API sync: company catalog products SKU test guest vs pro
Red team 10 prompts: access promised outside map without catalog lookup grant bot
404 PDP proactive: bot_privcat_sku trigger product_url hidden
Dashboard KPI: privcat_bot_* section 9 access_resolve promise_violations handoff
FAQ
Difference #811?
#811 = agents escalate commercial catalog assign. #812 = bot tier 1 verify access guide products.
Bot opens distributor access?
No. NO-GRANT-BOT. PRIVCAT811-HANDOFF-BOT agents #811 only.
Difference B2BSEGbot #810?
#810 = segmented price product visible. #812 = invisible product catalog access.
Product 404 Google?
bot_privcat_sku CATALOG-VERIFY-BOT. Often private catalog or country #814.
Going further
This week: deploy PRIVCAT-MAP RAG portal embed, red team access_promise_violations audit, sync bot_privcat_sku proactive scenario distributor SKU out of catalog test.
Enzo
July 1, 2026
