Shopify Gated Product Access: B2B Compliance in 2026

Key Takeaways

• Shopify's native B2B controls are strong when your access rules map cleanly to companies, company locations, and catalogs. That is the best place to start before adding theme logic or app-layer restrictions.
• Customer accounts are not optional for real B2B gating. Shopify's B2B documentation says customers must sign in with customer accounts and be attached to a company location before they can access B2B-specific pricing, products, or ordering.
• Catalog design is a compliance decision, not just a merchandising task. Shopify says Basic, Grow, and Advanced plans can use up to three active catalogs across all B2B markets, while Shopify Plus offers unlimited catalogs and direct company or location assignment.
• Approval workflow matters as much as store gating. Shopify says company account requests can automatically create the company, company location, and customer record on submission.
• Wholesale application intake still needs the right app layer. Shopify's company account request workflow depends on the Shopify Forms app.
• A fully locked B2B store creates a tradeoff. Shopify documents that when a store is restricted to B2B customers only, public company account request forms are no longer available to non-logged-in prospects.
• Maintenance is where gated setups usually fail. Your team needs testing for theme updates, catalog changes, approval exceptions, and audit ownership, not just initial configuration.

Prerequisites

Before you change storefront visibility, make sure your team has the basics in place:

• a clear decision on whether you are running a dedicated B2B store or a blended B2B plus D2C storefront
• Shopify B2B enabled in admin and the right internal roles assigned
• customer accounts turned on for the store
• defined company and company-location structure for wholesale buyers
• a catalog strategy for which buyers should see which products and prices
• a compliance checklist for tax exemptions, reseller permits, buyer approval, and record retention
• ownership for theme testing, app governance, and exception handling

If those decisions are still fuzzy, pause before you build. A storefront can look gated on the surface and still fail operationally if approvals, tax handling, and catalog ownership are not clearly assigned. Shopify's B2B requirements and considerations also note that feature availability still varies by plan, which is another reason to confirm scope before building around assumptions. Teams that need a broader architecture review often start with What is Shopify? to align stakeholders on what the platform does natively before they add custom logic. That upfront planning is what keeps Shopify gated product access maintainable after launch.

Step-by-Step Instructions

Shopify gated product access works best when you treat it as an identity, catalog, and governance project, not just a product-hiding task. Use the sequence below to keep your storefront stable while protecting pricing, restricted products, and compliance requirements.

Step 1: Define the access model before you change the storefront

Start by deciding whether you need a dedicated B2B store or a blended storefront with public discovery and gated buyer access.

• Choose a dedicated B2B store when only approved wholesale buyers should see products and pricing at all.
• Choose a blended storefront when prospects need to browse public content first and apply before they receive buyer access.
• Document which products, prices, files, and ordering paths must stay private.

This is the business-outcome step most teams skip. If your team does not agree on the access model first, you usually end up with rework, leaked pricing, and manual exception handling later.

Step 2: Turn on customer accounts and build the company structure

In Shopify admin, enable customer accounts first. Shopify's B2B customer account documentation says B2B customers must sign in with customer accounts and be attached to at least one company location before they can access B2B-specific pricing, products, and checkout behavior.

Then create the company structure your team will manage:

1. create the company record
2. create each company location
3. assign buyer contacts to the correct location
4. confirm location-level settings for catalogs, tax treatment, and payment terms

If your business also depends on ERP synchronization, keep the company and location model aligned with the records your finance and operations teams already maintain in NetSuite Integrations.

Step 3: Build catalogs around business rules, not one-off requests

Catalogs are the core control layer for Shopify gated product access. Shopify's catalog documentation says Basic, Grow, and Advanced plans can assign up to three active catalogs across all B2B markets, while Shopify Plus supports unlimited catalogs and direct assignment to companies and company locations.

Use catalogs to answer three questions:

1. which buyers can see this product
2. which buyers can see this price
3. who owns future changes to this entitlement rule

For most teams, the cleanest pattern is:

• one baseline wholesale catalog for broad approved access
• additional catalogs only when a true business rule changes by buyer type, geography, or regulated SKU set
• a named owner for every catalog so product inclusion and pricing changes do not drift

If multiple catalogs can overlap, test pricing carefully. Shopify says the storefront shows the lowest available price when multiple catalogs apply, so your commercial rules need to account for that.

Step 4: Separate application, review, and activation

Do not let storefront registration act as final approval. Use a three-stage workflow instead:

1. Application: collect company details, buyer contacts, tax ID, and resale or permit information.
2. Review: validate documents and confirm the right company location, catalog, and tax treatment.
3. Activation: assign the catalog and enable ordering only after internal approval is complete.

If you need inbound applications, Shopify's company account request documentation says the workflow requires the Shopify Forms app and can automatically create the company, company location, and customer record. That automation is useful, but it should not replace review. Your team still needs a clear approval gate before restricted products or pricing become visible.

This is also the point where system ownership matters. Decide whether Shopify or NetSuite is the source of truth for tax-exempt status, buyer class, payment terms, and audit history. Anchor Group's certified NetSuite consultants usually formalize that ownership before automation expands into SuiteAnalytics reporting, SuitePeople approvals, or broader managed services workflows.

Step 5: Add theme or app logic only for edge cases

Native Shopify B2B is usually enough when your rules map cleanly to companies, company locations, and catalogs. Add theme logic or a low-code app only when you need conditions that native catalogs do not cover well, such as:

• hiding specific landing pages or files outside the catalog model
• changing navigation by buyer state
• handling unusual direct-URL or merchandising edge cases

Treat those controls as exceptions, not your default architecture. The more access logic your team pushes into the theme or a third-party app, the more QA you will need after every product launch, theme change, and app update.

Step 6: Test the full buyer journey before launch

Before launch, test three user states from start to finish:

1. public visitor
2. unapproved applicant
3. approved buyer

For each state, confirm:

• product visibility
• price visibility
• account messaging
• catalog assignment
• checkout access
• tax and compliance status handling

If your team supports both commerce and ERP operations, run the same checks against the downstream records that feed fulfillment, billing, and reporting. That is the kind of operational review Anchor Group typically includes in Shopify Implementation planning so your business gets cleaner launches, fewer manual corrections, and faster time-to-value.

Common Mistakes to Avoid

Most gated Shopify failures come from governance gaps, not from the absence of one specific feature.

Watch for these issues first:

1. Public application path conflicts with full-store lockdown.
2. Too many catalogs for the plan limit.
3. Approval rules that grant access before compliance review.
4. Theme changes that break hidden content or buyer messaging.
5. ERP and Shopify disagreeing on tax or buyer status.
6. No owner for catalog edits and exception requests.
7. Testing only login, not product, price, and checkout behavior.

That list is the real maintenance checklist behind Shopify gated product access. A store can look correct in a demo and still fail when a new buyer type, product family, or theme release enters the picture.

Advanced Tips

Use these practices if your base setup is already stable and your team wants fewer manual exceptions over time:

• tie every catalog to a named business rule and owner
• keep compliance review status separate from storefront registration status
• test buyer experiences by company location, not just by customer email
• review Flow automations after every approval-rule change
• include theme-release regression testing in your release checklist
• maintain an audit note for unusual entitlement exceptions

If your team is also managing downstream ERP workflows, review those controls as part of a regular NetSuite Optimization cadence so entitlement changes, pricing exceptions, and operational workflows stay aligned.

Shopify gated product access checklist

Use this checklist before launch and after every major storefront change:

Run the checklist with a public visitor, an approved buyer, and an unapproved applicant. In 2026, that simple discipline catches more gating mistakes than most one-time implementation reviews.

Next steps for Shopify gated product access
Your best setup for Shopify gated product access depends on your business model. A dedicated B2B store is strongest when discovery should be private. A blended storefront is stronger when prospects need to apply before you approve them. Native catalogs usually win when access rules follow companies and locations. Additional app or custom logic only earns its keep when your storefront conditions are more complex than that model allows.

If your team needs help connecting Shopify B2B access rules to approvals, catalog governance, ERP synchronization, and long-term ERP optimization, Anchor Group is a premier NetSuite consulting and development firm specializing in ERP implementations, integrations, and SuiteCommerce. As a NetSuite implementation partner, Anchor Group supports manufacturers, wholesale distribution teams, retailers, and renewables companies that need their Shopify workflow to stay aligned with NetSuite Services, SuiteCommerce storefront strategy, and long-term managed services ownership.

Frequently Asked Questions

How to lock down a Shopify B2B store?

Restricting the whole store to B2B customers works best when you run a dedicated wholesale storefront and do not need a public application path. Shopify says a dedicated B2B store can be restricted so only logged-in B2B customers can access it, though that approach also blocks public company account request access.

Can Shopify hide products by customer?

Yes, Shopify can restrict products, pricing, and ordering paths for approved B2B buyers through catalogs tied to companies and company locations. That works best when the rule is account-based rather than a one-off storefront condition.

Can public visitors see products before login?

Yes, a blended Shopify storefront can keep public product discovery visible while reserving buyer-specific pricing and restricted catalogs for approved logged-in accounts. The key is clean customer-account and company-location setup.

How to collect reseller documents first?

Use company account requests to capture the applicant, then review tax, buyer, and entitlement details before enabling ordering or assigning the right catalog. Shopify says account requests can create the company, company location, and customer automatically, which makes the review step easier to standardize.

What if you outgrow Shopify catalog limits?

If your segmentation outgrows three active catalogs, Shopify Plus becomes the cleaner path because lower-tier plans cap B2B catalog scale. Shopify says Basic, Grow, and Advanced plans can assign up to three active catalogs across all B2B markets, while Shopify Plus supports unlimited catalogs and direct assignment to companies and locations.

How to hide products from non-logged-in users?

Hide Shopify products from public users by tying visibility to logged-in customer accounts, company assignment, and the correct B2B catalog. That works better than relying on theme-only hiding because the access rule stays tied to account and catalog logic instead of a visual storefront workaround.

What should you test after a theme update?

Test product visibility, price visibility, account messaging, and checkout behavior for a public visitor, an approved buyer, and an unapproved applicant. Most gating failures happen after a seemingly unrelated storefront change, so regression testing across those roles is more useful than checking login alone.

What if multiple B2B catalogs apply?

When multiple Shopify B2B catalogs apply, the storefront shows the lowest available price, so your team must test overlap carefully. Pricing behavior still needs to match the commercial rules you intended.

Disclaimer: This content is for general informational purposes only and may not reflect current updates or your specific configuration—please confirm details with your Anchor Group consultant.