Integrations

Works with the systemsyou already run

Keep your tools. Noah, ERP / POS, CRM, single sign-on, LINE and your own systems — data flows through one workflow.

Into SONUSSent by SONUS
SONUS SYSTEM at the centre, connected to Noah, ERP / POS, CRM, single sign-on, LINE and the API.

What connects

Plug into what your stores already use

What each integration carries, and in which direction — one card each.

  • Audiology standardCore

    Noah

    After a test, the audiogram and measurements come into SONUS AI and attach to that customer's record — the fitting AI and the audiologist read the same data.

    NoahSONUS

    Import

    What travels

    • Audiograms
    • Test measurements
    • Test dates
  • Business systems

    Your ERP / POS

    Products and stock follow the system you already run; orders closed in SONUS AI sync back, so stores and HQ reconcile to the same numbers.

    ERP / POSSONUS

    Two-way sync

    What travels

    • Products & prices
    • Stock & serials
    • Orders & sales
  • Customer data

    Your CRM

    Customer details and service history stay in step both ways — marketing or service teams keep their CRM, and stores never key the same record twice.

    CRMSONUS

    Two-way sync

    What travels

    • Customer details
    • Service history
    • Follow-up status
  • Identity & access

    Single sign-on (SSO)

    Staff sign in to SONUS with their company account (SAML / OAuth) — no extra password — and accounts and permissions are managed in one place.

    Company IdPSONUS

    Sign-in

    What travels

    • Staff accounts
    • Authentication
    • Roles & access
  • Messaging

    LINE

    When a booking or follow-up comes due, SONUS sends the reminder or check-in over LINE — in the app customers already open every day.

    LINESONUS

    Sent by SONUS

    What travels

    • Appointment reminders
    • Follow-up check-ins
    • Care reminders
  • Open platform

    APIs & Webhooks

    Internal systems read and write through a standard REST API; when something happens — a booking made, a device handed over — a webhook tells your systems.

    Your systemsSONUS

    Read, write & events

    What travels

    • REST API
    • Webhook events
    • Audit trail

These are typical set-ups; the exact scope and direction of each connection are confirmed during onboarding.

How it gets connected

Three steps, stores stay open

Integrations follow the three rollout phases: map, connect, then pilot before going live everywhere.

  1. 01

    Build & prepare

    Map what you run

    List the systems stores and HQ use, their data fields and owners — then decide what connects, and how.

  2. 02

    Build & prepare

    Map data and access

    Agree what comes in, what goes out and who can see it — set up and tested during the build, with our specs and support.

  3. 03

    Pilot → all stores

    Pilot, then roll out

    Pilot in one or two stores, check the data is right, then roll out to every store — with no store downtime.

Connected — controlled and auditable

  • Encrypted in transitTLS 1.3 in transit, AES-256 at rest
  • Role-based accessStores, managers and HQ see their own data
  • Audit logWho viewed or changed what, on record
  • Hosted in TaiwanHandled under Taiwan's PDPA

Questions

Before you connect, what teams ask

  • Do we have to replace our current systems?

    No. SONUS SYSTEM connects to what your stores and HQ already run; what comes in and what goes out is decided together during onboarding.

  • Do we need an IT team?

    Usually not. An operations or clinical lead can run it; for integrations, we provide specs and support.

  • How are scope and timeline set?

    They depend on store count, the systems to connect and workflow maturity, and are confirmed during onboarding. A full rollout takes about 2–3 months in three phases.

  • Don't see the system you use?

    We can scope a custom connection on the standard API and webhooks — tell us what you run.

    Talk to us about an integration

Bring SONUS SYSTEM into your stack

We confirm scope and timeline during onboarding.