Steve and Eric were having some discussions about the existing data model. We have some companies that are small and totally fit into our existing model (single corp with multiple locations under the same tax or EIN number). We are seeing some crazy stuff between bigger companies that have multiple corporations and virtually want to have sub corporations under that bigger umbrella (consolidated reporting, cross-corp look-ups, master/sub type levels, etc.). Steve and Eric were talking about master corporations and then having sub corporations. It gets into rules, permissions, and the flow of the data.

The topic sort of came back around to getting into aggregated data and being able to pass data back and forth between corporations (internal API sockets). Steve really liked the concept of a "master corporation" to hold high level things like global items lists, global part category list, global customer types, global customer/client lists, loyalty points, certain rules, consolidated reporting, high level financials, etc.

After that, Steve wanted to see some code to do some internal API socket stuff. He has a cross-corp report that needs data from two different servers. As a side note, that complicates things even further. Instead of just saying - I need data from all of these corps... you are virtually saying - I need data from this corp on this server and these corps on this other server and I need to pull it all together into one report. I spent some time looking up some code samples.

Wayne came on was asking some questions about a 3rd party solution that is trying to get super deep and looking into building out both a payment solution and an integrated but external ecommerce solution. It is crazy to see how every conversation keeps turning back to access to the data - basically, how can I plug into an API sockets and get and pass data back and forth. Very interesting.