Skip to main content

Buyer Email Removal – Impact to Customer Dynamics Reporting (Sellers Only)

On February 11, 2026, Amazon removed access to the BuyerEmail field (including the hashed version) from the Orders API for FBA orders.

Written by Shifty Mix
Updated over a month ago

Last Updated: February 2026
​Status: Temporary reporting limitation – fix in development
​Impacted Users: Amazon Sellers (FBA + partially MFN)
​Not Impacted: Vendors

Summary

On February 11, 2026, Amazon removed access to the BuyerEmail field (including the hashed version) from the Orders API for FBA orders.

MixShift relied on the hashed BuyerEmail value to:

  • Identify New vs. Repeat Customers

  • Calculate Customer Lifetime Value (LTV)

  • Determine First Purchase status

  • Power the Customer Dynamics Report

As a result, orders with purchase dates after February 9, 2026 cannot currently be tied to unique customers, which impacts customer differentiation metrics.

This change affects the entire Amazon analytics ecosystem, not just MixShift.

What Changed?

On February 9, Amazon notified developers:

“Starting February 11, 2026, you won't be able to access BuyerEmail through the Orders API v0 for Fulfillment by Amazon (FBA) orders…”

On February 11, BuyerEmail values (including hashed identifiers) stopped being returned entirely via the Orders API.

There was no extended deprecation window in the SP-API documentation.

What This Means for Your Data

For Seller accounts:

1️⃣ Orders After February 9, 2026

In the following tables:

  • mws_orders_list

  • mws_orders_metric

You will observe:

  • IsRepeatCustomer = 0

  • IsFirstPurchase = 0

  • All customer counts appearing as "New"

  • LTV calculations becoming inaccurate/incomplete for post-2/9 data

Because we cannot uniquely identify customers, the system cannot determine whether a customer has purchased previously.

2️⃣ Customer Dynamics Report Impact

The Customer Dynamics Report will:

  • Overstate New Customers

  • Understate Repeat Customers

  • Understate Lifetime Value

  • Show distorted cohort metrics for purchase dates after February 9

Historical data prior to February 9 remains accurate and unaffected.

Why This Matters

BuyerEmail (hashed) was the core linking key that allowed us to:

  • Build customer cohorts

  • Calculate repeat purchase behavior

  • Model LTV

  • Perform purchase path analysis

  • Estimate acquisition efficiency

Without a unique customer identifier, these analytics cannot be calculated in their original form.

Current Status

We have confirmed:

  • The Messaging API does NOT provide access to BuyerEmail

  • There may be a direct SP-API replacement

  • This is an Amazon platform-level change

🚧 Fix in Progress

We have identified a potential alternative:

FBA Shipped Orders Report

The FBA Shipped Orders report includes a Buyer Email value.

However:

  • The email is only available once an order is shipped

  • Merchant Fulfilled (MFN) orders may not provide coverage

  • There will be timing differences between purchase date and shipment date

  • Temporary overstatement of “new customers” may occur until shipment data is received

What This Means for Reporting During Transition

Until our new pipeline is implemented:

  • New customers will be overstated

  • Repeat customers will be understated

  • LTV will be artificially low

  • Merchant Fulfilled repeat behavior may be underrepresented

This is a temporary state.

Will Data Be Restated?

Yes.

Once the new data source is integrated and validated:

  • We expect to restate February 9 onward

  • Customer flags (New vs Repeat)

  • LTV calculations

  • First Purchase indicators

Restatement will depend on final validation and completeness of the new dataset.

Longer-Term Direction

In parallel, we are exploring:

  • AMC Retail dataset integration

  • Brand Analytics NTB metrics (if API access becomes available)

  • Pattern-based customer modeling (non-identifier driven)

  • Alternative customer value frameworks not reliant on direct identifiers

If your organization already subscribes to AMC Retail datasets, contact us to explore integration options.

What You Should Do

1️⃣ Inform Internal Teams & Clients

If you rely on Customer Dynamics metrics, proactively communicate that:

  • New customer counts will be inflated post-Feb 9

  • LTV values will be incomplete during this period

2️⃣ Continue Using Orders Data Normally

All other order metrics remain accurate:

  • Revenue

  • Units

  • Conversion metrics

  • Product performance

  • Operational reporting

Only customer differentiation metrics are affected.

3️⃣ Optional: Schedule a Discussion

If your workflows heavily depend on repeat behavior or LTV modeling, you may schedule a call with our team to review impact and alternatives.

Frequently Asked Questions

Is historical data affected?

No. Data prior to February 9, 2026 remains correct.

Is this a MixShift issue?

No. This is an Amazon API change affecting all analytics providers.

Will the legacy Customer Dynamics report be removed?

The original report will be deprecated with MixShift 2.0 after migration, and any new logic will live in the updated reporting framework.

Is there a risk Amazon removes the alternative source?

There is always platform risk. We are actively monitoring.

Bottom Line

This is an Amazon-driven change that temporarily limits customer-level reporting for Sellers.

We are actively rebuilding our data pipeline to restore functionality and expect to provide a restated and stabilized solution once implementation is complete.

We will continue providing updates here as progress is made.

Did this answer your question?