Shopify B2B / Plus company catalog prices or products not showing for logged-in buyers — catalogs, company location, payment terms.

Several products can look like “my wholesale buyer cannot see the right price.” They do not share a settings panel. This page is only when a logged-in B2B / company buyer never sees catalog prices or products — blank PDP, retail price when they expected catalog, or SKUs missing from the storefront while staff see them. Wholesale / company order confirmation or invoice email silence is wholesale order email not sending. Wrong currency or country price for a Markets shopper is Markets currency wrong. English fallback / missing translated strings is Translate & Adapt missing strings. Blank product metafields on a DTC PDP is product metafields not showing. This page is only: B2B / Plus company catalog prices or products not showing for logged-in buyers.

Six ordinary reasons catalogs stay blank: no catalog assigned to the company location the buyer belongs to, products never added to that catalog, products in the catalog but not published to Online Store, payment terms / location assignment mismatch, buyer logged into a retail customer account (or the wrong company contact), or you are debugging wholesale email / Markets currency / translate / metafields instead. Walk them in that order. You already pay for Shopify Plus B2B. You do not need another seat to assign a catalog and publish a product.

Customers → Companies → open the company the buyer claims. Locations: note which location the contact sits on and which catalog is assigned to that location. Contacts: confirm the exact email / login the buyer uses. Catalogs (or Products → Catalogs, depending on admin): open that catalog and confirm it is the one wired to the location. Then open an Incognito window, log in as that company contact, and hard-refresh the product URL.

Honest proof: if the location has no catalog, the contact is on a different location, or the buyer is not logged in as that contact, stay on this page. If order confirmation / draft invoice / B2B email never sends after a wholesale order, leave for wholesale order email not sending. If a country shopper sees the wrong currency without a company login, leave for Markets currency wrong. Do not mix those proofs.

Assigning a catalog to a company location does not auto-include every SKU. Products must be added to the catalog (or covered by the catalog’s inclusion rules) with the B2B price / quantity rules you expect. Separately: a product that is draft, not published to the Online Store sales channel, or only live on a wholesale channel while the B2B storefront reads Online Store will stay invisible to the logged-in buyer even when staff see it in admin.

Fix: open the catalog assigned to the company location → confirm the SKU is included with a non-empty catalog price. Open the product → Publishing / Sales channels → Online Store on. Status Active. Retest logged-in as the company contact. If the only blank is a custom metafield on a DTC PDP (not B2B pricing), leave for product metafields not showing.

B2B checkout and storefront eligibility often follow the company location’s payment terms, shipping address, and catalog together. A contact on Location A with Catalog X while payment terms only live on Location B can produce retail prices, missing add-to-cart, or an empty catalog experience. Staff preview without the company session will also look “fine” while the buyer does not.

Fix: Companies → location → confirm payment terms, catalog, and shipping / billing on the same location the contact uses. Have the buyer log out, clear cookies, log in as that contact, and open the marketed product URL again. If Markets currency for a country shopper is wrong without any company login, leave for Markets currency wrong.

Retail customer accounts and company contacts are different identities. A buyer who creates a storefront account with the same email but never accepts the company invite (or logs into a personal account on a shared device) will see retail / Online Store pricing — or no catalog SKUs — while staff swear the catalog is assigned. Multiple locations with different catalogs make the wrong contact look like “catalog broken.”

Fix: Companies → contact → confirm invite accepted and the contact is on the intended location. Buyer: log out fully, use the company login / invite path, confirm the account menu shows the company name, then retest. If language strings fall back to English on a Markets locale (not pricing), leave for Translate & Adapt missing strings.

Wholesale / B2B order confirmation or invoice email silence is wholesale order email not sending. Markets currency / country price wrong for a shopper (no company session) is Markets currency wrong. Missing translated strings / English fallback is Translate & Adapt missing strings. Product metafields / custom fields blank on the PDP is product metafields not showing.

The only honest test for this page: a logged-in company buyer cannot see catalog prices or products they should — prove location + catalog assignment, prove products in catalog + Online Store published, prove payment terms on that location, prove the login is the company contact, hard-refresh. Anything else is a different product.

Stay DIY if you can spend one afternoon on the list above: prove the company location’s catalog, add / publish products into that catalog for Online Store, align payment terms with the contact’s location, and stop confusing wholesale email / Markets currency / translate / metafields with a blank B2B catalog. That is the whole playbook. No agency required. Short answers also live on the merchant FAQ. Related pages: wholesale order email not sending, Markets currency wrong, Translate & Adapt missing strings, product metafields not showing.

Pay for help when the work is not the catalog assignment row — it is connecting the stack you already have so lead capture is not dying in DMs, storefront and checkout-ready exceptions land in a channel you already check, and the live store is one workflow instead of a spreadsheet plus a Slack bot you forgot. That is the Latch AI Ops install.

What $997 USD one-time buys: lead capture on the live store, ops alerts in a channel you already check, and a checkout-ready workflow. 72 hours after collaborator access, not after payment. One live Shopify store. Access plus a delivery thread. Store URL collected at checkout. Not a SaaS seat, not a theme rebuild retainer, not a conversion guarantee, not a brand or theme job.

Other shops’ public ranges, not testimonials: a checkout / ops install typically runs $500–$2,500. A full ops consulting block typically runs $2,000–$5,000. $997 is the cheap end of that work, sold as a 72-hour install of three systems — not as an earnings number or conversion-lift claim.

What it does not buy: more orders, recovered revenue, a forever B2B-catalog-proof theme guarantee, or a case study. Latch AI Ops has not published customer proof because there are no customers yet. You are buying the install.

Checkout is on Whop. Operator is Nico. United States offer. You can revoke collaborator access after handoff. We do not take owner passwords.