FAQ
Does OCart replace the WooCommerce checkout?
No. OCart sits on top of Woo. Your gateways, taxes, shipping zones, coupons, and order data stay native. OCart paints a polished funnel layer on top. The general.replace_woo_checkout setting defaults to false.
Will it conflict with my theme?
Storefront CSS is scoped to #ocart-wrap and .oc-storefront, so it cannot leak. Theme overrides only fire on OCart-rendered pages plus pages that contain the OCart shortcode or block.
Is HPOS supported?
Yes. OCart declares compatibility with custom_order_tables and cart_checkout_blocks on before_woocommerce_init.
How do upsells charge without re-entering the card?
Each gateway adapter implements charge_off_session(). Stripe uses payment intents with off_session=true. Paystack uses authorization codes. PayPal uses Vault / Reference Transactions. The buyer's payment method is stored at first-checkout time and the upsell handler charges it on accept.
Is the buyer's card stored on my server?
No. Only the gateway-side payment-method ID (for example pm_abc123 from Stripe) is stored in WC order meta. The card itself never touches your database.
How do recovery emails handle deliverability?
OCart sets RFC 8058 List-Unsubscribe-Post headers, maintains its own suppression list (shared with SMS), and records every send, bounce, and complaint to the wp_ocart_deliverability_events table for reporting.
Can I export funnel and offer config?
Yes. Settings, Backup, Export downloads a full JSON dump of funnels, steps, offers, sequences, tests, and settings. Import re-creates everything with new IDs.
Does OCart work with the WooCommerce Cart and Checkout Blocks?
Yes. The ocart/checkout block is registered as a server-rendered block compatible with WC's block-based checkout.