For Brand Teams

    The Data Layer for MAP Monitoring

    Seller, offer and pricing data for the marketplaces your MAP workflow monitors, normalized through one API, with changes delivered into your own compliance or brand-protection system.

    · Free tier available · Plans from €79/mo

    Seller Identity & Pricing · Flagged Violations

    What You Get

    Seller and Offer Data, One Schema

    01
    Seller Identity
    Every observed offer carries who made it, not price alone.
    seller_idseller_namesource
    02
    Observed Price & Shipping
    The offer values observed on the marketplace, per seller.
    priceshipping_costcurrencyobserved_at
    03
    One Schema
    The same fields across every supported marketplace.
    04
    Detected Changes
    Seller, price, shipping or offer availability moved.
    previouscurrentdetected_at

    Seller identities are source-specific and are not unified into one entity across marketplaces. kwery returns the values observed on the marketplace; your policy determines which of them count toward MAP compliance. Changes are detected when a subsequent observation sees the new state.

    MAP Workflow

    What Does MAP Monitoring Actually Require?

    A MAP workflow needs more than a price. It needs to know which product, which seller, which marketplace, at what price, when, and what changed.

    01 / Marketplace Observation

    The Signals kwery Returns

    One normalized record of the product, seller, offer, source, and observed change.

    02 / Policy Evaluation

    The Decision Your System Makes

    Your MAP policy interprets the observation and decides whether it needs review or action.

    IdentityProduct identity · Seller identity
    OfferObserved price · Shipping
    ContextSource & geography · Timestamp
    ChangePrevious state · Current state
    kwery Returns

    A MAP-ready marketplace observation

    Your Policy Decides

    Review, evidence capture, and enforcement workflow

    Ownership Boundary

    kwery does not store your MAP floor or classify policy violations.

    A MAP decision is only as reliable as the observation behind it, a false product match can create a false MAP signal, which is why resolution and data quality come first.

    Where kwery Fits

    Where kwery Fits in a MAP Monitoring Workflow

    Three layers sit between a marketplace listing and an enforcement action. kwery owns the first one.

    Marketplace Data

    kwery

    Product resolutionSeller & offer observationDetected changesOne schema
    Policy & Compliance

    Your system or MAP platform

    MAP floorReseller registryViolation rulesCase prioritization
    Evidence & Enforcement

    Your workflow

    Evidence captureCase recordsReseller outreachEscalation

    kwery supplies the marketplace observation. Your policy determines what it means.

    Not included: MAP-floor storage, violation classification, reseller-registry management, evidentiary screenshots, first-mover attribution or legal workflows. See marketplace data infrastructure →

    How It Works

    From Marketplace Offers to Your MAP Rules

    kwery observes the sellers and prices for the products you monitor. Your own MAP policy or monitoring system compares those observations against the applicable price floor and decides what happens next.

    1. Define your MAP policy

      Your system or MAP platform holds the price floor, reseller rules and policy exceptions. kwery never sees or stores them.

    2. kwery observes the marketplace

      The product is resolved and current offers return with seller identity, observed price, shipping and marketplace context, one schema, every supported marketplace.

    3. Your system evaluates and acts

      Compare the observation against your policy, capture what evidence you need, and route the case through your existing workflow.

    POST · api.kwery.co/stream
    {
      "event": "price.delta",
      "delivered_at": "2026-09-14T09:41:12.000Z",
      "product": {
        "source": "idealo",
        "country": "de",
        "key": "gtin",
        "value": "4006381333962",
        "name": "STABILO point 88 ocker"
      },
      "changes": {
        "price": {
          "old": 17.4,
          "new": 14.9
        }
      }
    }

    Coverage

    One MAP Workflow Across Supported Marketplaces

    Query supported marketplaces with the same request shape and consume seller, offer and source context through one normalized schema.

    By Marketplace

    How MAP Monitoring Differs by Marketplace

    The core input is consistent, seller identity, observed offer price, shipping, source, and timestamp, while each marketplace adds different context for your policy system to evaluate.

    Amazon spans 22 marketplaces under one seller ecosystem, so each marketplace needs an independent observation. Seller type, including FBA and merchant-fulfilled offers, adds useful context alongside seller identity, observed offer price, shipping, and timestamp.

    eBay's 18 markets each need independent monitoring. Active listings show current seller and offer data, while completed-sale data provides additional context for distinguishing a one-off listing from a sustained observed pricing pattern.

    Google Shopping spans 48 supported markets. Merchant identity, observed item price, shipping, and listing position show what appears in each market's comparison view, including listings that may also appear through paid Shopping placements.

    Walmart's Featured Offer includes both WFS and seller-fulfilled listings. Fulfillment type is useful source-specific context alongside seller identity and observed offer values when your system routes an observation for review.

    Otto exposes seller trust and delivery context alongside the observed offer. Those source-specific fields can help your workflow prioritize reviews without changing the underlying boundary: your policy determines what the observation means.

    Kaufland spans multiple Central European markets under one seller account. Observe each market independently because a seller's price, shipping, and availability can differ by country even when the seller identity is shared.

    Rakuten Ichiba uses independent branded storefronts rather than one shared listing. Seller identity therefore maps directly to the observed storefront, with listed price and points context kept alongside that source-specific identity.

    Idealo ranks offers using total landed price, so item price and shipping should be monitored together. kwery returns both fields; your MAP policy decides which observed value or calculation applies.

    billiger.de uses a cost-per-click merchant model. Monitor resolved merchant identity, observed item price, shipping, and offer position together so your workflow retains the visibility context surrounding each observation.

    guenstiger.de does not use paid placement in its merchant ranking. Observed price, shipping, merchant identity, and position therefore provide a direct view of the offer order your policy system can evaluate.

    AliExpress uses many independent listings for the same or a near-identical product. Monitoring needs to retain the specific listing and seller identity for each observed price, rather than treating the marketplace as one shared product page.

    Who It's For

    Brands, Compliance Teams, and Agencies

    01

    Brand & channel managers

    See which sellers are offering your products, at what observed price and on which supported marketplaces, so your own MAP policy can evaluate the market on current data rather than manual spot checks.

    Feeds → channel review

    02

    Distributor & reseller compliance teams

    Feed observed seller and offer data into your reseller-compliance workflow and compare it against the price floors, authorization lists and policy rules your organization already maintains.

    Feeds → compliance queue

    03

    Agencies managing MAP for multiple brands

    Use one marketplace-data schema across client portfolios instead of maintaining separate source-specific collection logic for every marketplace.

    Feeds → client reporting

    Self-Serve

    One Credit. One Resolved SKU

    MAP monitoring scales with the number of products, marketplaces and fresh observations your workflow requests, product matching, product page, and offers are billed as a single credit.

    01

    Product Matching

    Identify the correct product within the requested source using GTIN or URL.

    02

    Product Page

    Title, brand, specs, images, and category, fully normalized.

    03

    Offers

    Every seller, price, condition, and shipping option in the offer section.

    Entry Price

    €79 / mo

    Included

    10k credits / mo

    Included Usage

    Up to 20k SKUs / mo

    Amazon, Walmart & ebay count 2 SKUs per credit. Every other source counts 1.

    Free tier available · 1,000 one-time credits, no credit card required.

    Enterprise

    Need Custom Pricing, SLAs, or Support?

    Dedicated volume pricing, custom SLAs, and direct engineering support for teams running millions of SKUs.

    Talk to Sales

    Support

    Common Questions

    What teams ask before wiring marketplace observations into a MAP or brand-protection workflow.

    Browse all FAQs

    No. Your organization sets the MAP floor and policy rules. kwery returns the marketplace observation, including product, seller, observed price and source context, and your system determines whether that observation violates your policy.

    kwery returns the seller identity attached to observed marketplace offers. Your own reseller registry or MAP platform determines whether that seller is authorized, unknown or out of policy.

    kwery returns the price and offer context observed on the marketplace. Checkout-only discounts, coupons, membership pricing or other transaction-specific adjustments may not be represented in the same way. Your MAP policy should determine which observed values are relevant to compliance.

    No. kwery returns marketplace seller identity. Your authorized-reseller registry remains yours, so your system or MAP platform determines whether that seller is authorized under your policy.

    Yes, where kwery supports those marketplace-country combinations. Each country and marketplace combination is queried independently while the response schema stays consistent.

    Yes. kwery compares a fresh observation with the previous one and exposes a structured difference when the state changes. It does not know the exact instant the external marketplace changed; the difference is detected when a later observation sees the new state.

    No. kwery returns structured marketplace observations. If your monitoring process requires screenshots or other visual evidence, add that capture layer separately or use a dedicated MAP and brand-protection tool alongside kwery.

    Not currently. kwery can expose observed seller and price changes, but first-mover attribution across a sequence of sellers requires additional logic outside the current API.

    It is the same underlying capability. This page explains the general MAP and brand-protection workflow, while the source pages explain what is specific to each marketplace.

    Give Your MAP Workflow a Live Marketplace Data Feed

    Monitor supported marketplaces with normalized seller and offer data, then apply your own MAP rules, reseller policy and review process on top.

    Enterprise SLA
    Global Scale