Yes. Both versions store shop data as user meta on the vendor role, with the same pv_shop_name and pv_shop_slug keys. Pro adds additional meta for ratings and store hours, which SleekPixel can read if present without breaking on Free installs.

Yes. The template can branch on the vendor's user role and on the pending_vendor capability check. Pending vendors typically get a fallback marketplace card so a not-yet-approved store does not leak through previews.

If the vendor uploaded a custom avatar via WC Vendors Pro, SleekPixel uses that image. If not, it falls back to the WordPress avatar (Gravatar) and finally to a generated initial-based mark using the shop's first letter and accent colour.

The template defaults to the current effective price (sale if active, regular otherwise), matching what the storefront page renders. You can swap to a strike-through layout that shows both regular and sale price if your marketplace wants to emphasise discounts.

Yes. Cards generate on save rather than on request, so scale is bounded by save frequency, not by traffic. The first time you enable the template, a background regeneration via Action Scheduler queues every vendor and processes them in batches.

By default the template is set by the marketplace owner, so branding stays consistent. SleekPixel can expose a small set of vendor-controlled fields (accent colour, tagline) via the WC Vendors dashboard if you want vendors to personalise within marketplace guardrails.

The product card stops being generated for that listing, and the storefront card refreshes its product count automatically. Old share URLs for the now-unpublished product fall back to the storefront card or a generic out-of-stock card based on template settings.

No. SleekPixel only writes the og:image meta tag and generates PNG files in the uploads directory. The WC Vendors dashboard, commission calculations, and order routing are untouched. The plugins run in parallel without sharing state.