Your marketplace orders, in Sage 100 without retyping.
Amazon, eBay and BigCommerce orders land in Sage 100 as sales orders when they’re placed. Invoices post when the label is bought. Inventory goes back out to every channel, net of what’s already sold.
Start a projectWhat it does
- Orders in as they’re placed
- Marketplace orders become open Sage sales orders with the marketplace order number in the customer PO field, so Sage allocates the stock and blocks duplicates.
- Invoiced when the label is bought
- Buying a label in ShippingEasy triggers the invoice through Sage Business Objects, with freight calculated per box and packing notes added for the pick sheet.
- Inventory out every 30 minutes
- Each channel gets quantity on hand minus open orders, back orders and the stock you hold back for counter customers. Listings sold in packs are handled.
- Exceptions on a screen, not in your inbox
- Partial shipments, cancellations and orders shipped outside the normal flow show up on a staff page where they can be resolved without touching the database.
- Lot and shade checks
- For lot-tracked items, any order line a single lot can’t fill is flagged before the warehouse pulls pallets.
- Reports that stay current
- Sales history is mirrored hourly, so reports no longer depend on someone remembering to run an export.
How it’s built
Everything uses Sage’s own supported interfaces. Nothing changes about how your team uses Sage day to day.
| Reading from Sage | ProvideX ODBC with change detection, sending only what changed. Narrow column reads keep Sage responsive during business hours. |
|---|---|
| Writing to Sage | Visual Integrator for imports and the Business Object Interface (BOI) for invoicing and line updates, the same paths Sage’s own partners use. |
| Getting to the cloud | A small API on a PC inside your network, reachable only through an encrypted Cloudflare Tunnel with signed requests. No ports opened on your firewall. |
| Marketplaces | Amazon SP-API, eBay Trading and Fulfillment APIs, BigCommerce API and ShippingEasy API. Order tables store no buyer personal data; ship-to details come from the label at invoice time. |
| Monitoring | Every sync and script logs its runs. Dashboards and a nightly email flag anything that failed or drifted. |
| Hosting | Runs on servers we manage in the United States, under a monthly license and support plan. |
Proven in production
Distributors selling on marketplaces alongside a wholesale business usually key orders into Sage after they ship, and lean on CSV exports to keep their website in step. That’s the gap this closes.
With it in place, marketplace orders reach Sage as they’re placed, invoices post as labels are bought, and inventory updates every 30 minutes. In one rollout, the first inventory push corrected 16 listings, 10 of which had shown out of stock while the product sat on the shelf, and a backlog of 43 uninvoiced orders cleared in a single run.
How a project runs
Map it
A working session on your Sage setup, your channels and where the hours go. You leave with a written plan and a fixed price for the first build.
Build alongside
New systems run next to your current process, in a Sage test company first, so nothing changes for your team until it’s proven.
Go live
Switch over one channel or process at a time, with a dashboard showing every sync, every script and every error.
Keep it running
The monthly plan covers hosting, monitoring, fixes and small changes. When Amazon, eBay or Sage change something, we handle it.
Questions people ask first
Which versions of Sage 100 does this work with?
It runs on Sage 100 2020 in production. ODBC, Visual Integrator and BOI have been stable across recent versions, so most current installs work. We confirm yours in the first session.
Does this replace ShippingEasy or our store platform?
No. Your team keeps the tools it already knows. We connect them to Sage and to each other.
What gets installed on our side?
A small Windows PC or virtual machine on your network runs the bridge and the Sage scripts. Inside Sage, at most a Visual Integrator job or two.
What happens when Amazon or Sage changes something?
That’s covered by the monthly plan. API changes, expiring tokens and Sage updates are our problem, not yours.
Can you work alongside our Sage partner?
Yes. Your partner keeps the Sage relationship and the accounting setup; we handle the integration code.
Tell us which channels you sell on
List your marketplaces, your rough order volume and what your team does by hand today. You’ll get a reply from the developer, usually within one business day.
Your first call is with a developer, not a salesperson.