Ratgeber · B2B · 2 Min.
/ Kurz gesagt
Tracking numbers had to go from the ERP back to Shopify. Instead of an expensive integration, we built a clean CSV process that can be automated later.
Durstladen
The tracking numbers were generated in the ERP’s shipping process and had to get back to Shopify so customers would receive their shipping email with a link. A fully automated integration would have been possible, but expensive and unnecessary for the actual workflow. We built a clean CSV process. It runs reliably, and it can be automated later without reinventing anything.
A merchant ships through his ERP. That’s where the parcel numbers are generated. Shopify knew nothing about them: orders stayed open, customers got no shipping confirmation and asked support where their parcel was.
We set up a fulfillment app that imports shipping data from a file, and adjusted the ERP’s export format so the app understands it. A file like this doesn’t need more than:
Shopify then marks the order as fulfilled and automatically sends the customer the shipping email with a tracking link.
How the file gets from the ERP into the app is an organizational question, not a technical one. We talked through the options with the merchant:
| Method | Effort for the team | Fits when |
|---|---|---|
| Manual upload | Upload once a day | Shipping runs once a day |
| Shared spreadsheet | ERP writes to it, app reads it | Several shipping runs a day |
| ERP sends the file automatically | ERP can email reports | |
| FTP or server link | None | Full automation without a custom integration |
We started with the manual upload. It worked from day one.
Is something stuck between your ERP and Shopify? We look for the simplest solution that runs reliably, not the most spectacular one.
Weiterlesen · B2B


Erstgespräch · 20 Minuten · kostenlos
Du erzählst, wo dein Store steht und wohin er soll. Wir sagen, ob wir passen, und was es kostet. Ehrlich und unverbindlich.
Worum geht's?
BerlinDeutsch oder EnglischMaria oder Pascal, keine Juniors