Folio3 implemented Salesforce Sales Cloud and Service Cloud for a U.S. compounding pharmacy, connecting it to NetSuite and WooCommerce. Folio3 is a Gold-tier Salesforce Consulting, MSP, ISV and Agentforce Partner with 15+ years of CRM experience, 50+ certified Salesforce consultants and 200+ Salesforce consulting engagements delivered.
The client operates both a 503A pharmacy and a 503B outsourcing facility. Salesforce became the customer engagement layer on top of the pharmacy’s existing WooCommerce store, NetSuite ERP and pharmacy management system, without replacing any of them. The project started in October 2025 and went live in April 2026. By June 2026, the 10-user team answered prescriber inquiries in 2 business hours instead of 7, and was on track to release 2,392 staff hours a year.
Key takeaways
Keep what works
Folio3 kept NetSuite, WooCommerce and the pharmacy system, and added Salesforce as the missing relationship and service layer.
Integrate with clear ownership
Folio3 connected NetSuite through Celigo integrator.io and WooCommerce through the Webkul connector, with one source of truth per data type.
Keep PHI out of the CRM
Folio3 kept protected health information (PHI) in authorized healthcare systems; only necessary non-PHI data reached Salesforce.
What results did Folio3 deliver for the pharmacy?
| Metric | Before → After | What drove the change |
|---|---|---|
| Prescriber inquiry response | 7 → 2 business hrs (71% faster) | One prescriber record with full history, plus case assignment and escalation rules |
| Order-status resolution | 4 → 1.5 business hrs (62.5% faster) | Order and fulfillment status shown inside Salesforce from the source systems |
| Sales follow-up compliance | 60% → 90% (+30 points) | Standard opportunity stages and automated follow-up tasks |
| Lead-to-opportunity conversion | 15% → 18% (20% lift) | Structured lead qualification in Sales Cloud |
| Manual admin work per user | 10 → 6 hrs/week (40% less) | Integrations removed duplicate data entry across systems |
| Sales reporting effort | 8 → 2 hrs/week (75% less) | Salesforce dashboards replaced spreadsheet consolidation |
| Duplicate or inconsistent customer records | 10% → 3% (70% fewer) | Matching rules, duplicate rules and clear data ownership |
Baseline measured October 2025; post-implementation measured June 2026, two months after go-live. 10 CRM users.
Integration reliability: after go-live, Folio3’s integrations ran at 99.5% transaction success across all integrations, supported by retries, exception queues and reconciliation reports.
Project at a glance
| Item | Detail |
|---|---|
| Client | U.S. compounding pharmacy operating a 503A pharmacy and a 503B outsourcing facility |
| Customers served | Prescribers (physicians and other healthcare providers), clinics and patients |
| Channels | WooCommerce store, B2B prescriber ordering portal, patient refill platform |
| Salesforce products | Sales Cloud (prescriber accounts, pipeline) and Service Cloud (cases, service) |
| Systems retained | WooCommerce, NetSuite ERP, pharmacy management system |
| Integrations | NetSuite ↔ Salesforce via Celigo integrator.io (accounts both ways; order status and fulfillment into Salesforce); WooCommerce → Salesforce via the Webkul WooCommerce Salesforce Connector (online customers and orders) |
| Timeline | Kickoff October 2025; production go-live April 2026; post-launch support through June 2026 |
| Implementation budget | About $50,000, excluding Salesforce license costs |
| CRM users | 10 |
| Implementation partner | Folio3 |
What problem was the pharmacy trying to solve?
Before Folio3’s engagement, the pharmacy already had capable systems for commerce, ERP and dispensing. None of them gave sales and service teams one view of the prescriber relationship. Before the project, teams faced five issues:
- Fragmented prescriber data. Reps checked several applications to piece together an account’s history.
- Inconsistent follow-up. With no standard stages or task ownership, only 60% of follow-ups happened on time.
- Manual service coordination. An order-status question meant switching systems or calling another team.
- Slow reporting. Sales, service and ERP data used different structures, costing 8 hours a week.
- Unclear data ownership. Overlapping records left 10% of customer records duplicated or inconsistent across systems.
Folio3 adds Salesforce as the relationship and service layer on top of the ERP, e-commerce and pharmacy systems you already run.
Why Salesforce instead of extending NetSuite?
Folio3 kept NetSuite for what it does well (financials, inventory and orders) and added Salesforce for what NetSuite was not set up to do: managing prescriber relationships, the sales pipeline and service cases across every channel. Folio3’s fit-gap assessment (a comparison of required capabilities against what existing systems already provide) guided the decision.
| System | System of record for |
|---|---|
| Salesforce | Prescriber accounts, contacts, leads, opportunities, activities, service cases |
| NetSuite ERP | Assigned ERP transactions, financials, inventory and order management |
| WooCommerce | Storefront, catalog presentation and cart |
| Pharmacy management system | Prescriptions, compounding, dispensing and fulfillment records |
Why Sales Cloud and Service Cloud instead of Health Cloud?
Folio3 chose Sales Cloud and Service Cloud because this project was commercial, and Salesforce Health Cloud is built for clinical and patient-care workflows. The CRM had to manage prescriber relationships, sales and service, and no clinical records were to be stored in it. Sales Cloud and Service Cloud covered those needs at a lower license cost.
Architecture: before and after Salesforce
- Financials & accounting
- Inventory
- Order management
- Prescriptions & compounding
- Dispensing
- Fulfillment
- Email / SMS
- Payments
- Analytics
Figure 1. Before: channels and back-office systems were connected, but follow-up, service and reporting ran on spreadsheets, phone and email.
- Prescriber accounts & contacts
- Leads & opportunities
- Follow-up tasks
- Pipeline dashboards
- Cases & assignment
- Escalations
- Order-status visibility
- Service dashboards
- Financials & accounting
- Inventory
- Order management
- Prescriptions, compounding, dispensing
- Fulfillment
- Email / SMS
- Payments
- Analytics
Figure 2. After: Salesforce Sales Cloud and Service Cloud as the engagement layer, connected through Celigo integrator.io (NetSuite) and the Webkul connector (WooCommerce). PHI stays in the pharmacy management system.
What Folio3 delivered
Folio3 delivered Sales Cloud implementation, Service Cloud configuration and Salesforce integration services as one engagement:
| Capability | What was delivered |
|---|---|
| Prescriber and account management | Account details, contacts, activities and full relationship history in one record |
| Sales pipeline | Lead qualification, opportunity management stages, follow-up assignment and pipeline reporting |
| Customer service | Case assignment, prioritization, escalation and tracking to resolution |
| Order visibility | Order and fulfillment status pulled from the authoritative source system |
| Workflow automation | Event-based tasks, notifications and escalations, built with Folio3’s Salesforce automation services |
| Dashboards | Pipeline, account engagement, follow-up compliance and case resolution reports and dashboards |
| Data quality | Matching rules, validation and duplicate controls |
| Compliance-aware access | Access by approved role, business purpose and data-handling policy |
How a prescriber order flows now
Folio3 designed the order flow so Salesforce supports the pharmacy’s controls without replacing them:
- 01Prescriber shows interestA prescriber shows interest in an office-use product (stock a clinic keeps on hand, rather than a patient-specific prescription); the rep creates or qualifies the account in Salesforce.
- 02Opportunity recordedSalesforce records the opportunity, next steps and every interaction.
- 03Order processedThe order is processed in the designated ordering and ERP systems.
- 04Status flows backOrder status flows into Salesforce for sales and service follow-up.
- 05Exceptions routedExceptions are routed to the right operational team.
Salesforce does not approve prescriptions, authorize dispensing or replace the pharmacy’s operational controls.
How do Salesforce, NetSuite and WooCommerce stay in sync?
What syncs, and in which direction
Folio3 set up three integration flows, each with one direction and one source of truth:
| Integration | Direction | Data |
|---|---|---|
| NetSuite ↔ Salesforce (Celigo integrator.io) | Both ways | Accounts |
| NetSuite → Salesforce (Celigo integrator.io) | One way | Order status and fulfillment, for visibility only |
| WooCommerce → Salesforce (Webkul connector) | One way | Online customers and orders |
Folio3’s integration rules define which system can create or update each field, how conflicts are resolved and how records are reconciled. WooCommerce and NetSuite were scoped as separate integrations, because a WooCommerce connector does not cover NetSuite.
Single-vendor option. This client used Celigo and Webkul. Folio3 also builds its own native connectors for teams that prefer one partner across CRM and ERP: the Folio3 NetSuite Salesforce Integration Connector and the Folio3 NetSuite WooCommerce Integration Connector, a Built-for-NetSuite app.
Security and HIPAA. Folio3 kept PHI in the pharmacy’s authorized healthcare systems; only the non-PHI data each workflow needs is integrated into Salesforce. Every system has a defined source of truth, HIPAA requirements were validated with the client’s security owner, and all integrations were tested end to end before go-live. Access follows least privilege, with authentication, encryption and audit logging.
How did Folio3 run the implementation?
Folio3 ran the project in five phases:
- 01Discovery and fit-gapMapped systems, data ownership, prescriber workflows and service pain points; set KPI baselines.
- 02CRM foundationConfigured Sales Cloud and Service Cloud: accounts, pipeline, cases, access controls and dashboards.
- 03Integration and automationConfigured and deployed the Celigo and Webkul integrations with monitoring, retries and reconciliation.
- 04Testing and rolloutIntegration testing, user acceptance testing (UAT), data validation, training and production go-live in April 2026, followed by post-launch support through June 2026.
- 05Value realizationMeasured KPIs in June 2026 against the October 2025 baseline.
How many staff hours did the project free up?
Folio3’s integrations and dashboards freed up 2,392 staff hours a year across admin and reporting work:
| Source | Calculation | Hours / year |
|---|---|---|
| Admin work | 4 hrs saved × 10 users × 52 weeks | 2,080 |
| Reporting work (team) | 6 hrs saved × 52 weeks | 312 |
| Capacity released per year | 2,392 |
That is more than one full-time employee’s working year returned to prescriber engagement and service, without adding headcount, on an implementation budget of about $50,000 (excluding Salesforce licenses).
Folio3 baselines your KPIs, maps data ownership across ERP and e-commerce, and shows where Salesforce pays off before you commit.
What’s next: Agentforce
Agentforce implementation is in Folio3’s pipeline for this client. With prescriber records and order status already in Salesforce, the next step is AI agents that answer routine order-status questions from prescribers automatically.
Frequently asked questions
What is the best Salesforce setup for a compounding pharmacy that runs NetSuite and WooCommerce?
In this Folio3 project, it was Sales Cloud for prescriber relationships and the sales pipeline, Service Cloud for cases, Celigo integrator.io for NetSuite and the Webkul connector for WooCommerce. NetSuite and the pharmacy management system kept their roles; Salesforce added the relationship and service layer on top.
How much does a Salesforce implementation cost for a pharmacy?
Folio3’s implementation for this pharmacy cost about $50,000, excluding Salesforce licenses. It covered Sales Cloud and Service Cloud for 10 users, plus the NetSuite and WooCommerce integrations. License costs depend on the editions and number of users; implementation cost depends on the number of integrations, data migration and workflow complexity.
How long does a Salesforce implementation take for a pharmacy?
Folio3 took this project from kickoff in October 2025 to production go-live in April 2026, about six months, followed by two months of post-launch support. Integration complexity and data migration drive most of the timeline.
Can Salesforce integrate with NetSuite and WooCommerce?
Yes. Folio3 connected NetSuite through Celigo integrator.io, syncing accounts both ways and sending order status and fulfillment one way into Salesforce. WooCommerce connected through the Webkul WooCommerce Salesforce Connector, sending online customers and orders one way into Salesforce. Scope them separately: a WooCommerce connector does not cover NetSuite. Folio3 also offers its own native NetSuite–Salesforce and WooCommerce–NetSuite connectors.
Why did Folio3 choose Sales Cloud and Service Cloud over Health Cloud for this pharmacy?
Folio3 chose them because the CRM’s job was commercial and no clinical records were stored in it, so Health Cloud’s clinical features were not needed. See “Why Sales Cloud and Service Cloud instead of Health Cloud?” above.
How do you cut prescriber response time with Salesforce?
Folio3 put each prescriber’s account, contacts, activities and open cases in one Salesforce record and added case assignment and escalation rules. Prescriber inquiry response fell from 7 to 2 business hours, and follow-up compliance rose from 60% to 90% with standard opportunity stages and automated follow-up tasks.
How did Folio3 support a pharmacy running both a 503A pharmacy and a 503B outsourcing facility?
Folio3 set up Salesforce to manage prescriber relationships and service across both operations, while prescription, compounding and dispensing records stay in the pharmacy management system. The prescriber order workflow also covers office-use products, which 503B outsourcing facilities can supply.
How do you keep PHI out of Salesforce in a pharmacy CRM?
Folio3 kept PHI in the pharmacy’s authorized healthcare systems and integrated only the non-PHI data each workflow needed, with HIPAA requirements validated by the client’s security owner. See “Security and HIPAA” above.
Why not just use NetSuite CRM?
Folio3 found NetSuite strong for financials, inventory and orders, but not set up for prescriber relationship management, a sales pipeline and service cases across three channels. See “Why Salesforce instead of extending NetSuite?” above.
Sources
- Salesforce: Business Associate Addendum
- Folio3: NetSuite Salesforce Integration Connector
- Folio3: NetSuite WooCommerce Integration Connector
- Folio3 on Salesforce AppExchange
About the author
About Folio3
Folio3 is a Gold-tier Salesforce Consulting, MSP, ISV and Agentforce Partner with 15+ years of CRM experience, 50+ certified Salesforce consultants and 200+ Salesforce consulting engagements delivered. See Folio3 on Salesforce AppExchange.
More Folio3 Salesforce case studies: 40% faster quote-to-cash for a glass and door installer, 35% faster sales operations for an equipment manufacturer and 90% less manual reconciliation for a food verification company. Browse all Salesforce success stories.
Folio3’s Salesforce team will run a fit-gap assessment and show where a CRM layer pays off.