First product import

This guide walks through a complete NopBridge product import: source, typed schema, mapping, dry run, and real import.

Use a small sample first. A good first test is a CSV, XLSX, JSON, or XML file with 5 to 20 products and a few realistic fields such as SKU, name, price, category, attributes, image URL, and stock quantity.

Step 1: Open NopBridge

1. Sign in to nopCommerce admin.
2. Open Bitlogika in the left menu.
3. Open NopBridge.
4. Start with the dashboard to confirm the license, usage, and last run status.

Step 2: Create a source

1. Open Sources.
2. Select the source type.
3. Enter the required connection settings.
4. Save the source.
5. Use the test action when available before you continue.

You can do this directly in Sources or through the first step of the Import wizard.

Supported source patterns:

Source type	Typical use
File / UNC	Local files, shared folders, CSV, XLSX, XML, JSON
API	HTTP or HTTPS endpoints with headers and tokens
FTP / SFTP	Partner feeds and scheduled supplier exports
Drive / SharePoint	Cloud-hosted business files
S3 / Blob	Object storage feeds and generated exports
Database	Direct SQL-based source reads where configured

Step 3: Review the typed source schema

NopBridge stores a typed schema for the source. This is where the imported fields become understandable before mapping starts.

Check:

1. Source field is the technical field name from the feed.
2. Display name is a readable label for administrators.
3. Type matches the expected data: text, number, date, boolean, URL, image, collection, or object.
4. Required is enabled only for fields that must exist for a valid import.
5. Sample values help AI mapping and manual review.

For JSON and XML sources, nested fields can be flattened into paths such as category.name, images[0], or attributes.color. For XLSX and CSV, fields normally come from headers.

Step 4: Create a product mapping

1. Open AI mapping or Profiles depending on your workflow.
2. Choose the source.
3. Choose Products as the import entity.
4. Generate mapping suggestions with AI when available.
5. Review every target field before saving.

Minimum recommended product mapping:

nopCommerce target	Recommended source
SKU	External SKU, item number, barcode, or unique product ID
Name	Product title
Short description	Short marketing text or compact product summary
Full description	Long description, HTML description, or generated combined description
Price	Numeric sale price
Stock quantity	Available quantity or inventory
Category	Main category, breadcrumb, or department
Manufacturer	Brand or vendor
Pictures	Image URL, local file path, FTP path, or Drive file reference
Product attributes	Variant fields such as color, size, material
Specification attributes	Technical facts such as weight, warranty, rating

Step 5: Add rules where needed

Rules make imports reliable when supplier data is inconsistent.

Common rules:

1. Trim whitespace from text.
2. Convert decimal separators.
3. Normalize category names.
4. Split tag or attribute lists.
5. Map supplier stock status to numeric quantity.
6. Build image paths from a base folder plus file name.
7. Skip records that do not have SKU or name.
8. Use defaults for missing values.

Step 6: Run a dry run

Dry run validates the import without changing the catalog.

Check:

1. How many records will be created.
2. How many records will be updated.
3. Which records will be skipped.
4. Whether categories, attributes, specification attributes, and pictures resolve correctly.
5. Whether duplicate detection matched existing products by the selected source identity.

If the dry run does not look right, fix the mapping before running the real import.

Step 7: Run the real import

1. Open Runs.
2. Select the profile.
3. Start the import.
4. Watch the run status.
5. Open imported products in nopCommerce catalog and check the result.

After the run, validate:

1. Product count.
2. Product names and SKUs.
3. Categories.
4. Product attributes.
5. Specification attributes.
6. Images.
7. Duplicate update behavior on a second run.

Step 8: Repeat the import to test updates

Run the same profile again after changing a few source values. NopBridge should detect existing imported records and update them instead of creating duplicates.

Good repeat-test changes:

1. Change price.
2. Change stock.
3. Add one new image.
4. Add one new specification attribute.
5. Rename a category.
6. Add one new product.

The second run should show updated and created counts separately.