Orders
Web order to sales order
Every paid order becomes a Sage sales order with the right customer, terms, tax handling, freight, and deposit. Guest checkouts resolve to real Sage customers instead of piling up as junk accounts.
[ FEATURES ]
Everything between the order and the ledger
The core integration carries the money, the inventory, and the paperwork between your ERP and your storefront. Channel modules extend the same wire to the marketplaces. All of it inspectable, alarmed, and owned by you.
[ WHAT THE CORE SYNCS ]
The whole loop, not just the order feed
Inventory
Quantities by warehouse
Available-to-sell from the warehouses you actually ship from, with rules for what happens at zero: hide, backorder, or take the order and say so honestly.
Pricing
Prices that match the invoice
List prices always. Sage's customer-specific cascade when you want the store to honor it. Either way, the web price and the invoice price agree, which is the entire point.
Shipments
Tracking back to the buyer
Sage invoices and shipments flow back as Shopify fulfillments, so customers get tracking from the store they bought from instead of a mystery email.
Payments
Payout reconciliation
Shopify payouts against Sage deposits through a clearing account your accountant will actually accept. Card fees, refunds, and partial captures accounted for, not averaged away.
B2B terms
Net-30 and credit holds
Approved accounts check out on terms, and the store knows who they are. Credit holds surface to the customer before they order, not after, and the receivables side reconciles back to Sage.
The full core story, screens included, lives on theSage 100 ↔ Shopify page.
[ CHANNEL MODULES ]
More places to sell, on the same core
eBay, Amazon, and other marketplaces bolt onto the core as modules: listings driven by the item master, marketplace orders landing in the ERP like any other order, inventory pushed back out so you never oversell. A second channel shouldn't mean a second back office. Modules are scoped per channel.
Running today:an eBay sale becomes a Sage sales order untouched by human hands, announced in Slack with the order number attached.
Channel plumbing →[ WHAT IT RUNS ON ]
Your AWS account. Boring infrastructure, on purpose.
A ForgeSync deployment is a single, inspectable stack in your own AWS account: set up by us, owned by you, no mystery SaaS sitting in the middle of your order flow. Here's exactly what gets stood up.
The instance
One EC2 server, right-sized
A t3-class EC2 instance, typically t3.small or t3.medium depending on catalog size and order volume. Nginx, PHP, MySQL, Redis: a stack any competent admin can log into and understand. The AWS bill is yours and it's modest; most deployments cost less per month than a licensed connector costs per week.
Amazon SES, authenticated
Alerts, reports, and notifications go out through Amazon SES on your own domain, with SPF, DKIM, and DMARC configured properly. Mail from the integration lands in inboxes, not spam folders, and it comes from your name, not ours.
Backups
Off-site, nightly, tested
Nightly database dumps shipped off the server to S3, plus scheduled AWS Backup snapshots of the whole instance, kept on a retention window rather than a single overwritten copy. If the server dies, you restore. You don't rebuild.
Retained logs
Every sync, on the record
Every order export, inventory update, and price change is logged and retained. "What happened to order 10482 back in March" is a lookup, not an archaeology project. When an auditor, a customer, or your accountant asks, the answer exists.
[ IN OPERATION ]
Not slideware. The product, running.
Recreated screens from live installations, identifying data replaced. Queue depth, job health, and the last word from every import, errors included, on one screen your team would actually watch.
Tour the admin →Easier shown than told
Thirty minutes, real screens, your questions. We'll walk you through the product running on a live installation.
Get a demo