Erply Integration

Erply is a cloud-based POS and retail management system used by multi-location and chain retailers. Its REST API authenticates with a client code and session key, then lets integrations read and write data like products, stock levels, customers, and orders. Platforms like SKUPlugs connect to this API directly, so inventory and order data can flow automatically to eCommerce channels without manual exports

The simplest way is to connect both platforms through a middleware tool like SKUPlugs rather than building a direct integration. You'll enter your Erply client code and API session key, connect your Shopify store, and map product fields such as SKU, price, and stock. Once mapping is set, you choose the sync frequency and direction, then run a test sync before switching everything to automatic updates.

Erply doesn't sync with these platforms natively — it needs a connector layer in between, which is where a tool like SKUPlugs comes in. SKUPlugs pulls stock, pricing, and product data from Erply's API and pushes updates to WooCommerce, Magento, or BigCommerce through each platform's own API. Most retailers set this up as two-way sync, so online sales also deduct stock back in Erply and keep both systems aligned.

Sync issues usually come down to a handful of causes: mismatched SKUs, an expired API session key, incorrect product mapping, or a warehouse/location excluded from the sync. Rate limit throttling can also cause requests to silently fail if too many calls go out in a short window. Checking the sync logs in your integration platform, such as SKUPlugs, will usually point to the exact cause so you can reconnect or re-map the affected products.

Erply's API access is included with your Erply subscription, so there's no separate charge just to use the API itself. Your main costs come from your Erply plan tier and the middleware or connector platform you use to link Erply with your sales channels. Using a pre-built connector like SKUPlugs is usually more cost-effective than custom development, since it removes ongoing maintenance and API-monitoring work from your plate.

Start by generating an API session key in your Erply account, then install a WooCommerce connector also middleware platform such as SKUPlugs. Enter your Erply client code and session key into the connector settings, authorize the connection to WooCommerce, and map product attributes like SKU, categories, and pricing. Run a test sync on a small batch of products first, confirm stock and orders match on both platforms, and then switch to a regular automated sync schedule.

Erply doesn't connect to Amazon or Walmart directly, so a middleware layer is required to bridge the two. SKUPlugs handles this by pulling inventory and pricing from Erply and pushing listings, stock updates, and orders to and from Amazon Seller Central and Walmart Marketplace. This lets retailers manage marketplace listings centrally from Erply while SKUPlugs handles each marketplace's specific API rules and order formats.

Failed order imports are usually caused by a paused sync setting, a product SKU in the order that doesn't match anything in Erply, or an expired API session key. It's also worth checking whether the order came from a Shopify sales channel excluded from your sync scope, or whether a required field like tax or customer info is missing. Reviewing the error logs in your integration platform, like SKUPlugs, typically identifies the failed order and why, and most can be re-synced manually once fixed.