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 200 Evolution keeps inventory, warehouses and customers in a SQL Server database.
Sage 200 Evolution keeps inventory, warehouses and customers in a SQL Server database. We connect through the Evolution SDK, so online orders are created as proper sales orders with the right warehouse, price list and branch, and stock flows back out to each channel.
On-premises ERP on Microsoft SQL Server, often with branch accounting and several warehouses. We connect through the Evolution SDK, run by a service on your server or a hosted machine with access to the database.
Typical clients: mid-sized distributors, wholesalers and retailers with several warehouses or branches.
Sage 200 Evolution businesses rarely sell from one stock pile. A website might ship from the Johannesburg warehouse while a marketplace pulls from Durban, and branch accounting adds another layer. Before any code, we agree which warehouse feeds which channel, how much safety stock to hold back and which branch owns online sales. Those rules, written down and tested, are what stop overselling.
Seven channels we connect to Sage 200 Evolution. Each has its own page with the field map and failure points.
A Sage 200 Evolution Takealot integration sets each offer’s leadtime quantity from the warehouse you ship from, creates Takealot sales as Evolution sales orders for picking, and posts the seller statement against a Takealot customer account.
Sage 200 + TakealotA Sage 200 Evolution Amazon integration maps seller SKUs to Evolution inventory items, places merchant-fulfilled orders in the right warehouse, tracks FBA stock in its own warehouse and posts settlements to the branch that owns Amazon sales.
Sage 200 + AmazonA Sage 200 Evolution Shopify integration links each Shopify location to an Evolution warehouse, creates orders as sales orders through the SDK, and posts refunds and gateway payouts so branch accounts stay accurate.
Sage 200 + ShopifyA Sage 200 Evolution WooCommerce integration sends stock from your chosen warehouses and prices from Evolution price lists to WooCommerce, and creates WooCommerce orders as Evolution sales orders with the right warehouse and branch.
Sage 200 + WooCommerceA Sage 200 Evolution WooCommerce B2B integration publishes customer-specific prices, discounts and credit limits from Evolution to trade accounts on WooCommerce, and posts wholesale orders as sales orders under the right customer and branch.
Sage 200 + WooCommerce B2BA Sage 200 Evolution B2B ecommerce integration gives trade buyers a portal with their Evolution prices, stock from the warehouse that serves them, statements and delivery status, and turns their purchase orders into Evolution sales orders.
Sage 200 + B2B ecommerceA Sage 200 Evolution Ecwid integration feeds an Ecwid store embedded in your website with stock and prices from Evolution, and brings orders back as Evolution sales orders without heavy infrastructure.
Sage 200 + EcwidWhat shapes an integration with this system.
| Sage 200 | |
|---|---|
| Product | Sage 200 Evolution |
| Deployment | On-premises ERP on Microsoft SQL Server, often with branch accounting and several warehouses |
| How we connect | The Evolution SDK, run by a service on your server or a hosted machine with access to the database |
| Records we sync | Inventory item, customer account, sales order, warehouse quantity and general ledger account postings |
| Best suited to | Mid-sized distributors, wholesalers and retailers with several warehouses or branches |
| Tier that usually fits | Essential connector or Integration hub |
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 200 projects are Essential connector or Integration hub scope. Full details on the API integrations page.
We use the SDK for anything that creates or changes transactions, so Evolution’s own business rules, such as costing and stock movements, are applied. Direct database reads are only used for reporting where they are safe.
Yes. Each channel can read stock from one or more warehouses, with a safety buffer, and orders are placed against the warehouse that will fulfil them.
Yes. We agree which branch owns each channel’s sales and post orders accordingly, so branch reports stay accurate.
A Sage 200 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.