ecommerce_ops · workflow

iMi digital GmbH cuts ERP import time from one day to 10 minutes with n8n

iMi digital GmbH's development team needed a reliable, performant ERP import for their Shopware store that could handle multiple entity types and extremely large pricing datasets without memory issues. Separately, internal marketing operations such as moving seminar signups into a CRM and Mautic were still handled manually.

How it works
Common implementation structure
How this type of workflow is generally built, generalized across documented cases — not tied to any one vendor's stack. Click any stage to read what happens there. Specific products that implement these stages appear in “Tools commonly seen” below.
Stage 1 · File watcher on hot folder
A file watcher monitors a hot folder fed by CSV files from SFTP.
Tools used
n8nShopware APIShopware Sync APIMautic
Outcome

The n8n import workflow reduced product import runtime from about a day to around 10 minutes and now processes approximately 2.6 million price rows per week in a unified system. The marketing team no longer handles seminar participants manually, saving several minutes per participant and an estimated few hours per month.

What failed first

A previous importer built by an external ERP-focused party took about a day to run, creating operational friction and limiting how quickly the store could reflect new data.

Results
Time savedaround 10 minutes
Volumeseveral minutes per participant
Cost replacedabout 2.6 million
Source

https://n8n.io/case-studies/imi-digital-gmbh/

How we source this →

Grounding & classification
Source type: vendor customer story
28 fields verified against source quotes.
product catalogfailure mode describedmetric backednamed customerproduction runtime claimedtools describedworkflow describedprofessional servicescycle time reductionemployee productivitythroughput increasetime savedvendor customer storyback office opsdata entry opsecommerce opsmarketing opsdata sync enrichmentdocument to recordextract classify route