NopBridge Control Center

NopBridge Control Center is the Windows administration workspace by Bitlogika for NopBridge. It is designed for administrators who manage one or many nopCommerce stores and want faster catalog, source, mapping, run, and troubleshooting workflows than a browser-only admin experience.

Use NopBridge Control Center when you want to:

1. Connect multiple stores from one desktop app.
2. Review license, update, source, profile, and run health.
3. Create sources and profiles without jumping between web tabs.
4. Use a guided wizard for imports and exports.
5. Manage catalog data with product preview, pictures, attributes, specifications, categories, and bulk actions.
6. Drag products onto categories for faster catalog organization.
7. Generate AI mapping recommendations and manually review field rules.
8. Run dry runs and live runs with traceable logs.

Dashboard

The dashboard is the daily operations view for connected stores.

Use it to check:

1. Which stores are online.
2. Which stores are licensed for NopBridge Control Center.
3. Managed record volume.
4. Update availability.
5. Connection issues.
6. AI gateway status.
7. Recent source/profile/run counts.

The left store list is the main context switcher. Select a store first, then every tab works against that selected store.

Workflow Wizard

The wizard is the clearest path for new imports and exports. It exposes the same real settings used by the full tabs, but keeps the administrator inside one guided experience.

The wizard is useful when:

1. A user is creating a workflow for the first time.
2. A support person is walking a customer through setup.
3. A source has changed and mapping needs to be rebuilt.
4. A dry run needs to be reviewed before live execution.
5. A store has many profiles and the user wants a focused path.

Step 1: Connector

Choose or create the source/destination connector.

The connector step supports the same patterns as the web plugin:

Connector	Use
File / UNC	Local files, shared folders, CSV, XLSX, XML, JSON
API	HTTP endpoints with method, headers, auth type, and response root path
FTP / SFTP	Supplier or partner feed folders
Drive / SharePoint	Business files in cloud document storage
S3 / Blob	Object storage feeds and export targets
Database	Direct database reads when configured

Actions in this step:

1. Create a new connector.
2. Save connector settings.
3. Test the connector.
4. Upload a local source file when the store agent supports file upload.
5. Detect schema from source samples.

Step 2: Profile

The profile step decides what the connector will do.

Profile fields:

Field	Meaning
Direction	Import or export
Entity	Products, Customers, or another licensed workspace
Connector	Source or destination used by this profile
Schedule	Manual, hourly, daily, or weekly
Run only if source changed	Avoids unnecessary repeated runs
Backup/delete source options	File workflow safety and retention settings

For first setup, keep the profile manual until dry run and logs are clean.

Step 3: Mapping

Mapping loads source fields, target fields, AI suggestions, manual mappings, and generated rules in one place.

The recommended mapping flow:

1. Load mapping workspace.
2. Generate AI mapping if available.
3. Review provider and model status.
4. Review confidence per field.
5. Confirm required fields.
6. Confirm category, image, attribute, and specification rules.
7. Save mapping.

AI mapping can start the work, but an administrator should review every low-confidence or high-impact field.

Step 4: Preview

Preview runs a dry run or export preview before anything is written.

Review:

1. Created count.
2. Updated count.
3. Skipped count.
4. Failed count.
5. Category creation.
6. Picture resolution.
7. Duplicate detection.
8. Row-level warnings.

If this screen does not look right, go back to mapping or connector setup.

Step 5: Run

The final wizard step runs the real job.

Use this step only after preview is accepted. For repeated imports, NopBridge should update existing records based on source identity or SKU instead of creating duplicates.

Overview

The overview tab summarizes selected store readiness.

Use it to confirm:

1. License status.
2. NopBridge Control Center access.
3. Enabled workspaces.
4. Connector availability.
5. Store/version status.
6. Update status.

This is a good place for a support person to start before asking the customer to open deeper tabs.

Help

The help tab explains the most common workflows without leaving the desktop app.

Help should cover:

1. Wizard use.
2. Connector setup.
3. Catalog drag and drop.
4. Product card editing.
5. AI mapping.
6. Dry run and logs.
7. Licensing.
8. Troubleshooting connection errors.

Catalog

The catalog tab is the desktop catalog management workspace. It should feel faster than web admin for common admin work.

The catalog workspace contains:

1. Category tree.
2. Product list.
3. Product card preview.
4. Product Summary, Media, Attributes, Specifications, and Category editors.
5. Bulk actions for checked products.
6. Drag and drop from product list to category tree.

Drag and Drop Category Management

To move a product:

1. Select or search the product.
2. Drag the product row from the product list.
3. Drop it onto the target category in the category tree.
4. NopBridge Control Center updates the product's primary category through the NopBridge agent.
5. Refresh or reopen the product card to confirm the category.

Drag and drop is best for quick catalog cleanup, especially after imports that create products before categories are fully curated.

Product Summary

The Summary tab gives the administrator a product card instead of a plain form.

The preview should show:

1. Main product image.
2. Published status.
3. SKU.
4. Product name.
5. Category path.
6. Price.
7. Stock quantity.
8. Image/attribute/specification counts.
9. Core editable fields.

Use this tab for quick product review after import and for small manual corrections.

Product Media

The Media tab manages product pictures.

Supported actions:

1. Add picture by URL.
2. Browse and attach a local image.
3. Review thumbnails.
4. Edit alt text.
5. Edit title text.
6. Change display order.
7. Remove picture.
8. Save product media through the store agent.

Image sources can be different from the main product data source. For example, a CSV can map product data while pictures come from HTTP URLs, FTP paths, file paths, or cloud references.

Product Attributes

Product attributes are customer-selectable or variant-like values.

Use attributes for:

1. Color.
2. Size.
3. Material.
4. Capacity.
5. Packaging.
6. Bundle options.

For imported attributes, mapping rules should decide whether values are created, reused, split, normalized, or skipped.

Specification Attributes

Specification attributes are facts and filters.

Use specifications for:

1. Brand.
2. Rating.
3. Warranty.
4. Shipping information.
5. Return policy.
6. Weight.
7. Dimensions.
8. Availability status.

Keep specification names consistent. Avoid creating near-duplicate names such as Warranty, warrantyInformation, and Warranty info unless the mapping intentionally separates them.

Category Editor

The Category tab edits selected category data.

Use it to:

1. Create a new category.
2. Rename a category.
3. Move it under another parent.
4. Change display order.
5. Publish or unpublish it.
6. Edit description and SEO text where supported.

For imports, category mapping can create missing categories. The category editor is then used for manual cleanup and presentation quality.

Connectors

The Connectors tab is the full desktop source editor.

Use it when you need to:

1. Add a connector outside the wizard.
2. Edit a connector used by multiple profiles.
3. Test a connector after credentials change.
4. Upload a sample file.
5. Re-detect schema.
6. Review masked descriptor fields.

Profiles

Profiles are reusable workflows.

Use the Profiles tab to manage:

1. Import profiles.
2. Export profiles.
3. Product workflows.
4. Customer workflows.
5. Schedules.
6. Source retention rules.
7. Notes and operational context.

Separate business processes should usually be separate profiles, even when they use the same connector.

Mapping Editor

The Mapping editor is the advanced workspace for source-to-target mapping.

It includes:

1. Source fields.
2. Target fields.
3. AI suggestions.
4. Manual field mappings.
5. Transform rules.
6. Generated rules for product attributes and specifications.
7. Create-if-missing flags.
8. Review flags and reason text.

Use this tab when the wizard is too compact or the mapping requires detailed rule editing.

Runs And Logs

The Runs and logs tab is the traceability workspace.

Use it to:

1. Review dry run history.
2. Review live import/export history.
3. Load logs for a selected run.
4. See row-level warning/error messages.
5. Confirm duplicate matching.
6. Confirm image handling.
7. Confirm category, attribute, and specification creation.

For support, ask for the store name, profile name, run ID, and the first warning or error message.

Recommended Daily Workflow

1. Open NopBridge Control Center.
2. Select the store.
3. Check Dashboard for connection, license, and update status.
4. Open Runs and logs if a scheduled job needs attention.
5. Open Catalog to review imported products.
6. Use drag and drop or bulk actions for quick catalog cleanup.
7. Open Mapping editor only when the source shape or business rules changed.
8. Use the wizard for new workflows or support-guided setup.

Troubleshooting

If NopBridge Control Center cannot connect:

1. Confirm the store URL is valid.
2. Confirm the NopBridge plugin is installed and enabled.
3. Confirm the agent key is correct.
4. Confirm the agent endpoint is enabled.
5. Confirm the license allows NopBridge Control Center.
6. Confirm firewall, SSL certificate, and port availability.
7. Open Runs and logs for store-side errors.