EFCO: Digital Transformation for Global Construction Operations

Background & Challenge

EFCO supplies engineered formwork and shoring systems for complex construction projects worldwide. As customer expectations shifted to digital self-service, EFCO needed a unified portal that could sell and lease equipment, expose accurate project status, and centralize job documentation—all without fragmenting data across multiple tools.



The prior landscape siloed product browsing from pricing and fulfillment, and project teams relied on offline reports to understand allocations, shipments, returns, and on-lease quantities. Documents lived in SharePoint but were disconnected from the customer experience. EFCO set an ambitious goal: one platform where customers and internal teams collaborate from quote to job closeout.

Solution & Implementation

1. B2B Commerce Storefront

The storefront uses B2B Commerce APIs for catalog, pricing, and cart operations. Customers browse product content, filter with facets, and add to cart with **purchase** and **lease** options. Measurement preferences (Imperial/Metric) drive accuracy across specifications.
Checkout is guided through Flow with plug-in integrations for pricing, taxes, delivery, and inventory validation. Supports guest and authenticated users, with post-order summaries for transparency.

2. Project Equipment and Logistics

A project workspace surfaces the full equipment lifecycle—allocations, shipments, returns, and on-lease balances. Interactive tables enable drill-downs and export to CSV/PDF. Data is computed server-side for performance and delivered to LWCs for visualization.

3. Document Management With SharePoint

Customers and EFCO teams upload and access drawings, shipment docs, and submittals directly within the portal. A secure REST layer proxies SharePoint via named credentials, enabling uploads, folder navigation, and expiring links. This maintains SharePoint as the system of record while offering a seamless, contextual experience.

4. Sales Cloud and CRM Operations

The lead-to-opportunity-to-agreement pipeline is standardized. Trigger-driven services create key contacts, assign support teams, and propagate currency reliably. Address validation is asynchronous, and a Same-As utility ensures consistency across records. Result: cleaner CRM data, fewer manual steps, and tight handoff into fulfillment.

5. Agreement/Segment Domain Mode

Contracts are modeled via **Agreement** and **Segment** objects. Currency cascades from Opportunity, address validation runs before and after DML, and metadata toggles allow admins to safely enable or disable automations.

6. ERP "Project Plan" Integration

Legacy ERP is decoupled through a defined integration layer. Opportunities publish integration events; staging objects represent ERP data; and invocable Apex actions retrieve shipments, returns, and metrics.
Error handling and monitoring ensure visibility into failed integrations. ERP remains the source of truth, but project intelligence becomes accessible in real time.