Skip to content
ERP ⇄ E-commerce

Infor LN to Shopware integration — real-time, two-way sync

Keep Infor LN and Shopware in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Infor LN and Shopware

Keep the storefront in step with the back office: Shopware and Infor LN share products, inventory, and orders in real time, in both directions.

Shopware runs the storefront and takes the orders; Infor LN owns the item master, the stock on hand, and the finance behind every transaction. The two overlap wherever the same products, customers, and sales matter to both — and when re-keying or an overnight batch is what connects them, the store oversells items it can't ship, quotes prices finance never set, or leaves buyers waiting on status that already changed.

Stacksync syncs Order Transactions, Sales Channels, Media, Products in Shopware with Sales orders, Purchase orders, Production orders, Warehouse / inventory in Infor LN field by field, in real time, and in both directions. You decide which system owns which fields — stock and pricing from Infor LN, order and customer detail from Shopware — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 Consolidate orders and customers from multiple `sales_channel` storefronts into one Postgres database for cross-channel analysis.
  • 02 Two-way sync of the `product` catalog — titles, nested price arrays, and stock — between Shopware and an ERP or PIM so pricing and inventory stay aligned.
  • 03 Replicate LN data into a warehouse for production, OTIF, and supply chain reporting.
  • 04 Run a two-way sync of business partners between LN and a CRM so sales and manufacturing share account data.

Common sync patterns

Fulfillment and shipment status close the loop

As orders are picked, shipped, or invoiced in Infor LN, tracking and status flow back to Shopware so buyers see accurate updates.

One customer master

Where both systems keep customer records, a correction in either propagates to the other, ending dual maintenance.

Where Infor LN is the inventory system of record: stock stays accurate

Available quantities from Infor LN publish to Shopware, so the store shows what can actually ship and stops overselling.

What you can sync between Infor LN and Shopware

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Infor LN objects Shopware objects How this pairing syncs
Sales orders Demand documents synced in from EDI and commerce channels. Order Transactions Payment records (`order_transaction`) holding payment method and state; read to reconcile against a billing or finance system. Sales orders is specific to Infor LN and Order Transactions to Shopware — each maps to any object or custom field on the other side.
Purchase orders Supply documents shared with supplier and procurement systems. Sales Channels Per-storefront configuration (`sales_channel`); used to scope and consolidate orders and customers across multiple storefronts. Purchase orders is specific to Infor LN and Sales Channels to Shopware — each maps to any object or custom field on the other side.
Production orders Shop-floor work orders synced with MES for execution visibility. Media Media assets (`media`) such as product images; referenced by id so file URLs and metadata sync into downstream catalogs. Production orders is specific to Infor LN and Media to Shopware — each maps to any object or custom field on the other side.
Warehouse / inventory Stock positions exposed so external channels reflect real availability. Products The product catalog (`product`), including parent/child variants, per-currency nested price arrays, and stock; synced two-way with ERP, PIM, or a database. Warehouse / inventory is specific to Infor LN and Products to Shopware — each maps to any object or custom field on the other side.
Projects Project structures used in engineer-to-order manufacturing scenarios. Categories The navigation and catalogue tree (`category`); mapped to product taxonomy in a warehouse or written from a PIM. Projects is specific to Infor LN and Categories to Shopware — each maps to any object or custom field on the other side.
Service orders Aftermarket service documents synced with field service tools. Customers Storefront customer accounts (`customer`) with addresses and group; synced two-way with a CRM or support tool. Service orders is specific to Infor LN and Customers to Shopware — each maps to any object or custom field on the other side.

How changes propagate between Infor LN and Shopware

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Infor LN Shopware Interval-based propagation

DetectionStacksync polls Infor LN for changes on an incremental schedule, reading only records changed since the previous pass. Event-style BOD publications through Infor ION where configured.

DeliveryEach detected change is written to Shopware through its API, with automatic retries and rate-limit backoff.

Shopware Infor LN Sub-second propagation

DetectionShopware notifies Stacksync of record changes through webhook events. App-system webhooks on entity events (product.written, order.written, customer.written) deliver the changed record's primaryKey and updated field.

DeliveryEach detected change is written to Infor LN through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Infor LN: Subject to the ION API gateway's tenant rate limits in cloud deployments.
  • Shopware: No general throttle on Admin API entity endpoints; Shopware's RateLimiter guards only specific routes (login, oauth, password reset, guest order/contact) and is configurable on self-hosted stores.
What ships with Infor LN ⇄ Shopware

Connect Infor LN and Shopware for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Infor LN–Shopware connection.

Real-time

Two-way sync

Changes in Infor LN or Shopware instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Infor LN or Shopware data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Infor LN or Shopware record.

Observability

Monitoring

Track your Infor LN ⇄ Shopware sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Infor LN and Shopware.

How the Infor LN and Shopware connectors work

Infor LN

Integration surface
SOAP and REST web services, with standardized BOD exchange through Infor ION in Infor OS deployments
Authentication
OAuth 2.0 via the ION API gateway in cloud deployments; application credentials on premises
Change detection
Event-style BOD publications through Infor ION where configured; otherwise polling
Capabilities
read · write
Rate limits
Subject to the ION API gateway's tenant rate limits in cloud deployments.

Shopware

Integration surface
Admin API (REST / JSON:API) with a bulk POST /api/_action/sync endpoint
Authentication
OAuth 2.0 — client-credentials grant using an Integration's Access Key ID + Secret Access Key, or resource-owner password grant for a user; access tokens expire after 10 minutes
Change detection
App-system webhooks on entity events (product.written, order.written, customer.written) deliver the changed record's primaryKey and updated field names; otherwise poll on the updatedAt / createdAt fields
Capabilities
read · write · webhooks
Rate limits
No general throttle on Admin API entity endpoints; Shopware's RateLimiter guards only specific routes (login, oauth, password reset, guest order/contact) and is configurable on self-hosted stores
How it works

How to connect Infor LN to Shopware — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Infor LN and Shopware with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Infor LN connected
    Shopware connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Infor LN and Shopware objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Infor LN ⇄ Shopware
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Infor LN Shopware
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Infor LN and Shopware integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 463 integrations available for Infor LN and Shopware.

Popular · 7 of 463
All Infor LN integrations All Shopware integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own