ERP-connected applications

One system of record, many ways in

Start a conversation

Applications built as an extension of the ERP, so operational interfaces can be simplified without creating a second source of truth.

A clay render of slabs docked flush to one core.
In scope

What ERP integration covers

Four things an application inherits from the ERP rather than keeping its own copy of.

Shared data

Products, partners, stock and orders read from the ERP, so a figure changed on a phone is the figure everyone else sees.

Shared users

One account per person, with the permissions their role already carries, rather than a second directory to maintain.

Shared transactions

What the application records is a transaction in the ERP, posted once, not a message to be imported later.

Role-specific mobile screens

The subset of the system a job actually needs, on the device that job is done on.

The alternative

Two systems, and the meeting that reconciles them

Mobile and business applications

An application that keeps its own records becomes a second source of truth, and a second source of truth becomes somebody's weekly job. Building onto the ERP is what stops that job existing.

A clay render of surfaces docked to one base.
What changes

Three things that stop

Importing yesterday

The record is written where it belongs, when it happens.

A second login

One account, one set of permissions, one place to revoke it.

Reconciling two figures

There is only one, and everything reads it.