Amazon Vendor Integration Guide

Integrate your Amazon Vendor Central account with Helm to automate order ingestion, sync stock availability and streamline fulfilment directly with Amazon’s retail systems

What is Amazon Vendor Central

Amazon Vendor Central is Amazon’s first-party wholesale programme, where you sell your products directly to Amazon, which then sells them to customers

Unlike Amazon Seller Central (third-party), Vendor Central operates on a purchase order basis - Amazon issues POs to you, and you fulfil them to Amazon’s warehouses

Connecting Vendor Central to Helm allows for centralised purchase order management, inventory syncing and streamlined logistics reporting

PROS ✅

CONS ❌

Trusted first-party relationship with Amazon

Requires approval to become a Vendor, invitation only

Automated purchase order and fulfilment workflows

API credentials must be issued via Amazon Selling Partner (SP) API

Access to Amazon marketing tools and retail analytics

Vendor terms and payment schedules are controlled by Amazon

Step-by-Step Setup

To integrate Amazon Vendor with Helm

  1. Log in to Amazon Vendor Central
    Go to vendorcentral.amazon.com

  2. Create an Amazon SP Developer Profile
    Visit the Amazon Developer Console and register your app to obtain API credentials

  3. Generate API Credentials
    From the Developer Console, generate:

    • Client ID

    • Client Secret

    • Refresh Token

    • AWS Access Key and Secret Key

    • Role ARN

  4. Log in to Helm
    Go to Settings → My Store

  5. Add New Sales Channel
    Click Add New Sales Channel and select Amazon Vendor from the list

  6. Enter Your Credentials

FIELD

DESCRIPTION

Sales Channel Name

e.g. Amazon Vendor UK

Sales Channel Logo

Upload the Amazon logo or your custom icon

Client ID

From your Amazon Developer Console

Client Secret

Provided when you register the application

Refresh Token

Authorised user token for secure API access

AWS Access Key

Your Amazon Web Services access key

AWS Secret Key

Your Amazon Web Services secret key

Role ARN

The Role ARN used to authenticate your IAM role

  1. Click Continue

Interaction Settings

Configure how Helm communicates with your Amazon Vendor account

INTERACTION SETTINGS

DESCRIPTION

Sync Inventory

Import catalogue data from Amazon where applicable

Sync Stock Levels

Reflect availability for purchase orders issued by Amazon

Use Channel Names

Display Amazon product titles within Helm orders and stock reports

Max Stock Levels

Limit how much stock Helm presents to Amazon for potential POs

Stock Buffer

Reserve quantity to reduce overselling on replenishment cycles

Auto Merge Orders

Merge similar purchase orders for bulk handling or logistics grouping

Order Importing Type

Choose the start time/date for importing POs into Helm

Final Steps

  • Click Save once all settings are configured

  • Set the channel to Is Active at the top of the screen

Your Amazon Vendor integration is now live - and you’re ready to Take the Helm

Common Issues

ISSUE

SOLUTION

Invalid API Credentials

Ensure all values match exactly and the IAM role has the correct permissions

POs Not Importing

Check that the integration is active and that POs are being generated in Vendor Central

Stock Not Syncing

Confirm SKU alignment and interaction settings within Helm

API Access Denied

Recheck your SP API app scopes, role trust relationships and AWS configuration

Why Not To Merge Orders for This Integration?

We normally allow order merging so that multiple orders from the same customer can be combined into a single shipment. This is convenient for packing and can reduce shipping costs, because instead of sending several parcels, you dispatch just one consignment with one label.

However, marketplace channels such as Amazon, TikTok and Temu must not have their orders merged. These platforms track each individual order and shipment very strictly. When you merge their orders:

  • The tracking information no longer maps cleanly to each original order on the marketplace

  • This can create defects in your Valid Tracking Rate (VTR) and similar performance metrics

  • Repeated issues of this kind can trigger serious account-level consequences, including suspension of your store for around 10–15 weeks

Because of this, we actively prevent users from merging orders originating from Amazon, TikTok and Temu. This safeguard is there to protect your account health, your tracking performance, and ultimately your revenue; by blocking merges on these specific channels, we help you avoid accidental policy violations and the very real risk of your store being shut down

If you experience issues with label generation, pickup scheduling or syncing, contact Helm Support