Enterprise integration operations
SalesPro Hub managed connectors are an Enterprise-only integration runtime for customer-hosted Windows servers. A tenant administrator installs the signed package, enters a one-time activation key, and then monitors reachability, version, configuration and failures from the hub. The durable file-exchange adapter is the currently runnable adapter. Sage, Pastel, SYSPRO, Sage 300, SAP Business One, Xero and QuickBooks adapters must each pass product-specific implementation and release gates before they can be described as supported.
Test the field workflow firstSupport level: Enterprise only — managed runtime live; vendor adapters require release approval. The workflow below separates shipped SalesPro Hub capabilities from connector work your implementation must provide.
What this solves
South African distributors often keep accounting or ERP data inside an office network while field teams need current customers, product codes, stock context and order status in the cloud. The managed connector provides the repeatable operating layer around that boundary: secure tenant enrolment, authenticated outbound communication, durable local work, idempotent delivery, version reporting, remote configuration, signed upgrades, recovery and central visibility. It does not turn an unbuilt vendor mapping into a working integration. Each adapter still needs the correct vendor SDK or API, licensed test environment, field map and reconciled acceptance run.
Managed Windows Connectors integration evidence
A useful Managed Windows Connectors connection needs stable identities, explicit ownership and a visible exception path. These are the SalesPro Hub records the implementation must map and reconcile.
Written and maintained by Paul · Updated 7 August 2026
Operations, finance and IT should decide which system owns customers, products, stock, prices, orders and fulfilment before an adapter is approved.
The customer installs the signed Windows package and enters the tenant-bound activation key issued in SalesPro Hub; routine enrolment does not require an RDP support session.
The connector authenticates to the hub and polls for authorised work, reducing the need to expose an inbound management port through the customer firewall.
Tenant administrators and SalesPro Hub operations can review heartbeats, installed versions, configuration state and errors without treating every incident as a blind server problem.
Versioned settings are delivered over the authenticated channel, tested locally and rolled back when activation fails; secret values remain write-only in the management interface.
A durable local outbox, bounded retries, idempotency identities and a dead-letter path preserve work through temporary outages and make permanent failures reviewable.
A team on Professional can build and host its own middleware using scoped API keys and signed webhooks. The managed Windows runtime is a different commercial and operational service: SalesPro Hub enrols the connector, reports whether it is reachable, manages approved settings, records its version and controls signed releases. That surface is deliberately gated behind Enterprise.
Scope an Enterprise integration| Capability | Professional | Enterprise |
|---|---|---|
| Scoped REST API keys and signed webhooks | Included | Included |
| Customer-hosted custom middleware | Customer operates it | Optional |
| One-key Windows connector enrolment | Not included | Included |
| Heartbeat, version and fleet monitoring | Not included | Included |
| Remote schema-limited configuration | Not included | Included |
| Signed release approval and upgrade path | Not included | Included |
| Managed recovery and connector operations | Not included | Included |
Operating architecture
Writing the first successful ERP order is only the beginning. A commercial integration also needs to survive service restarts, internet loss, ERP maintenance, credential rotation, duplicated requests, partial batches, schema drift and software upgrades. The common runtime handles those cross-cutting concerns once so a vendor adapter can focus on the product's supported API or SDK and business mapping.
An activation key is short-lived, one-use and issued for a specific tenant. The key is exchanged for an agent identity; the secret is not written into normal audit messages. Revoking that agent blocks later heartbeat and work requests.
Heartbeat data identifies the agent, architecture, installed version, local configuration state and last contact. The tenant view makes routine health self-service, while the super-admin view supports cross-tenant operations without mixing tenant data.
The local SQLite outbox survives process restarts. Retry counters and bounded delays handle temporary faults; stable operation identities prevent the same business effect being applied twice. Exhausted or permanent failures become reviewable rather than disappearing.
A candidate configuration carries an expected version. The connector validates it before activation and preserves a previous encrypted version for rollback. Upgrade approval selects a signed release from an allowed origin; it does not permit an arbitrary executable URL.
Remote repair depends on the agent still reaching the hub. If an ERP password, database host or vendor token changes, an approved replacement can be delivered and validated remotely. If the Windows machine is off, DNS is broken, the outbound destination is blocked or the configured hub address itself is wrong, the failed channel cannot repair itself. The implementation runbook therefore keeps a narrow local break-glass path while removing the need for routine RDP access.
South African adapter roadmap
The runtime, installer and hub control plane are reusable. Every named ERP still needs its own supported interface, configuration schema, mapping, test fixture, failure taxonomy and acceptance evidence. The table below is the public claim boundary as of 7 August 2026; it is intentionally more conservative than a logo directory.
| System or path | Likely deployment | Current status | Release boundary |
|---|---|---|---|
| File exchange | Windows service; controlled local folders | Runnable and tested | The configured installation path is intentionally not remotely editable. This prevents the connector becoming a general-purpose remote file reader. |
| Sage 200 Evolution / Pastel | Customer Windows server; product SDK or approved data interface | Adapter implementation and licensed acceptance environment required | The exact edition, SDK entitlement, tax rules, warehouse mapping and document workflow must be proved before release. |
| SYSPRO | Customer network; SYSPRO-supported integration interface | Planned after representative environment is available | No native SYSPRO adapter is currently claimed. Business objects, company access and stock/order ownership require an edition-specific contract suite. |
| Sage 300 | Customer network or approved middleware host | Planned; not released | The adapter needs a supported Sage 300 interface, licensed test company and reconciled document lifecycle before support can be advertised. |
| SAP Business One | Service Layer or approved integration host | Controlled preview in source; activation by approval only | The preview is disabled by default. Company database, Service Layer behaviour, UDF mappings, automatic Hub order publication and SAP partner requirements must pass representative acceptance. |
| Xero | Cloud API adapter; Windows agent optional | Custom API path documented; managed adapter not released | OAuth consent, token rotation, accounting organisation selection and external rate limits remain part of the product-specific adapter. |
| QuickBooks Online | Cloud API adapter; Windows agent optional | Custom API path documented; managed adapter not released | OAuth consent, token rotation, company selection, accounting transaction policy and rate limits remain part of the product-specific adapter. |
Priority is driven by qualified South African customer demand and access to a lawful representative environment—not by publishing an unsupported keyword page. SAP Business One has a controlled preview with its own acceptance gate. Sage 200 Evolution/Pastel, SYSPRO and Sage 300 still require product-specific adapter work, exact interface proof and reconciled release evidence.
Questions buyers and answer engines ask
A sales manager searches for faster order hand-off; finance searches for accurate ERP documents; IT searches for remote monitoring; security searches for network and credential boundaries. A complete evaluation must answer all four intents.
Operations and sales leadership
The operating design keeps submitted work durable through temporary outages, reports connector reachability and version, and gives failures an explicit review path. The acceptance test must still prove the actual customer, SKU, price, tax and fulfilment workflow against the selected ERP edition.
Finance and ERP owners
The integration contract assigns one source of truth per entity and retains an immutable operation identity across retries. An adapter may only report success after the external commit and reference are durable. Reconciliation compares counts, totals, taxes, document references and rejected rows—not only HTTP success.
CTO, CIO and security reviewers
The service initiates an authenticated outbound hub connection. Remote settings are restricted to declared adapter fields; secrets are write-only in the management UI and protected locally. There is no arbitrary command channel. A procurement review should verify destinations, TLS inspection behaviour, service identity, Windows permissions, credential rotation, audit retention and the local break-glass procedure.
IT support and implementation partners
Normal enrolment, adapter settings, version visibility, signed release approval and configuration rollback are managed centrally. A working hub channel can carry corrected hosts, usernames, tokens and other approved values. Machine failure, a broken hub address or a network outage that blocks the channel still needs a documented local intervention path.
Procurement and acceptance
The acceptance pack should name the exact ERP edition and integration interface, show the supported data directions, list every required field, and identify the owner for rejected records. It should include a source-of- truth matrix, credential-rotation test, replay test, outage and restart test, partial-batch test, upgrade and rollback test, tenant-isolation evidence, reconciled business totals and the alert-to-resolution runbook.
For South African buyers, the data review should also cover POPIA roles, purpose and access; retention; operator obligations; cross-border or hosting disclosures confirmed during procurement; and the practical employment and device policies around field data. Product controls can support those obligations, but they do not make either party automatically compliant or certified.
Buyer decision guide
A good trial should prove the workflow with your data—not rely on a sales promise.
Implementation flow
Identify the ERP product, version, deployment type, licensed integration interface and data owner. A brand name alone is not enough to approve an adapter.
A tenant administrator creates a short-lived, one-use key in SalesPro Hub for one connector name, architecture and approved adapter.
The customer runs the MSI, enters the key and enrols the service. The resulting agent credential is tenant-bound and protected locally.
Approved host, company, database and credential fields are pushed as a versioned configuration. The agent validates them before making the candidate active.
Run representative customers, SKUs, taxes, prices, orders and statuses through both systems. Confirm counts, values, idempotent replay and exception ownership.
Use heartbeat, version, configuration and failure state to manage the fleet. Retry temporary failures, quarantine permanent ones and approve signed releases remotely.
| SalesPro Hub field/event | Managed Windows Connectors equivalent | Implementation note |
|---|---|---|
| customer.external_id | ERP account/customer code | Use the immutable external identity, never a mutable name. |
| order_number | ERP source/import reference | Primary inbound idempotency key for a field order. |
| external_reference | ERP order/invoice identifier | Write back only after the external commit succeeds. |
| items[].sku | ERP item/stock code | Reconcile unknown and inactive codes before go-live. |
| stock_qty | Absolute available quantity | Choose one stock owner and avoid double deduction. |
| configuration_version | Applied connector settings version | Acknowledged only after local validation and activation. |
| operation_id | Connector processing identity | Persist across retries to prevent duplicate side effects. |
Managed Windows connectors do. Enterprise includes activation keys, centrally managed credentials, connector heartbeat and version monitoring, remote recovery controls and signed upgrade approval. Professional retains API keys and signed webhooks for teams that operate their own middleware.
The tested runnable adapter is file exchange. The common Windows runtime and control plane are live foundations, but Sage, Pastel, SYSPRO, Sage 300, SAP Business One, Xero and QuickBooks adapters are not labelled supported until the product-specific implementation, licensed test environment and release evidence exist.
Yes for normal enrolment. The tenant administrator downloads the approved installer and enters the one-time activation key. Windows permissions and any ERP-specific SDK installation still need to be available on the customer machine.
An approved adapter can expose those exact schema fields. Public values can be updated from the hub and secrets are write-only. The connector validates the candidate locally before activation and can return to the last known good version if activation fails.
No. Configuration is limited to declared adapter fields and signed release controls. The management channel does not expose an arbitrary command runner, unrestricted file browser or generic RDP session.
Every operation keeps a stable identity through local persistence and hub retries. The adapter must use the field order number or another approved immutable key in its external transaction and reconciliation store, then return the committed ERP reference.
Durable work remains in the local outbox. Temporary failures retry with bounded backoff and survive service restarts. Permanent or exhausted failures move to a reviewable dead-letter state instead of being silently discarded.
The hub records the installed version and the approved signed release for each agent. An agent only accepts an allowed origin and trusted signing key, so a remote upgrade follows an explicit release decision rather than downloading an arbitrary package.
That is the primary deployment pattern. The service initiates its authenticated hub connection from the customer network. The exact ERP database or SDK access remains local to the Windows host and is constrained by the adapter configuration.
Ask for the exact adapter status, data directions, source-of-truth matrix, tenant isolation, credential handling, outbound destinations, idempotency design, failure recovery, monitoring ownership, upgrade verification, audit evidence and a reconciled pilot using the intended ERP edition.
Connected buying journey
Review the managed runtime, ERP, accounting, CRM and automation options before choosing a delivery model. Every page publishes its current support boundary, required custom work and Enterprise plan status.
Import real products and customers, capture a representative order, then scope the integration against evidence instead of assumptions.