What goes wrong.
- Ecwid orders failing Order Entry validation
- The wrong company’s stock published
- Prices in Ecwid not updated after a Sage 300 change
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.
Products, stock and orders from every Ecwid channel, synced between Ecwid and Sage 300.
A 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.
Large businesses sometimes need a small, fast retail presence: a staff shop, a spare-parts counter or a consumer range sold alongside the main trade business. Ecwid provides that without a full ecommerce project. The integration keeps Sage 300 in charge of stock and prices for one company and location, and makes sure each Ecwid order passes Order Entry’s validation like any other sale.
The field map we agree in discovery, before any code is written.
| Record | Ecwid | Sage 300 | Direction |
|---|---|---|---|
| Products | Product or combination SKU | Inventory Control item | Ecwid ↔ Sage 300 |
| Stock | Product quantity | Location quantity | Sage 300 → Ecwid |
| Orders | Order | Order Entry order | Ecwid → Sage 300 |
| Customers | Customer | Accounts Receivable customer | Ecwid → Sage 300 |
| Money | Payment gateway transaction | GL account | Ecwid → Sage 300 |
| Returns | Refund | Credit note in Sage 300 | Ecwid → Sage 300 |
| VAT | Ecwid tax amounts | Tax class | Mapped |
Exact fields depend on your setup and are confirmed in the written field map.
What we see go wrong with this pair, and how the connector prevents it. A single Sage 300–Ecwid connector is usually Integration hub or Enterprise integration scope; see integration pricing.
Not for a focused range. Ecwid is a quick way to add a retail storefront while Sage 300 continues to run the main business.
A Sage 300 to Ecwid connector is usually Integration hub or Enterprise integration scope, from R15,000 once-off.
Tell us how Sage 300 and Ecwid are used in your business today. We’ll reply with a Ecwid to Sage 300 field map and a fixed-scope proposal.