SkuNexus has working connectors for Shopify, BigCommerce, Magento 2 and Adobe Commerce, WooCommerce, Shopware 6, Walmart Marketplace, and QuickBooks Online, and connects to everything else through an open API and file-based transports. Each connector syncs orders, products, inventory, customers, and fulfillments in the direction you choose.
How a SkuNexus Connector Is Set Up
Every platform on this page connects the same way, in four steps. Reading them first tells you what a rollout involves before anyone books a call.
Step one: create the connector and pass the credential test
In Settings you choose the platform and enter the credentials that platform issues. Shopify installs as an app through OAuth, or accepts a store URL and access token if you already run a custom app. BigCommerce asks for a store hash, client ID, and access token. Magento 2 asks for a base URL and an integration access token. WooCommerce asks for a site URL, consumer key, and consumer secret. Shopware 6 asks for a shop URL, client ID, and client secret. Walmart asks for the client ID and secret from Seller Center. SkuNexus tests the connection and activates the connector only when the test passes, so a bad credential fails at setup instead of failing quietly a week later.
Step two: choose a direction for each record type
Orders, products, inventory, customers, and fulfillments each get their own setting: inbound, outbound, bidirectional, or off. Most merchants pull orders and products in, and push inventory and fulfillments out. When the same field changes on both sides between syncs, you decide who wins: the channel, the most recent edit, or a person working a review queue. That third option exists because on some fields, being quietly wrong is worse than being slow.
Step three: map locations and carriers
Inventory does not push correctly until every external location is mapped to at least one SkuNexus warehouse. Stock is summed across the warehouses in a mapping, so a channel can show one pooled number while your team keeps picking from real bins. For Shopify you can push a SkuNexus warehouse into Shopify as a new location and have the mapping created for you. Carrier names map the same way, with a tracking URL template so the tracking link on the channel resolves. Safety stock, an inventory cap, and a floor at zero are set per connector, with per-listing overrides where one channel needs different treatment.
Step four: build the connection that is not on the list
Not every system a mid-market operation runs has a packaged connector, and pretending otherwise wastes everyone's first call. SkuNexus is open infrastructure, so the systems without an adapter get built against the open API, or against whatever transport the other side speaks. In production that has meant REST and GraphQL APIs, webhooks, SFTP, CSV, pipe-delimited flat files written to an exact field specification, and purchase orders delivered by email from DMARC-aligned sending domains. Custom integrations covers how that work gets scoped.
eCommerce Platform Connectors
Five storefront platforms have working adapters today: Shopify including Shopify POS, BigCommerce, Magento 2 and Adobe Commerce, WooCommerce, and Shopware 6. Orders, products, inventory, customers, and fulfillments move across each one, and each connector is configured on its own rather than inheriting one global setting.
Merchants on older Magento builds usually get further with us in the first conversation, because the people behind SkuNexus have spent their careers inside those builds. Larry, evaluating SkuNexus on a demo call, put it this way: "My fascination with this is that you also understand Magento. I think that's a big part of it, because now you can look at us in a comprehensive manner, Magento and shipping together, and how does it work as one unit."
What "real time" means here
Order ingestion is polling first. A background worker checks each connected platform on an interval you control, five minutes by default on Shopify and sixty minutes by default elsewhere. Webhooks are registered where the platform supports them, on Shopify, BigCommerce, WooCommerce, and Shopware, but their job is catching changes made directly on the channel between polls, not replacing the poll. Expect up to one poll interval between an order being placed on a channel and it appearing in SkuNexus. If a vendor tells you every channel is instant, ask what their system does with a webhook that gets dropped.
Marketplace Orders and EDI
Walmart Marketplace has a working adapter and connects with a client ID and secret from Seller Center.
Amazon and eBay do not. There is no direct Amazon or eBay adapter in SkuNexus today, and any list that implies otherwise is out of date. What works instead is a feed. A kitchen equipment retailer running Shopware routes its Amazon and eBay orders through a marketplace feed into the storefront, and SkuNexus takes them from there and sorts them into priority waves grouped by shipping method, so marketplace delivery commitments get met without a second workflow for the crew on the floor. Where a storefront feed is not available, the same orders arrive as scheduled SFTP files.
EDI is treated as integration work rather than as a resold network subscription. In production that has covered EDI-derived 850, 855, 856, and 810 documents as flat files over SFTP, cXML and JSON purchase order push, and CSV written to a trading partner's exact field specification. The advantage of building it is that when a partner changes a spec or sends a malformed file, the fix is code your team can direct rather than a ticket in someone else's queue.
Accounting and ERP Sync
QuickBooks Online connects through the QuickBooks OAuth flow. It is an accounting connector, not a sales channel: it moves financial data and it does not bring storefront orders in. That distinction matters when somebody proposes QuickBooks as the system of record for inventory as well as for the books.
For ERP, the arrangement most mid-market operations land on is to keep the ERP for financials and let SkuNexus own the warehouse and the order lifecycle, with order and inventory data moving between the two on a schedule. Where the ERP exposes an API, that is an API integration. Where it does not, ERP order flows have run over SFTP in production. Either way, nobody is hand-exporting a CSV at the end of the day.
Seeing what actually synced
Each connector keeps a sync history of its recent jobs showing entity type, direction, status, records processed, and timestamp, plus an ID mapping table linking external record IDs to SkuNexus IDs. You can trigger a sync by hand for one entity type and one direction without waiting for the next poll. When a channel support agent asks for a record ID, it is in the mapping table.
Common questions about platform sync
Does SkuNexus sync two-way with Shopify, Magento or BigCommerce?
Yes, and direction is set per record type rather than for the whole connector. Orders, products, inventory, customers and fulfillments each get inbound, outbound, bidirectional, or off. The common setup pulls orders and products in and pushes inventory and fulfillments out, which is two-way at the connector level without letting a storefront overwrite warehouse quantities. When the same field changes on both sides between syncs, a conflict strategy decides it: the channel wins, the newest edit wins, or the record goes to a review queue for a person. Location mappings have to exist before inventory pushes at all.
Evaluating this against other options? The integration buyer's guide walks through the failure modes worth planning for, and order management and shipping and rate shopping cover what happens to an order after it lands.
