Initial Phase 1 requirements. Phase 2 may include on-line public access and a few other features.
1. The system will provide a means to create; edit; track; and print product orders. 2. Look up customer by: 1) Contact Info.; 2) Owner Number; 3) Non-owner Number; 4) Past Purchases Is customer on file as previous shopper (either owner or non-owner)? 3. The central database will be populated with product data from a POS register system. (ETL) 4. Clean up old "Initiated" orders by researching individually. Delete orders when: 1) older than 14 days and no payment can be found 2) older than one day and customer approves deletion 5. Search products against: 1) Description; 2) customer Purchase history; 3) Brand; 4) Department; 5) Category; 6) Attribute; 7) PLU; UPC; UNFI Order; Shelf Tag; Case Lot PLU/UPC; 8) All fields - OR - Browse by: 1) Purchase history; 2) Brand; 3) Department; 4) Category 6. The system will provide a means to create; edit; track; update status on; and print product invoices. 7. System will provide a method for reporting on and tracking product which has languished in our warehouse past the retrieval window. 8. Create a holding time field for each type of product that we order. Make it reviewable and editable and make it kick off flags to definable email targets when holding time is exceeded. 9. System will generate electronic notifications (such as updates) and hard documents; such as hard copy of orders and invoices; as well as offer a method by which customers can easily contacting staff and visa versa. 10. Create (non-member) account by entering: 1) Full Name 2) Email 3) Main phone 4) Cell phone 5) Work phone System generates unique non-member number. 11. vendor index will be created and maintained for generating item shipping time estimates (and other item deliver factors?) 12. system must have ability to print out paper work orders for customer's use at register 13. System generates emailed status update to customer indicating that order has been placed (and updating the estimated of arrival date?). 14. vendor index gui; whether an imported file with a column or a browser gui to the db; will allow department managers to opt certain vendors out of case availability On Feb 8, 12:29 pm, mdipierro <mdipie...@cs.depaul.edu> wrote: > If you can post some specs of what you need perhaps we can help. > > Massimo > > On Feb 8, 1:22 pm, snfctech <tschm...@sacfoodcoop.com> wrote: > > > I need to build an order-entry and tracking system for a Food Co-op. > > I was excited about using Python/web2py, but I'm struggling with the > > fact that existing e-commerce systems seem to have about 70% of the > > functionality I need. I don't need stuff like shipping addresses, > > postal prices and online features like a payment gateway - at least > > initially. And I think I will need to do a lot of customization - > > complicated discounts for products and members, a store->producer > > order/tracking flow (in addition to customer->store), printing > > invoices with line-item UPCs that can be printed and brought to a > > register for payment, and so on. But all the rest of it is already > > there - product catalog, customer_to_order relations, order status/ > > tracking, (some) notifications, etc. > > > My concern is that the 30% customization on the existing system will > > be more of a headache than building a clean system from scratch with > > nothing I don't need. Or is it silly to build a system that is 70% > > wheel-reinventing? Should I try to work with an existing project like > > Django/Satchmo and save my web2py project for something more unique? > > > Thanks in advance for any tips. -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
