SABSUS Support

Effective date: May 9, 2026. This page describes the general public policy. Specific commercial agreements, implementation scopes and signed contracts may define additional terms.

Support for demos, implementation, accounts, billing, integrations, data, apps and technical questions.

How to contact support

Email support@sabsus.com and include your company, account email, role, page or module, issue description, screenshots and steps to reproduce.

Implementation

Support can help define first modules, prepare catalog, employees, payment methods, locations, roles, customer storefront and core operating workflows.

Technical issues

For integrations, include the endpoint, request body, API response, date and time, company ID, flow ID or order ID if available.

Data and deletion

Data deletion, account deletion and customer information requests are handled through Data Deletion, Account Deletion or support email.

Commercial questions

For pricing, white-label, buyout and custom implementation, include number of locations, business type, required modules and expected launch timeline.

Support priorities

Support requests are usually prioritized by operational impact. A complete outage, payment issue, order-blocking error or security concern is more urgent than a design change, content edit or general setup question. Clear screenshots, timestamps, account details and step-by-step reproduction notes help support diagnose issues faster.

What support can help with

Support can help with demo planning, onboarding, module selection, CRM setup, catalog structure, payment method setup, document templates, customer storefront questions, delivery workflows, inventory setup, user roles and integration troubleshooting. Custom development, complex data migration or private deployment may require a separate agreement.

App and white-label support

If a white-label or app-based deployment is involved, support may also need information about the app version, platform, device, browser, operating system, user role and the exact workflow where the issue appears. Store approval, branding, legal pages, account deletion and data deletion requirements should be reviewed before publishing customer-facing apps.

Information to include in a support request

A strong support request should include the company name, user email, role, affected module, exact page, expected result, actual result, screenshots, time of the issue, browser or device, and whether the issue happens for one user or multiple users. For payment or integration issues, include non-sensitive transaction identifiers, request time and the response status if available.

Onboarding support

During onboarding, support can help decide the first launch path. For example, a restaurant may start with catalog, POS and kitchen; a service company may start with services, staff schedules and booking; a retail company may start with catalog, receiving and stock; a delivery operator may start with courier tasks and route control. The fastest setup is usually the one that solves one real workflow first and then expands.

Unsupported requests

Support may not be able to resolve issues caused by incorrect data entered by the client, unavailable third-party providers, revoked external API permissions, unsupported devices, custom code outside the agreed scope or business rules that were not configured in the system. In these cases, support can explain the likely cause and suggest the next step.