In SingleOps, there are six built-in categories into which you can divide your items. These can be explored more fully in the article here. These item categories cannot be modified or removed: they are an integral part of the application.
If you find, however, that you need to further sub-divide your items into different classifications, SingleOps offers the ability to create subcategories. These can be used as smaller 'buckets' into which you can divide your items - OR - you can create subcategories which span across different categories, e.g., you might have a pruning subcategory which represents both labor and a service.
Creating a New Subcategory
To create a new subcategory, complete the following steps:
• Go to Admin >> Items >> Item Subcategories
• Click on the New Item Subcategory button (upper-left)
• Type in the Name of your new subcategory. Make it as broad as necessary - but as specific as possible. You'll want the name to be descriptive enough to your users so they don't have to guess as to which category to use.
• The new subcategory will default so as not to be associated with any of the existing six item categories. Assign the subcategory to at least one category - but, as we mentioned earlier, you can assign the subcategory across more than one category.
• Once you have completed naming the subcategory and assigning it to the category, be sure and click the blue Create Item Subcategory button to preserve your changes.
Using the Item Subcategory
Now that you've created the subcategory, you can begin using it in your item configuration. When you create or edit your item, you'll now be able to click on the Item Subcategory dropdown list and select one of the subcategories you've created and assign it to the item. (NOTE: if you've not yet created any subcategories, the item subcategory dialog will appear grey and mousing over the pulldown arrow will yield a 'circle with line' icon. If you receive this, stop, create your subcategory, then return and complete your item edit.) Be sure to click the Update Item button at the bottom to preserve your changes.
Differences in Terminology
As you use items in your jobs, you may sometimes ponder the difference in terminology. Let's discuss briefly how the following terms are used in SingleOps.
• Items - these are the different materials, services, equipment, and labor your company offers to your customers. They are the building blocks that will make up your proposals, visits, and jobs. Some may have costs, others may not. Some may have a price, others may not. But each item can be listed separately to show your customer or crew what should be done to complete the job.
• Line items - line items are the items listed above, but are specific to the particular proposal, visit, or job at-hand. An item which has an ID of, say... '12345' may be used across many jobs: in Job #246, it may appear as line item '234678', and in Job#357, it may appear as line item '456890'. It is the same item; but the fact that it's unique to that job means it is a different line item, and, as such, bears its own ID number.
• Item category - as we mentioned in the opening paragraph, SingleOps contains six built-in item categories that cannot be modified. These are: materials, services, labor, equipment, expense, and discount. You will select one of these categories for each/every item you add to SingleOps - but you may further classify your items by the use of subcategories.
• Item subcategory - discussed here in this article, subcategories allow you to either break down your classification more specifically within a category - or you can show that the item extends across multiple categories.
• Item group - an item group allows you to 'kit' or package together those items which are commonly used together so that it saves you time (and prevents you forgetting to include an item) when you are creating a proposal or job. An item group is really not a way of classifying items - but more accurately, a way of grouping items together. In fact, an item group may contain items from multiple categories or subcategories.