Skip to main content
All CollectionsStructShare Support DocumentationItem Database
Item Database: Understanding Column Headers & Import Options
Item Database: Understanding Column Headers & Import Options
N
Written by Noam Karoly
Updated over 6 months ago


Objective

This article will give you a better understanding of all of the different columns in the Item Database and what they are each for. You will be able to import using any of these available fields.

Background

When building out your Item Database in StructShare you are only required to use Item Name & Unit of Measure, but there are several other available columns that you can use in addition to those two. Here we will define what each column is for so that you can decide which ones you may want to use.

Things to Consider

  • Admin permission is required to create/upload new items into the Item Database:

    • You can create your items list manually or via excel import.

    • Please leverage this Item Database Import Template for importing your item database and associated item groupings.

    • Once the excel sheet has been loaded into StructShare, you can adjust the columns to correctly label the item details.

  • StructShare restricts item duplication in your Item Database:

    • The item database is designed to be a centralized source of truth for item naming and labelling. Because of this, we will not allow duplicated records that share all attributes

      • Items will need to be unique. You can leverage any of these fields to ensure that items are recognized by our system as unique values:

        • Item Name

        • Item Code

        • UPC

        • Manufacturer

Item Attribute

Characters

Character Limit

Unique?

UPC

Characters

Numbers

12

Yes

Model#

Characters

Numbers

Specials Characters

35

No

Manufacturer

Characters

Specials Characters

30

Yes

Item Code

Characters

Numbers

Specials Characters

30

Yes

Steps:

  • Defining Each Item Database Column

  • Upload Mapping Options

Defining Each Item Database Column

  1. Item Name - The name of your item (this is a required field).

  2. Description - The Catalog Category selected for this item. This will show the full path of categories selected to get to the item name (Conduit > EMT > 1-1/2" would show as 'Conduit EMT 1-1/2"').

  3. Internal Identifier - a unique code for each item provided by your team (cannot be the same as another item's identifier).

  4. Search Keyword - also referred to as an item 'alias'. This is designed to expand search criteria on an item so that the field is empowered to search by item names they are familiar with. For example, a lift (scissor, fork, etc.) may be called a 'cherrypicker' onsite. This field needs to be unique for each item.

  5. Units - Unit of measure for the item (this is a required field).

  6. Categories - This is where you can select which category to sort the item within. These can be built out by following this article.

  7. Price by - A secondary unit used to measure the items you need to order. This field works in conjunction with the 'Price by Unit' field. This empowers our customers to measure item expected prices using one unit of measure, but then converting it into another unit of measure when creating a PO. (for example: Your units on an item could be 'Each' but they may be sold by the 100 'C')

    We recommend talking with your StructShare Customer Success Manager before using this field.

  8. Qty Per Unit - this is a field designed to create a calculation when ordering materials. For example, maybe materials are priced by 'each' but sold 'per 100 units'. This field empowers us to store the individual unit price but also have it purchased 'per hundred'. If buying things in 'bundles' or 'boxes' this can be helpful.

    We recommend talking with your StructShare Customer Success Manager before using this field.

  9. Cost code - A cost code is a series of alphanumeric characters used to represent the different labor and material costs for a specific type of work being performed on the job. Your cost codes are used to manage the dollar amounts and quantities on a project's budget.

  10. Budget Category - a compartmentalization tool to group job costs. You could group by cost types (equipment, material, tools, rentals, etc.). You could also group by sub trades the business performs (low voltage, testing, etc.)

  11. Expected Price - this is designed to show how much you should expect an item to cost. Many of our customers input an expected price and then change it based on the quotes they receive. Others leave it blank and manage price on a supplier-by-supplier basis.

  12. General Notes - Any notes you want to add for this particular item.

  13. Internal note - Add a note that only your internal team will be able to view.

  14. External note - Add a note that will be visible to suppliers.

  15. Files - Associate a file with the item (you can upload directly from your computer).

  16. Model # - can be unique to a manufacturer or supplier.

  17. Manufacturer - Name of the manufacturer of this item.

  18. UPC - More global than a Model #, typically used instead of Model # but not in addition to.

  19. Update date - Last time this item was edited.

  20. Updated by - last person to edit the item.

  21. Created by - first person to add this item into the database.

  22. Image URL - If you want to add an image you can plug in a URL here (you can’t upload a file directly from your computer at this time).

Upload Mapping Options

  1. Tax codes - Tax Codes are created in the System Settings, and then can automatically be applied to an individual item from here.

  2. Budget category - a compartmentalization tool to group job costs. You could group by cost types (equipment, material, tools, rentals, etc.). You could also group by sub trades the business performs (low voltage, testing, etc.)

  3. Expected price - this is designed to show how much you should expect an item to cost. Many of our customers input an expected price and then change it based on the quotes they receive. Others leave it blank and manage price on a supplier-by-supplier basis

  4. Warehouse - You can associate a particular Warehouse in your StructShare system with this item.

  5. Inventory - If you first add a Warehouse to an item, you can then also add inventory against it.

  6. Model - This field is generally leveraged to track the associated item's 'Model Number' - generally assigned to the item by its manufacturer.

Questions?

Contact Support:

  • Live Chat with Support through StructShare:

    • Click on ‘Talk to Support’ on the left side of your screen.

  • Email Support:

  • Call Support:

    • ‪(512) 222-3716‬

Did this answer your question?