| name | sales-ecwid |
| description | Ecwid (by Lightspeed) platform help — embeddable ecommerce that adds a store and checkout to any existing site (WordPress, Wix, custom HTML) plus a hosted Instant Site, with 0% transaction fees, multichannel selling (Instagram/TikTok/Google/Amazon), a REST v3 API (app.ecwid.com/api/v3/{storeId}, Bearer secret_/public_ tokens, 600 req/min), and HMAC-signed webhooks. Use when adding a store to a site you already run instead of replatforming, Ecwid webhook signature verification keeps failing (it uses client_secret, not your secret_ token), the free plan's 10-product cap or paid-plan-only API blocks you, product pages load slowly, syncing Ecwid orders into a CRM or warehouse via API/webhooks, QuickBooks inventory won't sync back, or comparing plans after recent price changes. Do NOT use for choosing between store builders or checkout optimization strategy (use /sales-checkout) or full-store platforms like Shopify (use /sales-shopify). |
| argument-hint | [describe what you need help with in Ecwid] |
| license | MIT |
| version | 1.0.0 |
| tags | ["sales","checkout","ecommerce","platform"] |
| github | https://github.com/Ecwid |
Ecwid Platform Help
Ecwid (by Lightspeed) is embeddable ecommerce: a widget that adds a full store — catalog, cart, checkout — to any site you already run, plus a hosted Instant Site. 0% platform transaction fees; automation via a REST v3 API and HMAC-signed webhooks. The core fit: adding commerce to an existing site instead of replatforming.
Step 1 — Gather context
If references/learnings.md exists, read it first for accumulated platform knowledge.
Ask only what you can't infer from the user's prompt:
-
What are you trying to do?
- A) Embed/add an Ecwid store to an existing site (WordPress/Wix/custom)
- B) Integrate Ecwid data (orders/products/customers) with a CRM, warehouse, or your app
- C) Set up or debug webhooks / signature verification
- D) Decide on a plan (Free/Starter/Venture/Business/Unlimited) or understand limits
- E) Fix a storefront problem (speed, customization, sync)
-
Plan tier? API access requires a paid plan; variations and digital goods are plan-gated — most "why can't I do X" questions are plan questions.
Skip-ahead rule: if the user's prompt already has enough context, go straight to Step 2.
Step 2 — Route or answer directly
| If the user's question is about… | Route to |
|---|
| Which store/checkout platform to pick (Ecwid vs Shopify/Square Online/Snipcart) | /sales-checkout {question} |
| Full-store Shopify questions | /sales-shopify {question} |
| Checkout-conversion strategy (bumps, upsells, cart abandonment) across tools | /sales-checkout {question} |
| Selling digital downloads strategy | /sales-digital-products {question} |
| Tax / Merchant-of-Record obligations | /sales-merchant-of-record {question} |
When routing, give the exact command: "This is a {domain} question — run: /sales-checkout {original question}"
Otherwise, answer Ecwid-specific questions directly using Step 3.
Step 3 — Ecwid platform reference
Read references/platform-guide.md for the full reference — capabilities & automation surface, pricing/plan gates, data model, and quick-start recipes (paginated order sync, signed webhook listener, bulk price update).
