EcomVerify

How we use Selling Partner API data

Case-by-case transparency on what data we process and for what purpose.

Minimization principle: we only request the roles and scopes strictly needed per feature. Nothing is accessed without explicit seller authorization.

Features and data used

Listing creation & management

No buyer PII

Data used: ASIN, SKU, titles, attributes, images and A+ content.

Purpose: create, publish and maintain the seller's listings. No buyer data required.

Product research & analytics

No PII

Data used: public catalog, rankings, sales estimates and market prices (aggregated).

Purpose: analyse demand, competition and assortment opportunities. No buyer data accessed.

Automated pricing & repricing

No buyer PII

Data used: own prices, competitor offers and Buy Box status.

Purpose: set and automate listing prices. No buyer data required.

Inventory & order management

Restricted PII

Data used: order status and lines, quantities, SKUs and order shipping data where applicable.

Purpose: order and inventory tracking and the basis for invoicing and accounting.

PII retention: buyer shipping data kept only as long as needed for the operation and tax obligation.

Logistics (FBA, AWD & MCF)

Restricted PII

Data used: shipments, inventory in Amazon centres and order delivery address.

Purpose: manage FBA/AWD shipments and multichannel fulfilment.

PII retention: delivery address processed minimally and not reused for other purposes.

Buyer communication

Restricted PII

Data used: order identifier and Amazon messaging channel (no direct buyer email).

Purpose: answer queries and request reviews exclusively through Amazon-authorised channels.

Note: we do not export or store messages outside Amazon; no marketing to buyers.

Brand & performance analytics

No PII

Data used: Brand Analytics, account and performance metrics (aggregated).

Purpose: provide the seller with brand and sales insight. Contains no buyer data.

Sustainability certification

No PII

Data used: product sustainability attributes and certifications.

Purpose: retrieve and submit sustainability certifications. No buyer data required.

Automated B2C invoicing

Restricted PII

Data used: buyer name, shipping address, billing address, country, buyer email (if Amazon provides it), order amounts and breakdown.

Purpose: issue the tax-legal invoice required by Spanish regulation (RD 1619/2012). Without this data the seller cannot meet tax obligations.

PII retention: 30 days active; after invoice issuance, data resides in the fiscal document under legal retention obligation.

Tax calculation (VAT, OSS/IOSS)

Restricted PII

Data used: destination country, amount, product tax category.

Purpose: apply correct VAT rate per destination, determine OSS/IOSS applicability, generate filings.

Note: destination country is derived PII. Full name/address not stored for B2B orders without legally required invoice.

Bookkeeping

No PII

Data used: settlement reports, Amazon fees, refunds, FBA charges, net amounts.

Purpose: generate accounting entries for ContaSol or other systems. No end-buyer data needed.

Reports and dashboards

No PII

Data used: sales aggregates per ASIN/SKU, margins, inventory.

Purpose: show the seller business metrics. Reports contain no end-buyer data.

Security and auditing

No buyer PII

Data used: seller access logs, API errors, security events.

Purpose: detect incidents, audit accesses, fulfill GDPR Art. 32.

What we do NOT do

Rights and control

Last updated: 2026-08-03. Read the full Amazon Data Protection Policy.