Ecwid Shopping Cart embeds a hosted store on WordPress through a plugin that keeps a small set of local references, store ID, embedded product IDs, embedded category IDs, last-sync timestamps. Those crumbs live in wp_options and postmeta, invisible from any admin view, and they are exactly the data a migration project needs to plan.

SleekView Charts reads the local references and joins them with post titles. A Number card counts every post embedding an Ecwid product, a Donut splits embeds by type (product vs category), a Bar ranks pages with the oldest sync timestamp, and an Area chart trends embed creation by post date.

The dashboard is purely a local-state view, no Ecwid API calls. That makes it reliable when the connection is flaky and useful when planning a move off the platform.

Most teams assume an Ecwid integration leaves nothing on the WordPress side. The truth is that every embed is a local reference that becomes load-bearing when planning a migration or hunting an outage. A dashboard makes those references visible without an API call.

Sync staleness shows up before customers complain. Embed counts answer the simplest migration question: how big is this. The dashboard exists to keep an outwardly-cloud integration accountable on the host side, which is where the rebuild bill always lands.