Mass product addition

Posts: 8
Joined: 09/29/2008

Has anyone done something like tabular way of bulk addition of products instead of adding them one by one?
Populating some grid with the product data (one product per row) and inserting them in the database at once.

Any ideas?

BR, Jovan

Posts: 110
Joined: 05/28/2008

I successfully used node_import 1.5 and Oliver Coleman's ubercart support add-on to import about 400 products at once. node_import can handle many more than that but it does take a while to import if you are doing thousands of nodes.

Posts: 116
Joined: 04/23/2008

I have been able to use node_import 1.6 with a ubercart patch to load 1.8 million+ nodes... I did it in batches of no more than 500,000 per run though. I also did some changes to improve my speed.

See:
http://www.ubercart.org/forum/support/4561/product_import#comment-23044 [this patch includes image load]

http://drupal.org/node/309563 [for my performance improvements]

Its still slow - 20k-30k nodes/hr depending on what patch/configuration you go with, but at least I could leave it running and come back to it, and get it done....

Posts: 8
Joined: 09/29/2008

Thanks for the suggestion, but I don't want to import products.
My idea was for example if i want to add 10 products of same product class in same product catalog category, not to add them one by one (creating new product each time) but to be able to show a table in which I'll pick/insert all needed data, the table will have some default values for the product parameters to save time when inserting data, and on one click all the products will be created on one click.

If i'm doing a product import, i'll have to create an interface for data insertion, generate the import xml and import the products.

cheers, jovan

Posts: 116
Joined: 04/23/2008

No problem. Don't think that exists.

But if you want to import products using node_import, create import file using spreadsheet as interface. Then once done, save as a csv file. It only uses csv.

Posts: 8
Joined: 09/29/2008

Thanks that's good to know. csv is even better.

The only thing that makes me worried is that I'm not sure how will the custom added fields be imported, because I've created product classes with some custom fields. Each product class is created as separate content type whose data is kept in separate table.