n-What Does Ecwid Actually Integrate With?
Ecwid, now part of Lightspeed, is built to embed into other site platforms and sell across multiple channels at once: WordPress, Wix, and Squarespace via official widgets; Facebook, Instagram, Amazon, and eBay as sales channels; Square, Stripe, Clover, and PayPal for payments. What it doesn't connect to natively is your accounting software, and that's almost always the first gap a growing Ecwid store runs into.
What Ecwid connects to out of the box
Embedding is Ecwid's core trick: official plugins drop the same catalog into WordPress, Wix, Squarespace, and a handful of other site builders, so the store isn't tied to one platform's checkout. If your site already runs on one of those, adding Ecwid is usually a plugin install, not custom work.
Selling across channels works the same way: Ecwid can list the same products on Facebook, Instagram, Amazon, and eBay from one catalog, syncing stock and orders back to a single dashboard instead of managing each channel separately.
Payments cover the common processors, Square, Stripe, Clover, PayPal, natively, and Ecwid's own payment gateway API lets a developer add a gateway that isn't on that list. That's a real documented option, not a hack, for businesses with a processor Ecwid doesn't support out of the box.
Since Lightspeed acquired Ecwid in 2021, it also sits closer to Lightspeed's POS and retail tools than it used to, which matters if a business already runs Lightspeed hardware in a physical location.
Where the native connections stop
Accounting is the clearest gap. There's no native QuickBooks or Xero connector, so every order from every channel Ecwid touches still needs someone to get it into the books, usually by hand, which defeats a lot of the point of selling across several channels at once.
CRM is similar: Ecwid tracks customer and order data inside its own dashboard, but getting that into a real CRM with purchase history attached is a custom job against Ecwid's REST API, not a toggle in the settings panel.
The payment gateway API is the one place custom development is genuinely the documented path rather than a workaround, worth knowing if a quote ever calls it anything less official than that.
What this usually looks like
Every channel's orders landing in your books
Orders from the Ecwid website, Facebook, Amazon, and eBay listings all turn into correctly taxed invoices in QuickBooks or Xero automatically, instead of someone reconciling four channels by hand.
A payment gateway Ecwid doesn't support natively
Using Ecwid's own payment gateway API, we add a processor that isn't on the native list, a real integration path, not an unsupported workaround.
Which Ecwid channel still needs someone to check it manually?
Tell us which sales channel or payment setup isn't flowing into the rest of your business automatically yet.
Running Ecwid across more channels than your other systems can keep up with?
Each channel Ecwid adds is one more place a sale can happen without your books, your CRM, or your warehouse system finding out right away. Tell us which channels you're actually running and where the data stops moving on its own.
Let's talk