eCommerce system with payment bypass on one site and normal eCommerce system as well
Permalink
I have a client who works with Marathon (the gas station brand) and has a difficult scenario. They need an eCommerce system that is:
1 - A shopping cart system that functions normally with checkout, cart and all that noise.
- - - - - - - - - - - - and here's where it gets tricky - - - - - - - - - - - -
2 - A "bypass" for the same shopping cart system that deals only with PO's (purchase orders) and doesn't have the payment function. This means that a specific user group can still add items to the cart but would need to checkout and send the order details/information without submitting payment. Instead of sending a payment through Authorize.net, which they have decided to use, they want users to be able to send only the order through the shopping cart without payment as most of the company's work is proposal-based. They also need to be able to have these orders show up on the user's account when they log onto the site.
Is this possible while having a normal functioning eCommerce section of the site? Any feedback is more than appreciated...
1 - A shopping cart system that functions normally with checkout, cart and all that noise.
- - - - - - - - - - - - and here's where it gets tricky - - - - - - - - - - - -
2 - A "bypass" for the same shopping cart system that deals only with PO's (purchase orders) and doesn't have the payment function. This means that a specific user group can still add items to the cart but would need to checkout and send the order details/information without submitting payment. Instead of sending a payment through Authorize.net, which they have decided to use, they want users to be able to send only the order through the shopping cart without payment as most of the company's work is proposal-based. They also need to be able to have these orders show up on the user's account when they log onto the site.
Is this possible while having a normal functioning eCommerce section of the site? Any feedback is more than appreciated...
Jon, you are the dope show! Just an FYI. But how do I make this happen?
Not sure I've ever been called that before! :)
Ummm - difficult question to answer without knowing how comfortable you are with programming...
You're gonna have to dig deep into the CoreCommerce package to do this.
Do you have a budget for this work? I could do it for you, but we're probably talking a couple of hundred bucks...
Jon
Ummm - difficult question to answer without knowing how comfortable you are with programming...
You're gonna have to dig deep into the CoreCommerce package to do this.
Do you have a budget for this work? I could do it for you, but we're probably talking a couple of hundred bucks...
Jon
We're web designers. We can do the work but we don't know where to start.
Ok well this page will tell you how to check which group a user is in:
http://www.concrete5.org/documentation/developers/permissions/users...
Using the information on that page you can find out almost anything you need to know about the current user.
As for the CoreCommerce part, you're going to have to get your hands real messy there. Download the code and work your way through it. You need to figure out where it actually displays the choice of gateways to the user and then use the group info from the page above to override the default behavior.
If you get stuck on something specific in the CoreCommerce package then post up and I'll have a look, but it would be quite a bit of work to figure it all out for you :)
Jon
http://www.concrete5.org/documentation/developers/permissions/users...
Using the information on that page you can find out almost anything you need to know about the current user.
As for the CoreCommerce part, you're going to have to get your hands real messy there. Download the code and work your way through it. You need to figure out where it actually displays the choice of gateways to the user and then use the group info from the page above to override the default behavior.
If you get stuck on something specific in the CoreCommerce package then post up and I'll have a look, but it would be quite a bit of work to figure it all out for you :)
Jon
A related problem, doing similar with shipping rather than with payment.
http://www.concrete5.org/community/forums/customizing_c5/certain-gr...
http://www.concrete5.org/community/forums/customizing_c5/certain-gr...
Hi there creativesolutions, I know this is an old thread, but I am looking to do exactly this for a site and I wondered if you came up with a solution...
I have got as far as to identify if the user is in the particular group but I am stuck with the code in method.php which triggers the payment systems available:
If you can give me any pointers, that would be awesome. Thanks in advance for your time :)
Rob
I have got as far as to identify if the user is in the particular group but I am stuck with the code in method.php which triggers the payment systems available:
Loader::packageElement('checkout/payment/method','core_commerce', array('action' => $action, 'o'=>$order,'form'=>$form,'form_attribute'=>$form_attribute, 'akHandles'=>$akHandles));
If you can give me any pointers, that would be awesome. Thanks in advance for your time :)
Rob
We have actually decided to switch eCommerce platforms due to the limitations of the c5 architecture. There are plenty of other options that are more fluid and in-depth than the c5 implementation. We still utilize the c5 CMS as you just can't beat it for editing capabilities. But, if the project requires eCommerce, we use another system entirely and build the entire website on that foundation.
Sorry, but we did not execute or finalize a solution for this issue.
Sorry, but we did not execute or finalize a solution for this issue.
Hey, out of curiosity, which eCommerce platform did you use? I have a similar situation as I need the eCommerce functionality without the payment step.
Thanks!
Thanks!
No worries guys, thanks for getting back to me.
I shall try to find a work-around :)
I shall try to find a work-around :)
No worries. Wish we could've helped. Good luck!
The 'default' payment method with Concrete5 is actually no payment method at all. The order just gets placed.
If you add on the Authorize.net payment gateway to the stock Core Commerce add-on, then when you get to the checkout, you are given a choice as to which gateway you would like to use.
So, with a bit of tweaking, it would be possible to change that behavior and pre-select the payment gateway based on which group the user is in. And then, while we're at it, we can add an additional attribute, which only gets displayed to customers in the corporate group, to store the purchase order number.
Definitely possible...
Jon