Odoo is the fully active adapter today. Microsoft Dynamics 365 is also selectable as a connection type and is built on the same extensible framework — additional adapters can be activated without redesigning the core.

Six entities are supported: Product, Customer, Order, Image, Price, and Stock. Products, Customers, and Orders sync outbound (nopCommerce → ERP) automatically. Products, Customers, and Prices also sync inbound (ERP → nopCommerce) on the polling schedule. Manual pull is available for all six entities; manual push is available for Product, Customer, Order, and Image.

Outbound changes are queued within seconds of a record save in nopCommerce — before the next scheduled task runs. The Event Processor then picks them up on its cycle (default every 60 seconds). Inbound changes from the ERP arrive on the Inbound Poll interval (default every 300 seconds, configurable in ERP Connector Settings).

Yes, fully. The Sync Entity Table Mapping screen lets you bind specific nopCommerce database tables to each entity, so only the relevant changes raise events. The Field Mapping screen then lets you define exactly which nopCommerce column maps to which ERP property — separately for the Inbound and Outbound directions — with type, required, key, default value, and optional condition rules, all without writing any code.

Every sync attempt is recorded on the Dashboard with its status, error message, and full payload JSON. You can open any failed event and retry it in one click — the event is re-queued as Pending and reprocessed on the next Event Processor run. One failing item never blocks the rest of the queue, and the Sync Log gives a step-by-step trace for deeper diagnosis.

Access is controlled by six independent permissions in the nopCommerce Access Control List: Manage Settings, Manage Connections, Manage Sync Entities, Manage Mapping, Manage Actions (manual sync), and Manage Events (Dashboard and Sync Log). Each permission can be assigned independently per customer role, so a support team can view and retry events without being able to change mappings or credentials.

Install Nop-Station Core first, then upload the ERP Connector plugin, restart the application, and enter the license string to enable it. It runs on nopCommerce 4.90.6 with the store's scheduled tasks enabled. From there, create an ERP Connection, configure your Sync Entity Table Mappings and Field Mappings, and the pipeline starts automatically.