Apollo by eBrands← Back to home
Data access & purpose

How we access Amazon Selling Partner data

Last reviewed: July 2026

eBrands Global operates its own Amazon seller accounts and connects them to our internal systems through Amazon's Selling Partner API (SP-API). This page explains, for the restricted data our integration is authorized to access, what we read and why. It covers the Amazon accounts that eBrands owns and operates; the integration is not offered to other sellers.

Tax Invoicing

What we access.For the EU marketplaces where eBrands is registered for VAT — Germany, France, Italy, Spain, and the United Kingdom — we retrieve Amazon's VAT Transactions Report (report type GET_VAT_TRANSACTION_DATA).

Why. We use it for our own internal EU VAT reconciliation and month-end reporting: matching the VAT figures Amazon reports against our accounting records so we can file accurate VAT returns in each country where we are registered.

How we handle it.The tax data is used only for internal reconciliation. We apply no AI-based processing to it — the reconciliation is a straightforward, rule-based comparison against our own records — and we do not alter the figures Amazon provides. The report reflects Amazon's reported transactions for the period it covers.

Direct-to-Consumer Shipping

What we access.For our own orders, we read the buyer's contact and shipping information — name, email, and delivery address.

Why. We use it solely to fulfill our own Merchant-Fulfilled orders. We create the sales order in our ERP, our warehouse picks, packs, and ships the parcel to the address provided, and we confirm the shipment back to Amazon. Orders that Amazon fulfills on our behalf (FBA) do not require this buyer information.

Keeping this accurate

We review this page against the Amazon data our integration actually uses, and we update it whenever those roles or that data change.

Questions

For data-protection or data-access inquiries, contact apollo@ebrandsglobal.com.