Connect your ERP to the online shop: JTL-Wawi and WinLine
A shop without an ERP behind it gets maintained by hand, and that only works while the range stays small. I connect JTL-Wawi and WinLine to WooCommerce so that products, prices, stock levels and orders flow automatically. The ERP stays the system of record, the shop shows what is maintained there.
How the sync works
The ERP sends what changed through its connector. The shop accepts it, checks it and returns orders. Sounds simple, and the technology is. The work is in the data.
- Products and variants: parent and child articles, attributes, images, copy per sales channel
- Prices: list prices, volume prices, sale prices with a time frame, unit prices
- Stock: levels per variant, reorders, blocked stock
- Orders back: line items with variants, discounts as coupons, payment method, status both ways
- Customers: created or linked, without duplicates
What I connect
- JTL-Wawi: via the JTL connector for WooCommerce, extended where the connector leaves data behind, such as nutrition facts, variant names or unit-price flags. Reference: ROC Sports, 101 products, headless frontend
- WinLine by mesonic: connected to WooCommerce through an interface by Sysco, covering products, prices, volume prices and orders. Currently being built for AllesWurst
- Headless frontends: if the shop has its own frontend, a bridge pulls the data after every sync so the site never shows a stale state
What silently breaks during sync
This is the part people hire me for. None of it throws an error, the wrong thing just arrives. All from live projects:
- Sale prices stay put: the ERP ended the sale, the shop keeps selling at the old price
- Short descriptions vanish: for some variants the push replaces the copy with the attribute line
- Variants get new URLs: a full sync turns single articles into variants, old links go nowhere
- One article takes ten down: a product missing its type entry aborts the whole transfer batch
- Copy in the wrong channel: descriptions maintained for the wrong sales channel, the sync empties hundreds of long texts
- Line items without the flavour: the order arrives, the ERP shows only the parent name, the warehouse does not know what to ship
- The shop cannot reach the frontend: the server resolves its own domain to itself, webhooks go nowhere
Check instead of hope
That is why every integration ships with tools that measure after the sync: are all products linked, do the prices match, is the copy where it belongs? A backup precedes every full sync, checks follow it, and you hear about deviations before a customer does.
If you have an ERP and a shop that does not talk to it, send me which systems are involved. You get an honest assessment of what works and what the data needs first.
Frequently Asked Questions
Which data does the sync cover?
Products with variants and attributes, prices including volume and sale prices, stock levels, images and copy towards the shop. Orders, customers and payment status towards the ERP. We define upfront which side leads.
Does the ERP stay the system of record?
Yes. Prices, copy and stock are maintained there only, the shop displays them. Once two places get edited, you have two truths, and the next sync overwrites one of them.
Does this work with a headless shop?
Yes. ROC Sports runs a Next.js frontend with WooCommerce purely as the backend and JTL-Wawi behind it. A custom bridge pulls the data into the frontend after every sync, including nutrition facts, unit prices and variant names.
How long does an integration take?
The technical setup takes days. The real work is in the data: sales channels, variants, attributes and copy have to be maintained in the ERP in a way the shop can take over cleanly. After a look at your ERP I can give you a range.
What if a sync damages something?
Every full sync is preceded by a backup, every sync is followed by check scripts: links between records, sale prices, short descriptions, variant URLs. Deviations get reported before customers see them.
Related Services
- Headless WooCommerce · Decoupled e-commerce with WordPress backend and blazing-fast Next.js frontend.
- Online Shop & E-Commerce · Your own online shop with product management, payment, and shipping, or make an existing WooCommerce system faster and more modern.
- WordPress & WooCommerce · Your WordPress or WooCommerce site runs on old or insecure hosting? I set up your site fresh on a Hetzner server in Europe and import your existing database: products, orders, and customers stay identical, only the foundation gets clean. Then I develop custom plugins, fix problems, and optimize your shop.