Grid inside a grid?

Help Center Get Answers
1

I have a complex, and very large inventory. 35k currently, 15k are duplicates

We have the titles of products which include a lot of the same part numbers in said title with some slightly different keywords because there are a lot of inter-compatibilities. I’m building this predominately to manage Inventory but would like the functionality later on to price products quickly based on predefined groups. The duplicates are done for Customers peace of mind. So they can match it to their product to theirs and purchase. The downside is this makes it very difficult to re-order inventory. When we go to order and try to identify what we’re ordering FOR we have ~10-50 different product titles to chose from all with different sku’s, details and sometimes even pricing. Technically all of them will work but its messy that way and we only need one in inventory to satisfy all of the possible orders.
So my idea is to organize my inventory where we have ONE product part number that will have the different product titles/skus/prices INSIDE of the details page. My concern is, how can I structure this in order to have the least amount of records possible, without duplicating information and wasting record space. Also, in order to change all group prices quickly and to be able to search for sku’s without having to find it’s parent part number. When changing prices, i’ll likely be using excel but using knack to do that would also be very cool.

So:
Currently the inventory is structured like:
Product A title part number 456456, Sku: 00019753, price.
Product B title part number 456456, Sku: 00019754, price.
Product C title part number 456456, Sku: 00019755, price.
Product D title part number 456457, Sku: 00019756, price.
Product E title part number 456457, Sku: 00019757, price.
Product F title part number 456457, Sku: 00019758, price.

I’m trying to make it more like:
Part number(456456):
-Product A title 456456, Sku: 00019753, price.
-Product B title 456456, Sku: 00019754, price.
-Product C title 456456, Sku: 00019755, price.
Part number(456457):
-Product D title 456457, Sku: 00019756, price.
-Product E title 456457, Sku: 00019757, price.
-Product F title 456457, Sku: 00019758, price.

Again, the reason for the change is to make re-ordering inventory easier.

2

Not exactly sure of your situation, of course, but…

For visual purposes you could have a grid grouped on the Part Number field.

However, it sounds like you want to streamline this a bit (i.e. normalize the data). In that case you will need two tables - Product Title(?) and Products(?).

The parent table would be like: Part number(456456)
The child table would be like: Product B, Sku: 00019754, price

Something like that perhaps.

1 Like
3

The Grid grouped on the part number side sounded like a great idea! Unfortunately I think it would still give me the duplicate listings. Streamline? Yes, pretty much, just trying to reduce the “overwhelming” amount of data that comes at you when reordering inventory. I think creating a second table with all the part numbers alone is inevitable sadly. I can’t find any way around it.

4

It’s guess work trying to figure out your situation from here, but it still sounds to me like you need to normalize your data.

If your not familiar with data normalization, click this.