In my case, the Locations/Warehouses change frequently, so the way to summerize the stock levels is very impractical for me since you have to add and delete columns each time
Great video Julian. Thanks for sharing. I am following along with your videos to build out an inventory system that has parts that are bundled into products. I am in the process of trying to add inventory store locations to the system and am running into a problem. I am set up to enter sales in an order table, that links to a customer. The orders resolve to a Products Sold table that lists all individual line items. Those line items are then connected to my "Parts x Products" junction table that provides a "Line Item Quantity Sold" for each part. I subtract "Line Item Quantity Sold" from "Total Parts Received" to compute an "In Stock" quantity. I understand how to Receive parts and identify specific locations. However I'm having a bear of time trying to figure out how to define/record where those parts are coming from when a sale is made. Is this an overly complicated situation...or I am just making it so? Any tips or insight would be appreciated.
Hi Julian! Thanks for your great videos. I've been following along your series on building out an inventory system on Air Table. Thanks for sharing. In following along on this video, I'm running into a problem. I have table "Parts" that are assembled into table "Products" using a "Parts x Products" junction table. I record inventory reductions through "Orders" table that links to "Customers" table. When I record an order, line items are created in the "Products Sold" table, which is then rolled up into the "Parts x Products" for a total "Line Item Quantity Sold". I have crated a "Locations" table and can successfully add location to parts when I enter them in the "Parts Received" table, but cannot for the life of me figure out how to reference the location of parts sold for computing in-stock quantities for specific locations. Is this a simple situation to rectify or am I overly complicating the situation somehow? I appreciate any guidance you can provide.
Hi Paul, trying looking over this discussion to see if it's helpful: community.3rings.co/t/how-to-set-up-an-inventory-system-if-you-have-multiple-locations/26/6. If not, you can schedule a call with me to discuss (through my website). The first 30min call is free
@@julian_post Thanks for the reply Julian! I looked at the discussion and it was helpful in better understanding the challenge. I solved my problem by adding an additional table for Assembling Products and better organizing my data. I added an "Assemble Products" table to record the transfer of parts into products. Parts locations are defined in the parts table. Products locations are defined in products table. Total parts inventory is the sum of (1) Parts In - (non-sale) Parts Out and (2) rollup of Parts x Products (from junction table). In the end, I think I was trying to do too much in the Parts table and didn't have a clear understanding of the simplest path for data flow. Using the Data Schema Extension was also incredibly helpful in making the data flow as streamlined as possible. Thanks for introducing me to that. Keep up the great work. I'll be sure to watch your other videos to better master AirTable.
In my case, the Locations/Warehouses change frequently, so the way to summerize the stock levels is very impractical for me since you have to add and delete columns each time
Great video Julian. Thanks for sharing.
I am following along with your videos to build out an inventory system that has parts that are bundled into products. I am in the process of trying to add inventory store locations to the system and am running into a problem.
I am set up to enter sales in an order table, that links to a customer. The orders resolve to a Products Sold table that lists all individual line items. Those line items are then connected to my "Parts x Products" junction table that provides a "Line Item Quantity Sold" for each part. I subtract "Line Item Quantity Sold" from "Total Parts Received" to compute an "In Stock" quantity.
I understand how to Receive parts and identify specific locations. However I'm having a bear of time trying to figure out how to define/record where those parts are coming from when a sale is made.
Is this an overly complicated situation...or I am just making it so? Any tips or insight would be appreciated.
Yes you can do that!
Hi Julian! Thanks for your great videos. I've been following along your series on building out an inventory system on Air Table. Thanks for sharing.
In following along on this video, I'm running into a problem.
I have table "Parts" that are assembled into table "Products" using a "Parts x Products" junction table. I record inventory reductions through "Orders" table that links to "Customers" table. When I record an order, line items are created in the "Products Sold" table, which is then rolled up into the "Parts x Products" for a total "Line Item Quantity Sold".
I have crated a "Locations" table and can successfully add location to parts when I enter them in the "Parts Received" table, but cannot for the life of me figure out how to reference the location of parts sold for computing in-stock quantities for specific locations.
Is this a simple situation to rectify or am I overly complicating the situation somehow? I appreciate any guidance you can provide.
Hi Paul, trying looking over this discussion to see if it's helpful: community.3rings.co/t/how-to-set-up-an-inventory-system-if-you-have-multiple-locations/26/6. If not, you can schedule a call with me to discuss (through my website). The first 30min call is free
@@julian_post Thanks for the reply Julian! I looked at the discussion and it was helpful in better understanding the challenge. I solved my problem by adding an additional table for Assembling Products and better organizing my data.
I added an "Assemble Products" table to record the transfer of parts into products. Parts locations are defined in the parts table. Products locations are defined in products table. Total parts inventory is the sum of (1) Parts In - (non-sale) Parts Out and (2) rollup of Parts x Products (from junction table).
In the end, I think I was trying to do too much in the Parts table and didn't have a clear understanding of the simplest path for data flow. Using the Data Schema Extension was also incredibly helpful in making the data flow as streamlined as possible. Thanks for introducing me to that.
Keep up the great work. I'll be sure to watch your other videos to better master AirTable.
@@PaulMiller-h5g Sounds like a great solution! Glad you figured it out!
How do you sell the same product at multiple store though?
This allows you to do that! If not in your case, can you clarify further?
@@julian_post How would you show the available stock at each store individually? This will only show total stock between all stores.
@@ScadooshGoat Starting at 3:30, it shows you how to summarize by individual store
Thanks
Welcome!