- Calvin's question... what exactly does this solve? Meaning conversions?
	- they don't want to ballon all of their inventory into tons of new items
	- conversions are somewhat of a smoke and mirrors type interface
	- as an example: say they have 100 items, each one could be broken into 5 different types (we are now at 500 items). Each of the 500 could then be split and blended again and again... where does it end and/or stop? We are hoping that these mini conversion would help us break things up (_z spacing and layering) without blowing things up. Basically, a stacked one-to-many model.

- what about locking of the records and transactional entries

- how many tables are we looking at? one, mulitple, etc

- there is a process that already exists...
	- when it is made, when it is quoted, when it is added cart, when they checkout and pay for it? etc.

- scenario from steve - check in at the front door, you get checked in, they go into a new door (gift shop area), as one of the associates (employees) gets freed up - they let the next person in, the person is now allowed to browse and build a virtual cart (cart and/or a quote), the associate is using buttons to add to the cart, as soon as the person is done - they save the quote. they then make the the payment, in the back the fulfillment person is starting to build the ticket, the counter person restores the cart and turns it into the invoice and takes the payment.

- chain of custody handling is crazy deep...

- they need to label every piece and product - that is huge - this is key and will help with the tracking of the subs, and subs of subs (conversions and micro manufacturing stuff).

- as a side note, the clients are trying to save money so that they don't have to keep buying more and more RFID tags. It kinda comes down to time, effort, and money.

- There is a whole other level with valuts, storage, etc.

- on a side note, there is waste, trim, evaporation, loss, etc. As another side note, we need to help record that waste and/or loss to help keep values straight. This is currently totaly left to the user and is somewhat falling through the cracks. We want to get things into more of a real-time type model.

- we need to open up all of the visual unit of measure stuff into variables and/or open fields.

- We may need a whole new table just to build the conversion matrix. See steve's mini conversion page for building QR codes.

- When they print things... we are currently recording the pieces in the sub inventory attributes. This is kinda a small work around and requires specific verbage, mapping, and tons of sub attributes. We are trying to take some of these concepts and put them into real database tables (rows, columns, fields, etc.).

- We know that there is still a human element in the puzzle. We are trying to help where possible.

- We may want to move away from the print being the only "made" checkpoint. We may want a different checkpoint and/or form entry to record that data. Make it editable and searchable. We may want to take the current print button and push it to a differnet page. Basically, store the data (virtual checkpoint) and then let them print. That way if they have to reprint or whatever, they can.

- on a different note, the verify on the cart is just a verify. We don't need to record that data. This is somewhat of its own little piece.

- small invite to Calvin - we have a platform for reoccurring sales and have a great spot to help sell some of your other tools.

- small side projects such as the emerald fields kitchen (auto print from an API), file monitor, back-up plans, gmexting, label wizard, api sockets, ftp tools, database editors, auto process stuff, etc.

- what if we could setup virtual checkpoints and flow processes? that would be totally awesome.We have other places and pages where we have talked about being able to setup custom flow and checkpoints of sorts. Think of the digital and data assembly line. it would be super cool if you could set it up however you wanted... custom to fit.