BranchFlow

For IT and systems owners

We will not show you a connection we have not made.

Connect POS, supplier, accounting, BI, and messaging data to branch operations — once your credentials are provided, the connection is scoped and a test succeeds. Nothing is connected by default, and connections read data without writing back.

What we can state plainly

Each line here is something the running system does today, not an ambition.

  • Test and live environments are separate, and credentials are held server-side only.
  • Sync runs keep a history with failures, retries and what changed.
  • Reading sales and supplier data has been built; nothing writes back to your systems.
  • Until a connection is tested in your workspace it shows as not configured, never as connected.

How it works in practice

  1. 1

    Choose the connection

    Pick the system and the environment you are setting up.

  2. 2

    Add credentials

    You provide them; they are stored server-side and never shown in the app.

  3. 3

    Map fields

    Match your fields to ours, with AI suggestions an administrator approves.

  4. 4

    Test

    Run a sync and reconcile differences before going live.

  5. 5

    Monitor

    Review sync history, failures and retries.

What you get

  • Connection states

    Not configured, testing, connected, warning, failed and paused.

  • Field mapping

    Explicit mapping with suggestions that require approval.

  • Sync history

    Runs, records, failures and retry queue.

  • Read-only by design

    Sales, supplier and headcount reads; no writes into your systems.

The screens behind this page

Every entry names a real screen in the application and its state today.

  • /integrationsNeeds your system connected

    Connection setup, field mapping and sync history

    Connection management exists today. No customer system is attached, so nothing is shown as connected.

    Data shown: No customer system attached

What's included

What you get on day one, and what we connect to your own systems during onboarding.

Included

  • Connection management, mapping, sync history, reconciliation and a safe test mode

Connected during setup

  • POS, Oracle, accounting and business-intelligence connections need your credentials
  • WhatsApp, SMS and email delivery need your accounts and approved message templates

Common questions

Is there a public API?
A public sales-feed endpoint is available; further API access is scoped per customer.
Will it change data in our POS?
No. What is built reads data. Nothing writes back into your systems.

How access and records are handled

Each organisation's records are separated in the database, and people only see the branches they are assigned to. Status changes, approvals, rejections and verifications are recorded with who did them and when. We do not claim any external certification or audit at this stage; if you need a formal security review, ask us and we will tell you exactly what exists today.

Walk this part of the system yourself.

The demonstration workspace is loaded with clearly labelled sample branches and records, so you can test this workflow end to end before deciding anything.