Team - When I set up our Pricebook, I tried looking ahead to inventory. Because of the nature of garage doors being a combination of many parts, I worked under the premise that you have to inventory all of the parts that make up a door, not the whole door itself, to have a meaningful count. The result was a Pricebook in which full garage doors were Equipment and all of the component parts were linked Materials. The perceived benefits of this were that we could accurately track inventory with linked Materials, but that we'd put Equipment on Estimates and Invoices so that we don't have to manually add the Materials to each installation job. But this has a number of problems: The Pricebook is huge (like, tens of thousands). The biggest drawback of that is decreased performance/speed in ST. It simply struggles with that many items in certain use cases. Example: one piece of equipment is "16x7 LI1000 TW SP" (LI1000 = Door Model; TW = True White; SP = Short Panel). Linked to the "16x7 LI1000 TW SP" are the materials: INT panels, BTM panel, track, hardware box, springs, tube, strut, stop mold, etc. We have 20,000+ doors as Equipment for different models, colors, panel styles, windows, insulation values, etc. Of course, this also makes it more difficult to find certain items and easier to choose the wrong item. Job Margin numbers within the UI are incorrect and way off because it double counts my costs (once for Equipment and once for Materials). I can download Margin reports and fix that there, but it ruins the UI's helpfulness. I hear folks in here advise to "simplify" the Pricebook. However, one of my assumptions has to give in order to do that. It sounds like this isn't how other folks do their inventory, but then I'm not sure how that's an effective inventory count. One idea is to stop using Equipment and start using Services w/ linked Materials to track inventory parts. For ex, the Service "16x7 Non-Insulated White Short Panel Installation" (for lack of better name right now), and then all of the panels, springs, etc. would be linked. This solves the double costing problem but not the Pricebook size problem, so I'm not sure which way to go and hoping for some guidance. Thanks for reading a lengthy post and thanks for any guidance. - Jared @AdamCronenberg @stashleyk @jeisenman
... View more