How to Think About Inventory in Salesforce Field Service Before You Build It
In this Office Hours Insight session, Leigh-Anne Nugent walks through a practical inventory challenge in Salesforce Field Service: how to manage siloed inventory across multiple lines of business while still keeping the system centralized. Using a real-world scenario involving separate inventory buckets and an Epicor ERP integration, this session highlights what the core object model can do, where sharing rules matter, and why inventory is never as “simple” as it first sounds.
LESSONS YOU CAN TAKE FROM THIS:
1. Centralized does not have to mean visible to everyone
A major takeaway from this session is that inventory can still live in one Salesforce environment without being wide open to every team. Separate locations, ownership models, role hierarchy, and sharing rules can be used to keep each line of business working from its own inventory while still keeping the overall architecture centralized and manageable.
2. Inventory setup starts with more groundwork than people expect
Leigh-Anne shows that inventory is not something you casually switch on. You need locations, products, product items, page layout updates, service resource setup, and clear decisions about how warehouse and van inventory should work. Even getting a technician to see the right stock in mobile can depend on getting those foundational records and permissions right.
3. Product requests and transfers solve different parts of the process
This discussion highlights an important operational distinction. Sometimes technicians request parts and warehouse staff fulfill them. Other times inventory is pushed automatically based on what is already known about the work. Those are different workflows, and Salesforce Field Service gives you objects for both—but the right model depends on whether the field team is asking for parts, receiving preplanned fulfillment, or both.
4. Inventory gets complicated the moment real operations show up
One of the strongest lessons here is that inventory is never just about “showing what was consumed.” Partial receipts, serialized items, replenishment, warehouse transfers, van stock, ERP integration, and mobile usability all come into play quickly. That is why a simple-looking inventory requirement often expands into a much larger operational design conversation.
KEY TAKEAWAYS:
Inventory can be centralized in Salesforce while still being segregated by line of business.
Locations, products, product items, and page layouts are part of the minimum viable setup.
Sharing rules matter if technicians should only see specific inventory buckets.
Requests, transfers, and receipts each represent different operational steps.
ERP integration and replenishment logic often become part of the design much faster than expected.
