Sage Addons Internal portal for Sage 200
Hosting & implementation

Deploy the portal the way the company needs it.

Offer either a managed cloud portal for speed and simplicity, or a self-contained on-premise deployment for companies with stricter infrastructure requirements.

Compare hosting View requirements
Required for live deployment

Sage 200 API setup + Sicon where used

The company must have the required Sage 200 API access/licensing and the relevant Sicon module installed for Sicon-backed workflows.

Hosting options

Cloud managed or on-premise self-contained.

Managed cloud

Best for fast launch

Hosted and managed for the company, with portal access available through secure public or restricted endpoints depending on scope.

  • Lower internal IT burden
  • Faster rollout path
  • Managed updates and support approach
  • Good for distributed internal teams
From £4,950 setup + £995/month
On-premise

Best for controlled IT environments

Installed into company-controlled infrastructure, suited to teams that need tighter network, data residency or internal governance control.

  • Company-controlled infrastructure
  • Private network options
  • Self-contained deployment model
  • Ongoing support and upgrade plan
From £7,500 setup + £695/month
Requirements

What companies need before go-live.

This should be confirmed during discovery before you promise a launch date or fixed price.

Sage 200 environmentSupported Sage 200 setup with appropriate API configuration.
API licence / userValid Sage 200 API licence/user or authorised API setup according to the company’s Sage terms.
Sicon moduleRequired where purchase order or other Sicon-backed workflows are being sold.
Operational data mappingAccounts, contacts, pricing rules, addresses, departments and permissions must be mapped.
Security reviewAuthentication, password policy, roles, audit trail, data retention and access boundaries must be agreed.
Test environmentRecommended for integration testing before production access is enabled.
Implementation plan

A practical path from demo to go-live.

01

Discovery

Confirm Sage 200 version, Sicon modules, users, data, workflows and internal access requirements.

02

Scope & quote

Select hosting, user packs and modules. Confirm exceptions, third-party licences and support assumptions.

03

Build & configure

Set up portal, roles, API integration, module settings, branding and initial test workflows.

04

Pilot

Run key users through order, PO, stock, finance and reporting tests using controlled data.

05

Go-live

Onboard users in packs, monitor early usage, tune workflows and plan the next module upsell.

Security & governance

Designed to protect the ERP, not expose it.

The portal should be scoped around least privilege. Users see permitted portal workflows - not unrestricted Sage 200 access.

Role-based accessPermissions by user, role, department, account and module.
Audit trailsTrack key submissions, edits, overrides and admin actions.
Validation layerCheck data before approved workflows touch Sage 200.
Data protectionGDPR responsibilities, retention, backups and access logs must be agreed.
Implementation ready

Choose a hosting route and scope the first implementation.

Start with a sandbox demo, then validate requirements and price the core app plus add-ons.

Book discovery call View pricing