Automations · CODEFIX

API integrations, supplier crawlers and server jobs.

See what we built for Upoptic, ToolsBox and Golden Drinks: supplier data, stock updates and imports.

Discuss an automationExplore the implementations

From our projects

What we have built.

Supplier integration on a server

Upoptic

MerchantPro

  • Node.js
  • API
  • Webhooks

Catalogue, prices and stock, from the supplier’s API.

The situation

Supplier products and availability need to reach the store and stay up to date.

What we built
  • A service running on a server, connecting the supplier’s API to MerchantPro.
  • New product imports with brand and image preparation, plus updates to existing prices, stock and statuses.
  • Scheduled jobs, resumable imports and checks before writing data.
What it addresses

A supplier-to-catalogue workflow with repeatable updates and checks when the source is unavailable.

Discuss a similar integration
  1. Supplier API
  2. Integration service
  3. MerchantPro catalogue

Crawling for suppliers without an API

ToolsBox

Gomag

  • Python
  • macOS
  • Windows

Supplier availability in a dedicated application.

The situation

Suppliers do not offer a stock API. Checking availability means visiting their websites.

What we built
  • A Python crawler reading availability directly from supplier websites.
  • Data prepared for updating the store’s information.
  • An application for macOS and Windows that the team can use.
What it addresses

Availability information brought together in a tool adapted to the store’s sources.

Read the case study
  1. Supplier websites
  2. Python crawler
  3. Availability data

Data migration between platforms

Golden Drinks

WooCommerce · MerchantPro

  • API
  • Dry-run

Products, customers and orders, without duplicate records.

The situation

Products, customers and orders need mapping and checking. When the import runs again, it needs to update existing records.

What we built
  • An importer reading data through the WooCommerce API and writing it through the MerchantPro API.
  • Matching existing records for repeatable imports without duplicates.
  • A dry-run mode to review changes before the actual migration.
What it addresses

A migration that can be checked and rerun, updating existing records.

Read the case study
  1. WooCommerce API
  2. Mapping and checks
  3. MerchantPro API

Cross-store synchronisation

MerchantPro / CS-Cart

MerchantPro · CS-Cart

  • Python
  • API

Products and stock coordinated across stores.

The situation

When the same products appear in several stores, stock changes need to be coordinated across systems.

What we built
  • Matching products across stores and mapping their fields.
  • Stock synchronisation and a record of operations already applied.
  • Tracking changed and cancelled orders to reconcile their effect on stock.
What it addresses

A connector that tracks what has been updated and handles stock differences across stores.

Discuss cross-store synchronisation
  1. Connected stores
  2. Python connector
  3. Coordinated products and stock

For your store

What we can automate.

We agree the data source, rules and destination. Each integration is built for the platform and access available in your project.

Supplier data

We connect APIs and build crawlers for sources without a stock integration, preparing data for catalogue updates.

Server jobs

We build services running at agreed intervals, with source checks, resumable operations and logging.

Cross-store synchronisation

We match products across stores, update stock and handle the effects of changed or cancelled orders.

Migration and cross-platform imports

We map products, customers and orders, check data before writing and handle records that already exist.

Rules for product pages

We generate fields and options according to the product or category. For Sefinni, we built visual attributes and a ring size converter.

Explore the Sefinni example

Technical sheets and PDF documents

We process and translate technical sheets in batches, including German to Romanian. Terminology and formatting are reviewed before use.

Where we start

Which operation do you repeat manually?

  1. Show us the current process

    Show us the data you receive, where you enter it and what happens when a value is missing or changes.

  2. Agree the rules and access

    We identify available APIs or sources, data to update and cases that need review.

  3. Build and verify the workflow

    We test with a controlled dataset, check the results and prepare the workflow to run under the agreed conditions.

Discuss an automation

Your next project

Let’s connect the systems you work with.

Tell us which store you use, where the data comes from and which operation you want to simplify. We start with your process.

david@codefix.ro
Discuss a projectWhatsAppSchedule a call
Free auditSEO · GEO · UX
PDF

Reviewed by our team

Clear recommendations
for your website.

Our team reviews your website and prepares a free PDF with findings and recommendations in priority order.

  • SEO for GoogleSEO
  • GEO for AI searchGEO
  • Design and mobile experienceMobile UX

No obligation to work with us.

View a sample PDF (Romanian) · 22 pages

Where should we send your audit?

We’ll use it if we need to clarify anything about your audit.

Terms

We use your details to respond to your audit request. Privacy policy.

No obligation to work with us. Website and email are required; phone number is optional.