E-commerce

How to handle customer questions about private catalogs

How to handle customer questions about private catalogs

July 1, 2026

"The product exists on Google but 404 page on your site." "My pro account does not see the range reserved for distributors." "Expired partner link, no more catalog access." Three tickets where a poorly explained private catalog blocks an order or generates sales escalation.

The e-commerce private catalog support covers account access, SKU visibility rights and restricted Shopify B2B catalogs. Distinct from pricing segmentation (#809): here, product is invisible or inaccessible, not a wrong price displayed.

This guide #811 covers policy PRIVCAT-SUP, flow PC-1 to PC-8 and matrix PRIVCAT-MAP. Future support pair PRIVCAT bot (#812).

Summary

Why do private catalogs generate tickets?

Marketing shares partner link. Shopify B2B restricts catalog by company. The buyer browses as a guest, via an account without permissions, or via a direct URL to a hidden SKU: the agent promises access without verifying the assigned catalog_id.

Five typical private catalog frictions

  • Not logged in: guest does not see restricted range map

  • Account without permissions: pro verified but catalog not assigned map

  • Hidden SKU: product outside of assigned catalog map

  • Direct URL 404: Google link to private PDP map

  • Access request: wants distributor catalog map

Shopify B2B allows dedicated catalogs by company and location (Shopify, B2B catalogs 2026). Without PRIVCAT-MAP, agents confuse catalog access and segment pricing.

PRIVCAT #811 vs B2BSEG #809, B2B #50, wholesale, country visibility and bot #812

Six contents, six distinct catalog pathways.

Quick matrix

#811 = can I see this product. #809 = what price for this account.

Which privcat_* typologies should be classified?

Eight scenario tickets for private catalog access visibility.

Eight privcat typologies

  1. privcat_not_logged_in: guest expects restricted catalog map

  2. privcat_no_access: pro account with no assigned catalog map

  3. privcat_pending_account: validation pending, no access yet map

  4. privcat_wrong_location: wrong site purchasing catalog map

  5. privcat_sku_hidden: SKU absent from assigned catalog map

  6. privcat_url_404: direct link hidden PDP map

  7. privcat_access_request: request to open catalog map

  8. privcat_lost_access: access removed post order map

Tags: privcat, private_catalog, catalog_access, sku_visibility. ACCESS-CITE: access_rule_copy catalog_id_copy map only.

How to structure the PRIVCAT-MAP matrix?

The PRIVCAT-MAP matrix documents catalog access rules for agents and the future bot #812.

PRIVCAT-MAP Columns

  • privcat_program_id: private catalog program identifier map

  • catalog_id_copy: restricted catalog identifier map

  • access_rule_copy: general catalog access rule map

  • login_required_copy: login required to see catalog map

  • company_location_copy: purchase site location catalog map

  • eligible_accounts_copy: eligible professional distributor profiles map

  • sku_visibility_copy: visible/hidden SKU rule map

  • request_access_copy: access request procedure map

  • b2bseg809_reroute_copy: visible price distinct access map

  • bot_intent_map: bot_privcat_* #812 mapping

Sync Shopify B2B catalogs admin by company. Post-onboarding distributor audit.

PRIVCAT-SUP Policy in six rules

Six rules support private catalog access visibility.

  1. PRIVCAT-MAP-GROUNDED: access response from map only

  2. ACCESS-CITE: access_rule_copy catalog_id_copy cite map

  3. ACCOUNT-VERIFY-FIRST: verify company catalog assigned before explaining

  4. NO-ACCESS-PROMISE: do not promise access outside of eligible_accounts map

  5. B2BSEG809-REROUTE: product visible wrong price → #809 distinct access

  6. COUNTRY813-REROUTE: hidden by country → #813 distinct B2B account

Flow PRIVCAT PC-1 to PC-8

Flow agent eight steps private catalog access visibility.

  1. PC-1 Intake : privcat_* intent + company_email SKU product_url order_ref

  2. PC-2 Account lookup : Shopify company catalog assigned login location verify

  3. PC-3 PRIVCAT-MAP : catalog access login eligible sku request b2bseg country handoff

  4. PC-4 SKU verify : admin catalog products list SKU in assigned catalog Y/N

  5. PC-5 Triage : ACCESS-CITE NO-ACCESS-PROMISE escalate commercial ops policy

  6. PC-6 Respond : macro PRIVCAT grounded access catalog map

  7. PC-7 Action : login redirect request access form escalate commercial catalog assign

  8. PC-8 Close : tag privcat_resolved access_cited catalog_fixed Y/N

SLA : privcat_not_logged_in answered ACCESS-CITE in 10 min B2B portal chat.

Essential PRIVCAT macros

Four macro private catalog agents.

PRIVCAT-LOGIN-01

"Catalog [catalog_id_copy map]: access after account login. [login_required_copy map.] Log in: [portal URL]. Eligible profiles: [eligible_accounts_copy map.] ACCESS-CITE."

PRIVCAT-NO-ACCESS-01

"Account [company_name]: assigned catalog [catalog_id / none map]. [access_rule_copy map.] [request_access_copy map.] ACCESS-CITE."

PRIVCAT-SKU-01

"Reference [SKU]: [sku_visibility_copy map.] Active catalog: [catalog_id_copy map.] Product [in / out of assigned catalog admin verify]. ACCESS-CITE."

PRIVCAT-REQUEST-01

"Catalog access request [catalog_id_copy map]: [request_access_copy map.] Processing time: [sla map.] Documents: [eligible_accounts_copy requirements map.] ACCESS-CITE."

Edge cases: wholesale, B2B lead, indexed SEO, and loss of access

Five cases outside the standard private catalog macro.

Access rule = ACCESS-CITE. Unit price = B2BSEG809-REROUTE.

Essential privacy KPIs

Five PRIVCAT steering metrics.

  • privcat_access_cite_rate: ACCESS-CITE / total privcat tickets

  • privcat_resolve_no_escalate: resolved login redirect without sales / total

  • privcat_access_promise_violations: promised access outside map audit target 0

  • privcat_misroute_rate: incorrectly routed b2bseg country / total

  • privcat_request_convert: access granted post-request / total privcat_access_request

Target: privcat_access_cite_rate 100% and privcat_access_promise_violations 0.

PRIVCAT anti-patterns

Five common private catalog support mistakes.

  1. Promising chat access: NO-ACCESS-PROMISE eligible_accounts_copy only

  2. Explaining without account lookup: ACCOUNT-VERIFY-FIRST catalog assigned admin

  3. Confusing access and price: B2BSEG809-REROUTE if product visible price wrong

  4. Treating 404 as bug: PRIVCAT-SKU-01 sku_visibility_copy explain policy

  5. Ignoring access request process: PRIVCAT-REQUEST-01 request_access_copy map

PRIVCAT with Qstomy

Qstomy on Shopify : detect privcat intent, company catalog lookup, PRIVCAT-MAP RAG grounded, ACCESS-CITE guardrail, handoff #812 bot tier 1.

Pipeline : #812 bot verify tier 1 access → #811 agents escalate commercial catalog assign.

Explore AI support and request a demo.

Checklist, FAQ and going further

PRIVCAT Checklist (8 steps)

  1. PRIVCAT-MAP v1: catalog access login eligible sku request b2bseg country

  2. PRIVCAT-SUP Policy: 6 rules ACCESS-CITE VERIFY NO-PROMISE B2BSEG COUNTRY

  3. 8 typologies privcat_*: tags helpdesk private_catalog catalog_access

  4. 4 macros PRIVCAT-*: LOGIN NO-ACCESS SKU REQUEST

  5. Sync Shopify B2B catalogs: admin products by catalog company test

  6. Agent training 30 min: ACCESS-CITE before promising commercial access

  7. Access request page: request_access_copy aligned with portal form

  8. KPI Dashboard: privcat_* section 9 access_cite promise_violations convert

FAQ

Difference B2BSEG #809?
#809 = wrong product price visible. #811 = product invisible or access denied.

404 page for known product?
PRIVCAT-SKU-01 sku_visibility_copy map. Often private catalog or country #813.

Pro account without product range?
PRIVCAT-NO-ACCESS-01 verify catalog assigned. PRIVCAT-REQUEST-01 if eligible.

Relation to #812 bot?
#812 = bot verify tier 1 access. #811 = agents escalate commercial catalog assign.

Going further

This week: index PRIVCAT-MAP catalogs by company, sync private_catalog tags, test macro PRIVCAT-SKU-01 distributor scenario for SKU outside assigned catalog.

Enzo

July 1, 2026

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

Subscribe to the newsletter and get a personalized e-book!

No-code solution, no technical knowledge required. AI trained on your e-shop and non-intrusive.

*Unsubscribe at any time. We do not send spam.

Subscribe to the newsletter and get a personalized e-book!

No-code solution, no technical knowledge required. AI trained on your e-shop and non-intrusive.

*Unsubscribe at any time. We do not send spam.