# Amazon Seller Central

{% embed url="<https://www.loom.com/share/2c024a1ee8324172a47f22f4ef5e8fd2?sid=fbede64d-e836-4690-9558-74932c69e41bw>" %}

[**Loom Link**](https://www.loom.com/share/ab6d426b368941b380c6632aa2fd5ddf)

### **Required Permissions to Connect to AmazonSP**

* You either have to be an **Amazon Seller Central Admin** OR
* **If you're not an admin**, then you need an Amazon Admin to give you "Performance -> Selling Partner Appstore" access. They can do that via User Settings.&#x20;

*Here's an email of what to send your Amazon SP admin*

*Hi NAME,*&#x20;

*I would like to request access to "Selling Partner Appstore" in order to connect our Amazon to a FP\&A tool that I am currently demo-ing. Here's what to do:*&#x20;

1. *Log into* [*Amazon SP User Management*](https://sellercentral.amazon.com/account/permissions#/user-management/users)
2. *Click on "Edit" next to my name*
3. *Select "View & Edit" under "Performance -> Selling Partner Appstore"*

<figure><img src="https://2089194542-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuPhWdKX288WBK7UyaQZw%2Fuploads%2Fsm4dyhzMk6FgABR4v3xM%2Fimage.png?alt=media&#x26;token=53ef2330-6bd6-4a81-a3da-f976f4a807ee" alt="" width="375"><figcaption></figcaption></figure>

4. *Keep all other default permissions the same*
5. *Save the configuration*
6. *Done✅*

*Thank you so much for helping me out!*

## FAQ: Connecting Seller Central to Drivepoint

<details>

<summary>I can't seem to be connecting through the UI. Is there another why?</summary>

Yes! There's a manual way to connect Drivepoint to AmazonSP. You can invite our email <finance@bridgegrowth.com> to AmazonSP. Check out the Loom to learn how to do that and which permissions are required: <https://www.loom.com/share/ab6d426b368941b380c6632aa2fd5ddf>

</details>

<details>

<summary>Why do some Amazon Seller Central Stores not connect to Drivepoint?</summary>

* We tried to pull historical data but unfortunately our data pulls failed because we do not have permissions to the "restricted orders"
* The restricted orders are not necessarily relevant but we currently do not have a way to exclude them in our datapulls
* Hence, the whole things fails because we lack the permission to one of the table

There are some providers that offer to pull the data (through some weird loophole that Amazon seems to be unaware of or weirdly allow). If you are curious to learn more email <support@drivepoint.io>.

**If you want to dive deeper:**

Amazon considered requests for PII data as restricted operations, and require special authorization in the form of a Restricted Data Token (RDT). An RDT allows an authorized applications permissions to to access restricted data such as shipping, tax invoicing, or tax remittance services.

**What is Amazon PII? Amazon's definition of PII:**

"any information that can be used on its own or with other information to identify contact, locate an individual (e.g., Customer), or identify an individual in context. This includes, but is not limited to, a Customer name, address, e-mail address, phone number, gift message content, purchases, and latitude/longitude of buyer addresses".

Amazon Does Not Supply PII For Fulfillment By Amazon (FBA) Traditionally, Amazon's data protection policies limit buyers' access to personally identifiable information (PII). Amazon introduced the policy of not sharing the FBA PII data in 2019. **As a result, Amazon does not share this information via API or your Amazon Seller Central account.**

Restrictions to PII data apply to the Selling Partner API as to the legacy MWS API application. In many ways, the process for accessing PII in the new SP-API is significantly more complex as the review and approval process is extensive.

**Drivepoint does not support PII data requests.**

**Additional Resources:**&#x20;

<https://developer-docs.amazon.com/sp-api/docs/tokens-api-use-case-guide#terminology>

<https://youtu.be/PbPIHdcHXmA?feature=shared&t=696>

</details>

<details>

<summary>How does Drivepoint pull Customer IDs with Amazon's removal of customer IDs?</summary>

</details>

## **FAQ: Amazon New vs. Returning Customer Data**

<details>

<summary><strong>What happened to new vs. returning customer data on Amazon?</strong></summary>

In February 2026, Amazon removed a key customer identification field from their Selling Partner API without advance notice. This affected all platforms that rely on Amazon order data for customer segmentation — not just Drivepoint.

</details>

<details>

<summary><strong>Was my data affected?</strong></summary>

If you have an Amazon sales channel connected to Drivepoint, your new vs. returning customer breakdown between approximately February 9 and late March 2026 may have been less accurate than usual. Our system's built-in fallback kept data populated during this period, but the underlying accuracy was degraded.

</details>

<details>

<summary><strong>How has Drivepoint resolved this?</strong></summary>

We identified and built an alternative data pipeline that restores accurate customer identification for Amazon orders. Most affected customer accounts have been backfilled and are running on the updated pipeline going forward. We're in close collaboration with the customers who are still in the progress of being backfilled.

</details>

<details>

<summary><strong>Is my data accurate now?</strong></summary>

Yes. For the vast majority of customers (those using Fulfilled by Amazon), new vs. returning segmentation is fully accurate. For brands that primarily use merchant fulfillment (MFN/FBM), we use an approximation method that is typically within a few percentage points of actual — this is a known limitation of Amazon's current API surface and not specific to Drivepoint.

</details>

<details>

<summary><strong>What if I notice something off in my historical data?</strong></summary>

Reach out to your Drivepoint contact and we'll review it with you. Most accounts will see no material difference, but a small number of customers experienced shifts of a few percentage points.

</details>

Resources:&#x20;

<https://developer-docs.amazon.com/sp-api/docs/tokens-api-use-case-guide#terminology>