Help starts with the workflow
The fastest support path is to explain what you are trying to do: launch a store, invite distributors, fix product data, process an order, or connect an integration.
Find help for setup, product catalogs, distributors, orders, invoices, storefronts, integrations, and buyer-facing workflows.
The fastest support path is to explain what you are trying to do: launch a store, invite distributors, fix product data, process an order, or connect an integration.
Founders, operators, finance users, and buyers should all be able to understand the next step without needing technical language.
Set up your account, import products, invite team members, and configure your first distributor.
Manage orders, invoices, storefront publishing, distributor details, and daily workflows.
Connect BrandGate with finance, ecommerce, payments, shipping, API, and export flows.
Help center
Good help content makes the product feel more professional because users know what to do next.
Guidance should use the same words users see in the app.
Disconnected, empty, loading, and validation states need plain explanations.
Some support questions come from distributors, not only the admin team.
Users should know when to contact support instead of guessing.
Help center
Send enough context that the team can reproduce the issue or map the workflow.
Mention where you were working: products, orders, store editor, settings, or live store.
Explain what you clicked, entered, uploaded, or expected to happen.
Add screenshots, error text, browser, device, and whether it affects buyers or admins.
Most questions fall into one of these operational buckets.
Products, categories, distributors, price lists, and store settings.
Orders, invoices, fulfillment, reports, and buyer questions.
Stripe, Fortnox, domains, DNS, API, imports, and exports.
Use the contact page or email support@brandgate.dev with the workflow and page where you need help.
Yes. Share your distributor count, catalog size, and current process so the setup can be mapped clearly.
Route, browser, steps, expected result, actual result, screenshot, and any console or network errors if available.
Send the route, action, and expected outcome so support can help faster.
Contact support