Home | 6Street Digital

Why a Customer Portal Is the Next Logical Step If You're Already on Salesforce

Mon, 29 Jun 2026 00:00:00 +0000

Most companies that invest in Salesforce focus on what it does internally: managing pipeline, tracking service cases, automating workflows. That’s the right starting point. But there comes a point — usually when your support volume is growing and your customers are asking for more visibility — where the question shifts from how do we use Salesforce better to how do we give our customers access to what Salesforce knows.

That’s where a customer portal comes in. And if you’re already on Salesforce, you’re closer to having one than you probably realize.

What a customer portal actually is

A customer portal is a branded, self-service web experience where your customers can log in and interact directly with your business — viewing their account status, submitting support requests, tracking open cases, accessing invoices, downloading documents, or completing whatever transactional tasks matter in your industry.

Built on Salesforce Experience Cloud (formerly Community Cloud), it’s not a separate system bolted onto Salesforce. It is Salesforce — surfaced in a way your customers can access directly.

The case for building one if you’re already on Salesforce

1. Your data is already there

The biggest cost in building a customer-facing application is usually the data layer: standing up a database, designing schemas, building APIs, keeping it in sync with your back-office systems. If you’re running Salesforce, that work is already done.

Your customer accounts, contacts, cases, contracts, and orders are already structured, governed, and maintained. A portal built on Experience Cloud reads from the same records your internal teams use. There’s no ETL pipeline to maintain, no risk of data being out of sync, no second system of record to manage.

2. Your security model is already configured

Salesforce has a sophisticated permission model — profiles, roles, sharing rules, record-level access. When you build a portal on Experience Cloud, you’re extending that same model to external users. You control exactly what each customer can see: their own cases but not other customers’, their own account data, specific document types.

Most companies dramatically underestimate how long it takes to build a secure, multi-tenant access control model from scratch. On Salesforce, you’re building on top of infrastructure that’s been hardened over two decades.

3. Support deflection is immediate and measurable

The most direct ROI from a customer portal is reduced inbound support volume. When customers can check their case status, find answers in a knowledge base, or submit and track requests themselves, they don’t call or email.

Industry benchmarks consistently show that self-service case submission and tracking can deflect 20–40% of inbound support contacts. For a team handling 500 cases a month, that’s meaningful capacity — redirected to complex issues that actually need human attention.

4. It elevates the customer experience without scaling headcount

B2B customers increasingly expect the kind of self-service experience they get as consumers. They don’t want to email to find out the status of their order or open ticket. They want to log in, see the answer, and move on.

A well-designed portal signals maturity and investment in the customer relationship. It’s often a competitive differentiator — especially in industries like financial services, life sciences, and manufacturing where competitors are still running on email and spreadsheets.

5. It connects to every Salesforce cloud you already use

If you’re on Sales Cloud, you can expose account and contract data. If you’re on Service Cloud, customers can create and track cases. If you have CPQ, customers can view quotes. If you’re using Salesforce Files or Content, you can surface documents. The portal becomes a single pane of glass for the customer relationship — powered by data that already exists across your Salesforce environment.

What it actually takes to build one right

A customer portal is not a configuration-only project. Done well, it involves:

UX design: The internal Salesforce UI is built for trained users. A portal needs to be intuitive for customers who log in once a month.
Data architecture: Deciding what to expose, how to organize it, and what record relationships need to be in place before the portal can surface meaningful information.
Authentication and identity: Configuring login methods, self-registration flows, and how portal users are linked to existing accounts and contacts.
Customization: Most mature portals go beyond out-of-the-box Experience Cloud components. Custom Lightning Web Components are often needed for specific workflows or to match brand standards.
Integration: If relevant data lives outside Salesforce — in an ERP, a billing system, a document management platform — that data needs to be brought in before the portal can surface it.

The teams that struggle with portal projects usually underinvest in the design and data architecture phases, and overestimate how much out-of-the-box configuration will cover. Starting with a well-scoped pilot — one key use case, one customer segment — is almost always the right approach.

Where to start

The best starting point is mapping the top five things your customers contact you about today. Chances are, most of those are status inquiries or document requests — exactly what a self-service portal handles well.

From there, the question is whether your Salesforce data model already supports surfacing that information, or whether it needs cleanup before the portal can work reliably.

6Street Digital designs and builds Salesforce Experience Cloud portals for mid-market and enterprise organizations. If you’re evaluating a portal project, reach out — we’ll help you figure out where to start.

Why Salesforce CPQ Fails Without the Right Architecture

Mon, 29 Jun 2026 00:00:00 +0000

Salesforce CPQ is one of the most powerful tools in the Salesforce ecosystem — and one of the most frequently misimplemented. After working on dozens of CPQ projects, we’ve seen the same failure patterns repeat across industries.

The most common mistake: treating CPQ as a configuration project

CPQ is fundamentally a software engineering problem, not a configuration exercise. Companies often underestimate this and hand the implementation to a team without deep Apex or data modeling experience. The result is a system that works in a demo but breaks under real sales conditions — complex product bundles, multi-tier pricing, or high quote volume.

What good CPQ architecture looks like

1. A clean product catalog before you touch CPQ

The most overlooked prerequisite is a well-structured product catalog. CPQ’s product rules, option constraints, and pricing logic all depend on a clean, hierarchical catalog. If your products are a mess in Salesforce before CPQ, they’ll be a bigger mess after.

Invest time in rationalizing your products, bundles, and SKUs before the CPQ configuration begins. This isn’t glamorous work, but it determines whether your implementation succeeds.

2. Pricing logic that belongs in CPQ, not in heads

One of the core value propositions of CPQ is moving pricing knowledge out of individual reps’ heads and into a governed system. That only works if the pricing rules are genuinely comprehensive — covering edge cases, partner tiers, volume thresholds, and promotional discounts.

Incomplete pricing models mean reps still override quotes manually, which defeats the purpose.

3. Integration with your ERP from day one

CPQ doesn’t live in isolation. Quote-to-cash requires clean handoffs to your order management, billing, and ERP systems. Designing that integration after CPQ is live — rather than alongside it — leads to painful retrofits and data quality problems downstream.

4. Approval workflows that reflect how deals actually get done

Standard CPQ approval workflows are straightforward. The complexity comes when you layer in regional management structures, partner discounts, special pricing agreements, and executive override paths. Map these workflows completely before building them — a change to approval logic mid-implementation is expensive.

The payoff when it’s done right

When CPQ is architected properly, the results are significant: quote cycle time drops, pricing errors disappear, and sales operations gets the reporting they’ve always wanted. Reps spend less time on administrative work and more time selling.

The investment in doing it right upfront pays back quickly.

6Street Digital has deep experience designing and implementing Salesforce CPQ for mid-market and enterprise organizations. If you’re evaluating a CPQ project, [reach out](/# contact) — we’re happy to talk through your requirements.

Unified Service & Commerce Portal for Advanced Sterilization Products

Mon, 01 Jun 2026 00:00:00 +0000

Advanced Sterilization Products (ASP), a global leader in sterilization and infection prevention solutions, needed to consolidate a fragmented customer experience into a single, secure digital platform. Their customers — hospital systems and healthcare facilities — were managing field service requests, asset tracking, and product purchasing through separate systems, creating friction and operational inefficiency.

The Challenge

ASP required a comprehensive digital transformation that could handle the complexity of their enterprise customer base. The platform needed to be multilingual to serve their global customer base, secure enough for regulated healthcare environments, and capable of surfacing both service and commerce functionality in a single unified experience — while maintaining ASP’s brand standards throughout.

The Solution

6Street Digital designed and built a robust Customer Portal plus a fully customized B2B Commerce solution on Salesforce Experience Cloud.

Service Epic

The core of the portal is a “Service Epic” — a purpose-built service management interface that gives ASP customers full control over their service relationship:

Case submission: Customers can submit field service requests across multiple request types, each with tailored forms and routing logic
Service contract management: Customers can view and manage their active service contracts, renewal dates, and coverage details
Asset history: Full visibility into installed equipment, maintenance history, and service records for each asset in their environment

Commerce Experience

Alongside the service functionality, 6Street Digital built a customized B2B commerce storefront that allows customers to browse and purchase ASP products directly within the portal — creating a true one-stop-shop for both service and procurement.

ERP Connectivity

The portal is deeply integrated with SAP via the SAP Integration Suite, enabling:

Real-time shipping calculations at checkout
Live tax calculations across multiple jurisdictions
Bidirectional order synchronization between Salesforce and SAP, ensuring operations and fulfillment teams have accurate, real-time data

The Result

ASP customers now have a single, branded destination for everything related to their ASP relationship — service requests, asset management, contracts, and product purchasing. The customized UI maintains full brand consistency while prioritizing ease of use for clinical and procurement staff who need to move quickly.

The platform supports ASP’s global customer base with multilingual capability, and the real-time SAP integration eliminates manual handoffs between the customer-facing portal and ASP’s back-office operations.

Nexeo Plastics: Lightning Migration & Managed Services

Fri, 01 May 2026 00:00:00 +0000

Nexeo Plastics, a leading global thermoplastic resins distributor, needed to modernize their MyNexeo digital commerce platform. Built on CloudCraze (Salesforce B2B Commerce Classic), the platform required a full replatform to Salesforce B2B Commerce Lightning to unlock modern features, improve performance, and support a more scalable architecture across global regions.

The Challenge

The existing MyNexeo platform carried years of complex B2B logic — real-time entitlement calculations, customer-specific pricing, localized product catalogs, and deep SAP integrations. The goal was to replatform all of this functionality to Lightning while improving the user experience for both guest and registered users, without disrupting Nexeo’s global customer base during the transition.

The Solution

6Street Digital executed a comprehensive digital transformation combining deep technical migration, frontend development, and long-term operational support.

Replatforming & Integration

The team migrated complex B2B logic from the legacy CloudCraze system to Lightning, including real-time entitlement adjustments, automated localized product catalog management, and deep SAP integrations for customer-specific pricing and tax calculations across jurisdictions.

Enhanced User Experience

Beyond the technical migration, 6Street Digital built custom, mobile-responsive cart and checkout interfaces. Product tiles were redesigned with testimonials, and advanced self-service tools were added — including “My Forecast,” schedule line tracking, and “Shop Deal” administration — giving Nexeo’s customers more control over their purchasing experience.

Managed Services

Following the successful migration, Nexeo transitioned into a Managed Services engagement with 6Street Digital. This provided a flexible pool of resources for day-to-day technical support, enhancement management, and strategic advisory — ensuring the Lightning platform continued to deliver high business value. This phase also included building out the initial Google Analytics reporting foundation to support data-driven decision making.

The Result

By migrating from Classic to Lightning, Nexeo Plastics achieved a high-performance, mobile-responsive global storefront that significantly reduced friction in the complex buying process for thermoplastic resins. The move to a managed services model allowed Nexeo to remain agile — rapidly responding to change requests and business growth while ensuring their Salesforce investment continued to deliver maximum value.

Hormel Foods: Architecting a Global, Multilingual B2B Ecosystem

Wed, 01 Apr 2026 00:00:00 +0000

Hormel Foods Corporation, a global food industry leader, needed a sophisticated digital commerce infrastructure to support international B2B customers across multiple continents. The platform had to handle the complexities of international trade — diverse language requirements, localized product catalogs, and intricate supply chain integrations — while delivering a seamless, branded buying experience.

The Challenge

Hormel’s international B2B customers operate across vastly different regions, each with unique language, catalog, pricing, and compliance requirements. A single commerce platform needed to serve buyers in the Philippines, Europe, Singapore, Hong Kong, Japan, and LATAM — with real-time ERP connectivity for pricing and order submission, and enough flexibility to accommodate complex cart validation rules like weight limits and credit holds.

The Solution

6Street Digital partnered with Hormel to execute a series of large-scale technical implementations across multiple rollout phases.

Platform Foundation & Deep Integration

Built a robust Salesforce B2B Commerce storefront integrated with Salsify for product data management, Azure for identity management, and Hormel’s internal ERP systems for real-time order submission and pricing. The team developed specialized logic to handle requested delivery dates and complex cart validation rules including weight limits and credit holds.

Global Expansion & Localization

Executed a phased international rollout across the Philippines, Europe, Singapore, Hong Kong, Japan, and LATAM. Each region included localized UI components and large-scale data translations into Japanese, Spanish, Cantonese, and Mandarin Chinese — ensuring buyers in every market had a native, intuitive experience.

Omnichannel Marketing & Training Support

Beyond technical development, 6Street produced a high-fidelity marketing media package including an animated introduction video and comprehensive PowerPoint training programs to ensure rapid adoption by international buyers across all regions.

Continuous Operational Partnership

Established a long-term Managed Services model providing Hormel with flexible resources for day-to-day administration, break-fix support, and strategic advisory. This included a specialized Knowledge Transfer initiative to empower the internal Hormel team with technical architecture guidance and system design documentation.

The Result

The partnership successfully launched Hormel’s international B2B services across multiple continents, significantly increasing order efficiency and reducing manual processing costs. By combining high-touch technical implementation with a proactive managed services model, Hormel achieved a scalable, mobile-ready, and globally localized commerce environment — one that continues to drive customer loyalty through personalized, connected digital experiences.

v1.1 — Footer & Icon Improvements

Wed, 18 Feb 2026 00:00:00 +0000

What’s New

Multi-column Footer — New columns footer style with logo, tagline, and navigation
Social Icons — Site-wide social links rendered in the footer via identity.social.links
Icon Rendering — Robust SVG sizing strategy with 1em default for inline icons

Improvements

Icons now self-size to 1em by default, eliminating 0px collapse bugs
Footer branding supports configurable logo height and SVG scaling
Feature block icons bumped to larger size for better visual presence

Content

Changelog Section — New standalone section at /changelog/ using the date-title-summary view

v1.0 — Initial Release

Thu, 15 Jan 2026 00:00:00 +0000

What’s New

Page Builder — Build landing pages with drag-and-drop blocks
Block System — Hero, Features, CTA, Testimonials, Stats, and more
Tailwind CSS 4 — Modern utility-first styling with dark mode support
Preact Components — Fast, lightweight client-side interactivity
SEO Optimized — Automatic sitemaps, RSS feeds, and structured data
Multi-language — 35+ language packs out of the box

Getting Started

Check out the documentation to get started with your first site.

Privacy

Fri, 01 Dec 2023 00:00:00 +0000

Add your company privacy policy here…

Terms of Service

Fri, 01 Dec 2023 00:00:00 +0000

Add your company legal terms here…