Ecommerce ERP Integration, Stated Plainly
Runner AI has no built-in connector for an ERP system. Your Runner AI store keeps its own products, stock, orders, and customers, and it can send order, refund, return, and customer events to a web address you choose. Your ERP, or an integration tool in front of it, can receive those events.

Start from your store’s own products, stock, and orders now. Publishing and automation depend on your plan.
What Your Store Can Share with an ERP
Runner AI does not read from or write to an ERP. These are the parts of the store an ERP project can still work with.
Order Events Through Webhooks
Add an endpoint on your project’s Webhooks page, and the store sends an event when an order is placed, shipped, or canceled. Your ERP or integration tool decides what to do with each event.
Refund, Return, and Customer Events
The same webhooks cover refunded payments, received returns, and new customers, so finance and customer records elsewhere can follow what happened in the store.
Products Imported from a CSV File
Export products from your ERP as a CSV file in the store’s import template, then import it in Store Operations, or attach the file in chat and ask Runner AI to import it.
Stock You Keep Current in the Store
The store keeps stock for each product variant and warehouse location, and every order lowers it. When stock or prices change in your ERP, update them in Store Operations or ask Runner AI in chat.
A product principle for Ecommerce ERP Integration
Say plainly what connects and what does not, then make the store’s own data easy to pass on.
— Runner AI product principle
Plan the Integration Around What the Store Sends.
Most ecommerce ERP integration projects follow the same list: products flow from the ERP to the store, orders flow back to the ERP, stock updates prevent overselling, and invoices and shipments stay in step. With a Runner AI store, only part of that list runs by itself. Order, shipment, refund, return, and customer events leave the store through webhooks as they happen, so an ERP that accepts incoming web requests, or an integration tool in front of it, can record them. Products come in from a CSV file. Stock and prices do not flow back automatically, because Runner AI has no connector that reads them from an ERP. Someone updates them in the store instead. If your ERP must push stock levels to the store every hour, you need a dedicated connector or middleware, and Runner AI does not provide one.
Keep Shopper Promises Accurate Without a Sync.
The point of ERP integration is that shoppers see what the business can really ship. Without a live stock link to an ERP, the store’s own stock count carries that promise. Each order lowers the count, and shoppers cannot buy a sold-out variant unless you allow backorders. Runner AI reads your store’s products, stock, and orders together, so you can ask it in chat which variants are running low, update counts after a delivery arrives, or, if your plan includes automations, turn on the Low Stock Alert, which emails you a daily list of variants running low.
Explore the integration platform
Product principle
The useful result is an ERP plan built on what the store really sends, not on a connector that does not exist.
— Runner AI product principle
Ecommerce ERP Integration in Runner AI
What is ecommerce ERP integration?
Ecommerce ERP integration links an online store with the enterprise resource planning system that holds a business’s orders, stock, prices, customers, invoices, and shipments, so nobody types the same data into both. Runner AI does not include an ERP connector; its store sends order, refund, return, and customer events through webhooks, which an ERP or integration tool can receive.
Does Runner AI connect to my ERP?
No. Runner AI has no built-in connector for NetSuite, SAP, Microsoft Dynamics, Odoo, or any other ERP. Your store can send events to a web address through webhooks, and you can import products from a CSV file. Stock or price updates from the ERP need a connector or integration tool outside Runner AI, or a manual update in the store.
Which ERP data matters most for ecommerce workflows?
Usually orders, stock levels, prices, customer accounts, invoices, payments, refunds, and shipments. In a Runner AI store, orders, shipments, refunds, returns, and new customers can leave the store as webhook events, and products can come in from a CSV file. Stock and prices are kept in the store itself, because Runner AI does not read them from an ERP.
Can ecommerce ERP integration improve inventory accuracy?
It can when the ERP updates the store’s stock automatically. Runner AI does not do that, so accuracy depends on keeping the store’s own counts current. Each order lowers stock right away, and you update counts after deliveries in Store Operations or in chat.
Which Runner AI features help with ERP work?
Order management, inventory management, catalog management, and returns management all work on the store’s own data, the same data the webhooks send out. Those are the places to keep orders, stock, products, and returns accurate.
Ready to Pass Your Store Data On?
Use Runner AI to keep products, stock, and orders accurate in your store, and send order events to the systems that need them.
- Order, refund, return, and customer webhooks
- Product import from a CSV file
- Stock kept per variant and location
Help me import my products from a CSV file, then list the variants that are low on stock.
