Last updated:
Adobe Commerce Hyvä Redesign & Performance Engineering for Benum's B2B2C Commerce Platform
Platform evaluation and replatforming strategy for a commercial LED lighting manufacturer, comparing Shopify Plus and Adobe Commerce and defining a phased NetSuite-connected B2B architecture
Project Summary
Litetronics, a commercial and industrial LED lighting manufacturer, needed to replace its WooCommerce-based website with a B2B commerce platform capable of supporting technical product discovery, ERP-connected customer and sales-representative portals, and a phased path to transactional commerce.
Elogic Commerce mapped Litetronics’ full set of business and technical requirements and evaluated Shopify Plus and Adobe Commerce against them. Shopify Plus was identified as the recommended platform, with a target architecture that allowed Litetronics to launch ERP-connected experiences first and introduce transactional B2B workflows in a subsequent phase. Implementation is planned as the next phase of the project.
Key Outcomes
Shopify Plus
recommended platform, selected through comparative evaluation against Adobe Commerce
2-phase
commerce architecture defined for progressive rollout from ERP-connected experiences to transactional B2B commerce
2
ERP-connected portal experiences architected, one for sales representatives and one for customers
190 hours
of structured discovery, requirements mapping, and platform evaluation
About the Client
Litetronics is a commercial and industrial LED lighting manufacturer founded in 1970, producing high bay, hazardous location, area, flood, and retrofit lighting products sold through a network of sales representatives and dealers, alongside direct customer accounts. The company serves schools, healthcare facilities, industrial sites, government buildings, retail spaces, and street lighting projects.
Before the engagement, the existing WooCommerce implementation was not aligned with the company’s ERP-linked reporting needs, dedicated rep and customer portals, or the growth and lead-generation goals leadership had defined for the redeveloped site.
Project Complexity
The platform needed to support two distinct, ERP-linked login experiences: a representative portal with territory sales history, commission data, price books, and overdue account reporting, and a separate customer portal with order history, invoices, payment history, credits, and customer-specific pricing, each with its own admin and permission structure.
Phase 1 required one-way data flow from NetSuite into the platform for reporting and inventory visibility, while Phase 2 required two-way data flow to support quote creation, order creation, RMA submission, and potentially payment. That is a materially more complex integration than a standard ERP product-and-price sync.
The catalog needed to support searchable product lines, compatibility information, downloadable technical literature such as spec sheets, brochures, and compatibility lists, and IES file downloads for lighting design use, going well beyond a standard ecommerce product detail page.
The roadmap defined Phase 1 as the initial ERP-connected experience and Phase 2 as the subsequent transactional rollout, meaning the recommended platform had to be architecturally suited to incremental rollout rather than a single big-bang launch.
Business Challenge
Litetronics' core challenge was determining which ecommerce platform could support a technical B2B catalog, dual ERP-linked portals for reps and customers, and a phased rollout, while giving the internal team the reporting and content-management capability they were currently missing entirely.
01
The existing WooCommerce implementation was not adequately supporting the ERP-linked rep and customer portal experience, structured technical catalog, or reporting capabilities the business required.
02
Sales reps and customers had no self-service access to inventory, pricing, order history, or account information tied to NetSuite.
03
The business had no structured reporting for ROAS, AOV, conversion rate, cart abandonment, or lead generation, limiting its ability to measure and improve digital performance.
04
Content updates required ongoing reliance on third-party developers, making internal content-management capability a first-class platform requirement rather than an afterthought.
05
Leadership had set defined post-launch objectives for the redeveloped site, including target monthly visitor, lead, and subscriber volumes within twelve months of Phase 1, alongside a reporting stack covering ROAS, AOV, gross profit, conversion rate, cart abandonment, CTR, and funnel performance. These were client targets to be pursued after launch, and they shaped the platform recommendation’s requirements for native and extensible reporting capability, not just storefront functionality.
06
Leadership needed an objective platform recommendation, comparing Shopify Plus and Adobe Commerce against the actual requirements, before committing implementation budget.
Elogic Commerce's Solution
Requirements Discovery
Elogic Commerce ran stakeholder interviews across marketing, operations, technology, and store management, documented current-state store operations, website performance, and inventory flow, conducted user behavior research, and ran benchmark and competitor analysis, producing a complete mapping of Litetronics’ business and technical requirements against which platform options were evaluated.
MVP Scope Alignment
Elogic Commerce worked with Litetronics to align on must-have versus nice-to-have functionality, translating the RFP’s broad goals and the detailed sitemap covering product catalog, industries pages, resources, and the rep and customer portals into a scoped, phased delivery plan matching the Phase 1 and Phase 2 structure Litetronics had defined.
Platform Selection Criteria
Elogic Commerce assessed the existing WooCommerce implementation against Litetronics’ requirements, then evaluated Shopify Plus and Adobe Commerce as replatforming candidates across five dimensions:
- B2B commerce: customer accounts, permissions, pricing, portal requirements
- ERP integration: NetSuite data flows, reporting, inventory, future transactional workflows
- Catalog and content: technical specifications, compatibility data, literature and IES files
- Operational flexibility: internal content management and reduced developer dependency
- Scalability and roadmap: ability to support Phase 1 launch and subsequent transactional capabilities
Technical Feasibility and Integration Assessment
Elogic Commerce identified pain points in backend speed, checkout, and inventory handling on the existing WooCommerce site, defined the required integrations across ERP, CRM, and CMS, and mapped to-be processes for order management, inventory, returns, and the rep and customer portal experience.
Platform Recommendation
Elogic Commerce recommended Shopify Plus, on the basis that it provided the required B2B account foundation with NetSuite remaining the system of record, supported a phased integration path from one-way data flows to two-way transactional workflows, and reduced developer dependency for routine content and commerce administration while keeping specialized ERP and portal workflows separate from day-to-day storefront management.
Adobe Commerce was technically capable of supporting the requirements. For Litetronics’ scope, however, its customization depth would have introduced operational overhead the defined requirements did not call for. The resulting architecture allowed Litetronics to establish ERP-connected visibility and portal experiences in Phase 1, then extend into transactional B2B workflows in Phase 2 without requiring a new platform decision.
Strategic Outcomes and Implementation Readiness
Because this was a pre-implementation strategy and discovery engagement, the outcomes below are decision-readiness and planning outcomes rather than post-launch performance metrics.
Platform direction
Shopify Plus
selected as the recommended platform following comparative evaluation against Litetronics' business and technical requirements
grounded
the platform decision in documented B2B, portal, ERP, catalog, content, and scalability requirements
Architecture definition
defined
two-phase commerce architecture
mapped
NetSuite integration for one-way Phase 1 and two-way Phase 2 data flows
defined
separate ERP-connected experiences for sales representatives and customers
Implementation readiness
aligned
MVP scope with stakeholders
established
Implementation roadmap with defined scope, architecture, timeline, and budget
incorporated
Litetronics' growth and reporting targets into the target architecture and measurement framework for post-launch evaluation
Strategy Deliverables
Capabilities Demonstrated
01
Independent ecommerce platform selection and technology advisory
02
Multi-platform evaluation across Shopify Plus and Adobe Commerce
03
B2B ecommerce consulting for technical, specification-driven catalogs
04
NetSuite ERP integration strategy, including phased one-way and two-way data flows
05
Rep and customer portal architecture planning
06
Requirements engineering and structured technology assessment
07
Phased implementation roadmap development
08
Analytics and reporting requirements strategy covering ROAS, AOV, conversion, and cart abandonment
When This Solution Is a Good Fit
01
The business has outgrown its current platform and the replacement decision is genuinely open rather than already made.02
Both sales rep and customer self-service portals need to be tied to an ERP system.03
ERP integration is expected to deepen over time rather than remain static, making phasing a real architectural requirement.04
The catalog is technical and specification-driven rather than merchandising-led.05
Implementation budget is large enough that validating the platform decision first is cheaper than correcting it later.Planning a B2B Ecommerce Platform Strategy?
Outgrowing your current platform, or need to validate a platform decision against ERP integration, rep or customer portal requirements, and a phased rollout plan? Elogic Commerce can map your business and technical requirements, evaluate platform options objectively, and build an execution-ready roadmap before you commit to implementation.