What goes wrong.
- Settlement posted as one GL journal with no order trail
- FBA stock not separated by location
- Optional fields missing on Amazon orders
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.
Seller SKUs, FBA and merchant stock, orders and settlements, synced between Amazon and Sage 300.
A 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.
In Sage 300, sales, receipts and journals live in different modules. An Amazon settlement touches all of them: sales in Order Entry, fees as Accounts Payable or GL entries, and the net payout as a receipt in Accounts Receivable. We post each part where it belongs and link them with the settlement ID, so auditors can trace a single Amazon payout from the bank statement back to every order in it.
The field map we agree in discovery, before any code is written.
| Record | Amazon | Sage 300 | Direction |
|---|---|---|---|
| Products | ASIN and seller SKU | Inventory Control item | Amazon ↔ Sage 300 |
| Stock | FBA or merchant-fulfilled quantity | Location quantity | Sage 300 → Amazon |
| Orders | Amazon order | Order Entry order | Amazon → Sage 300 |
| Customers | Amazon as the selling channel | Accounts Receivable customer | Amazon → Sage 300 |
| Money | Settlement report with referral and FBA fees | GL account | Amazon → Sage 300 |
| Returns | Amazon return or refund | Credit note in Sage 300 | Amazon → Sage 300 |
| VAT | Amazon 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–Amazon connector is usually Integration hub or Enterprise integration scope; see integration pricing.
Amazon.co.za sales are in rand. If you also sell on other Amazon marketplaces, those orders can post in their own currency with your Sage 300 exchange rate rules.
A Sage 300 to Amazon connector is usually Integration hub or Enterprise integration scope, from R15,000 once-off.
Tell us how Sage 300 and Amazon are used in your business today. We’ll reply with a Amazon to Sage 300 field map and a fixed-scope proposal.