ecwid

Plan Ecwid app integrations using JavaScript SDK events and REST API scopes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Builds a correct integration plan for creating an Ecwid (Lightspeed eCom) app, covering both storefront customization and server-side data access without breaking the SPA lifecycle or OAuth security requirements.

Core Features & Use Cases

  • Storefront app design (JavaScript SDK): Customize category/product/cart/checkout experiences by using Ecwid widget page events and cart APIs rather than relying on DOM lifecycle events.
  • Server-side integration (REST API): Create and manage products, orders, customers, categories, and discount coupons through OAuth-authenticated endpoints.
  • App extensibility (App Market + webhooks): Register apps for marketplace distribution and use webhooks for real-time updates instead of polling.
  • Native vs storefront app approaches: Choose between iframe-based native apps (Control Panel UI) and storefront JS-based apps (widget-injected behavior).

Quick Start

Use the ecwid skill to draft your app architecture by selecting storefront JavaScript SDK events and defining the REST API scope set and webhook strategy for your target features.

Frequently Asked Questions about ecwid

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

FAQPage Schema
How do I build an Ecwid app that customizes the storefront using the JavaScript SDK?

To build an Ecwid storefront app, use the JavaScript SDK and subscribe to SPA page events like OnAPILoaded, OnPageLoaded, and OnPageSwitch rather than relying on standard DOM lifecycle events to inject custom widgets.

How do I authenticate Ecwid REST API requests for managing products and orders?

Authenticating Ecwid REST API requests requires implementing OAuth 2.0 to obtain access tokens, then scoping your base URL to your numeric storeId to securely manage products, orders, and customers.

Can I use webhooks for real-time order updates instead of polling the Ecwid API?

Yes, you can register webhooks in your Ecwid App Market listing to receive real-time updates for events like new orders, avoiding the need to continuously poll the REST API endpoints.

What is the difference between native and storefront Ecwid app approaches?

Native apps use iframe-based interfaces for the Control Panel, while storefront apps use the JavaScript SDK to inject custom behavior directly into category, product, cart, and checkout pages.

Why does my Ecwid storefront JavaScript app break during page navigation?

Ecwid is a single-page application, so custom JavaScript breaks during page navigation if it relies on DOM events instead of the native SPA lifecycle events like OnPageLoaded and OnPageSwitch.

Do I need an App Market listing to distribute my Ecwid integration?

Yes, registering your app on the Ecwid App Market is required for distribution, enabling both iframe-based native Control Panel apps and storefront widget extensions for users.