The downpayments module allows store administrators to add partial payment(s) as a product feature. They can assign a down payment amount and the due date to any product, and manage down payments and partially paid orders in the admin section.
For products with the downpayment feature configured, buyers can select if they wish to pay the full price or only the down payment. If they choose down payment, a certain number of days before the due date, as determined in the downpayment product feature settings by the store administrators, they will receive an email remainder about the remaining payment balance. They can see the information about their partial payments under a new tab in My Account where they can add the remaining balance to the cart and finalize the payment.
We have developed this module over several months and it is already in production use on our site and going live this week on another site (by one of the ChipIn contributors). Thanks to everyone who helped with the bounty to get this on drupal.org - the community support has been great!
Sandbox project page: http://drupal.org/sandbox/covenantd/1103142
Ubercart thread with votes, ChipIn's totaling over $1,000 and patch contributions: http://www.ubercart.org/forum/bounties/15764/1000_partial_payment_module
P.S. We sat in CVS account approval "purgatory" for several months (see http://drupal.org/node/988244) while D7 so are excited to be in the promised land of Git!
| Comment | File | Size | Author |
|---|---|---|---|
| #15 | add_to_cart.png | 14.91 KB | sukr_s |
| #15 | checkout.png | 7.49 KB | sukr_s |
Comments
Comment #1
sokrplare commentedUh-oh, now I'm getting nervous we'll never get out of the Git project approval queue either!
Comment #2
tr commentedIt's not on the radar unless it's set to "Needs review" ...
Comment #3
WillHall commentedAwesome module - thanks for the contrib!
Comment #4
sokrplare commentedThanks for the status switch, TR! I've updated the project application doc to note this as well (http://drupal.org/node/1011698/revisions/view/1412522/1438238)
Comment #5
sokrplare commentedBump!
Comment #6
arcaneadam commentedYou should run the module through Coder and fix any errors or warnings.
Comment #7
arcaneadam commentedSetting to needs work till it is run through coder and cleaned up.
Comment #8
sokrplare commentedThanks, Adam - will do.
Comment #9
sokrplare commentedWas confused where you were seeing those errors since when we had checked with Coder before none of that came up. Just realized you gave it a go for D7 whereas the module was written for D6 (actually, D7 wasn't even out when this was written - slow module approval process, but that's another story!). Will see if porting to D7 makes sense right now since Ubercart itself is still beta for D7. We're just wanting this approved for D6 for now though.
Comment #10
sokrplare commentedWent ahead and followed up with Coder for D7 and figured it wouldn't hurt to deal with all the issues we could now so easier to port later.
The only critical warning being reported is that the theme() function is used in the Drupal 6-style without the $variables array, however, since this is Drupal 6 module we are supposed to use it in D6 way. When ported we'll make that little switch.
All normal warnings remaining are related to "Include the CVS keyword $Id$ in each file. This should be in the format // $Id$ or // $Id$”. With Git no longer applicable.
I have fixed all other minor errors so none are being reported in either version. Committing the new version shortly.
Thanks, Adam!
Comment #11
sokrplare commentedCommitted (see http://drupalcode.org/sandbox/covenantd/1103142.git/commit/8043ffa) so setting back to needs review.
Comment #12
sukr_s commentedthe following is not transalatable at line 336. need to fix this... haven't tested the functionality still
Comment #13
sokrplare commentedGood catch - thanks, Sudhir! Will get that fixed up.
Comment #14
sokrplare commentedCommit made! See http://drupalcode.org/sandbox/covenantd/1103142.git/commit/325d9db
Comment #15
sukr_s commentedHi Joshua,
it did not work for me. See the attached screen shot. The steps i followed
1. add a down payment option for the product.
2. as a customer, i selected the product, selected the downpayment and clicked add to cart
3. then i do a checkout.
what i see in the checkout pane is the original price and not the down payment that was chosen. note that i use ajax based add to cart from module uc_ajax_cart.
A very interesting module and has a great scope (would love to use it myself with...). Specifying the down payment per product is quite intense work in a typical ecommerce site. would be great if there is a general setting like
1. x% of product is down payment value
2. y% of order is down payment value
3. exclude products from part payment.
4. full payment within z days of order or -z days before shipment date
(and the list can go on)
great work,
Sudhir.
Comment #16
sokrplare commentedHey Sudhir!
Thanks for the report. Sounds almost like an incompatibility issue with uc_ajax_cart. Since this isn't a fundamental module architecture issue or anything, probably better to pursue it in the issue queue so this doesn't hold up approval and prevent others from using the module. I know this module has been implemented on 6-12other sites already with no issues so it does work.
Love the feature ideas too - a couple of these have already been mentioned in the Issue queue and if you can add the others that would be great. We're hoping to get those added, but want to first make sure the module is approved before we start feature additions.
Setting this back to needs review so we can hopefully get it approved shortly!
Comment #17
sukr_s commentedJoshua,
I had further chance to test the module. it seems that the currency is hardcoded to $ (USD). My site runs in Rs. (INR). However when i access user/%/downpayments, all the amounts are shown in $ and not in Rs.
Comment #18
beringstrasse commentedHey. I'm testing this module for a school selling conferences and it fits my purpose perfectly.
However I don't think I'm receiving an email when my payment is due. And how could I test it other than setting the due date to one day from now...and wait. I feel kinda stupid doing that.
Comment #19
jordojuice commentedAdding UC tags.
Comment #20
tr commentedPlease remove all trailing whitespace.
Please add doxygen comments to all your functions, including @param and @return tags where needed. Please add a doxygen block with a @file tag at the beginning of each file. See http://drupal.org/node/1354
Comment #21
sokrplare commentedThanks for the feedback (#20 especially). Will get these changes made!
Comment #22
sokrplare commentedFixed the problem in comment 17 (hard-coded currencies).
Comment #23
sokrplare commentedRegarding comment 18, the easiest way to test this is to set the the due date to one day from now and run cron, it should work.
Comment #24
sokrplare commentedCommitted changes related to comment #20 (Doxygen and comment formatting conventions as at http://drupal.org/node/1354).
Many thanks for your input.
Comment #25
sokrplare commentedAny opposition to switching status to reviewed and tested based on all the great input we've had so far?
Comment #26
sokrplare commentedI believe we're ready to go!
Comment #27
mlncn commentedYou are not supposed to RTBC these things yourself (which would be why others haven't fixed this), but i do think that eight months is sufficient wait time, and you've demonstraited your project maintainer chops in this issue. You are now a vetted git user and can promote full projects.
Thanks and looking forward to your Drupal offerings!
Comment #28
interestingaftermath commentedsubscribe
Comment #29
sokrplare commented@mlncn - I figured going RTBC myself wasn't the standard procedure, but like you noted - after eight months I just want this thing released! Thanks SO much for getting this rolling - very excited on my end - was starting to give up hope!
Just tried promoting the project, but I think from the trouble in http://drupal.org/node/988244#comment-3960120 (and comments 22-23) the URL for it is "taken" - http://drupal.org/project/uc_downpayment
Anyone know how to remove that node since it is the most accurate name for the module? Cross-posting this on the other thread to see if George or someone else can do this.
Comment #30
sokrplare commentedChecked with George and looks like the node is created, but Unpublished. So we need someone with administrative access to delete the now-rogue project, give ownership to me, or publish it so George can do one of these things. Any hope?
Comment #31
sokrplare commentedAny admins? I could rename the project, but would be a shame as this name fits best.
Comment #32
tim.plunkettI have republished the node. If you need the ownership switched, please have george@dynapres.nl comment here to verify.
Comment #33
sokrplare commentedThanks so much, Tim - passed on to George to see if he can switch ownership or otherwise comment to verify.
Comment #34
mo6Tim, could you please transfer the ownership of the project to Joshua? Thanks.
Comment #35
tim.plunkettDone. Thanks George and Joshua!
Comment #36
sokrplare commentedHooray! Cheers all!
Comment #37
sokrplare commentedAnd live!
http://drupal.org/project/uc_downpayment