Export/Import Data field Mismatch between Bear CSV Fields and Woocommence Native CSV Fields
The support doesn work on Saturdays and Sundays, so some Friday requests can be answered on Monday. If you have problems with registration ask help on contact us page pleaseIf you not got email within 24~36 business hours, firstly check your spam box, and if no any email from the support there - back to the forum and read answer here. DO NOT ANSWER ON EMAILS [noreply@pluginus.net] FROM THE FORUM!! Emails are just for your info, all answers should be published only here.
The support doesn work on Saturdays and Sundays, so some Friday requests can be answered on Monday.
Good Day, I purchased the full version yesterday and I have encounter a problem whereby the following is happening - Bear is using WooCommerce's native import export module, its here where the problem is as Bear is exporting its field data but when importing it back WooCommerce is trying to map it's data fields. it does bring up a mapping screen during the import procedure, whereby you can choose from a dropdown box but there a few names that don't match at all or are called something completely different which is very difficult and time-consuming to fix. I request the following to resolve this critical issue as it is part of my workflow when adding bulk new items using csv import, it was one of the key considerations when I chose Bear Bulk Editor and Products Manager Professional. Your assistance will be greatly appreciated
Contact BEAR support directly - they should provide official field mapping guidance
Ask them for a field mapping reference sheet specifically for WooCommerce native imports
Request they document this change in their update notes
Kind Regards
Kevin
Here is the file with what I have managed to match, the sheet called Bear Field Import has the comparing Fields for Bear vs Woocommerce and an explanation.
Hello Kevin
Thank you for your detailed explanation.
BEAR has its own export/import system with specific field names (like post_title, _regular_price, etc.) which are the actual WordPress/WooCommerce database field names. This format is designed to work with BEAR's own import functionality.
The native WooCommerce importer uses different column names (like Name, Regular price, etc.) which are more user-friendly but different from the actual database structure.
Your options: use BEAR's import function - Simply import the CSV file you exported from BEAR back into BEAR. It will work perfectly since it uses the same format.
Map columns manually - If you need to use WooCommerce native importer, you'll need to rename the columns in your CSV to match WooCommerce's expected format, or use the column mapping feature during import if available.
Feature request - I can add your suggestion to export in"WooCommerce native format" as a feature request for future versions. However, this would require maintaining two different export formats.
Why BEAR uses database field names: this approach gives you more control and allows bulk editing of any product meta field, including custom fields that WooCommerce's native importer might not support.
Welcome!
Thank you Alex for the Reply. Your explanation does make sense but it seems the latest version jumps into WooCommerce to do the import portion
I have BEAR - WooCommerce Bulk Editor Professional v.2.1.4.7 version, the issue is when I click Import from within Bear, it immediately jumps out of the Bear Screen and launches into the WooCommerce CSV Import tool, I verified this myself again. You mentioned using Bear's own import tool, I would gladly use it but where would that be found in the Bear plugin? When I bought Bear, I was also sent the older versions. Would they perhaps have the older embedded import/export module?
Thanking you kindly
I have tried the older versions 2.1.4.1, 2.1.4.3 & 2.1.4.5 these also use the Woocommerce import tool, Please let me know where the Bear import tool is in the plugin
Regards