IEMSuite is a native embedded app, not a sidecar with a CSV habit. Orders flow in, lot-accurate stock flows out, and fulfillment status closes the loop.
What syncs, and in which direction
| Data | Direction | What it means |
|---|---|---|
| Products | Shopify ⇄ IEMSuite | Catalog stays consistent in both systems |
| Orders | Shopify → IEMSuite | New orders arrive via verified webhooks and allocate stock lots |
| Stock levels | IEMSuite → Shopify | Allocations, production output, and adjustments update storefront availability |
| Fulfillment | IEMSuite → Shopify | Shipping from IEMSuite updates the Shopify fulfillment status |
Every incoming webhook is HMAC-verified before processing, and idempotency guards mean a redelivered webhook can never process an order twice or double-count stock.
Order allocation runs in a database transaction with row-level locking on the source lot. Two simultaneous orders for the last unit cannot both succeed.
The embedded app and the web app share the same organization and data. Work inside Shopify admin, in the browser at app.iemsuite.com, or both.
No. IEMSuite is a complete standalone web application. The Shopify embedded app is an additional front door onto the same data for brands that sell there.
The order arrives via a verified webhook and allocates stock lots with FIFO/FEFO inside a locked transaction. Storefront availability updates from the resulting stock level.
No. Idempotency guards recognize redelivered webhooks, so each order is processed exactly once even when Shopify retries.
Yes. Confirming a shipment updates the Shopify fulfillment status, so the customer-facing order reflects what actually left the warehouse.
Lots, production, and QC behind the storefront - synced both directions.
No credit card required to get started