Tools Used:

• Salesforce CRM Non Profit Success Pack
• Salesforce Flow
• Inventory Manager for Nonprofits

Key Wins: Simplified Inventory Management | Stronger Auditability | More Reliable Inventory Data

About the Organization

For nonprofits that distribute physical goods, inventory is more than an operational number. It determines what resources are available and what can be distributed to the community. It also affects how purchasing decisions are made. Moreover, inventory impacts how accurately the organization can report its financial position.

One nonprofit serving children, families, caseworkers, and community partners manages a substantial warehouse operation. This warehouse contains everything from diapers and hygiene products to larger items such as car seats and portable cribs. Additionally, staff combine individual products into resource bundles designed to meet specific client needs.

As the organization grew, accurate inventory became increasingly important. Leadership needed to know what was available and where it was located. In addition, they needed to know how much had been distributed and what those items represented financially. However, the problem was that the existing Salesforce inventory process had become increasingly difficult to trust.

The Challenge: Years of Customization Created an Inventory Problem

The nonprofit had been managing inventory through a highly customized Salesforce environment. This environment was built around Opportunities, Opportunity Products, forms, custom fields, Flows, and roll-up calculations.

Over time, the system accumulated tens of thousands of historical transaction records. Some inventory tables contained more than 60,000 to 70,000 records before individual product line items were even considered. As transaction volume increased, Salesforce had to work through years of historical activity. This was required just to answer a basic question: How much of this product do we have right now?

That complexity began creating visible discrepancies. In one example, staff purchased 50 units of a high-value product. Yet the inventory system continued showing the same quantity weeks later. In another, inventory was brought to zero before 452 new units were entered. As a result, the system eventually reported more than 1,000 units.

For products that are easy to count, errors like these can be spotted quickly. However, for a warehouse containing hundreds or thousands of smaller items, discrepancies may not become apparent until a physical inventory count or year-end audit.

There was another complication. Some resource requests submitted through an external form could fail to reach Salesforce because of duplicate contacts or other data issues. The physical goods still left the warehouse, but the corresponding transaction was never recorded. Consequently, the result was simple: the warehouse and Salesforce could tell two different stories.

The Solution: Simplify Before Automating

Revenue Ops approached the project by questioning the existing model rather than adding another layer of customization.

The goal was not to recreate every field, automation, transaction type, and report accumulated over the years. It was to identify what the nonprofit actually needed to operate its warehouse effectively.

Those requirements came down to a manageable set of activities: inventory entering the warehouse, products leaving it, and inventory moving between locations. Other activities included individual products being converted into bundles, the financial value associated with inventory movement, and the resources ultimately distributed to the people the organization serves.

Cost also mattered. Instead of immediately recommending an expensive commercial inventory platform or another completely custom application, Revenue Ops evaluated inventory management options available within the Salesforce ecosystem.

A dedicated Salesforce sandbox was created so the new model could be configured, tested, and reviewed without disrupting active warehouse operations.

Building Inventory Around Real-World Transactions

One of the most important changes was moving toward a cleaner transaction-based inventory model. Instead of trying to reconstruct today’s inventory by continually recalculating years of historical activity, the new design treats inventory movement as a transaction.

When products arrive, they are added. When products leave, they are removed. In addition, when inventory moves between locations, that movement is recorded. If a physical count identifies a discrepancy, an authorized user can make an adjustment that brings Salesforce back in line with what is actually on the shelf.

Each adjustment can capture the quantity changed, inventory location, user making the change, transaction date, and reason for the correction. This gives staff something the previous process struggled to provide: the ability to say, “We counted the warehouse. This is what we actually have,” while still maintaining an audit trail.

Making Bundles Work the Way the Nonprofit Works

The organization also creates resource bundles using multiple individual products. That sounds straightforward until actual warehouse operations are considered.

A hygiene bundle, for example, might normally contain several products. If one item is unavailable, staff may still create the bundle using the supplies currently on hand. The inventory system therefore cannot assume that every bundle always contains exactly the same components.

Revenue Ops built Salesforce Flow logic to create the appropriate inventory transactions when bundles are assembled. Individual products are deducted while completed bundles are added to available inventory.

The design is also being adapted so employees can identify which components are actually included in a particular bundle assembly. Only the products physically used are removed from inventory. Salesforce can also warn users when there is not enough stock to create the requested quantity of bundles.

This gives the nonprofit automation without forcing warehouse staff to change the way they actually work.

Making Inventory Easier for Staff to Manage

User experience has been a central part of the redesign. Warehouse employees should not need to understand the technical structure behind Salesforce automation. Instead, they need a straightforward way to record where inventory came from, where it is going, which products are involved, and how many items are being moved.

Revenue Ops is designing the experience around those actions. Users can select the origin and destination, enter products and quantities, review the transaction, and confirm it. The underlying automation and transaction creation happen behind the scenes.

Just as importantly, the system is being built with users rather than around them. Working concepts have been demonstrated throughout development, and feedback from employees who actually manage the warehouse has already changed the solution. For example, early bundle logic assumed bundle components would remain consistent. Yet, operational feedback showed that employees regularly adjust bundle contents based on available supplies, so the design evolved accordingly.

Improving Reporting and Financial Visibility

Reliable inventory also matters to nonprofit financial reporting. The organization uses average inventory pricing for year-end reporting and audits. Revenue Ops incorporated this requirement into the new transaction model so quantity and financial value can be tracked together.

The reporting foundation is being designed around practical questions, including current inventory by location, low-stock items, out-of-stock products, inventory transactions, bundle creation, and the financial value of inventory movement.

The project also created an opportunity to clean up confusing data definitions. During the review, Revenue Ops discovered that one metric labeled as a measure of children served was actually calculating the number of products distributed. Therefore, the metric was redefined to accurately represent what the data was measuring.

That distinction matters. A reliable system depends not only on accurate calculations, but also on users understanding what those calculations mean.

The Expected Outcome: Inventory the Organization Can Trust

The replacement inventory system remains in development and validation, but many core capabilities are already functioning in the Salesforce sandbox. These include inventory in and out transactions, location-based inventory, transaction records, bundle assembly, component deductions, bundle additions, financial calculations, reporting foundations, and validation for insufficient quantities.

The larger objective is not simply to deliver a new inventory screen. It is to give the nonprofit a system its staff can trust.

When fully implemented, the organization should have a clearer way to understand what inventory is available and where resources are located. They will also know what has been bundled or distributed and what those products represent financially. Additionally, staff should also be able to reconcile physical inventory without requiring technical intervention whenever the numbers do not match.

For a nonprofit, that reliability has an impact far beyond Salesforce. Better inventory data can help identify shortages earlier, inform purchasing and donation decisions, improve financial reporting, and reduce the time employees spend investigating discrepancies.

Most importantly, a more reliable inventory operation allows more of the organization’s time and resources to remain focused where they can do the most good: supporting the children, families, and communities that depend on them.