Web plugin screens

This guide explains the NopBridge web plugin screen by screen. Use it when you want to understand what each tab is for, what to fill in, and how the screens connect into one import or export workflow.

The main idea is simple: Dashboard shows health, Import wizard guides new work, Sources describe where data comes from, Profiles describe what to do with that data, AI mapping creates the first mapping draft, and Runs/Logs prove what happened.

Dashboard

The dashboard is the operational landing page for store administrators.

Use it to check:

1. License and plan status.
2. Remaining usage against plan limits.
3. Connector health.
4. Recent dry runs and imports.
5. Whether AI mapping used the Bitlogika AI Gateway or a fallback path.
6. Whether NopBridge Control Center access is enabled for the current store.

The dashboard should be the first place to look when a user says "nothing imported" or "AI did not map anything". It gives the shortest route to the relevant source, profile, run, or log.

Import Wizard

The import wizard is the recommended path for a first workflow. It keeps the administrator inside one guided flow instead of forcing them to jump between tabs.

The wizard has five steps:

Step	Purpose	Result
Connector	Choose file, API, FTP/SFTP, cloud, object storage, or database source	Source is saved and tested
Profile	Choose import/export, entity, schedule, and safety options	Repeatable workflow is saved
Mapping	Generate AI mapping or edit manually	Field mapping and rules are saved
Dry run	Validate create/update/skip results without changing catalog data	Import is proven before live run
Live import	Execute the real operation	Products, customers, or exports are written

Step 1: Connector

Choose the data source, format, authentication, root path, and schema options. The same connector form is used by the full Sources tab.

Good connector practice:

1. Use a clear source name such as Supplier API products.
2. Keep secrets in a credential reference, not directly inside the descriptor.
3. Test API/FTP/cloud connections before mapping.
4. Let NopBridge detect the typed source schema from real sample rows.
5. Confirm that nested JSON/XML paths are flattened into readable field paths.

Step 2: Profile

The profile decides what the connector will do.

Important profile fields:

Field	Meaning
Direction	Import or export
Entity	Products, Customers, or another licensed workspace
Source	Connector used by this workflow
Schedule	Manual, hourly, daily, or weekly
Run only if source changed	Avoids unnecessary repeated imports
Backup source before import	Keeps a dated copy of source file when applicable
Delete source after successful import	Useful for drop-folder style workflows

For first tests, keep scheduling disabled and run manually until the dry run is clean.

Step 3: Mapping

Mapping connects source fields to nopCommerce target fields and rules.

The mapping screen has three important parts:

1. Source fields: detected fields, types, and samples from the source.
2. Target fields: nopCommerce fields available for the selected entity.
3. AI recommendation: generated field suggestions with confidence and provider visibility.

For product imports, mapping should cover more than basic fields. A strong production mapping usually includes SKU/source identity, name, price, category, manufacturer, stock, pictures, product attributes, and specification attributes.

Step 4: Dry Run

Dry run validates the import without changing nopCommerce data.

Review:

1. Created records.
2. Updated records.
3. Skipped records.
4. Missing required values.
5. Category creation.
6. Attribute/specification creation.
7. Picture resolution.
8. Duplicate matching.

If dry run looks wrong, return to mapping before running the live import.

Step 5: Live Import

The final step starts the real job.

Only run live import after the connector is tested, mapping is saved, and dry run results are acceptable. Repeated runs should update existing records by source identity or SKU instead of creating duplicates.

Sources

The Sources tab is the connector inventory.

Use it to:

1. See all configured connectors.
2. Check source type and format.
3. Confirm field count and last analysis time.
4. Open a source for editing.
5. Add new sources for future profiles.

Source Editor

The source editor defines connection settings and typed schema.

The top connector buttons select the source type:

Type	Typical use
File / UNC	CSV, XLSX, XML, JSON on local disk or network share
API	HTTP/HTTPS endpoints with method, headers, body, token reference, and root path
FTP / SFTP	Supplier drop folders or scheduled partner feeds
Drive / SharePoint	Business files managed in cloud document storage
S3 / Blob	Object storage feeds or generated export targets
Database	SQL-style source reads where direct database access is configured

Typed schema tells NopBridge what each source field means. It improves AI mapping, manual review, validation, and dry run explanations.

Profiles

Profiles are saved workflows.

A profile combines:

1. Source connector.
2. Direction.
3. Entity.
4. Schedule.
5. Source-change check.
6. Backup/delete options for file workflows.
7. Mapping and generated rules.

Use separate profiles for separate business workflows. For example, keep supplier product import, customer migration, and product export as different profiles even if they use the same source.

AI Mapping

The AI mapping tab is where administrators can generate and review mapping recommendations.

The screen should clearly show:

1. AI provider: Bitlogika AI Gateway, Direct OpenAI, or Heuristic fallback.
2. Model or Bitlogika model alias.
3. Confidence score.
4. Field-level suggestion.
5. Generated rules for attributes, specifications, categories, and pictures.
6. Fields requiring manual review.

AI mapping creates the first draft. The administrator still owns the final mapping decision.

Runs

Runs show every dry run, import, and export execution.

Use runs to verify:

1. Total records read.
2. Inserted count.
3. Updated count.
4. Skipped count.
5. Failed count.
6. Run mode: dry run or live run.
7. Summary of what happened.

For support, a run ID plus logs usually gives enough traceability to understand a problem.

Logs

Logs explain the run at row and entity level.

Useful log messages include:

1. Source read started/completed.
2. Duplicate matched by source identity or SKU.
3. Category created or reused.
4. Picture downloaded or skipped.
5. Attribute/specification created or reused.
6. Required field missing.
7. External connector/authentication error.

Logs should never expose raw API keys, passwords, or tokens. Use masked values and credential references.

Settings

Settings control license, AI gateway, agent API, update checks, and connector defaults.

Recommended production settings:

1. Validate license through Bitlogika API.
2. Use X-NopBridge-Agent-Key for NopBridge Control Center access.
3. Keep secrets out of visible descriptors.
4. Show AI provider and fallback status to administrators.
5. Keep update checks enabled when outbound access is allowed.
6. Log warning-level messages when API/license services cannot be reached.

Help

The Help tab gives administrators quick explanations without leaving nopCommerce.

Good help content should cover:

1. Creating a source.
2. Understanding typed schema.
3. Building product/customer mapping.
4. AI mapping review.
5. Dry run and live run.
6. Schedules and source retention.
7. Licensing and limits.
8. NopBridge Control Center connection.

For deeper setup, link to the full Bitlogika documentation pages.