Connect Gorgias to Amazon: A Step-by-Step Guide

Last verified: June 2026

Amazon's Buyer-Seller Messaging system works. It is not, however, a pleasant place to spend your day — especially when you're also handling Shopify support, returns emails, and the occasional warehouse fire drill. Every channel in a separate tab is a slow way to run customer service. And on Amazon specifically, slowness has real consequences: miss the 24-hour response window and your seller account health takes a hit.

Gorgias is already the helpdesk of choice for a lot of Shopify-first brands, so the natural question is: can you pull Amazon messages into it too? Yes — you can, but not with a simple one-click native connection. Amazon doesn't play nicely with direct helpdesk integrations, which means you need a middleware connector sitting between your Seller Central account and Gorgias. This guide walks you through every method, honest about the tradeoffs.

If you're building out a broader operations stack — combining support tooling with accounting, inventory, and marketplace expansion infrastructure — getting your support layer sorted first is the right call. Everything downstream runs better when your team isn't drowning in message queues.

Before you start

• Active Amazon Seller Central account
• Gorgias account (any paid tier that supports integrations)
• Subscription to a third-party connector tool (e.g., ChannelReply, Commercium)
• Admin access to both your Gorgias workspace and your Amazon Seller Central account
• Your Amazon Seller Central store region noted (US, EU, UK) — some connector tools require you to connect each region separately

Methods at a glance

Method 1: connector tool (ChannelReply or Commercium)

This is the right route for the vast majority of sellers. ChannelReply and Commercium act as middleware — they pull your Amazon Buyer-Seller messages, attach order metadata, and push everything into Gorgias as structured tickets. The connector also handles reply routing back to Amazon, so your agents never need to leave Gorgias. Both require a paid subscription; neither offers a meaningful free tier for production use.

1. Sign up for your chosen connector tool (ChannelReply or Commercium) and complete their onboarding flow. You'll be asked to select Gorgias as your helpdesk during setup.
2. Authorise the connector to access your Gorgias account — click the OAuth prompt when it appears, log in to Gorgias if needed, and grant the requested permissions. You'll be redirected back to the connector dashboard with a "Gorgias connected" confirmation.
3. Connect your Amazon Seller Central account inside the connector dashboard. This typically means clicking "Add marketplace" → "Amazon", then authorising via Amazon's SP-API flow. If you sell across multiple regions (e.g., Amazon US and Amazon UK), add each region as a separate connection.
4. Configure your message routing rules in the connector — set which Amazon message types should create tickets in Gorgias (buyer messages, order notifications, A-to-z claim alerts). A test ticket should appear in your Gorgias inbox within a few minutes.
5. Verify that order data is appearing in the ticket sidebar in Gorgias. Open the test ticket and check the right-hand sidebar — you should see the buyer's order ID, item purchased, order status, and tracking information pulled through automatically.
6. Send a test reply from Gorgias and confirm it lands in Seller Central's Buyer-Seller Messaging thread. Log into Seller Central in a separate tab and check the thread manually. Do this before it affects a real customer.

For the exact steps Gorgias documents on their end, refer to the official Gorgias integration guide.

Method 2: native app (Gorgias App Store)

Gorgias maintains an App Store where vetted integration partners publish connectors. Some connector tools — including ChannelReply — publish a listed app here, which means you can initiate the connection from inside Gorgias rather than starting on the connector tool's own website. The underlying technology is identical; you're just starting the flow from a different place. This suits teams who prefer to manage all their integrations from one dashboard.

1. Log in to your Gorgias admin panel and navigate to Settings → App Store.
2. Search for "Amazon" in the App Store search bar. You'll see available marketplace connectors listed — look for ChannelReply or any listed Amazon integration partner.
3. Click "Install" on the connector you want. A permissions prompt will appear outlining what data the app will access in your Gorgias workspace.
4. Accept the permissions and complete the OAuth handshake. You'll be redirected to the connector tool's setup flow.
5. Follow steps 3–6 from Method 1 to connect your Amazon Seller Central account, configure message routing, and verify the integration end-to-end.

And that's genuinely all that's different. The App Store method is really just an alternative entry point into the same connector-tool setup. Don't overthink it.

Method 3: direct API

Amazon exposes a Selling Partner API (SP-API) that includes Messaging endpoints, and Gorgias has its own REST API. In theory, you could build a custom integration that pulls messages from Amazon's SP-API and creates tickets in Gorgias programmatically. In practice, this is a serious engineering undertaking — Amazon's SP-API access requires going through an application approval process, and you'd be responsible for handling rate limits, message threading, reply routing, and failure states yourself. When Amazon changes their API (and they do), your integration breaks. Maintenance burden is high.

1. Apply for SP-API access via the Amazon Developer Console. Complete the use case questionnaire and wait for Amazon's approval — this can take several business days.
2. Register your application and generate your SP-API credentials (Client ID, Client Secret, Refresh Token). Store these securely; you'll need them in your integration code.
3. Build a polling or webhook-based listener that calls Amazon's getMessages endpoint on a schedule to retrieve new buyer messages.
4. Transform the Amazon message payload into a Gorgias-compatible format — map buyer email (or Amazon's anonymised address), order ID, and message body to the appropriate Gorgias ticket fields.
5. POST the transformed payload to the Gorgias API (POST /api/tickets) to create a new ticket. Include the order data as custom fields or sidebar metadata.
6. Build a reply listener in Gorgias (via webhooks on ticket updates) that captures agent replies and POSTs them back to Amazon's sendMessage endpoint.
7. Test end-to-end with a real Amazon buyer message and confirm both directions work — message in, reply out.

Unless you have a developer who knows both APIs well and can maintain the integration over time, use Method 1. The connector tools have already solved these problems and handle API version changes for you.

Common errors and how to fix them

Replies sent from Gorgias don't appear in Amazon Seller Central

This is the most common complaint, and it usually comes down to reply routing misconfiguration in the connector tool. Open your connector dashboard, find the reply routing settings, and confirm the outbound path is mapped correctly to your Amazon account. Send a test reply, then check Seller Central directly. If it still doesn't appear, raise a ticket with your connector tool's support team — not Gorgias support, since this is a partner integration. Also check that the buyer's Amazon anonymised email address is being used as the reply-to, not a real email address.

Initial messages don't show full customer or order information

When a brand-new buyer message arrives, some connector tools need a moment to resolve the order data against Amazon's API before populating the ticket sidebar. If you open a ticket immediately and the sidebar looks empty, wait 30–60 seconds and refresh. If order data never appears, check whether your Amazon SP-API connection is still authorised — tokens can expire, and a re-authorisation in the connector dashboard usually fixes it immediately.

Only buyer messages appear — not your own previous replies

This is an Amazon API limitation, not a bug in your setup. Amazon's messaging API surfaces buyer messages to third-party tools, but seller replies sent directly from Seller Central before you set up the integration won't be backfilled. Going forward, once the integration is live, replies sent through Gorgias will appear in both places. For historical threads, check Seller Central directly.

The integration requires a paid third-party subscription

Not an error — but a surprise for sellers who expected a free native connection. There's no way around this currently. Amazon doesn't expose a direct helpdesk webhook that Gorgias can consume without middleware. Budget for a connector tool subscription as a line item in your support stack costs. Given the alternative is a dedicated person manually checking Seller Central all day, the maths almost always work out.

Best practices for managing Amazon support in Gorgias

Once the integration is running, a few habits will make a real difference to how efficiently your team handles Amazon tickets.

Tag Amazon tickets immediately. Set up a Gorgias rule that auto-applies a tag (e.g., amazon, amazon-us, amazon-uk) to every ticket that comes in through the connector. This keeps filtering and reporting clean from day one, and means macros can be scoped to fire only on Amazon tickets.

Build macros for your top five Amazon message types. For most sellers, those are: order status enquiry, where's my refund, item not received, wrong item sent, and A-to-z claim notification. A well-built macro pre-fills the order ID and tracking number from sidebar variables — your agent clicks once and the response is 90% done. Every bit of order data the connector pulls into Gorgias can be used as a placeholder in macros.

Watch the 24-hour clock. Amazon's response time requirement is real and it affects your account health. Set up a Gorgias rule that escalates or reassigns any Amazon ticket that's been open for 18 hours without a reply — that gives you a 6-hour buffer before the deadline hits.

Don't try to resolve A-to-z claims from Gorgias. Connector tools like ChannelReply can deliver A-to-z claim notifications to your Gorgias inbox and include a direct link back to Seller Central, but the resolution process itself has to happen in Seller Central. Treat those tickets as alerts, not resolvable support issues.

Automating Amazon support with Gorgias rules and macros

The real leverage from this integration is automation. Once Amazon messages are in Gorgias as structured tickets, the full rules engine applies — the same tools you'd use for Shopify support. A few practical examples.

Auto-respond to order status enquiries. Build a rule that fires when a ticket contains the words "where is my order" or "tracking" and the tag amazon is present. The rule sends a macro that pulls in the tracking number and carrier from the sidebar, then closes the ticket if no reply comes back within 48 hours. For a seller handling 200 orders a day, this deflects a significant chunk of first-contact messages without any agent involvement.

Prioritise feedback and review requests. Amazon sends notifications when a buyer leaves negative feedback. Tag these with amazon-feedback and assign them immediately to your most experienced agent — the faster you respond, the better your chance of resolution before it compounds.

Use Gorgias statistics to track your Amazon response time. Filter your Gorgias reports by the amazon tag and monitor first response time as a standalone metric. If it creeps above 10 hours on average, you've got a staffing or process problem to fix before Amazon notices.

For a broader look at how support tooling fits into your overall operations setup, the 7-figure DTC operations stack breakdown is worth reading alongside this guide.

Frequently asked questions

Can Gorgias integrate with Amazon?

Yes — but it requires a third-party connector tool such as ChannelReply or Commercium. There's no native, direct connection between the two platforms. Once a connector is in place, Amazon Buyer-Seller messages flow into Gorgias as tickets with order data attached.

How do I manage Amazon messages in Gorgias?

Connect your Amazon Seller Central account to Gorgias via a middleware connector tool (see Method 1 above). After setup, all incoming buyer messages appear as tickets in your Gorgias inbox, and replies you send from Gorgias are routed back to the buyer through Amazon's messaging system. Use tags and views to keep Amazon tickets separated from your other channels.

What are the benefits of connecting Amazon to a helpdesk like Gorgias?

Centralisation and speed, mainly. Instead of monitoring Seller Central separately, your team handles Amazon messages alongside every other support channel in one place. Order context — status, tracking, customer history — appears in the ticket sidebar, so agents don't need to look anything up. And because Amazon's 24-hour response requirement isn't negotiable, having Amazon tickets in a managed helpdesk queue with automation and escalation rules makes it much easier to stay on the right side of it.

How can I automate customer service for my Amazon store?

Once Amazon messages are flowing into Gorgias via a connector tool, you can use Gorgias's built-in rules engine and macros to automate responses. Set up rules to auto-reply to common enquiry types (order status, tracking), auto-tag tickets by issue, and escalate anything approaching Amazon's 24-hour deadline. Macros can use Amazon order data as dynamic placeholders, so a single click sends a fully personalised response without any manual data lookup.

Which method should you pick?

For almost every seller reading this: Method 1 or Method 2. They're effectively the same thing with different starting points. The connector tool handles the hard stuff — SP-API authorisation, message threading, reply routing — and you're up and running in under an hour.

Method 3, the direct API build, only makes sense if you have a development team, a compelling reason the connector tools can't satisfy, and the appetite to maintain custom integration code indefinitely. That's a narrow use case.

Get the connector running, build your macros, and spend the time you save somewhere that actually grows the business. If you're expanding into additional marketplaces at the same time, the right listing and operations tooling pairs well with a properly set up support stack.