I am using Spree 2.4.1. From User perspective, i am able to order a product. But being a user, how can i cancel the order.?? Can anyone tell how a customer can cancel the order in Spree. If Spree 2.4.1 version does not support this functionality, then which version of Spree will support? I am using Spree Pay-pal Express and Rails 4.1 version.
Thanks..
As a user, you just empty your cart if you don't want to proceed with your order. There is no need for users to cancel an order themselves.
Admins can cancel orders, and there is a cancel state on the order if you need to build the functionality in, though I wouldn't recommend it.
Spree doesn't provide this feature in any version. Only Admin can cancel the order. It totally depends on nature of e-commerce app if you should provide 'cancel order' feature for users. Many of the e-commerce sites provide 'cancel order' to minimize the customer support efforts( cancel order via email or call).
Related
I am researching Django Oscar for the ecommerce part of our business. One of the required features is that we need to host multiple shops on one Oscar instance, i.e. every shop owner should manage his own products, his own partners etc. And should not have access to other owner's content.
Google says it had this feature as of version 0.6: https://django-oscar.readthedocs.io/en/releases-0.6/howto/multi_dealer_setup.html
But the current version (1.5 as of today) does not mention this feature. How to do multitenancy in later Oscar versions?
Oscar is great! I'm using the "multiple dealers" as described in here
https://django-oscar.readthedocs.io/en/releases-0.6/howto/multi_dealer_setup.html
Until now I don't know another solution for multi-vendor.
Cheers,
EDIT
The multiple dealers support is now possible in Oscar 0.6 without any
code changes, and called "permission-based dashboard". It's documented
here:
http://django-oscar.readthedocs.org/en/latest/ref/apps/dashboard.html
"Staff users (users with is_staff==True) get access to all views in the dashboard. To better support Oscar’s use for marketplace scenarios, the permission-based dashboard has been introduced. If a non-staff user has the partner.dashboard_access permission set, they are given access to a subset of views, and their access to products and orders is limited."
I know this post is old, however there is shuup if you are looking for a multi-vendor python based shop. It does basically everything Oscar does with a really responsive and productive admin.
https://www.shuup.com/
I would like to build a third party application which is used to make orders from the my opencart store.My opencart store is using version 2.2 and I planned to build this app using OPENCART API.
The features this third party app consist of
able to autosugges the products from the opencart store and add the
selected product to a table
after adding all products, We can submit the order and the the order will also automatically completed
the delevery method is set to "collect from store"
payment method is set to "Cash ON delivery"
after the order has been completed the stock should be deduct from the opencart store.
I would like to know is it possible to build this third party application? Also I would like to hear guides on how to do this .
You are ideas are appreciated very much
I made a Django online-store site and I need to include paypal checkout system for the cart, but solutions I found online either just for one item only(Buy Now buttons) or something like django-paypal-cart, which is not well-documented and I can't figure out how to make it to the checkout.
Please, give me some hint, maybe good article about how to make your cart items go to the checkout, anything will be highly appreciated, I don't know what else to google now
There are numerous options for tying PayPal into your website or app. Depending on exactly what you're doing or how good you are with web service API's you may choose one or another.
If you want to keep things simple, you can stick with Payments Standard. This is basically what you're referring to about the one item only buy now button, but you can use the cart upload command method to build a form that includes multiple items and pass it all over to PayPal at once.
If you prefer web service API's I'd recommend using Express Checkout. This consists of SetExpressCheckout, GetExpressCheckoutDetails, and DoExpressCheckoutPayment. Read through that general EC documentation to get familiar with the calls and how it all flows.
Another thing I would highly recommend utilizing is Instant Payment Notification (IPN). This is a feature where PayPal will POST transaction data to a listener script that you have sitting on your server any time a transaction occurs on your PayPal account. This includes payments, refunds, disputes, cleared payments that were pending, etc. This allows you to automate tasks like updating your database, sending out custom email notifications, hitting 3rd party web services, etc. and it happens in real-time, so it's very powerful.
this is a newbie satchmo question...so I've implemented satchmo for a django e-shop I am building. I have setup sathcmo following the tutorials, created some products, tested that I can make an order, and then switched to 'real mode', on http://site/settings, clicking on 'accept real payments'. The question is how I can setup the payments to be made on my bank account (a bank in Greece)?
I have not found any reference on this, so please help!
btw, on the checkout page, I get this
You'll need to fill out at least the fields with a *
How do you want to pay?
Payment method*
Payment test module
Gift Certificate
so what does payment test module means? Do I have to install another application? Currently setting.py contains
'payment',
'payment.modules.dummy',
'payment.modules.giftcertificate',
Thanks a lot for any help!
Satchmo has multiple payment methods. I am not sure exactly what payment methods would support interacting with your Greek bank account. Typically people use something like Authorize.net, paypal or google to collect payments.
Once you decide which processor you want to use, then we can help you decide if there's a processor available or if you'll need to build one.
I want to implement Facebook connect login for my Django site and I've checked the already existing apps.
So far, I have found Django-Socialauth, django-socialregistration, and django-facebookconnect for this purpose.
The question is which one to choose, and I would like to hear from other developers who have experience with any of these apps.
It is important for me that the Facebook Connect login app plays nicely with #login_required, with the default auth system, and with django-registration.
Please share your experience :)
Update (11/26/2013): I'm updating my recommendation. Since a sufficient amount of time has passed since I wrote this answer, I would recommend python-social-auth or django-allauth as the best tools for the job. They are active projects with good documentation and support for a lot more than just Facebook. I've had success using both.
I have had the most luck with adapting django-socialregistration with django-registration (0.8). Since you're working with django-registration, you're going to have to do a little bit of work, since all three of those packages assume the role of both the creation and the authentication of the user.
I was just going to explain what needed to be done, but you inspired me to finally get my version out: hello-social-registration.
Like I alluded to, it separates gives the registration functions to a django-registration backend and handles all the authorization itself. I've been using this on my near-beta application for a while now with no problems (I also handed it to a friend to use a few months ago and he got it to work without much modification).
It's definitely not ready to be a plug-and-play reusable application, yet, but hopefully it'll provide you with some insight. :)
By far the most commonly used package for Facebook authentication in Django is Django Facebook:
https://github.com/tschellenbach/Django-facebook
It also gives you access to the facebook APIs using the included Open Facebook api client.
I wanted to implement a basic "Login using Facebook" functionality in my Django app. I didn't want to show the user a form to fill or have her choose a password. I preferred to make it seamless.
Based on my requirements, django_facebook_oauth was the best app for me. It simply allows the user to login using facebook, and gets the user info my Facebook app requests from her (based on my Facebook Auth Dialog). It creates a new user in Django with the user's facebook email, a username and a blank password.
I highly recommend it.
Hi Take a look at fbconnect app that we (actually, Hernani, a guy on our team) put together for osqa (a clone of CNPROG).
You will have to, probably, tinker a bit to adapt that to your needs. It does work with #login_required decorator and the standard django.contrib.auth system, but we do not use django-registration.
Our app also works with openid and password login, but the openid part is tightly coupled with the Q&A component at present.
We may separate it though some time in the future, if anyone might be interested in "anything-signin" django pluggable app or has something better already - pls let us know.
I've used django-allauth and django-facebook on two different projects.
django-allauth was great and provided very good support for logging in and creating user profiles. It could also work with other auth providers, which I didn't implement.
django-facebook worked out of the box, but it's only compatible with Facebook. It also provided simple APIs for fetching users' likes and friends from Facebook directly into the db, which I liked very much!
facebook.get_and_store_likes(user)
facebook.get_and_store_friends(user)
I played with .NET based libraries and found them to be frustratingly out of date. Facebook seems to change their APIs frequently, so if you cannot find a library that is routinely maintained, you will find that you will get halfway through your implementation before you realize that there are serious problems.
I had some success with the javascript API that Facebook publishes and maintains. While the documentation may not be always up to date, I found that I was always within striking distance of the correct implementation (one or two changes needed).