Quote from Kevin on November 26, 2025, 12:15

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.

https://docs.google.com/spreadsheets/d/1BvsIyctSN4VdvD1IM7zncMRcg_MwlInj/edit?usp=drive_link&ouid=103368142141213502907&rtpof=true&sd=true

Quote from Alex Dovlatov on November 27, 2025, 12:20

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!

Quote from Kevin on November 27, 2025, 13:45

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

Quote from Kevin on November 27, 2025, 20:16

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

Quote from Alex Dovlatov on November 28, 2025, 12:52

Hello Kevin

I apologize for the confusion in my previous response. I need to clarify how BEAR's import/export functionality actually works.

You are absolutely correct in your observation. Let me explain what's really happening:

EXPORT (BEAR's own functionality):
BEAR exports CSV files using actual WordPress/WooCommerce database field names (post_title, _regular_price, _stock, etc.). This is BEAR's native format and gives you direct access to the database structure.

IMPORT (WooCommerce native tool):
When you click "Import" in BEAR, it redirects you to WooCommerce's native product importer at:
wp-admin/edit.php?post_type=product&page=product_importer

This is standard WooCommerce functionality - BEAR doesn't have its own import processor. The import button simply provides a convenient shortcut to WooCommerce's importer.

The Issue:
The mismatch happens because:
- BEAR exports using database field names: post_title, _regular_price, _stock
- WooCommerce importer expects user-friendly names: Name, Regular price, Stock

Solution:
During the WooCommerce import process, there IS a column mapping screen where you can match fields. You need to manually map:
- post_title → Name
- _regular_price → Regular price
- _sale_price → Sale price
- _stock → Stock
- etc.

I understand this is time-consuming, especially for bulk operations.

Workaround Options:

1. Save the mapping template: WooCommerce importer should remember your column mappings for future imports if you use the same CSV structure https://share.pluginus.net/image/i20251128125002.png

2. Feature Request: I will add your suggestion to our development roadmap - an option to export CSV in "WooCommerce native format" would indeed solve this workflow issue. However, this would require maintaining two different export formats in BEAR.

Pro Tip for Your Workflow:

If you consistently export with the same column structure from BEAR, you can create a reusable header template:

1. Do the WooCommerce column mapping once and note which BEAR fields map to which WooCommerce fields
2. Create a header row template with WooCommerce-friendly names (Name, Regular price, Sale price, Stock, etc.) in the same order as your BEAR export columns
3. When you export from BEAR, open the CSV in Excel/LibreOffice/Google Sheets
4. Replace the first row (BEAR's database field names) with your pre-made header row template
5. Save and import into WooCommerce - it will recognize the columns automatically without manual mapping

This way you only need to set up the mapping once, then just swap the header row each time. Much faster for regular bulk operations.

Why BEAR uses database field names:
This approach allows BEAR to handle ANY product meta field, including custom fields and fields from third-party plugins that WooCommerce's native format doesn't support. It's more flexible but requires the mapping step when using WooCommerce's importer.

I apologize again for the initial confusion. The import functionality in BEAR is simply a shortcut to WooCommerce's own importer, not a separate BEAR import processor.