Session proxy is not a module: it is a replacement for Drupal core session handling API.
It acts as a proxy between fixed core procedural API towards a fully object oriented, more flexible and easier to extend session management API.
Basically, it strongly encapsulate the original API, separating user management against raw session storage: by using it you are able to implement any session storage engine (memcache, redis, ... ) without handling cookies and by users yourself.
This module will assist anyone in setting up a store in the EU with configuring their VAT rates. It is especially ideal if the store exports to other EU countries and outside the EU. If the store only ships to its home country it may be too much.
To be used in calculating VAT rates for inta-member state transaction.
Features
- checks the VAT structure and outputs an error message with infos about vat format
- checks vat against EU SOAP server
- check if VAT country matches shipping country, supporting commerce_shipping and standard commerce address fields (this will be moved to a separate module one day)
Some legal info
Often it is not enough to only check the VAT to be protected against VAT fraud (like someone using the VAT of another company). In germany for example you need to check the VAT over a goverment page that forces a check against name, street, plz ....
This module makes a bridge between Drupal Commerce module and Userpoints.
It allows users to create commerce_line items with negative points value, behaving like a discount system in the order process.
The user can choose how many points he wants to use, they will be automatically taken from his userpoints account.
Features
Select the type of Userpoints taxonomy should be used as "money"
Allow your Drupal commerce customers to complete orders using Userpoints points in the checkout process.
Select the a Commerce currency -> Userpoints points conversion rate (very basic for now)
it DOES NOT behave as a Commerce payment method:
Depending on how your site will manage points, user will or will not always have the exact amount nor enough points to fully pay an order
I don't want to overload the payment process by displaying an odd interface asking the user how he will pay (userpoints and CB ? CB only ? Userpoints only etc...)
Requirements
- Commerce
- Userpoints (7.x-1.x)
- Entity API
Installation
Steps for a quick install
Enable the module
Create a taxonomy term in userpoints vocabulary (Say "Credit" for instance)