SKU Use Cases??

Hi @Kyle,

Not using it yet, still working out how it fits into a real estimating workflow.

If SKU is meant to standardise products and drive quantities & pricing consistently across jobs, I can see the value especially for repeatable scopes.

Just need to understand how it’s practically applied day-to-day.

@Todd a short walkthrough would definitely help 😂

I haven't started with ZZ yet but I'm guessing it would be used similar to material cost centres / building stages etc. In PS, I had a use for Cost Code doing exactly that. By the time the estimate is done, you could then orientate all the items in the take off (via reports) into the appropriate cost centre and filter for the sake of ordering when the job was won.

I use SKU in a couple ways right now. I'm still working on building my assemblies and formulas so that i can get close enough results to our excel sheet right inside of ZZ instead but here's what I've got so far. We're a solid surface fabricator so a lot of what we do is counter tops. The below assembly is what I've come up for that. The one thing that ZZ does not currently allow, which IMO needs to change is see all those "material" items labeled "MAT."? They have to be changed 1 at a time. What reallllllly needs to happen is to be able to ctrl+click a bunch of them > right click > update properties then set the product once and have it populate through every selected material item.Would be a huge time saver....

Every labor item has "Labor" in the SKU like this

and every material item will have the product list/product drop down chosen, which automatically fills in the SKU/description/cost based on the selection. This is done by properly formatting your product list when you import to ZZ

same thing with substrates..

So what is the point of doing all this? This is how it comes out in the report screen when sorting by SKU

Also not related to SKU, but inside my area take off template I have a bunch of custom properties that everything below the area take off references for thier own formulas. That's why I have my assembly set up as everything being a child item of the area

Haha I actually use sku and not description because it’s shorter to reference with tags