OptiFlowPro

Architecture

Wired into your Sage database,
not sitting beside it

The question that decides whether a Sage integration succeeds is not “does it connect”. It is “what writes, and how”. OptiFlowPro keeps the two strictly apart.

Channel 1

Read

Direct database access

Lookups, searches, reports and dashboards go through direct access to your SQL Server database. Screens stay instant even on large databases, with no limit on how far back you look.

Channel 2

Write

Dedicated web service

Every document creation or change goes through a service that talks to Sage via its own components. The resulting document is identical to one keyed in Sage: same checks, same counters, same postings.

Why we never write directly to the database

The Sage data model carries business rules that are not all expressed in the database schema: counters, header-to-line consistency, analytical postings, document chaining. A direct write that ignores one of them produces a database that is consistent for SQL Server and inconsistent for Sage. The symptom appears only weeks later, often at period close. That is why all of our writes go through the web service.

What does not change on your side

  • No change to your Sage configuration
  • No replication of your data to a third-party cloud
  • No direct writes into Sage tables
  • Your existing customisations are surveyed during the audit

Sage remains your system of record. OptiFlowPro is an operations layer on top of it, not a second ERP to reconcile.

Prerequisites

Sage 100c
An existing installation with a SQL Server database. Your version is confirmed as compatible during the audit.
Application server
Windows with IIS, or Apache. The application installs next to Sage, on your infrastructure.
Network access
A link between the application server and your Sage database. No inbound access from the internet is required for basic operation.
User devices
A recent browser. Nothing to install on desktops or phones.

Multi-company

An installation with several companies means several Sage databases. OptiFlowPro handles them from a single application, keeping each company's data strictly separate.

Separation

Each company has its own users, permissions and data. A user in one company sees nothing of the others.

Declared databases

The Sage databases covered are declared by name. A database that is not declared stays invisible to the application.

Consolidated view

Management functions can aggregate several companies for the profiles authorised to see them.

Is your installation compatible?

Version, modules in place, customisations, data volume: the audit answers those questions before the first line of code is written.

Request an audit