Custom Integration Development

Every e-commerce business eventually hits the same sentence: “These two systems don’t talk to each other.” Your accounting software has no connector for your platform, the carrier only works from its own panel, your supplier emails a stock list once a day. That’s exactly where we come in: if there’s no ready integration, we write one.

What kind of work

From scratch

  • ERP or accounting software without a ready connector (Logo, Mikro, Netsis, Nebim, SAP B1, custom systems): orders, stock, prices and invoices
  • Carriers or local delivery companies with no plugin for your platform: labels, tracking, returns
  • Marketplace APIs (Trendyol, Hepsiburada, Amazon, N11, Pazarama, Çiçeksepeti) connected directly, without an aggregator
  • Automatic stock and price updates from supplier or manufacturer systems (XML, CSV, FTP, API; whatever exists)
  • Warehouse management systems, barcode scanners and handheld terminals
  • CRM, call centre, SMS/email platforms and loyalty systems

Fixing and extending

  • Root-cause fixes for integrations that “sometimes work”
  • A middle layer adding the one thing a ready integration doesn’t do (variant-level stock, return invoices, multi-warehouse)
  • Speeding up slow syncs; adding queues and retry logic
  • Updating existing integrations when APIs change (Trendyol, Shopify and ikas change theirs regularly)
  • Handing over from one aggregator to another without data loss

Which platforms

On Shopify we work through the Admin API, webhooks and, where needed, a custom Shopify app. On ikas we use the ikas API through our partner account. On WooCommerce we work via the REST API or directly at plugin level. We’ve also worked with the APIs of Ticimax, İdeasoft and T-Soft; for custom platforms your API documentation is enough.

We build with .NET, Node.js and Ruby on Rails; integration services can run on our infrastructure or yours (AWS, Hetzner, your existing server). Your choice.

How we work

  1. Discovery: Which systems, which data, which direction, how often. We produce a one-page flow diagram in one or two calls and ask for API docs and access at this stage.
  2. Scope and timeline: Most integrations get a first working version in a few days to two or three weeks. Written, itemised, fixed-price quote.
  3. Build and test: In test stores or sandbox accounts. With live data we start in read-only mode to avoid writing wrong stock or issuing duplicate invoices.
  4. Controlled go-live: A few products or orders first, then everything. We watch the logs together in the first days.
  5. Monitoring: You and we get alerted when the integration stops or error rates rise. Integrations don’t break on day one; they break quietly in month three, so we don’t skip this.

We have a fast-track mode for urgent cases: a marketplace campaign that needs stock sync by a deadline, or an aggregator that discontinued its service. We narrow the scope, ship a working version in days and complete the rest afterwards.

Does the integration need maintenance afterwards?

When the other side changes its API, yes. Shopify changes twice a year; Trendyol and ikas at irregular intervals. Optional monthly maintenance covers this; otherwise we hand over code and documentation.

Do we get the source code?

Yes. The integration’s code and setup documentation are yours.

Where does the integration run?

Your server, your cloud account or infrastructure we manage. For sensitive data we recommend your own.

Can you do a feasibility check first?

Yes. We review the other system’s API in one or two days and tell you in writing whether what you want is possible, including when it isn’t.

Systems that won’t connect?

Tell us which system you want connected to what. If a ready solution exists we’ll name it; if not, we’ll say how long it takes to build.