Multiple Dependent Records
Creating a product required more than inserting a Product record. Price Books, Price Book Entries, Features and related configuration all needed to be created and linked correctly.

Product & Data Operations
Turning a manual, multi-day Salesforce product-creation process into a structured, repeatable workflow capable of processing hundreds of products and their related records efficiently.
Environment
Enterprise Salesforce
Primary Challenge
Complex product catalogue loading
Key Tools
Excel · Data Loader · Salesforce Products
The Challenge
The requirement involved creating a catalogue of approximately 200 Salesforce products.
The challenge was that each product depended on additional configuration including Price Books, Price Book Entries, Features and other related records.
Those records could not simply be loaded independently. Relationships had to be preserved, newly generated Salesforce IDs had to be carried forward and imports had to happen in the correct sequence.
Previously, the business supplied a list of the products it needed: names, parent products, product families and so on. It was written from a business perspective, with no knowledge of the Salesforce IDs behind any of it.
Developers then built each product by hand in Salesforce, usually by cloning an existing product and manually editing and linking everything. For around 200 products that took several days and was prone to errors.
Why It Was Difficult
Creating a product required more than inserting a Product record. Price Books, Price Book Entries, Features and related configuration all needed to be created and linked correctly.
Records had to be created in sequence because later records depended on Salesforce IDs generated during earlier stages.
Requirements arrived as a list of product names, parent products and families. Every parent, family and related record had to be found in Salesforce and linked by hand.
Each product was created manually, usually by cloning an existing one and editing it. Fine for a handful of products, but several days of repetitive, error-prone work at catalogue scale.
The Solution
Rather than building each product by hand, I designed a structured Excel workbook around the Salesforce catalogue data model. The product team only had to fill in that one workbook; the developers handled everything else.
The workbook separated data according to the Salesforce records that needed to be created while retaining references between each stage of the process.
This made it possible to validate data once, perform predictable Data Loader operations and reconcile generated Salesforce IDs into downstream records without repeatedly rebuilding the mappings.
Technical Process
Identified every object and relationship required to create a complete product, including dependencies between Products, Price Books, Price Book Entries, Features and related records.
Created an Excel-based preparation framework that organised source data around the required Salesforce objects and relationships.
Used structured identifiers and mapping fields so newly generated Salesforce IDs could be reconciled with downstream records.
Checked required values, duplicates, relationship dependencies and source-data consistency before records reached Salesforce.
Executed repeatable Data Loader operations in the correct dependency order, carrying generated identifiers into subsequent imports.
Validated that expected products and related records had been created correctly and that the resulting Salesforce relationships were intact.
Before & After
Before
Built by hand in Salesforce, one product at a time
After
One workbook in, a fixed load sequence out
Outcome
Once the catalogue data had been prepared using the structured framework, approximately 200 products and their related records could be processed in around one hour of Data Loader operations.
~200
Products processed
~1 hour
Data Loader operations after preparation
Days → Hours
Operational effort dramatically reduced
The one-hour figure refers to the Salesforce loading operations after catalogue preparation. The key improvement was not magically making data preparation disappear, but turning that preparation into a structured and reusable process instead of repeating the same manual work for every product.
Business Value
Once the process existed, future catalogue work no longer meant building products one by one in Salesforce. The product team filled in a workbook and the load did the rest.
Reduced repetitive product creation and manual data handling
Created a repeatable process rather than a one-off import
Made dependencies between catalogue records explicit
Reduced the likelihood of incomplete or incorrectly linked records
Made future product loads easier to prepare and execute
Created the foundation for a reusable commercial accelerator
Product Direction
The original work solved an immediate enterprise catalogue-loading requirement, but the underlying problem is not unique to one Salesforce environment.
Organisations regularly need to create, migrate or restructure large product catalogues containing records that depend on one another.
That experience now forms the basis of the Product Catalogue Accelerator, which is being rebuilt independently as a reusable implementation framework for future Salesforce projects.
Product Catalogue Accelerator
The commercial version will combine structured catalogue preparation, validation, relationship mapping and controlled Salesforce loading.
The Bigger Lesson
Data Loader is extremely useful, but repeatedly performing the same mapping, validation and relationship-management steps by hand is not an especially intelligent use of engineering time.
When a process is predictable and repeatable, the better long-term solution is often to standardise the process and automate the parts that create the most operational effort.
Product Catalogue Projects
I can help design a controlled approach for preparing, validating and loading complex Salesforce product structures without turning the project into weeks of repetitive manual operations.