WebsitesDesign, build and look after it.
SearchBe found on Google and in AI answers.
Software & AIProducts, integrations and agents.
Selected workSites we’ve launched, and why they work.
South AfricaEighteen cities across the country.
IndustriesSites built for how your buyers decide.
Sage 50 is desktop accounting, so it has no public web address an online store can call.
Sage 50 is desktop accounting, so it has no public web address an online store can call. We install a small agent beside the company data that pushes stock to your channels and pulls orders back into Sage 50, on a schedule you choose.
Desktop software on a server or PC in your office (the product many businesses still call Pastel Partner or Xpress). We connect through a small sync agent installed next to the company data, using Sage’s SDK.
Typical clients: small and medium businesses that have run their books on Pastel for years.
Sage 50 only syncs while the machine that holds the company data is on and connected, so the first design decision is where the agent runs and what happens during load-shedding or after-hours shutdowns. We queue changes while the agent is offline and replay them in order when it reconnects. Most Sage 50 businesses also carry years of item codes that do not match their online SKUs, so a clean mapping table is the real foundation of the project.
Seven channels we connect to Sage 50cloud Pastel. Each has its own page with the field map and failure points.
A Sage 50 Takealot integration runs a small agent beside your Pastel data that sends leadtime stock to your Takealot offers and brings each sale and seller statement back into Sage 50 as invoices and fee journals.
Sage 50 + TakealotA Sage 50 Amazon integration maps your Amazon.co.za seller SKUs to Pastel item codes, imports merchant-fulfilled and FBA orders through a local agent, and posts each settlement report so fees and payouts reconcile in Sage 50.
Sage 50 + AmazonA Sage 50 Shopify integration takes Shopify’s order webhooks into a queue, posts them into Pastel through a local agent and sends stock levels from your Sage 50 stores back to the matching Shopify locations.
Sage 50 + ShopifyA Sage 50 WooCommerce integration connects your WordPress store to Pastel through a local agent: WooCommerce orders and customers flow into Sage 50, and stock and selling prices flow from Sage 50 back to WooCommerce.
Sage 50 + WooCommerceA Sage 50 WooCommerce B2B integration publishes your Pastel price lists and customer credit limits to trade accounts on WooCommerce, and brings wholesale orders back into Sage 50 as sales orders against the right customer.
Sage 50 + WooCommerce B2BA Sage 50 B2B ecommerce integration lets trade buyers reorder, see their Pastel prices and download statements from a portal, while the portal’s purchase orders arrive in Sage 50 as sales orders with the buyer’s PO number.
Sage 50 + B2B ecommerceA Sage 50 Ecwid integration keeps a small Ecwid store in line with Pastel: stock and prices from Sage 50 update Ecwid products and combinations, and Ecwid orders post back as invoices, wherever the store is embedded.
Sage 50 + EcwidWhat shapes an integration with this system.
| Sage 50 | |
|---|---|
| Product | Sage 50cloud Pastel |
| Deployment | Desktop software on a server or PC in your office (the product many businesses still call Pastel Partner or Xpress) |
| How we connect | A small sync agent installed next to the company data, using Sage’s SDK |
| Records we sync | Inventory item code, customer account, sales order or tax invoice, store quantity and general ledger account postings |
| Best suited to | Small and medium businesses that have run their books on Pastel for years |
| Tier that usually fits | Essential connector |
The problems we design around from the first workshop.
Every connector is built in staging, run in parallel with your team and monitored after launch.
We audit SKUs, warehouses, customers and accounts on both sides and agree a written field map.
The connector is built and tested against test data or a copy of your company.
Both the old process and the connector run side by side until the numbers match.
Alerts, logs and a runbook, with monitoring plans from R2,500 a month.
Typical integration scopes. Final pricing depends on systems and complexity.
Two-system sync, a single workflow automation or a pilot integration.
Multiple SaaS tools, retail or finance operations, growing product teams.
ERP + CRM + ecommerce, legacy modernisation and SLA requirements.
Keep connectors healthy after launch.
| Plan | Price | Includes |
|---|---|---|
| Monitor Lite | R2,500/mo | Uptime checks and email alerts |
| Monitor Pro | R5,500/mo | Dashboards and incident response |
| Managed integration | R9,500+/mo | Changes, patches and SLA options |
Most single-channel Sage 50 projects are Essential connector scope. Full details on the API integrations page.
The machine with the Sage 50 company data needs to be on and connected for changes to flow. While it is offline, orders and stock changes queue in the middleware and are replayed in order once it comes back.
Yes. We map each online SKU or marketplace listing to its existing Sage 50 item code, so your team keeps the codes they know and the website keeps the SKUs customers see.
It handles typical small and medium volumes well with scheduled batches. If you are processing hundreds of orders an hour across several channels, we will discuss whether a cloud system or Sage 200 Evolution is a better hub.
A Sage 50 connector to one channel is usually an Essential connector at R15,000–R35,000 once-off. Connecting several channels, warehouses or companies is Integration hub scope, R45,000–R120,000. Monitoring plans start at R2,500 a month.
Tell us which systems you run and where the manual work is. We’ll reply with a field map and a fixed-scope proposal.