Thanks for your honesty, Chris. I'll keep the community posted if we go the Django and/or Satchmo route.
On Feb 9, 8:55 am, Chris Moffitt <ch...@moffitts.net> wrote: > Based on the additional details describing what you're trying to do, you may > be reaching the threshold where Satchmo (or any current package) is going to > have to be so heavily modified that it might make sense to roll your own. > It sounds like you're trying to develop almost an ERP type of application > and that's definitely an area where Satchmo has minimal functionality. Don't > get me wrong, I always like to see new uses of Satchmo but you are going in > a direction that hasn't been well blazed. > > There may be a few parts of Satchmo you can leverage or at least learn from > but I don't see that much that you'll gain at this point. > > If you do decide to continue with Satchmo, let us know, I'm sure folks would > be interested in hearing how it goes but I do want to make sure you go in > with your eyes wide open. > > -Chris > > On Mon, Feb 8, 2010 at 11:32 AM, snfctech <tschm...@sacfoodcoop.com> wrote: > > Thanks for your reply, Chris. And thanks for the links. > > > However, the Stack Overflow example seems to be talking about cloning > > and a tendency of developers to exaggerate their ability to understand > > the complexity of a piece of software and how long it would take them > > to do it. My point is not about cloning Satchmo - but trying to > > understand how easily extensible it is and at what point I may as well > > build my own solution, because the gap between what I need and what > > Satchmo does is too great. And, for that, you're right - I need to be > > more specific. So here a couple things I think I may need to do to > > modify Satchmo: > > > 1. Pull out a lot of e-commerce specific clutter. I'm building > > (primarily) an internal order entry and tracking system. I don't need > > shipping addresses or postal rates or a payment gateway. > > > 2. Add a bunch of business specific stuff: > > - bizarre discount rules that apply on certain days, that customers > > can only use once a month or once a quarter, that can only be stacked > > in strange ways, etc. > > - adding lots of additional attributes/relations to products and > > customers such as: upc_unit, upc_case, plu_unit, plu_case, > > quantity_case, is_organic, has_redemption, measure, size, require_id, > > category_id, location_id, producer_id, etc. > > - product holding time/ notifications (e.g. how long we can keep > > perishables vs. dry-goods before someone needs to be notified/ > > business process initiated) > > - customer/member/product lookup by contact info, past purchases, > > member number, producer order number, PLU, etc. > > - a producer/mfg. schema for tracking store->producer orders, status, > > modifying lead-times > > - printing invoices with UPCs that can be brought to POS registers > > > Btw,http://djwarehouse.orggave me "Oops…Trac detected an internal > > error:" I've looked into LFS but their motto "The online shop for for > > search engines, which appreciate speed" threw me off. Plus I had to > > dig into the FAQ to find the source and it broke on some dependencies > > when I tried to install. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
