Connect Amazon Seller Central to Klaviyo: A Guide

Last verified: June 2026

If you've ever tried to connect Amazon Seller Central to Klaviyo, you've probably hit a wall pretty quickly. The integration that used to exist is gone. Amazon pulled it, Klaviyo deprecated it, and sellers were left piecing together workarounds. There are real, working methods in 2026 — they just require more deliberate setup than a one-click OAuth flow.

Why bother? Because Amazon keeps your customer relationships locked inside its own ecosystem. If you're running post-purchase flows, review request sequences, or abandoned checkout campaigns for your Buy with Prime storefront, Klaviyo is where that logic lives for most brands. Amazon's own retention tools don't come close. For brands managing operations across multiple channels, pairing this with a solid cross-border e-commerce stack is worth the effort.

This guide covers four methods — native app, connector tool, direct API, and manual export/import — with honest assessments of when each one makes sense. We'll also cover Amazon's communication rules, because getting the data into Klaviyo is only half the job.

Before you start

• Active Amazon Seller Central Professional account
• Admin access to your Klaviyo account
• Admin access to your Amazon Buy with Prime account (required for the native app method)
• Subscription to a connector tool like Zapier (if using that method)

Methods at a glance

Method 1: Buy with Prime native app (recommended)

This is the closest thing to a real, supported integration between Amazon and Klaviyo. The Klaviyo for Buy with Prime integration syncs order and customer data — including abandoned checkouts — directly into Klaviyo as events. It's the only method that gives you reliable customer email data, because it operates within Amazon's permitted data-sharing framework.

1. Log in to your Amazon Buy with Prime merchant console at buywithprime.amazon.com and confirm your account registration is complete. Incomplete registration is a known cause of connection failures — resolve any pending tasks before proceeding.
2. Navigate to the Integrations section within the Buy with Prime console and find the Klaviyo app listing, or go directly to the Amazon Buy with Prime Klaviyo app page.
3. Click Connect and authenticate with your Klaviyo admin credentials when prompted.
4. Authorise the data permissions — you're granting Buy with Prime permission to push order events, customer data, and abandoned checkout events to Klaviyo.
5. Select your target Klaviyo account if you manage multiple workspaces, then confirm the connection.
6. Return to Klaviyo and navigate to Integrations to verify the Buy with Prime integration shows as active.
7. Place a test order through your Buy with Prime storefront and confirm the corresponding event appears in Klaviyo's activity feed within a few minutes.

Once connected, Klaviyo receives a defined set of event types including Placed Order, Ordered Product, and Started Checkout. That's enough to build post-purchase flows, abandonment sequences, and product-specific automations. One thing to note: this integration doesn't backfill historical data. It only captures events from the moment you connect onward.

Method 2: Connector tool (e.g. Zapier)

Not on Buy with Prime? A connector platform like Zapier can bridge Amazon Seller Central order events to Klaviyo. You're working with order-level data here — don't expect customer email addresses to flow through, because Amazon's PII restrictions block that in standard Seller Central data exports. Think of this as triggering Klaviyo events based on order activity, not building a full customer profile.

1. Log in to your Zapier account and click Create Zap.
2. Set Amazon Seller Central as the trigger app and choose a trigger event — "New Order" is the most common starting point.
3. Connect your Seller Central account by entering your MWS credentials or authorising via SP-API when prompted by Zapier.
4. Test the trigger by pulling a recent order and confirming the data fields Zapier captures.
5. Add Klaviyo as the action app and select "Track Event" or "Add Subscriber to List" as the action type.
6. Map the Amazon order fields — order ID, product ASIN, fulfilment status — to the corresponding Klaviyo event properties.
7. Turn on the Zap and monitor the task history for the first few runs to confirm events are posting correctly.

A paid tier on your connector tool is required for multi-step Zaps and anything beyond basic triggers. Factor that into your stack costs. For brands thinking through their broader operations tooling, our EU expansion operations stack guide covers how connector tools fit into a larger architecture.

Method 3: Custom API integration

For high-volume sellers who want full control, building a custom integration using Amazon's Selling Partner API (SP-API) and Klaviyo's Track API is the most flexible approach. It's also the most work. Honestly, most brands underestimate the maintenance burden — Amazon API changes become your problem to fix, permanently. You're realistically looking at meaningful developer time to build, test, and keep it running, not a one-sprint job you hand off and forget.

1. Register your application in the Amazon Developer Console and request SP-API access for the relevant data roles (Orders, Notifications).
2. Set up SP-API Notifications using the Notifications API to receive push events when order status changes — this is more efficient than polling.
3. Generate a Klaviyo private API key from your Klaviyo account settings under API Keys.
4. Build your middleware service — a small application (AWS Lambda works well) that receives SP-API notification payloads and transforms them into Klaviyo Track API calls.
5. Map the event schema: order events should POST to Klaviyo's /api/events/ endpoint with properties matching your Klaviyo flow triggers.
6. Implement error handling and retry logic — API rate limits on both sides will cause dropped events without it.
7. Test end-to-end with sandbox orders before pointing at production credentials.
8. Monitor your middleware logs for the first two weeks in production to catch edge cases.

The upside is precision — you define exactly what gets sent and when. If your team already manages integrations like a Shopify to Dynamics 365 connection, the architecture will feel familiar.

Method 4: Manual CSV export/import

This isn't a real integration. But it has its place — testing Klaviyo flow logic before you've built the live connection, or running a one-off campaign against a specific order cohort.

1. Open Amazon Seller Central and navigate to Reports → Business Reports or Orders → Order Reports.
2. Generate an order report for your chosen date range and download the CSV.
3. Review the columns — note that directly identifiable customer PII (emails, full names) won't be present in standard order exports due to Amazon's data restrictions.
4. Clean the CSV to match Klaviyo's import format: at minimum you need an identifier column and any event properties you want to use.
5. Log in to Klaviyo and go to Lists & Segments → Create List → Import Contacts.
6. Upload your cleaned CSV and map columns to Klaviyo profile properties.
7. Confirm the import and spot-check a few profiles to verify the data landed correctly.

Run this more than once a month and you'll spend more time on it than any of the other methods cost to set up. Use it once, automate it next.

Common errors and how to fix them

The Klaviyo Amazon integration no longer works / data stopped syncing

The direct integration between Amazon Seller Central and Klaviyo was discontinued. Order and customer data no longer sync automatically through that legacy connection. Switch to one of the four methods above — the Buy with Prime native app is the most straightforward replacement for sellers who qualify.

Buy with Prime connection fails or won't authenticate

The most common cause is an incomplete Amazon Buy with Prime account registration. Log in to your Buy with Prime console and check for any pending tasks or verification steps flagged in your account dashboard. Resolve all outstanding items before attempting to reconnect. Also confirm you're using admin-level credentials for both platforms.

Return and cancellation events aren't appearing in Klaviyo

The Buy with Prime integration doesn't currently sync return or cancellation events to Klaviyo. If your flows depend on these triggers, you'll need to handle them through a separate mechanism — a connector tool or custom API call that listens for those specific order status changes.

No historical data after connecting Buy with Prime

The Buy with Prime integration doesn't backfill historical data. Only events that occur after the connection is established will appear in Klaviyo. If you need historical context for segmentation, a one-time manual import of order data (minus PII) is the only workaround.

Customer emails missing from synced data

Amazon's PII policy prevents standard Seller Central data exports from including customer email addresses for use in marketing platforms. The Buy with Prime integration is the exception — it provides more complete customer profile data within Amazon's permitted framework. Standard connector tool integrations pulling from Seller Central order reports won't include emails.

Frequently Asked Questions

Can you connect Amazon Seller Central to Klaviyo?

Not directly — Amazon deprecated the native Klaviyo integration for Seller Central. You can connect the two platforms using Amazon's Buy with Prime app (if you use that programme), a connector tool like Zapier, or a custom API build. Each method has different data access and setup requirements.

How do I import Amazon contacts into Klaviyo?

Amazon's PII policy prevents sellers from exporting customer contact lists — including email addresses — for bulk import into marketing platforms. You can import order-level data (ASINs, order IDs, fulfilment status) via CSV, but customer emails are restricted. The Buy with Prime integration is the only supported path to getting customer email data into Klaviyo from Amazon.

How do I automate review requests for Amazon orders?

Amazon's Communication Guidelines permit proactive messages requesting product reviews or seller feedback. You can trigger a Klaviyo flow on the Placed Order event from your Buy with Prime integration and send a post-purchase review request — but the message must comply with Amazon's rules. No promotional content, no external links, and the request must relate to the specific order.

Does Klaviyo have an Amazon integration?

Klaviyo has a supported integration specifically with Amazon's Buy with Prime programme, which syncs order events, customer data, and abandoned checkout data. There's no direct integration with standard Amazon Seller Central — that connection was discontinued. Sellers not on Buy with Prime need a third-party connector or a custom API solution.

Amazon's communication policies: what you can and can't do

Here's the part most brands skim and later regret. Amazon takes communication violations seriously — account suspension is a real outcome, not a theoretical one. Worth understanding before you build a single flow.

Amazon's Communication Guidelines permit proactive messages for a narrow set of purposes: completing the order, requesting reviews or feedback, or providing essential order information. Marketing and promotional content — including coupons or discount codes — is not permitted in messages to Amazon customers. Directing customers away from Amazon via external links is also forbidden, unless those links are strictly necessary to complete the order.

And then there's the PII angle. Amazon's data policy restricts storage of customer personally identifiable information. According to Amazon's SP-API data protection policy, PII obtained through the Buy with Prime integration or SP-API may only be retained for as long as needed to fulfil the order, with a 30-day post-fulfilment window in most cases (verify the current version of Amazon's data protection requirements directly, as these terms are updated periodically). In practice, your Klaviyo flows need explicit suppression logic to stop contacting customers once that window closes — don't assume the integration handles this for you.

Keep your Amazon-triggered Klaviyo flows transactional or review-focused. Not promotional. Tightly scoped. If you're building out a broader post-purchase architecture for a multi-channel brand, the sustainable fulfilment tech stack guide covers how these data flows fit into the wider picture. And for brands managing Amazon alongside other sales channels, pairing this with good customer support tooling — see our guide on how to connect Gorgias to Amazon — ties together the post-purchase side without running afoul of messaging rules.

One last thing: Amazon data should not be used to build retargeting audiences or seed lookalike lists on ad platforms. That's outside the permitted use case for data obtained through the Buy with Prime integration or SP-API.

If you're already on Buy with Prime, the native app is the clear answer — lower maintenance, supported by both platforms, and the only path to reliable customer email data. On standard Seller Central and want order-event triggers without writing code? A connector tool gets you there with moderate setup. Custom API is for teams with developer resource who need precise control at volume. Manual CSV import is fine for a single test run — automate it as soon as you can. The decision mostly comes down to your technical capacity and how central Klaviyo is to your retention stack.