Frequently asked questions
Everything you need to know about FlxWoo: hosted Next.js + Tailwind rendering for WooCommerce with SEO reuse, Core Web Vitals guardrails, and instant WordPress fallback.
Getting started
Do we need to migrate off WordPress?
No. FlxWoo is a hosted rendering layer. WordPress still runs your theme, plugins, hooks, and SEO. We only replace the final HTML for the routes you map (e.g.,
/shop, /product/*).What routes should we map first?
Most teams begin with PLP (product listing) and PDP (product detail). These benefit most from caching and UI improvements, while Cart/Checkout stay native (no-cache) for safety.
How long does integration take?
Small stores can map initial routes in days. Agencies with designs ready (Figma/Tailwind tokens) often launch a first cut within 1–2 weeks.
Performance & Core Web Vitals
How does FlxWoo improve LCP/INP/CLS?
We render via Next.js + Tailwind with predictable image sizing, minimal client JS, and caching on content routes. Checkout is no-cache by default to protect interactions. Targets: LCP ≤ 2.5s, INP ≤ 200ms, CLS ≤ 0.1 (actuals vary by site).
What’s cached and what isn’t?
PLP/PDP and other non-transactional pages can use ISR/SWR-style caching. Cart, Checkout, and account pages avoid cache by default.
Can we monitor Web Vitals?
Yes. You can send Web Vitals to GA4/BigQuery or your monitoring tool. FlxWoo integrates cleanly with common libraries.
SEO & URLs
Will our SEO be preserved?
Yes. FlxWoo reuses output from SEO plugins like Yoast or RankMath (titles, canonicals, JSON-LD). URLs remain the same for mapped routes.
Do we need to rebuild schema markup?
No. We surface your existing JSON-LD in the rendered HTML to maintain parity.
Does SSR/ISR affect indexing?
No adverse effect—pages are server-rendered and cacheable; search engines can crawl them normally.
Checkout & safety
Is Checkout safe with FlxWoo?
Yes. Cart/Checkout are no-cache by default, and WooCommerce security constraints remain in place. Sensitive flows bypass the cache entirely.
What if the renderer has an outage?
Health checks trigger an instant fallback to your original WordPress theme for mapped routes, so customers aren’t blocked.
Can we opt-out certain routes?
Absolutely. Route mapping is granular—only switch what you’re ready to switch.
Plans, pricing & white-label
How is pricing calculated?
Traffic-based per site. Lite (~50k monthly views), Standard (~300k), and Pro (custom with overages/SLA). View counts are soft limits; we’ll notify you about sustained overages.
Do you offer a white-label option for agencies?
Yes. Branding removal + custom domain/CNAME (e.g., store.agencybrand.com) starts at $10/mo and is included with Pro.
What’s the difference between FlxWoo and FlexWoo?
FlxWoo is hosted SaaS (no infra to manage). FlexWoo is a self-hosted plugin + Next.js code for teams wanting full code control. You can start on FlxWoo and later migrate to FlexWoo if needed.
Security & data
Does FlxWoo store customer data?
By default, no PII is persisted in the renderer. Sensitive operations remain within your WooCommerce/WordPress environment.
Is there a DPA or enterprise terms?
Yes. Pro/Enterprise engagements can include DPAs, SLAs, and custom terms—contact sales to discuss.
Still have questions?
We’ll recommend the right rollout and plan based on your traffic, plugins, and goals.