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 300 separates Inventory Control, Accounts Receivable and Order Entry into modules with their own rules.
Sage 300 separates Inventory Control, Accounts Receivable and Order Entry into modules with their own rules. We connect through its views or Web API, so online orders enter Order Entry correctly, against the right company, location and currency.
ERP for larger businesses, often multi-company and multi-currency, on-premises or hosted. We connect through Sage 300’s business views, or its Web API in recent versions, through a service near your installation.
Typical clients: larger, multi-company and multi-currency businesses.
Sage 300 often runs several companies in one installation, each with its own item list, optional fields and currency. An online channel has to know which company it belongs to and how foreign-currency orders convert. We document those routing rules first, then test them with real orders from each channel, because a mistake in a multi-company ERP is much harder to unwind than in a small accounting package.
Seven channels we connect to Sage 300 (formerly Accpac). Each has its own page with the field map and failure points.
A Sage 300 Takealot integration routes Takealot sales into Order Entry for the company and location that sells on Takealot, publishes leadtime stock from that location, and posts seller statements in rand to the right Accounts Receivable customer.
Sage 300 + TakealotA Sage 300 Amazon integration places Amazon.co.za orders into Order Entry for the selling company, keeps FBA stock in its own location, and posts settlement reports with currency and fee detail so Accounts Receivable reconciles to each payout.
Sage 300 + AmazonA Sage 300 Shopify integration maps each Shopify store and location to a Sage 300 company and location, creates orders in Order Entry with optional fields filled, and posts refunds and gateway payouts in the right currency.
Sage 300 + ShopifyA Sage 300 WooCommerce integration publishes Inventory Control stock from chosen locations to WooCommerce and creates orders in Order Entry with the customer, tax class and optional fields Sage 300 expects.
Sage 300 + WooCommerceA Sage 300 WooCommerce B2B integration publishes contract pricing and credit status from Accounts Receivable to trade accounts on WooCommerce, and creates approved wholesale orders in Order Entry for the right company.
Sage 300 + WooCommerce B2BA Sage 300 B2B ecommerce integration powers a buyer portal with contract prices, stock by location, statements and order status from Sage 300, across companies and currencies, and creates buyer orders in Order Entry.
Sage 300 + B2B ecommerceA Sage 300 Ecwid integration publishes a selected retail range from one Sage 300 company and location to an embedded Ecwid store, and returns Ecwid orders to Order Entry with the required optional fields.
Sage 300 + EcwidWhat shapes an integration with this system.
| Sage 300 | |
|---|---|
| Product | Sage 300 (formerly Accpac) |
| Deployment | ERP for larger businesses, often multi-company and multi-currency, on-premises or hosted |
| How we connect | Sage 300’s business views, or its Web API in recent versions, through a service near your installation |
| Records we sync | Inventory control item, Accounts Receivable customer, Order Entry order, location quantity and GL account postings |
| Best suited to | Larger, multi-company and multi-currency businesses |
| Tier that usually fits | Integration hub or Enterprise integration |
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 300 projects are Integration hub or Enterprise integration scope. Full details on the API integrations page.
Yes. Each channel is routed to the right company, and shared products are mapped per company, because item numbers and optional fields often differ.
Where your version includes it, yes. Older versions use the business views through a service on your network. We confirm which applies in discovery.
Usually. Multi-company routing, optional fields and currency handling make most Sage 300 projects Integration hub scope rather than a simple connector.
A Sage 300 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.