KitSure Support

Get routed by the SureCart workflow you are working on: presales fit, migration discovery, addon setup, issue reports, or documentation questions.

Support paths

Choose the path that fits the question

The fastest route is to name the workflow first, then include the store context KitSure needs to understand the next step.

Presales and fit

Use this for questions about which KitSure track fits a SureCart store, what is available now, and what still needs review.

Ask fit question

Migration discovery

Use this when moving from WooCommerce or another setup into SureCart and you need scope review before production work.

Plan migration

Addon issue

Use this for Wishlist, Gift Cards, or Filters behavior after you can describe the page, action, account state, and expected result.

Report issue

Documentation help

Use this when you need setup notes, workflow guidance, or a pointer to the right public page while the help center grows.

Open docs

What to include

Send the context that makes the answer useful

This page is for routing and context collection. The goal is to gather enough information for a focused answer or a proper discovery conversation.

Store URL, staging URL, or a short description of the SureCart build.

Which KitSure track is involved: Wishlist, Gift Cards, Filters, Migration, POD waitlist, Docs, or Guides.

SureCart version, KitSure version, active theme, and whether the issue happens for guests, logged-in customers, or admins.

The exact workflow: page, button, checkout path, account view, filter state, gift card action, or migration source.

Expected result, actual result, screenshots, console notes, logs, and steps to reproduce when reporting an issue.

For migration, include source platform, data scope, subscriptions, redirects, integrations, and launch timing concerns.

Contact

Send a support message

This local form is a placeholder until an approved form provider is connected. Use the message field to describe the workflow, store context, and evidence.

Looking for setup guidance first?

Start with the public docs landing page or the practical guides, then send a support message if your workflow needs store-specific review.

Open docs