An industrial supplies distributor needed to move its storefront without rebuilding its back office. Sage 100 held the item, customer, and order records. Magento held a large catalog and years of links that still needed to lead customers to the right products.
The work combined a Shopify migration, catalog cleanup, and a ForgeSync connection to Sage. Shopify went live in July 2026; the eBay order, inventory, and tracking workflows followed in August.
The scale of the migration
More than 10,500 products were involved in the catalog cleanup and restructuring. That is the merchandising scope of this migration, not the current count of items mirrored from Sage. The integration has since handled a Sage item master above 18,000 items.
More than 52,000 redirects were mapped for the storefront move. Product titles, tags, collections, and SKU links were reviewed so the new catalog could support both buyers and the integration.
Verify the connection against business data
The engineering team used a corpus of 2.18 million captured request and response payloads to understand the existing integration’s behavior. Representative comparisons and tests helped identify required fields, expected responses, and differences that needed a deliberate decision.
The historical migration write-up recorded 473 automated tests. That figure describes an earlier stage of the project; it is not the current combined product and bridge test count.
Orders into Sage and tracking back
ForgeSync receives Shopify orders, resolves the Sage customer, and queues the export with the purchase order, shipping, tax, and payment context. Rejected orders remain visible for review. Tracking from connected Sage orders flows back to Shopify.
Approved terms customers use a configured draft-order flow. The production storefront uses list pricing; customer-specific storefront pricing is not part of this implementation. Credit-hold visibility and checkout enforcement are distinct capabilities.
eBay joins the same operating process
The eBay module maps existing listings to Sage items, imports orders, updates listing quantities from the channel warehouse, and returns tracking. Invoice-total checks flag differences for investigation. Listing creation and price updates are not part of this automated loop.
What remains a separate workflow
The integration does not make every accounting or customer-service task automatic. Returns, refunds, reships, and some exceptional orders need an agreed operator process. Shopify payout reporting is built but awaits activation; it is not presented here as completed automatic cash application.
Separate legacy costs from net savings
Earlier project notes identified approximately $20,000 a year in legacy platform hosting and developer-retainer costs and $25,000 a year in connector licensing. Those figures describe the legacy cost baseline. They are not a verified claim that $45,000 of net annual savings has already been realized: remaining contracts, replacement hosting, support, and project investment must be considered.
What this means for another implementation
A storefront migration and an ERP integration should share a plan, but each customer’s data and operating rules need their own validation. The Sage 100 and Shopify service explains the current qualification baseline, and pricing explains the ForgeSync Enterprise subscription.