all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||
|
|
|
Blue
|
|
||||||
|
||||||
|
|
|
Notes:
|
|
-Tied to comment below – what about recipe/builds, internal invoices, or PO’s tied to stock/units. Just some ideas – maybe part of a build and build recipe or reverse build of sorts. -On stock/units we need the ability to have them produce child inventories (new items or new stock/units) of be broken (chop shop) in to smaller sell-able pieces. Start with something and then have it multiply or divide into something else. (Idea from another associate.) What about renting or borrowing from a master stock/unit? Does it totally go away or are we able to use it again? What does the word sell or sale mean? Brainstorming and recording ideas while cleaning out my email inbox: o On the eCommerce side – we need a customer portal where they can pay for past bills, create quotes, statements, buy new things and get access to custom paperwork or forms. Most of these ideas have been recorded before but the paperwork and forms (PDF, Word, Excel) have not been recorded. o On the label generator – it would be cool if we could make assignments to main application types and then build custom mappings for that type. It would be cool to be able to save these settings and be able to name them. Basically a custom 1-many between application types and fields or values. It may also be cool if you could hard code a value or let the system show an option. What about custom stuff like sized, logo, yes/no, font color, font size, positioning. o We need to make the words “make” and “model” dynamic if using specific units. o The calendar interface needs to be a back drop for any date/time related report, invoices per month, customer birthdays, bills and due dates, etc. o We need a mini calendar app to help on some of the date fields – not required but available. o We have a known issue with PO payments and the balance sheet. It has to do with force payments and how does that effect something. No way of searching, editing, fixing or finding what happened. o We need to circle back around and work on automating sales tax, collected fees, standalone declarations, watchers, feeders, callouts, etc. o On inventory items – we have been asked about multiple categories and sub categories. Currently using either the reference field or the RFID tag field as a text copy of the categories. o We were also asked about a part number grid (grid items) to hold values like red, white, blue, large, medium, small, etc. – attributes. o We have had requests for more flexible “Google-type” searches. These are called regular expressions or we can check for spaces and build our own list or array searches. o Add drill-down links from vendors to all incoming items (lines), all sold items, (invoice lines), all payments made (PO parts or e/r parts), all e/r line items, etc. o When starting a new location – it takes quite a while to get the starting inventory in. The system requires it, the parts inventory, to be entered one at a time. It would be cool if we could do something like an update PO but pull from all inventory items. This could be as simple as a switch or a permission to include all parts in the update or just location specific activity. Anyway, once completed, it would do what we want and setup initial inventory levels. (This whole idea could be done with the duplicate PO tool.) o The more we use the flex-grid, the more we will need ways of getting data in and out of it. The flex grid also needs to be a filter (pre-search filter) for other main application types. o We have a growing need to help manage cash drawers, petty cash, pay outs, etc. o On build PO’s – we need a way to add a new product (with a variable vendor) while in the build PO mode. Currently this is not allowed and requires a user to first prep and create the placeholder part and then go back and use it on or as a part of the build. Basically, they need a live PO to create the item and build PO to use it. It would be nice to have it all wrapped up together in a single step. o We had a request to make the customer log types dynamic per corporation. These are recorded as the customer log reason or subject field. Currently they are held in the contact_types table. All we would need to do is add a corp_id number and an add/edit interface and it could be done. o ICC’s (internal cost corrections), cost of goods corrections, cost differences – this is location specific, date sensitive and according to part numbers, what we need is a 1-many relationship from parts to the corrections. We virtually track what came in (PO’s), what was sold (invoices) and calculate the differences of cost differences between the two. This correction could really help with perfect Cost of Goods Sold (COGS). o On the accounting side, the cost differences would need to play into the P&L or income statement as part of COGS. It would also be cool if they, the differences or manual corrections, would show up under the part usage sections. o We talked about a thing called watchers and feeders for the balance sheet. This could be things like taxes, collected fees, etc. Why not cost of goods sold corrections or differences. It automatically sits in the background and runs logic on items sold vs. items sitting in inventory. This would be cool and would take out the manual portion of this task. If it was virtual, it could be very dynamic but may take more processing power. If it was manual, it would take up more storage space but would be quicker to get to. o What about correcting per location – locations play a part of inventory. o Steve wants to use an invoice depending on whether the cost needs to go up or down. Use a -1 of a +1 on the quantity. Each entry would have two lines. You would then adjust the cost accordingly, pretty creative. The price on both lines would be $0.00. Doing it this way only effects COGS and does not affect inventory because a -1 or a +1 =0 on the quantity side. Pretty cool! General ideas: o We need to go through the application and show/hide stock/unity fields, permissions and settings. This could be kind of a big project. However, it may make the interface simpler. o We’ve had request to be able to clean-up old inventory items. This is twofold: 1. COGS and 2. Quantities on hand. Basically, we need a “sweep the floor” function to get everything in order and then really hide the items on the look-back reports. Even if they are inactive, they still show up if there is a problem with COGS and quantities on hand. (ICC’s - internal cost corrections, see next page for another idea – April 30th entry) |