Manufacturing & Industrial
PumpCatalog
Salesforce and FinancialForce cleanup that protected order, invoice, address, and customer history.
PumpCatalog had Salesforce Sales Cloud, FinancialForce Accounting/ERP, and duplicate account and customer data tied to orders, invoices, addresses, phone numbers, website orders, and payment flows.

Operating challenge
Duplicate customer accounts were being created when new orders came in from existing customers, likely through a mix of website and Authorize.net paths. Matching and duplicate rules had been deactivated, open sales orders and sales invoices blocked merges, and standard account merges risked losing custom address data and phone details.
What Lodestone shaped
- Reviewed the duplicate account problem across Sales Cloud and FinancialForce.
- Evaluated sandbox, DupCatcher, duplicate rules, matching rules, and master-record selection approach.
- Mapped the need to preserve customer addresses, phone numbers, orders, invoices, and financial history during cleanup.
- Scoped root-cause investigation to prevent the same duplicates from being recreated by ordering and payment integrations.
Resulting direction
- PumpCatalog had a safer cleanup path for duplicate accounts tied to active order and invoice history.
- The project protected operational and accounting context instead of treating dedupe as a simple merge exercise.
- The root-cause investigation created a path to stop future duplicate creation at the integration source.
Profile context
Industrial pump catalog and ecommerce/distribution operation
Pump catalog and distribution operation with Salesforce, FinancialForce, duplicate account cleanup, and order and invoice history constraints.
Meet the people behind connected delivery.
Explore the leadership and specialist responsibilities that connect business priorities, architecture, and implementation.