Skip to content

Integrations

Keep stock and prices aligned from source to shop.

When the shop and a warehouse, CRM or price file disagree, we map the fields and make failures visible. The result is a data flow with clear rules and a log someone else can use.

Send a wrong product A similar situation

Included

Concrete tasks

A mapping you can read

Which field in the file or API becomes which field in the shop. Written down, not remembered.

Files and APIs you already have

CSV, XLSX, JSON, XML, REST, webhooks. We use the source that actually exists.

Catalog, stock, prices

The numbers a buyer sees, kept in step with the warehouse, CRM, or price file.

A log, not a silent fail

Rejected rows listed. Someone other than us can see why a product did not update.

How we approach the work

From first review to handover

  1. 1

    You send one wrong example

    A sample file or the API notes you have, and one product where the shop and the source disagree. No full dump required.

  2. 2

    We write the mapping and the rejects

    Which fields can be imported, how each row is validated and what happens when the source is incomplete.

  3. 3

    You see a run, including the bad rows

    Failures visible before they are half-applied to the catalog.

  4. 4

    You can re-run it without us

    Who watches the log, and how to start the job again. A schedule that pings you is automation, if you want it.

Common situations

Issues that often share a cause

  • Stock on the site lags the warehouse by a day, or by a week.
  • Prices in the shop do not match the current price file.
  • The import “succeeds” and still writes the wrong column.
  • The only copy of the script is on a laptop that left the company.
  • A CRM has the order. The shop never hears about the status.

Scope boundaries

When an integration is not the right fit

  • Replacing the ERP. We sync with it. We do not become it.
  • “Make it ping me.” That is automation.
  • A one-off converter for a single spreadsheet. That is a custom tool.
  • A bus for every system in the company. We connect the shop to the source that matters.

If the numbers already disagree

Send one product that is wrong, and where the right number lives. That is enough.

Write about the mismatch

A practical question

“Can you just connect everything?”

We start by mapping one source and the fields the shop needs. That shows which systems are in scope and what a realistic sequence looks like. If the source file is more complex than it first appeared, we agree the next stage before continuing.

A useful first message

Start with one example

The shop URL, and one example where stock or price is wrong. Say where the right number lives. We reply with what we need to see.

Go to contact Read the case