Adilas Key Contributors:

Steve Berkenkotter - Main owner and business partner - original ideas, concepts, and training - sales, relationships, dreamer, visionary, custom code, coordinator, builder of the first industry specific skin, and the list goes on. Huge player in the adilas story and timeline. One of the original owners in Moring Star Automotive - where the system came from. There are three known Steve's in the system notes. Most of them are this Steve (99 out of 100 times). He won't admit it, but adilas was his brainchild.

David Berkenkotter - Steve's brother and business partner in Morning Star Automotive. David was a system user and helped us create the adilas quick search. He liked using that feature, the quick search, but it only existed on one page originally. He wanted us to put it on every page. That ended up being in the header. He was also one of the original partners in adilas. Power user in the system. Sadly, he passed away due to cancer.

Shari Olin - Commonly known as "Shari O.". She worked in the accounting department back in the Morning Star days. She has been somewhat of a mother hen to help all of us crazy chickens keep going. She helps with customer support, training, payroll, bill collection, and tons of backend office functions. Major power user. Just being silly, but she can have the mouth of a sailor but the heart of an angel. Part of the adilas admin team and a great friend.

Craig Leitner - Also part of the original Morning Star team. Craig was the automotive floorplan and bank guy. He is a power user in the system and does a lot of bank reconciliation and other tasks. He currently works with Steve and asks as the adilas controller (money flow guy).

Cory Warden - Originally an adilas rep and consultant. Cory become part of the team after being a rep for quite some time. She helps with customer care, client support, project management, and keeping the team on track. She also does all of the news and updates and other training material. Cory does tons of oversight type services for our clients. Power user and part of the admin team.

Sean Carlton - Sean was a manager at a Cannabis dispensary in Colorado that used adilas for years and years until they sold. Steve recruited Sean to help with sales, deployment, and training. Sean brings lots of usage experience. Often, he is one of the helpers if we need to send someone onsite to help with a deployment or training session. Power user.

Brandon Moore - I'm one of the guys that writes most of the developer's notebook entries. Originally, I was hired by Morning Star, the automotive dealership, to help with data entry, accounting, and website stuff. I ended up being one of the main adilas developers and architects. I build content, write code, help other developers and team members, and help with training. Helped start the project back in 2001 under the Morning Star name.

Chris Dunsey - One of the first adilas interns (developers). Helped with a number of projects. Ended up being somewhat of a consultant later on.

Shawn Curtis - Kinda a funny story. He was taking a developer's class at Bridgerland. He knew my brother Russell. He asked to join our developer class and became one of the first interns along with Chris Dunsey. Shawn ended up helping with payroll and other projects. Some of the photo galleries in the system came from Shawn's help. He also worked on the media/content (file upload) pieces. Later on, he did more payroll work and acted as a buddy to Brandon and did some consulting work. We worked together for years and years.

Russell Moore - Russell is my younger brother. Originally, he was added to the group because of his graphic skills. He ended up being a great backend developer and project manager. He has also acted as a trainer and mentor for Brandon along the way. Much of the current system came from projects and efforts that Russell was involved with. He has also been Brandon's AI tutor in recent years. Great help to the system. Huge contribution.

Chris Johnnie - He is an entrepreneur who teamed up with Russell to help create a company called "Adilas For Business" or "AFB". Eventually, both Russell and Chris sold their pieces back to adilas. They were honestly the first ones to really try to run as a white label of adilas. This was back in 2015 and 2016. Chris really helped to push the product to the next level along with Russell's help.

Danny Shuford - Longtime friend of Steve's. Danny helped with some website design, sales, and videos for adilas. He even got into creating custom PDF labels for clients. Light development work.

Marisa Shaw - She is Danny's daughter. Danny brought her to an adilas training event in Denver, CO. Marisa was the star student. She ended up helping with some graphics, flyers, marketing material, teaching, instruction, and planning. Power user. Very helpful.

Shannon Scoffield - Shannon is Brandon and Russell's sister. Her maiden name is Shannon Moore. Huge help and virtual assistant to Brandon. She has helped with training, project management, and content creation. Most of the major content sessions were or have been with Brandon and Shannon working together. When they, Brandon and Shannon, were traveling, Shannon was one of the primary adilas instructors. If she was teaching Brandon was taking notes. If Brandon was teaching, Shannon was taking notes. Power user.

Cheryl Moore - Cheryl is my mom. What an asset. She owns a small business and has owed a few different ones. When we were doing training sessions, she came to every one of them. She asked wonderful questions and was a great supporter. Sometime, I would use her as a test subject - can my mom do this? If yes, we are good. If not, we may need to keep tweaking it. Thanks mom!

Wayne Moore - Wayne is my dad. He was my hiking buddy and more than willing to talk about ideas and concepts on our walks and hikes. He helped out with video stuff and was a great coordinator for making other connections. He worked at Bridgerland (technical college) and helped us get setup with classrooms, computer labs, and other great connections. Huge cheerleader! There is another Wayne, Wayne Andersen, he is a backend developer, systems guy, and database guy.

Wayne Andersen - This Wayne lives in Portugal and helps with all of the backend security, server, and code testing. Major skills, writes code, helps push all of us to new technologies, partially retired but loves to play with tech stuff. If you search for Wayne and it deals with concepts and coordination stuff, that's my dad, Wayne Moore. If you search for Wayne and it sounds like a master backend guy, that's Wayne Andersen.

Alan Williams - One of the lead developer's at adilas.biz. Alan joined us in 2015 and quickly came up through the ranks. Trainer, CTO, team lead, master developer, prototyper, and system architect. Alan has helped with many projects and features over the years. He also helped Brandon with some of the prep work for the adilas lite (fracture) plans and project. Sometimes called "Dr. Alan" by the other developers. Example: This might be a project for Dr. Alan.

Bryan Dayton - Bryan has been one of the most versatile guys on our team. Originally, he joined a development class out of curiosity. He and Brandon live in the same town and know each other from church. Bryan has done more custom code or small system projects than almost any other developer. He also joined the team in 2015. He helps with sales, custom projects, pushing on projects that he thinks will yield a return. Lots of work on the adilas lite and fracture project. Very hard working and versatile.

Dustin Siegel - Developer who helped with numerous cannabis and cultivation type projects. He worked directly under Steve to help with that business vertical. Many of the original pages that Steve built were taken over and remade by Dustin.

Eric Tauer - Developer and custom code guy. Originally, Eric knew Steve and lived in Salida, CO. As a note, adilas is Salida spelled backwards. Eric has a background in database work and data warehousing. Eric has done tons of custom systems for clients. Often, Eric would pioneer certain features or logic, as custom code, and then we would bring those features into the main adilas application.

Garrett Kirschbaum - Adilas intern and then full developer back in 2015. Stressful time of building and expansion. He and others helped run the adilas shop with Brandon's help. Garrett was a great developer and helped us standardize a number of tools and features. He was the first developer to work on sub inventory, back in the day. He also did other projects and helped with some developer management stuff.

Charles or "Chuck" Swann - Charles was an instructor at Bridgerland for web development. He builds custom websites, does amazing mock-ups, prototypes, and is a CSS master (styling a website using code). Chuck worked with Russell to help with redesign work, projects, and vision. Chuck worked fulltime for a number of years and now works and coordinates work done by a small hand-picked design and development team. Anything that needs some design loving gets passed over the Chuck and his small team.

Steve McNew - Friend of Steve Berkenkotter's. This Steve helped prep some whitepaper documents to help with getting adilas standardized and some internal audit type stuff. Mostly white papers and putting things down on paper. He ended up getting hired by the local school district and wasn't able to finish the process, but he got it started. He asked some great questions, and we had some good conversations.

Abby Elkins - Abby is Brandon's daughter. Her maiden name was Abby Moore. Abby, when she was little (10-12 years old) helped with some of the original concept artwork for adilas. Later on, she helped with content for the presentation gallery and then the adilas lite plans (fracture). Currently, she is working graphic artwork for different adilas pages. She's now in her mid 20's and has some awesome art and content skills.

Aspen Moore - Aspen is Abby's younger sister and Brandon's daughter. Aspen helped Brandon with some planning and counseling (mental help). Aspen also did some general business consulting with her dad Brandon.

John Maestas - Developer, backend server guys, and designer. John came to us through Dustin. John was uses as a jack of all trades on the backend and frontend. He did numerous projects, documentation, payroll, and page redesign projects. John was also very help to Brandon in working on the notes and comments on the SWOT analysis document. Many other projects as well. Good vision of the future.

Kiva Berkenkotter - Steve's wife. She helped Steve with various projects and planning sessions. At one point, she was in charge of paying commissions and collecting monthly reoccurring payments. Huge supporter to Steve!

Heather Moore - Heather is Brandon's wife. What a trooper. Cheerleader, support, ideas, and consulting. Huge asset to Brandon (me). Thanks Heather!

Jonathan Wells - Designer and mock-up guy. He helped to map out the system and created a number of deep mock-ups for adilas lite (fracture) projects. Great job catching the vision and putting those pieces into a visual representation. We still refer to his work when talking about fracture (future project for adilas).

Jonathan Johnson - Business consultant from Epic Enterprises. Met with Brandon and Steve in end of 2019 into 2020. Really helped us see some needs and opportunities. Later, helped Brandon with some other consulting when trying to define the fracture plan.

Calvin Chipman - Windows software developer. Calvin also did a bunch of web-based work, database stuff, label printing, and API socket stuff. Calvin was the first developer to use the adilas API's to create a native mobile app for a client. He also built a number of special developer tools used by some of our team to speed things up. He's the tool guy!

Cody Apedaile - Bryan Dayton's cousin, Cody helped with a bunch of JavaScript code and changes. He also spent some time working on the UML diagram for the adilas database. We didn't get things finished, but he was working on a new build your own interface (custom to you) for adilas. We ran out of funding. We want to get back to that project at some point.

Dave Forbis - Dave was the official "high tech gofer". He did a bunch of things. Graphics, project management, brainstorming, planning, sales, and helped with managing developers for the adilas shop. He was another great student. He came to a number of training courses and brought so much to the courses. He was also a big support to Brandon during some rough times.

Josh - There are three Josh's. Josh Wheeler, Brandon's friend and developer. Josh Sagert, developer and adilas user (worked tons on the discount engine), and Josh White, Steve's friend from California. Josh White has brought us a number of bigger leads and bigger players, like franchises, and other higher-end clients. Anything recent is Josh White, from California. He helps with networking, sales, and dreaming of new things.

Suzi Distelberg - Sales, training, and deployment. She also worked with some custom projects and doing step-by-step user guides. She has helped with all kinds of projects and even gone onsite for setups and training. Great asset!

Kelly Whyman - Kelly is Dustin's wife. Kelly was single handedly the best independent sales rep that adilas had. She did training, consulting, and sponsored a number of custom projects. Kelly helped Steve and Brandon with reports, functionality, and other things. She got so good at things, state contracts snagged her up to work at state and multi-state level stuff.

Molly Hennessy - Molly was another independent sales rep and consultant. She had numerous clients and got into doing SOP's (standard operating procedures) and other high-end documentation and training. Molly was an entrepreneur and even started creating some of her own product and services. If you search adilas on google, some of the other results are from Molly. Super creative and a great consultant.

Hamid Karbasi - Developer - He has worked with Brandon doing small websites, training, and small tasks. He currently is a manager at a retail store and brings some managerial type skills to the table. Willing to talk about concepts and how they apply to retail and other environments. He is also lightly helping with some planning for fracture.

Gene Spaulding - Friend, entrepreneur, and businessman. Gene is an old college friend. We had a number of friends in common. He has been a small mentor to me over the years. Way back, before adilas, he helped me get my first business loan for a project that I was working on.

Sharik Peck - Friend, entrepreneur, public speaker, physical therapist, and businessman. Good influence and mentor in ways. Sharik and I used to exercise together back in the day. Many of fun walk, run, and weightlifting session. Learning some conference and training skills from him and his wife. They have done really well pushing their product lines and doing some marketing. Trying to get some ideas.

Bridgerland Technical College - Use to be Bridgerland Applied Technology College. Not a person, but a huge help. This is a local technical college in the Logan, UT, area. Brandon's dad, Wayne, worked there. Tons of assets. They provided classrooms, training options, computers, and even an small incubation spot (starter office space) for the adilas shop during the startup phase. Huge asset!

McCorvey's Pro Shop - Also known as Bowling World. Client that had multiple locations. The started out with around 30 and grew up to the 90+ location level, all using adilas. Long time client.

Emerald Fields - They were the first client that wanted their own fully dedicated box and server. They had multiple locations and requested some custom code, reports, and features.

Beaver Mountain Ski School - Client that we helped them track their ski school (snow sport) lessons. Students, instructors, classes, and schedules. Custom interface dealing with elements of time and flex grid.

Bear 100 - This was the first event or annual event client that we did. They used the system for about a week each year. They had 350+ runners and their families that would be on the site for multiple days straight. It was a 100 mile running race with 13 aid stations and a small social portal for the family and friends to watch their runners. This one was special as it had custom input options to upload CSV files to populate the database vs normal HTML form field entries. Records were sent in batches from remote places to adilas for storage and race progress.

High Valley Bike Shuttle - Online ecommerce and scheduling client. They also have a cafe and small retail store. Fun online scheduling and bulk flex grid projects.

Herbo - Mike Roundtree, owner of Herbo, was the first company to do a small white label of adilas. Mike has been a great asset to Steve and the two of them have worked on projects, plans, and dreams. Herbo also has a custom payment solution that they are trying to market and get rolling. Mike has been a great supporter for years. He is also a certified CPA and that credential helps us and him. We would like to get other CPA's on board as well. Thanks Mike!

Nxtlinq AI - AI assistant. These guys really pushed us to get an AI agent inside of adilas. Tons of development took place and lots of prep stuff. We wanted to do a 3-part plan for integrating AI. 1. Teach it how to navigate using the AI quick search (check - done), 2. Teach it all things adilas. and 3. Teach it how to be clear up at the consultant type level. We only got the first phase done. Lots of other plans and such, but we ran out of funding.

Grok AI - Steve loves using Grok. He has built a number of image generation options inside of adilas. He is also working with Grok to feed it data to help with analytics and AI insight. This is not finished yet, but we may end up using Grok as an AI assistant inside of adilas. We have simple and emerging connections available right now but need to really polish things up before going live with the AI assistant options.

ChatGPT AI - We have started using ChatGPT to help with code, explanations, explore resources, planning, and help with training and flow for people and other AI bots. Currently, Brandon, Steve, Bryan, Alan, Josh, Russell, Chuck, and Wayne are using AI in either ChatGPT chat sessions or some other form of AI. We have some using Copilot, Gemini, Claude, etc. AI is actually helping in many ways. ChatGPT is a big one for use. Anyways, they are earning their place in the adilas key contributors list.

There are so many more that I can't list. Developers, users, power users, reps, consultants, trainers, clients, accountants, friends, family, and even critics. They have all helped out the idea farming process and progression. Good stuff! We couldn't have done this alone. It takes a community to do what we are doing.

Debugging session with Eric. We were looking into a bug on credit card processing and how that relates to the new gift card code that we pushed up. Looking into the flow and process of our existing merchant processing code. We got on a call with Missy from McCorvey's Pro Shop - bowling world - and chatted with her about for a bit. She gave us some info and we went into the system and looked around. We then ran a number of pages through a code diff (what is different per page) and actually found a small typo error. We fixed it, made the changes, and pushed up new code. Hopefully that will fix the problem as we couldn't duplicate it. We checked a bunch of shopping cart checkout pages and credit card processing pages. Everything else seemed to be working fine.

Two different projects. One was expanding the max character length for customer and vendor searches. Took off the old max of 4 characters for the searches and opened up the fields to allow for unlimited characters, in the search field. Pushed up code and let Michael Webber from McCorvey's Pro Shop (bowling supplies) know about the new change. He had requested an increase there on those pages.

Fixing some data for Cory. 710 Labs had one sub inventory item that got double booked. Made a backend data change for the client. This took about 45 minutes to find it, change it, and make sure everything was good to go.

We had a request to up the max character count for the customer search - when creating a new invoice. I wrote back (to Michael Webber of McCorvey's) about the advanced search and the quick search. Those exist right now, maybe we could up the max to 10 or 12 and it would help out. Just a thought! We have had other requests to do the same thing. People feel limited by the 4 character limit.

Here is what I wrote in the email back to Michael:

Good afternoon. Thanks for the note and the request. Please see the attached image and screenshot. I added some notes to help you out. The answer may be a slight retraining of your guys and gals. There is an option, right below the existing one, that has all of the power that you are requesting. You only fill out the info that you want, leave the rest blank. Both the simple and the advanced searched go to the exact same search results place.

Please try that out and see how that works. Another free option is to use the quick search. There is no limit using the quick search. The only thing that it can't do is blend first and last names. For example: You could totally search for "Webber" or "Michael" and it would find you. However, if you tried "Michael Webber" it won't be able to match that up with a database record because both Michael and Webber are stored in different database fields. I hope that make sense.

The quick search is super powerful and has tons of options that you may or may not know about. Here is a quick and simple help file with some tips and tricks for using the quick search.

Web link - help.cfm?id=376&pwd=quick

////////

Small update on 7/27/22 - Michael wrote me back via email and requested that we remove the limit. We decided that it was a good idea and took off all of the 4-character limits on the fields for both customer searches and vendor/payee searches. New code and changes were made and pushed up to all servers today on 7/27/22.

Danny and I touching base. He feels like we need to focus, in order to be more productive. We tend to run around with our heads cut off and virtually change direction at every gust of wind. We are trying, but we do lack focus sometimes.

I did some permission review for a client. I then had a meeting with Kristi from McCorvey's at 9:30 am. We covered some stuff and I told her that I would send her some links to some of the snow owl theme documentation and videos. Currently, they are still using the classic themes inside of their adilas accounts.

Here are some news and updates dealing with snow owl themes:

https://news.adilas.biz/2017/02/20/snow-owl-theme/

https://news.adilas.biz/2017/03/03/snow-owl-custom-colors/

https://news.adilas.biz/2017/05/15/snow-owl-templates-and-more/

Steve and I worked through some questions that he had on some code. After that, we started talking about marketing ideas and small pieces of the sales plan (up and coming plans).

Proposal for all that want to sell adilas

- Old whole message - how do we sell the model that we have right now?
- So many people say - we can't sell it, it needs to be fixed
- What are we focusing on...

- Some salespersons need the wagon loaded for them - almost after the fact sales vs up front sales

- Side note, we are gaining control on the custom code stuff. We want to do the same thing for sales.

- If people want to play, game on. If not, we'll get the next one.

- It is what is... (meaning the system). We can build it out to your specs but that is by quote - pitch some of the other services.

- What do we tell to the salespeople that is available (our current offering)? Sell what we have. It has value.

- A good problem to have is - how many new clients we need to setup.

- McCorvey's is one of our poster child type accounts
- A stud who takes care of the whole thing
- Mel and Tish were the salespersons, but they didn't do any of the real setup

- Salespersons don't need to know too much... enough to play the game

- No contract - minimal risk

- $1,000 simple start-up - that could cover, setup, some light training, 1st month, and some custom code and/or data import

- Selling is telling - get the word out. Not everybody likes strawberry ice cream, but some people do.

- We have people wanting to help with setup, but they don't like to do cold sales.
- We keep trying to force these setup and consulting people to be salesperson but they aren't that person.

- We would like to get a full sales force... we could sell the opportunity to sell adilas to other salespersons... It is all about potential and realizing that potential.

- Sell the vision

- Pricing - we need a basic model with enough to cover the salesperson and the house

- What is produced on a sale... that we could share with those who are helping the process
- Bird dog fees - one time deal
- Monthly reoccurring - able to share that with the salesperson
- Commissions based on participation
- just talking about this... hourly vs commissions - hero to zero or zero to hero - leaning towards strictly commission based

- On sales and a sales force - full commission based doesn't cost us anything

- In real estate, they have to pay a broker fee to play the game (where are you hanging your hat) - basically, charging for the opportunity (taking care of the house) - We, adilas, have time and energy in this as well. - We almost want the persons to either fly and thrive or weed themselves out and move on.

- Pitch the opportunity to make reoccurring revenue - Sell it once and then reap and reap (harvest that effort).

- Bonuses, games, and other stuff

- We've got to have salespeople on our team but we can't force non salespersons to be that salesperson.
 
- There is an old sales opportunity flyer... Maybe look at that and revamp it and/or pull some pieces from there

Tech support and helping to fix a custom page setting error dealing with 2nd vendor/payees for PO's and expense/receipts. Pushed up new code. Emails to other developers and sending some new setup info to Michael Webber with McCorvey's Bowling World. Michael did some work for us back in 2012 and will be helping with an upcoming project. Good stuff.

Random notes from the day. Brian Stewart is a friend and 30+ year computer guy and programmer. He works for a different company but we go walking and hiking together in the mornings. We talk business and code while we walk. Here are a couple of gems from today.

- There is a difference between working in your business or working on your business - Brian Stewart on a morning hike.

- Create systems... Instead of setting pass/fail goals... create a small system and then start playing the game. Success is playing the game and working the system. The results will usually end up following. - Brian Stewart on a morning hike.

- Brian and I spent quite a bit of time talking about good cop, bad cop, and helping to setup the community and environment that you want for your company. A lot of the discussion was dealing with finding that balance point between speed, function, stability, and beauty. Not everybody has the same personality and/or skill sets. Lots of mixing and blending. Some of the conversation was how to mix senior developers and junior developers and to help them play well together. Sometimes that mixing becomes an issue and also a who gets credit for what and who gets paid for what. Sometimes a tough mix.

On the morning meeting with Steve, Dustin, Alan, and Josh. We started out and got things going. Dustin is going on a trip soon and was reporting about some areas in the North East that he will be visiting. Sounds fun. Here are some other things that happened on the meeting.

- Helping Dustin with some FORM logic. He has a ton of form field data that needs to be dynamic, grouped, and passed over to an action page and still be able to maintain its complex data format and maintain its special groupings. We went through a number of scenarios and he took a number of screen shots. We talked strategy and I showed him some similar code that is used for duplicating PO's and passing dynamic data from page to page.

- Talking with Alan about the idea of on purpose allowing the view of the pages to fracture and be more controllable. We did a small graphic (drawing) and talked about how we have known form field values. We also have a known database table that could hold the data field settings such as show/hide, defaults, data types, special instructions, sort values, field name aliases, etc. We then talked about how we could potentially use ColdFusion custom tags to hold the logic to dynamically populate and/or build the HTML (web format) pages based on the custom tags. The custom tags are a combo between a function and an include. Anyways, we had a good discussion on that. Alan was saying that this plays in perfectly to the MVC (model view controller) type scenario that we would like to use. See attached for a small drawing.

- We had two other outside parties come into the meeting. We had Molly (an adilas consultant) and a guy by the name of Ryan McCorvey (a user for McCorvey's Pro Shop - Bowling). They both had similar requests. They have different pages and reports (or functions) that are hitting time outs. Both companies have tons of data and Alan and I were taking notes and looking for possible bottlenecks and either slow queries and/or slow database tables. They could do the same reports and actions with small amounts of data, the system just choked and/or timed out when trying to process too much data. Kinda like getting a huge mouth full and not being able to chew and/or swallow. Anyways, we worked with both individuals and took some notes. Alan started looking into some research on what causes those table level slow-downs and what not.

- As we get into bigger and bigger datasets, we have to play well with scalability, indexing, and being able to play the big data game. Interesting how things keep progressing.

Morning GoToMeeting

I was working on sales tax expansion project for Kelly - tying in the tax by customer type stuff.

Alan and Steve were working on some Leaf Data and Metrc API stuff

Russell and Steve went over the new WordPress news and updates section (adilas university, help files, media/content) for adilas features and such. Lots of good ideas and what not. Good meeting between Steve and Russell. Lots of questions and answers.

Michael with McCorvey's Pro Shop jumped on and chatted with me on some needs that they have. Below are some bullet points from the conversation:

Indiana - need this asap - county specific

North Carolina - I didn't know about that

FUTA - check Florida calcs

Employees clocking in at one store but they really want that value to be split between locations. We talked about departments and how the internal setup goes. We also talked about a combined P&L between multiple locations (across states) and across multiple departments. Maybe relate the employee taxes to where the person lives vs where they work. Somehow we need to combine some hours and maybe even allow for cross bridging of hours between different departments. They would really like to be able to clock in/out at different locations and have the system calculate things properly.

Problem with the cost of goods sold - they get items at all kinds of costs (sales, promotions, bulk, etc.) but they sale things and the system uses the last known cost. That creates all kinds of problems with the P&L.

ICC - internal cost corrections - this is important to do for items and usage under the bridge - bring things back to 0 quantity and 0 costs, where appropriate. This needs to be managed going forward. This needs to be done location by location - per item.

Michael would really like to get some data and the code for the part usage page and inventory adjustment pages - this would be database tables, data, code and page logic and also methods that are used.

Possible black box code for average costs - tied to the add to cart logic - this is a new twist and/or option since we last talked

Michael would really like it built in with a corp-wide setting that says something like - use last known cost or use average cost - this could be huge... it creates a nice alternative for similar businesses.

There size and the number of locations complicates the issue. Some of their managers are paid based off of the percentage (back to the P&L)

Item life cycles - at some point, the product will reach the end and/or die out.