Everything you might want to know.

RefundMind imports cases from any CSV export — Shopify, Trendyol, WooCommerce, custom platforms. You can also create cases manually. Direct, live integrations with Shopify and Trendyol are on the roadmap.

Yes. Your case, customer, and recovery data is yours — you can export it. We never lock your operation inside the product.

Yes. The import engine is multi-platform — bring Shopify, Trendyol, WooCommerce, and custom exports into one workspace, and cases stay tagged by the channel they came from so you can filter and work them separately. As you add channels, the operation scales in one place rather than one tool per platform.

The CSV engine is platform-agnostic — if you can export orders and returns as a CSV, RefundMind can import them. For custom systems, we map your fields during onboarding.

On infrastructure hosted in EU regions. Workspace data is fully isolated — we never share data across customers.

RefundMind is built with KVKK (Turkish data protection) and GDPR principles. Data is encrypted in transit and at rest, and we sign a Data Processing Agreement (DPA) with every customer.

You can export your data before you leave, and we delete it on request in line with our retention policy. The specifics are covered in the DPA and Privacy Policy.

Not today. We follow the security practices SOC 2 is built around — encryption, access control, data isolation — and formal certification is something we will pursue as we grow. Happy to walk through our current posture in a demo.

Most teams are running their first imported cases within a day: workspace setup (~15 min), CSV import + field mapping (30–60 min), team invitations and roles (~15 min). Onboarding is guided, not figure-it-out-yourself.

No. Importing a CSV and mapping fields is designed for the operations team. We work alongside you during onboarding.

Yes. Importing past returns is a good way to see recovery patterns from day one. The same CSV engine handles historical and ongoing imports.

RefundMind has role-based access with distinct roles, so the right people see and act on the right cases. Roles are configured per workspace.

Every brand's mix is different — case volume, channels, team complexity all matter. We tailor the plan to your operation, and the demo is where we figure out what fits and what it costs.

Yes — every account starts with a guided trial.

No. Volume is counted by cases created per month — one return handled end to end is one case. The historical returns you bring in during onboarding do not count against that monthly number, so you can load your back-catalogue to see recovery patterns without it affecting your plan.

Yes. As your case volume or channel mix changes, the plan moves with you.

A case is a single return handled end to end — from intake, through the decision (refund, exchange, store credit, or decline), to recovery tracking. The case is the unit the whole product is built around.

The decision engine suggests an outcome for each case using rule-based logic you control — your policies, channels, and thresholds. You stay in control of the final call.

Yes. The rule engine (advanced on Growth and up) lets you encode your returns policy so cases route and resolve the way your operation actually works.

It tracks what happens after the decision — exchanges, store credit, and recovered value — so a return is measured as recovery, not just a refund reflex.

Some places, honestly. Today, RefundMind uses rule-based logic for decision suggestions — not AI in the magic sense. The Intelligence module (on the roadmap) will introduce pattern detection and machine-learning territory: customer risk scoring, product defect signal aggregation, channel risk surfacing. When we use AI, we'll be specific about what it does and where. We don't want to be a company that puts 'AI-powered' on every screen.

The roadmap covers customer risk scoring, product defect signals aggregated across cases, and channel-level risk surfacing — patterns that are hard to see one case at a time.

Starter includes email support; Growth adds priority support; Enterprise adds a dedicated success manager. We work closely with early customers.

Yes — onboarding is guided, and we help your team get comfortable with the case workflow.

Most teams are running their first imported cases within a day — workspace setup is about 15 minutes, CSV import and field mapping 30–60 minutes, and team invitations and roles another 15 or so. It is work the operations team can do; you do not need engineering, and onboarding is guided rather than figure-it-out-yourself.

RefundMind is an early-stage product focused on the operator side of returns — the case lifecycle, decision-making, and recovery tracking. We build in the open about what is live, what is on the roadmap, and where we are headed.

If it is in the product and working today, we call it live. If it is not, we call it roadmap — plainly, on the same page — rather than dressing up a plan as a shipped feature. That is why the risk-scoring and defect-pattern work shows as roadmap here: we would rather under-promise and let the product speak than put “coming soon” on everything.

We're in early access and working with our first brands. We don't publish customer logos or case studies we can't stand behind yet — when we have results worth sharing, we will.