The hard part is not connecting, it is what happens when it breaks
Every integration looks elegant in a demo. The problems start the day the supplier answers in forty seconds, sends a price with a comma instead of a dot, or returns a negative stock figure.
We build integrations starting from those situations: automatic retries, a log of every call, alerts when something stays stuck, and a screen where the operator sees exactly what failed and why.
- Importing products, prices and stock from suppliers in any format: API, XML, CSV, FTP
- Generating shipping labels and pulling delivery status from couriers
- Automatic invoicing and synchronisation with the accounting software
- Publishing and synchronising on marketplaces
- Two-way links with ERP and CRM systems
What adding a new supplier really involves
We do not start from code, we start from their real data. We take a full export and look at which fields arrive, how often the structure changes, and where the values that break an import appear: prices written with a comma, negative stock, products without a unique code, the same brand spelled four different ways.
Only once the mapping between the supplier's fields and your structure is written down do we write the import. That avoids the classic outcome where an integration runs flawlessly for two weeks and then fills the shop with wrong prices overnight.
- A documented field mapping, so someone outside the technical team can check it too
- Pricing rules: markup, rounding, exceptions per category or per product
- Products that disappear from the feed are hidden, not deleted — order history stays intact
- A schedule that matches the supplier's rhythm rather than an arbitrary one