Kaufland Offer Sync (Update-Only): The Safe Way to Keep Price and Stock Fresh

In marketplaces, “create” is risky.

It’s easy to create the wrong offer with:

• the wrong condition
• the wrong storefront
• missing compliance fields
• the wrong EAN mapping
• inconsistent identifiers

Those mistakes can be expensive.

So update-only sync is the disciplined, traditional approach:

> First, prove you can update reliably. Then expand scope.

In Kaufland, an offer (unit) is uniquely identified by the combination:

**EAN + Condition + Storefront**

That means the connector looks at these three pieces of information to locate the existing unit.

 Behavior

• If a matching unit is found → update price/stock/handling time
• If no matching unit is found → mark the sync as failed with:
  • `Cannot find existing offer`

This is the correct kind of strictness. It prevents “phantom offers” from appearing because a mapping was wrong.

You can export offers using either:

• `OutputConnector` (single item)
• `OutputConnectorByBatch` (bulk)

Batch mode supports up to 150 offers per batch, which is ideal for real-world offer volume and helps reduce request overhead.

A high-level flow looks like:

1. build a pipeline that produces Offer objects
2. add an output processor (single or batch)
3. configure a `targetId` that represents the Kaufland storefront destination
4. onboard the channel using that same `targetId` so the connector knows where to send updates

This keeps the pipeline definition and the channel onboarding aligned – no hidden mapping magic.

• Always include valid EAN and Condition on offers. They’re mandatory for correct unit matching.
• Treat `targetId` as a stable contract. If it changes, your connector routing changes.
• Prefer batch export for high-volume updates. It’s cheaper, faster, and friendlier to APIs.
• Use Data Flow Tracking to monitor failures and spot “offer not found” patterns early – those usually indicate mapping issues.

Developers

• clear identification logic (less ambiguity)
• safer connector behavior (less risk during rollout)
• batch export for operational throughput

Merchants

• safer price/stock updates without accidental new offers
• predictable behavior under load
• cleaner error signals when something isn’t mapped correctly

Agencies

• easier rollout strategy: start with updates, validate matching logic, then scale
• fewer marketplace “oops moments” during go-live

Investors

Connector depth expands addressable value. Update-only is a reliable first step toward full lifecycle sync while keeping risk low.

January will focus on the developer and operations experience again:

pipeline testing mode and expanded UI capabilities – so teams can validate flows safely before turning them loose on production channels.

Fast and reckless breaks things.

Slow and deliberate builds trust.

Qilin.Cloud is taking the deliberate path – because that’s how integrations survive in the real world.