nopcommerce

Guide nopCommerce .NET plugin development with manifest, lifecycle, and integration patterns.

1|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/biggora/e-commerce-plugin-skills --skill nopcommerce
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nopcommerce
Source: https://github.com/biggora/e-commerce-plugin-skills/tree/main/skills/nopcommerce
Command: npx skills add https://github.com/biggora/e-commerce-plugin-skills --skill nopcommerce

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It solves the confusion and trial-and-error involved in creating a correct, production-ready nopCommerce plugin for .NET/C#.

Core Features & Use Cases

  • Plugin architecture guidance: Covers where plugins live, how to structure code, and which nopCommerce layers (Nop.Web, Nop.Services, Nop.Data, Nop.Core) to target.
  • Lifecycle + compatibility setup: Explains the plugin.json manifest, BasePlugin install/uninstall flow, and how to align with SupportedVersions.
  • Implementation-ready building blocks: Provides patterns for DI (INopStartup), data access (entity builders, Linq2DB, IRepository, migrations), and extensibility mechanisms (events, view components, admin extensions).

Use case example: You want to build a nopCommerce payment plugin with dependency injection, database tables/migrations, and an admin configuration page that saves store-scoped settings.

Quick Start

Use the nopcommerce skill to scaffold the structure and implementation plan for a plugin that follows plugin.json, BasePlugin lifecycle, NopStartup DI, and Linq2DB + FluentMigrator data patterns for the .NET/C# nopCommerce architecture.

Frequently Asked Questions about nopcommerce

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure a nopCommerce plugin for .NET?

nopCommerce plugin development requires following specific directory conventions and creating a plugin.json manifest with SupportedVersions compatibility. You target nopCommerce layers like Nop.Web, Nop.Services, Nop.Data, and Nop.Core, using BasePlugin for lifecycle management.

How do I add database tables and migrations to a nopCommerce plugin?

Database schema extension in a nopCommerce plugin uses Linq2DB and FluentMigrator for migrations. You implement entity builders and use IRepository for repository-based data access, ensuring proper database tables are created during the BasePlugin InstallAsync method.

How does dependency injection work in nopCommerce plugins?

Dependency injection in nopCommerce plugins is configured by implementing the INopStartup interface. You register your plugin's services and dependencies within this startup class, allowing the nopCommerce application container to resolve and inject them throughout the Nop.Web and Nop.Services layers.

What is the correct way to handle plugin installation and uninstallation in nopCommerce?

Plugin installation and uninstallation in nopCommerce are handled by overriding the BasePlugin InstallAsync and UninstallAsync methods. You must ensure proper cleanup of database schemas and store-scoped settings during uninstallation to maintain system integrity.

Does nopCommerce plugin development support store-scoped configuration settings?

Yes, nopCommerce plugin development supports store-scoped configuration settings. You can save and retrieve these settings through an admin configuration page, using safe admin extension patterns with localized UI and view components for the configuration interface.

Can I extend the nopCommerce admin interface with a custom plugin page?

You can extend the nopCommerce admin interface using safe admin extension patterns within your plugin. This involves creating view components and localized UI elements to add custom configuration pages for features like payment, shipping, or widget integrations.