ERP and accounting
SalesPro Hub can exchange submitted orders, customer records, fulfilment status and SKU stock with Sage or Pastel through its REST API and signed webhooks. A Sage SDK script, scheduled task or middleware must still implement the accounting-side mapping; this is not a one-click native Sage connector.
Test the field workflow firstSupport level: Guided API recipe — custom setup required. The workflow below separates shipped SalesPro Hub capabilities from connector work your implementation must provide.
Client-provided ERP licence required: SalesPro Hub Enterprise covers the managed connector service only. It does not include or resell the ERP product, ERP modules, API, SDK, e.net, runtime, user or vendor-partner licences. The client must provide and maintain every third-party licence, supported integration interface, vendor permission and licensed test or production environment required by their ERP.
What this solves
The practical pattern for South African distributors is a small scheduled connector: SalesPro Hub owns field capture, Sage or Pastel owns the accounting document, and both systems retain the same reference. Polling is usually the simplest option behind office firewalls; signed webhooks can reduce the delay when a public HTTPS endpoint is available.
Sage & Pastel integration evidence
A useful Sage & Pastel 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 28 July 2026
A go-live check should match the field order, customer, totals and resulting accounting reference rather than treating a successful request as sufficient evidence.
On-premise products commonly need a scheduled Windows-side process, while cloud editions may use a different API and authentication path.
Customer codes, product codes, warehouses, taxes and document references need explicit mapping and a review path for unknown values.
A controlled pilot exposes inactive accounts, unknown SKUs, price differences and stock ownership questions before they become live exceptions.
Finance, IT, operations and the implementation partner should agree who rotates credentials, investigates failures and reconciles each reporting period.
The field order number and returned ERP document reference give both teams a common trail through retries and status changes.
Architecture and ownership
Most South African Sage or Pastel projects use a customer-hosted scheduled connector because the accounting product and its data interface sit inside the office network. The exact design depends on whether the buyer uses Sage 50cloud Pastel, Sage 200 Evolution, Sage 300 or Sage Business Cloud Accounting; those products are not one interchangeable API. A responsible scope starts with the product name, version, database or SDK entitlement, company code, warehouse model and document type.
Sage or Pastel normally owns the posted accounting document, customer account code, VAT treatment and the official external order or invoice number.
SalesPro Hub owns the rep’s mobile draft, visit context and the submitted field order before the accounting hand-off.
The implementation must choose which system owns prices and available stock, including when each quantity becomes effective.
Customer and product master data may flow from accounting to the field platform, but creation and change authority must be declared separately.
For an on-premise edition, the Windows service should run under a least-privilege service identity with only the SDK, database and folder access the adapter needs. The customer should record the outbound hub destinations, proxy or TLS-inspection behaviour, credential rotation procedure and local break-glass owner. Managed remote settings are restricted to an adapter schema and do not create a generic command shell or unrestricted database browser.
Failure recovery
A useful Sage & Pastel integration is not defined by one successful demo. It is defined by what remains durable, what can be replayed safely, what must stop, who sees the exception and how both systems are reconciled.
| Failure or conflict | Required response |
|---|---|
| Unknown customer or SKU | Reject the individual record with the unmapped identity visible; never substitute a similar name automatically. |
| Accounting service unavailable | Keep the operation durable, retry only a bounded temporary fault and preserve the same order identity. |
| Response lost after commit | Look up the stable source reference before attempting another document creation. |
| Tax or warehouse validation error | Quarantine the permanent mapping error for finance or ERP administration instead of retrying forever. |
| Credential or host change | Deliver an approved versioned setting, validate locally and retain the previous known-good configuration for rollback. |
Acceptance plan
A sandbox proves API syntax. Production readiness requires representative identities, accounting or CRM rules, failures and reconciliation. Record the result against the exact product edition and adapter release; do not transfer evidence from a different vendor version by assumption.
Delivery lifecycle
Treat the connection as a small operational product with owners, release evidence and a lifecycle. These phases stop a promising prototype from becoming an invisible production dependency that only one developer understands.
Name the exact Sage & Pastel product, edition, company or tenant, licensed interface and deployment. Follow one representative customer and order from field capture to its final external state. Record current manual checks, approval points, cut-off times, volumes and the people who resolve errors. Brand-level assumptions are not a technical scope.
List required and optional fields, types, formats, allowed values and stable identities. Declare a source of truth for customers, outlets, products, prices, tax, stock, documents and status. Define create, update, deactivate and delete behaviour separately. Include the idempotency key, cursor or event identity and the external reference returned after a successful commit.
Classify authentication, rate-limit, connectivity, validation, mapping, conflict and external-service errors. Decide which faults retry, how often and with what backoff; which stop immediately; and where exhausted work becomes visible. Assign a named business or technical owner and define the evidence needed to replay, correct, reject or manually reconcile an operation.
Use representative South African customers, addresses, SKUs, rand values, VAT rules, discounts, warehouses and approval cases. Include duplicates, missing mappings, offline or network loss, service restart, expired credentials and a lost response after external commit. Reconcile counts and commercial totals in both systems; a green API response alone is not acceptance.
Version the mapping, adapter and configuration together. Record the approved package, supported architectures, required runtime, database or API prerequisites and the previous known-good state. Start with a bounded customer or order cohort, monitor exceptions and keep a tested way to pause new work without deleting the durable queue or losing reconciliation evidence.
Monitor reachability, authentication, latency, retry and dead-letter trends, external rate limits, installed version and reconciliation differences. Rotate credentials and exercise recovery before an emergency. Review vendor API or SDK changes and the adapter support matrix before upgrades. Retire obsolete credentials, mappings and data under the agreed security and POPIA operating process.
Decision-maker intent
Finance
The document type, status, tax, account, warehouse and approval rules must be agreed and tested for the exact Sage or Pastel edition. The field order alone cannot choose those accounting policies.
IT
Routine enrolment, monitoring, approved settings and upgrades are designed for self-service or remote control on Enterprise. Machine or network failures that break the hub channel still need a narrow local support path.
Operations
A production adapter needs visible operation state, retry count, last error, external reference and reconciliation ownership. A background task with no exception queue is not an acceptable go-live design.
Professional includes scoped APIs and signed webhooks for custom, customer-operated middleware. A managed Windows connector, remote configuration, heartbeat/version monitoring and managed recovery require Enterprise—and only become available for this named system after its real adapter passes the published release boundary.
Buyer decision guide
A good trial should prove the workflow with your data—not rely on a sales promise.
Implementation flow
Poll pending, unacknowledged orders or react to an order-submitted webhook. Stable cursors prevent ties from skipping orders.
Your connector maps customer code, SKU, quantity, price, discount and VAT into the appropriate Sage sales-order workflow.
Acknowledge the SalesPro Hub order with the new Sage reference. Conflicting retries return a 409 instead of silently relinking the order.
Return status as the office fulfils the order and publish current stock by SKU according to the agreed system-of-record policy.
| SalesPro Hub field/event | Sage & Pastel equivalent | Implementation note |
|---|---|---|
| customer.external_id | Sage customer/account ID | Immutable identity; do not match by name. |
| order_number | Import/source reference | Use as the inbound deduplication key. |
| external_reference | Sage sales order/invoice number | Written back after creation. |
| items[].sku | Sage item code | SKUs must be aligned before go-live. |
| stock_qty | Quantity on hand | Absolute quantity, not a relative movement. |
It provides the order, customer, inventory, webhook and status APIs plus a guided implementation recipe. A Sage SDK script or middleware is still required, so it is not described as a one-click native connector.
Yes, once a scheduled connector or webhook consumer has been implemented. The connector polls submitted orders, creates the Sage document, and acknowledges the SalesPro Hub order with the Sage reference.
Use the SalesPro Hub order number as the inbound idempotency key. Acknowledgement and status callbacks are replay-safe, and conflicting external references are rejected.
Yes. Publish absolute stock quantities to SalesPro Hub by SKU and configure the inventory deduction policy so the same delivery is not deducted independently in both systems.
SalesPro Hub Enterprise covers the managed connector service only. It does not include or resell the ERP product, ERP modules, API, SDK, e.net, runtime, user or vendor-partner licences. The client must provide and maintain every third-party licence, supported integration interface, vendor permission and licensed test or production environment required by their ERP.
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.