Danny and Steve were chatting and checking in on the message marketing options and what the next steps are going to be. We talked about a small little mini app that would be native to the client's phone or device that would ping the correct servers for the correct client id and any possible message marketing options. We talked about making it native for android and iOS (apple). We drew out some ideas and concepts.

Alan had some questions about sub inventory and adding new custom and automated logic out in ecommerce land. We went over all of the different fields and the data that we record and store per item (part number), per parent line item (invoice or quote or PO line item), all sub inventory values, and what options we have there. Alan was lightly proposing a change so that the main time sub inventory tables would just hold the packages (main lot, batch, or package info). We would then build another table to handle and track the sub inventory transactions in a new table. Currently, all of that is done in one table, but it expanding and somewhat bloating the table. Lots of talk about ideas and options and timing.

We are not planning on jumping on this project right this minute as we have some other fires and things that we are working on. When ready, we will circle back around and check things out. I also mentioned to Alan that we need to make these tables easy to get data into, easy to pull reports, totals, sums, and also be able to go (virtually) backwards in time based on dates. We also talked about histories and the need to add histories in for sub or child inventory. Quite a bit of talk about some future plans, including adding some more backward compatibility options and look-ups for the custom data tables (sub string, sub numbers, and sub dates). Currently, we can get the data into these tables pretty easy, but searching them requires lots of joins and virtual jumping around.