| name | sales-cartflows |
| description | CartFlows (cartflows.com) platform help — WordPress/WooCommerce sales-funnel & checkout builder: checkout layouts, custom fields, order bumps, one-click upsells/downsells, and A/B split testing. Self-hosted WordPress only — no hosted REST API and no MCP; automation runs on WP-CLI, personalization + offer-JS shortcodes, WordPress hooks, OttoKit/Zapier, and Cart Abandonment Recovery webhooks, with funnel revenue read from WooCommerce orders. Use when your CartFlows checkout 404s or falls back to the default WooCommerce checkout, a checkout-field or theme plugin conflicts, building one-click upsells/order bumps, sending abandoned-cart events to Zapier via webhook, reading funnel revenue via the WooCommerce API, wiring offer-accepted JS triggers, or choosing CartFlows vs FunnelKit/WPFunnels or Free vs Pro. Do NOT use for funnel/CRO strategy across tools (use /sales-funnel), checkout-conversion strategy across platforms (use /sales-checkout), or generic iPaaS wiring (use /sales-integration). |
| argument-hint | [describe what you need help with in CartFlows] |
| license | MIT |
| version | 1.0.0 |
| tags | ["sales","funnel","wordpress","platform"] |
CartFlows Platform Help
Step 1 — Gather context
If references/learnings.md exists, read it first for accumulated platform knowledge.
-
What are you trying to do?
- A) Fix a broken funnel — checkout 404 / "Page Not Found", default WooCommerce checkout showing instead of CartFlows, a plugin/theme conflict
- B) Build/optimize the funnel — checkout layout, custom fields, order bumps, one-click upsells/downsells, A/B test
- C) Wire automation — offer-accepted/rejected JS triggers, personalization shortcodes, Cart Abandonment Recovery webhook, OttoKit/Zapier
- D) Read funnel revenue/orders programmatically (via WooCommerce)
- E) Choose a plan/tool — Free vs Pro vs Suite vs lifetime, or CartFlows vs FunnelKit/WPFunnels
-
Free or Pro? Order bumps, one-click upsells/downsells, A/B testing, offer JS triggers (Pro vars), and WP-CLI are Pro. The free plugin builds basic funnels only.
Skip-ahead rule: if the user's prompt already provides enough context, skip to Step 2.
Step 2 — Route or answer directly
| If the question is about... | Route to... |
|---|
| Funnel / CRO strategy across tools (which builder, funnel design) | /sales-funnel {question} |
| Checkout/cart conversion strategy across platforms (AOV, order bumps as strategy) | /sales-checkout {question} |
| Connecting CartFlows to a CRM/ESP generically (iPaaS) | /sales-integration {question} |
| Abandoned-cart email sequence strategy beyond the recovery plugin | /sales-email-marketing {question} |
When routing, give the exact command, e.g. "This is a strategy question — run: /sales-funnel design a tripwire funnel with a post-purchase upsell".
Step 3 — CartFlows platform reference
Read references/platform-guide.md for the full reference — capabilities + what's WP-CLI/shortcode/hook/webhook vs UI-only, best-effort pricing (plugin tiers vs the Suite vs lifetime), the funnel/step/WooCommerce-order data model, and quick-start recipes (offer-accepted pixel; abandoned-cart webhook to Zapier; read funnel revenue via WooCommerce).
Read references/cartflows-api-reference.md for the developer surface — : WP-CLI (), personalization shortcodes (, ), Offer JS triggers/variables (, on Accept/Reject), WordPress filter hooks, Cart Abandonment Recovery webhooks, and reading funnel revenue via the .
