MAP Monitoring

Yes. Where a marketplace exposes seller identity and observed price, your own policy system can evaluate those fields in a separate monitoring workflow. Your team remains responsible for the policy and any action taken. Explore MAP Monitoring.

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.