Last updated 2 May 2017. Created on 26 December 2010.
Edited by BD3, gregoryshearer, brunodbo, lhridley. Log in to edit this page.

Installing dependent modules

If you're installing Drupal Commerce on an existing Drupal site or on a new Drupal site without using Commerce Kickstart, you first need to install the latest packaged release of the following modules:

Note: These modules may have more recent -dev releases that fix bugs and add new features, but releases of Drupal Commerce are developed to work with the latest tagged releases of each of these modules.

Installing Drupal Commerce modules

When turning on the sub-modules of Commerce, you will notice that some modules are dependent on other modules. You may wish to turn them on one at a time so as to pinpoint any error messages. This is the order to satisfy dependencies:

  • Commerce and Commerce UI
  • Customer and Customer UI
  • Price
  • Line Item and Line Item UI
  • Order and Order UI
  • Checkout, Payment, Product
  • Product Reference
  • Cart and Product Pricing
  • Tax
  • Product UI
  • Tax UI
  • Payment UI
  • Product Pricing UI

Note: You can also enable those modules via drush in the aforementioned order:

drush en commerce commerce_ui -y;
drush en commerce_customer commerce_customer_ui -y;
drush en commerce_price -y;
drush en commerce_line_item commerce_line_item_ui -y;
drush en commerce_order commerce_order_ui -y;
drush en commerce_checkout commerce_payment commerce_product -y;
drush en commerce_cart commerce_product_pricing -y;
drush en commerce_product_ui -y;
drush en commerce_tax_ui -y;
drush en commerce_payment_ui -y;
drush en commerce_product_pricing_ui -y

Missing Fields

If your installation of Commerce encounters an error that indicates that a field required by Commerce was not created properly, you may try the Commerce Repair module to create the field.

Installing additional contributed modules

There are a wide variety of other modules that you may need or want to use in conjunction with Drupal Commerce. These are contributed by the community at large to integrate with payment services, extend core features, and add other essential e-commerce features like Coupons and Shipping.

The community maintains a rough list of contributed modules on this wiki page, but there may be new modules listed on that have not been added yet. To find the absolute latest modules added to, you should use the module search functionality for the keyword "Drupal Commerce" (in quotes).

Uninstalling Drupal Commerce

If you need to uninstall the Drupal Commerce modules for any reason, you will have to first disable them a few at a time based on their dependencies. For example, the Line Item module cannot be disabled until the Product Reference module is disabled, because Product Reference depends on Line Item.

  1. Check your Drupal version. The uninstallation process has been updated in Drupal Commerce 1.2 to work around new behavior added in Drupal 7.4. Nothing changed in the Commerce modules depends on the new behavior, but the uninstallation process wasn't tested on versions earlier than Drupal 7.10. There have been security releases since Drupal 7.4, anyways, so sites are encouraged to update as a best practice in general.
  2. Work your way several times through the modules list disabling all the Commerce modules.
  3. Repeat the process on the uninstallation form.
  4. While the modules and all their various entities and fields will be deleted, Drupal's field system does retain deleted field data in the form of a variety of field_deleted_data_* and field_deleted_revision_* tables. It is up to your database administrator to delete these tables once you confirm the data is no longer necessary. There will also be rows in the field_config and field_config_instance table representing the deleted fields that may be deleted if you desire. Deleting this data is not required for continued operation of the site or even for reinstallation of Drupal Commerce.

Note: Disabling modules may cause some functionality to be disrupted, but no data will actually be deleted. For example, disabling the Example Payment Method module will cause the payment method rule enabling that payment method to malfunction, but neither the rule itself nor payment transactions made via that method will be deleted. When you uninstall a module, expect any data stored by that module to be deleted, including (but not limited to) customer profile data, order and line item information, and payment transactions.

For a collection of useful materials for anyone building an eCommerce website in Drupal, see Resource Guide: Building an eCommerce Website.

Looking for support? Visit the forums, or join #drupal-support in IRC.


jorge.aqp.23’s picture

Hello :)

When I tried to install the commerce 7.x-1.0 module the following error appeared:

An AJAX HTTP error occurred. HTTP Result Code: 404 Debugging information follows.
StatusText: Not Found ResponseText: No input file specified.

I'm using Drupal 7.9 and I have installed all the pre-requisites succesfully.

I hope you can help me.

nally’s picture

When installing as per the suggested order for installing modules by hand, I got this:

You must enable the Product Pricing, Product Reference, Rules UI modules to install Tax.

Perhaps a very minor update to the order and steps for installing modules is in order?

Christian Nally - B.C., Canada -

jacobson’s picture

Per this Issue thread, you may need to use Drush to disable (drush pm-disable) and then uninstall (drush pm-uninstall) some of the Commerce suite modules. A bug seems to mislead Drupal to believe that entities exist that are using the Commerce modules' field definitions, when, in fact, all use of those definitions have been deleted. As a result, Drupal's UI will not allow the affected Commerce module (usually Product Reference) to be disabled. Drush, however, will disable and uninstall the module.

rszrama’s picture

Just committed a fix so the Drush workaround is no longer necessary. It will be live in Drupal Commerce 1.2, and I've updated the uninstallation instructions to reflect the changes. See #1403972: Make uninstallation possible again.

rudesindus’s picture

First of all I wanna thank the Commerce Guys for maintaining the Drupal Commerce project which is crucial for our business.

My question is: can I update my CTools module?

CTools is no more a beta and my update status says that the earth is gonna open a swallow me if I don't update to the final release (security risk!). Aparently the problem is related to the comments and thats not important for me at the moment, but always is better to keep updated your modules so...

matteoraggi’s picture

Which is the minimum memory needed o install and manage drupal commerce?
32mb or max 64mb are enough?

stuzog’s picture

The btn_linkedin and btn_flickr images are missing from Commerce Kickstart 7.x-1.4 so the LinkedIn and Flickr buttons show in as gray once installed.

As these OAuth connector providers are available for enabling, so should be their buttons.

Note: I haven't got these two working yet; the other three (Google, Facebook and Twitter) seem to be working OK.

rakesh.gectcr’s picture

First I enabled the all the module. but that time i was not able to find the products under store module.

Then i followed the above instructions. its works for me, this time i got the problem admin menu. Please check the below link.

Rakesh James’s picture

Would instil some confidence in the process :)

pietpomp’s picture

Hopefully this will save others some time, as it had me running is circles whilst considering Drupal Commerce as a solution.
Under: Installing additional contributed modules it talks of a rough list on a wiki page with link For some reason they do not list the ‘better’ link(IMHO) which is AND for some even stranger reason the internal links on all point to the rough list to!?

Getting people to the better list may just aid in contribution and development as I was pleasantly shocked to get a completely different image of the ‘liveliness’ of the project. So for free Drupal Commerce extensions, add on modules and themes make sure to check as well.

Not to diminish the advise to search for “Drupal Commerce”, but in real life, we know often that advise is actually followed.

rszrama’s picture

We just hadn't done a final review on /extensions to push it live. Fine for you to link it in, but we'll make sure it gets linked in and blogged about as soon as it's complete. : )

(There are other revamps, too, like a new fancy-pants showcase and new interfaces to make Q&A easier to use.)

pietpomp’s picture

Thanx rszrama, that's good to hear.
Also well done on your efforts so far!!

odisey’s picture

I know the instructions say "Latest Tagged Release" as compatible, but the list versions are behind the current versions. Makes me cringe to think about installing the wrong modules on a fresh Drupal install. Should I install the listed versions:

Address Field 1.0-beta3
Ctools 1.2
Entity API 1.0-rc3
Rules 2.2
Views 3.5

.... or should I install the latest versions:

Address Field 1.0-beta4
Ctools 1.3
Entity API 1.1
Rules 2.3
Views 3.7 .... ?

I'm afraid I do not understand the term latest "TAGGED" versions. Does that refer to the listed versions above - as tagged, or the most recent versions on the project's download page that are available for download -- aside -dev versions?


EDIT --------------------------

I see the correct installation versions are listed on project page under requirements now, regardless of what is currently listed above on this page ...

Index_sr’s picture


there is a possibility that customers profiles were filtered by "Owned by"?
Respectively previewed user "test" only providers with which it was filled by "Owned by == test" ?

Thank you

italdenko’s picture

Hello , I installed and configured a module commerce 7.x-1.9 and Booking Commerce 7.x-1.0-alpha2 and all dependencies , then added field to events content type booking settings , after that go to event node and when i click book i always got this error EntityMetadataWrapperException: Unknown data property commerce_product. in EntityStructureWrapper->getPropertyInfo() (line 335 of also this module Commerce Repair didnt help

sambathbask’s picture

i have install views-8.x-3.x-dev.tar.gz but i got error message of [views-8.x-3.x-dev.tar.gz does not contain any .info.yml files.]

mikeohara’s picture

Views ships with Drupal 8, so you should not need to install it again

valdir.marcos’s picture

Sorry, I have posted this comment wrongly, please delete it.

valdir.marcos’s picture

I am trying to install Drupal Commerce 8.x-2.0-rc1 (latest version) on Drupal core 8.3.5 (latest version).
I am not updating alphas or betas of Drupal Commerce 8.x-2.0, it's a fresh new installation of rc1.
I can import the file, but I can't activate it.
Why I can't check Drupal Commerce 8.x-2.0-rc1 modules on http://www.../drupal8/admin/modules?
Why they are locked or blocked?

Uninstalled modules
Updated Ok
Drupal Commerce 8.x-2.0-rc1
Include: Commerce, Commerce Cart, Commerce Checkout, Commerce Log, Commerce Order, Commerce Payment, Commerce Payment Example, Commerce Price, Commerce Product, Commerce Promotion, Commerce Store, Commerce Tax


[] Commerce
Defines common functionality for all Commerce modules.

[] Commerce Cart
Implements the shopping cart system and add to cart features.

[] Commerce Checkout
Provides configurable checkout flows.

[] Commerce Log
Provides activity logs for Commerce entities.

[] Commerce Order
Defines the Order entity and associated features.

[] Commerce Payment
Provides payment functionality.

[] Commerce Payment Example
Provides payment gateway examples.

[] Commerce Price
Defines the Currency entity.

[] Commerce Product
Defines the Product entity and associated features.

[] Commerce Promotion
Provides a UI for managing promotions.

[] Commerce Store
Defines the Store entity and associated features.

[] Commerce Tax
Provides tax functionality.