Please introduce an optional, native core architecture mode where Stripe (or external payment processors) acts as the immutable source of truth for products, pricing, and checkout.
The Pain Point:
I have worked with clients who do not trust entering sensitive product, pricing, or financial configuration directly into WordPress/WooCommerce, but completely trust doing so inside Stripe. This exact issue led me to develop my own custom plugin, Storefront for Stripe.
Github: https://github.com/leadstartorg/storefront-for-stripe
When pricing errors, tax calculation mismatches, or plugin conflicts occur inside WordPress, clients struggle to audit. By allowing merchants to manage and audit their product catalog and pricing directly in Stripe , this eliminates ambiguity, reduces liability, and solves deep-seated client-developer trust issues.
If WooCommerce operates in an Import-Only / Read-Replica Mode:
– Products, prices, metadata, and subscriptions are managed directly within the Stripe Dashboard (or via Stripe APIs).
– WordPress is used purely for content, SEO, rich layouts, and frontend catalog browsing, while checkout and billing execution map directly back to Stripe’s secure infrastructure.
– Stripe metadata fields can be standardized to handle custom merchandising attributes (e.g., display tags, category sorting, variant swatches, related items) so merchants retain full design flexibility.
– We are offloading core billing and state validation reduces custom cart/checkout plugin bloat, and mitigates database sync drift.
Last updated: October 12, 2026
0 comments
Log in to comment on this feature request.