all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||||||||
|
|
|
Yellow
|
|
|||
|
|||
|
|
|
Notes:
|
|
On a GoToMeeting session with Steve. More notes on the QR codes. - They want to be able to put their own SKU or item number on the label. - Steve is allowing them to go to an open package and then populate what they are wanting... (mini preset conversions). They have preset multipliers (0.7grams, 1gram, 3.5grams, etc.). They can then enter amounts and watch to see what the total is. - Steve is recording the number of the presets as a sub attribute held on the sub entry itself. He can then check against those numbers to see how much has been sold and what is still available. - Instead of going subs and sub attributes... what if we break more into a traditional model (one-to-many) and start going vertical vs. horizontal. Create a physical grandchild id, record the weight, the cost, the price, how many made, how many sold, special description, etc. Example: Say PO #27, Line # 4, Sub ~15, Conversion `77 (`=back tick or #=pound). We could then use a QR code that was something like: ~15`77 or ~15#77. - Keep going vertical in a one to many relationship. - On pricing tiers and conversion templates... make these their own free roaming tables. We could then attach them to any sub templates. They exist outside (so we don't have to remake them over and over). We could then attach them as needed. - Conversions will need rules, setup options, verbage, and conversions that allow back and forth traffic. Steve was calling conversions - never land - off in the clouds. - We need to track cart status, quote status, and reserved status. See attached for a simple drawing. Here are some notes. The ~15 is the sub. It is in grams. The `77 and `78 are conversions. The m is for made, the s is for sold, the p is for price, the q is quantity (in grams - same as the parent), a visual unit of measure, and possible pricing rules. Along with that, we also talked about tracking the cart status, quote status, and a new one called reserved (who else if asking for it) status. - We really need to get into sub categories before we get into smart cart logic. This will then make it easier for sales, promotions, campaigns, etc. - How will loyalty points and coupons play into this model? Build the whole system out and let the computer help solve the problems. The loyalty points need to be as automatic as the pricing tiers. Think all roads lead to the same virtual outcome. Mix and blend as needed. - The end goal is the employees scan the item and it knows how much, what, where, and when... Lots of one to many relationships. - Along with this... we will eventually need to look into custom labels. Track _x and _y coordinates, custom verbage, auto feeds, dynamic mapping, etc. Logos, backgrounds, symbols, hard coded stuff, conversion stuff, and pricing tiers. - Conversion land... You may be required to label with a QR code so we could track things back down. We may need to nail down conversions before we get into custom labels. - This may bring things into the 3D world building level. _x = time, _y = resources, and _z = stacking and layering. Conversions and labels might be part of the _z level or Z axis. - We are also seeing more need to track things via RFID tag and other digital models. - Doing conversions... we still need to figure out how to show this on an invoice, quote, and/or cart. We still may need to get into more smoke and mirrors (hidden fields, hidden lines, visual quantities vs actual quantities, etc.). We have lots of other brainstorming ideas and notes on this. Check here in the shop, in adilas, and in the adilas university. - On a different note... What about a cash drawer reconciler? We could add a new placeholder inside the cart struct and populate it with some kind of setting or something. Tie it to the login. It will change on a daily basis. We would then need to look at a way of recording this on the deposit or invoice payment level. We may also have some options based off of users, banks, and other things. This gets into sub locations or more Z axis layering and stacking. - tie the deposits to the drawers. This could also include over and short options if off. - small idea on the cart... if you need drawer management, maybe have a watcher on the view cart page that prompts for a who are you and what drawer. We could keep some of this stuff in the session scope so we don't have to prompt each day. Another option might be to have an assignment where a drawer could be assigned to one or more users per day. Kind of a management tool. If yes, it could look it up and record the values based off of the management tool. |