#Need Assistance with Inventory Structure in Laravel

8 messages · Page 1 of 1 (latest)

clear ridge
#

The quantity must be computed. So normalize your product so that the quanities will be counted per product barcode.

Ex:
Product->productSkus()

So product can have many skus(barcode). And each skus can go into their own packagings(this will also be another model in your system). And each skus will have their own expiration date.

arctic depot
shrewd void
#

This can get very complicated very quickly - in warehouses (which is effectively what your shop is) this is typically segregated out - right from the beginning an inventory record with an expiry date and a location (in your case a shelf location) then a product master record which has a footprint (as referred above) this footprint has many uom records - so in your situation there's always for example:
1EA = $1
6EA = $5
and so on.. in a warehouse this is used for length/width/height but you get the jist..

#

In fact you probably just need product has many detail records (price/size/qty etc in one model) also has many possible eans(another model) - expiry dates should be on inventory records from receipt..

arctic depot
clear ridge
#

you can normalize the product details into a more generic table like the example here in my stackoverflow question: https://stackoverflow.com/questions/78302392/laravel-advanced-search-in-parent-table-using-child-table-values

so Products can have many ProductSkus and productSkus can have many CustomDetails.

This way your Product's properties are more dynamic and can cater to any products.

Stack Overflow
Laravel Advanced Search in parent table using child table values

so i have a products table and custom_details table in my database.
products can have custom_details and their custom_details can be of type number ,date, or text.
each products can have many custom

arctic depot
#

i cant get it to work any other help please

shrewd void
#

which part specifically is not working...maybe some code?