Opencart Amazon Connector

 

• Connect multiple Amazon seller accounts with Opencart.
• Set the default quantity and weight of import products.
• Select the default Opencart store for order sync and import products.
• Update import and export products’ prices & quantities on Amazon.
• Select the default Opencart order status of Amazon orders.
• Add custom price/quantity rule for the import/export products.
• Provide the currency exchange rate of the Amazon store.
• The admin can check the feed status of export products.
• Import the Amazon orders according to the date or order ID.
• View the customer data (name, address, email) from the Amazon orders.
• Import the Amazon product using ASIN (Amazon Standard Identification Number).
• Export Opencart Un-mapped products to the Amazon Store through the cron job
• Update Map product stock, price, and product image according to their Sync Source through a cron job.
• Admin can set the images as per the product variations.
• The source code is open for customization.

This extension will work only in the region that’s listed on this page: Click here

How to create/get the required credentials for the Amazon connector module

​ 1. Registering as a developer

You must register as a Selling Partner API developer before you can register your Selling Partner API application.

We will use the following:

• Private seller applications: Applications for sellers that are available only to your organization, and are self-authorized.

To register as a developer (for private seller applications)

1. Sign in to Seller Central using the credentials that you want to associate with your developer account.
2. In the Partner Network menu, click Develop Apps.
   The Developer Central page appears.
3. If you have not yet completed a developer profile for this selling account, click the Proceed to Developer Profile button. Otherwise, click the Your Developer Profile link.
4. Complete the form. In the Data Access section, in the dropdown box.
5. Select My organization sells on Amazon, and I only want to integrate to manage my own business.

Note: If you want to import the buyer information and shipping address with the orders, then you must have access to the customer’s Personally Identifiable Information (PII).

For this, you need Approval for the roles that are required to access buyer information and/or shipping address information. These are:

• Direct-to-consumer shipping. Required to access shipping address information.
• Tax remittance. Required to access buyer information.
• Tax invoicing. Required to access buyer information.

2. Checking the status of your request to register as a developer

After you have submitted your request to register as a developer, Amazon evaluates the information provided and approves or denies your request.

If denied, you can address the reason for the denial and then resubmit your Developer Profile.

The following procedures show you how to check the status of your request to register as a developer, depending on the type of application you want to create.

To check the status of your request (private seller applications)

1. Sign in to Seller Central with the credentials that you used when you registered as a developer.
2. In the Partner Network menu, click Develop Apps.
   The Developer Central page appears.
3. Follow the instructions in the Your developer registration under the review banner. The banner will change to reflect the status of your application.

After we have registered you as a developer, you can create and configure IAM policies and entities. To view your developer information, see Viewing your application information and credentials.

​ 3. Creating and configuring IAM policies and entities

The following steps explain how to create and configure IAM policies and entities with the end goal of creating an IAM role that you provide when you register your application.

In this workflow, you create an IAM user (with an AWS STS policy attached) that assumes an IAM role that has permission to call Selling Partner API.

Steps:

You need an AWS account because the Selling Partner API security model uses AWS authentication credentials.

If you’re not already an AWS customer, you can create a free AWS account. For more information, see AWS Free Tier.

Step 1. Create an AWS account

Step 2. Create an IAM user

You need to create an IAM user to get AWS keys to authenticate calls to the Selling Partner API. We recommend creating a new IAM user exclusively for this purpose.

Use the IAM user to assume the IAM role that you create in Step 4. 

To create an IAM user

1. If you are not already signed in, sign in to the AWS Management Console and open the IAM console at console.aws.amazon.com/iam.
2. In the navigation pane on left, click Users and then click Add user button.
3. Enter a user name for the new user.
4. Select Programmatic access and then click the Next: Permissions button.

5. On the Set Permissions page, accept the defaults and click the Next: Tags. You will set permissions when you create an IAM role.

6. On the Add tags (optional) page, add optional tags if you want them, and then click the Next: Review button.

7. On the Review page, review the choices you have made. You can ignore the This user has no permissions warning.

You will set permissions when you create an IAM role. When you are ready to proceed, click the Create user button.

The AWS access key ID for your new IAM user is displayed.

8. Click Show to view the AWS secret access key. To save the AWS access key, click Download .csv and then save the file to a safe location.

Important:

This is your only opportunity to view or download your AWS secret access key, which you will need to authenticate your calls to the Selling Partner API. Save the AWS access key ID and AWS secret access key in a safe and secure place. 

You will not have access to the AWS access key again after this step. If you lose your AWS secret access key you will need to create a new IAM user with its own new set of keys.

9. Click Close.

10. In the User name column, click your new IAM user and make a note of the User ARN. You will need it in Step 4. Create an IAM role.

11. Save your User ARN. You will need it:

i. In Registering your Application

ii. In Step 4. Create an IAM role.

Note: The created AWS access key ID and AWS secret access will be used for module configurations: Access Key of AWS IAM User, Secret Key of AWS IAM User

​ Step 3. Create an IAM policy

This IAM policy defines permissions to make calls to the Selling Partner API. You will attach it to the IAM role(that you create in Step 4. Create an IAM role) and the IAM user(that you created in the previous step).

Note: If your AWS account leverages AWS Organizations you must ensure that your organization level policy allows access to the Selling Partner API.

For more information, refer to Managing AWS Organizations policies in the AWS documentation.

To create an IAM policy

1. Sign in to the AWS Management Console and open the IAM console at console.aws.amazon.com/iam.

2. In the navigation pane at the left, click Policies.
If this is your first time choosing Policies, the Welcome to Managed Policies page appears. Click Get Started.

3. Click the Create policy button.

4. Click the JSON tab.

5. Paste the following code into the text box, replace the existing code, and then click Review policy.{ “Version”: “2012-10-17”, “Statement”: [ { “Effect”: “Allow”, “Action”: “execute-api:Invoke”, “Resource”: “arn:aws:execute-api:*:*:*” } ] }

6. On the Review policy page, type a Name and a Description (optional) for the policy that you are creating.

7. Review the policy Summary to see the permissions that are granted by your policy, then click the Create policy button.

Your new IAM policy appears in the list.

​ Step 4. Create an IAM role

Now, Create an IAM role that trusts the IAM user that you created in Step 2. Create an IAM user and has permission to call the Selling Partner API.

To create an IAM role

1. If you are not already signed in, sign in to the AWS Management Console and open the IAM console at console.aws.amazon.com/iam.

2. In the navigation pane on left, click Roles and then click Create role button.

3. On the Create role page, click Another AWS account.

4. In the Account ID box, enter the account identifier for the AWS account in which you created your IAM user in Step 2. Create an IAM user, and then click the Next: Permissions button.

5. On the Attach permissions policies page, under the Policy Name, select the policy that you created in Step 3. Create an IAM policy, and then click Next: Tags.

Tip: Click Filter policies and then select Customer managed to narrow your choices.

6. On the Create role page, enter a role name in the Role name box, an optional role description in the Role description box, and then click the Create role button.

7. On the Add tags (optional) page, add optional tags if you want them, and then click the Next: Review button.

8. Under Role name, click the name of your new role.

The Summary page appears

9. Save your role ARN. You will need it:

i. In Step 5. Add an AWS Security Token Service policy to your IAM user.

Step 5. Add an AWS Security Token Service policy to your IAM user

Adding AWS Security Token Service (AWS STS) policy to your IAM user enables you to request temporary AWS access keys that you can use to authenticate your requests to the Selling Partner API.

These credentials expire after a set period of time, helping you to control access to your AWS resources.

1. If you are not already signed in, sign in to the AWS Management Console and open the IAM console at console.aws.amazon.com/iam.

2. In the navigation pane on left, click Users and then click the user that you want to add the AWS STS policy to.

In this workflow, choose the user you created in Step 2. Create an IAM user. You might choose a different IAM user for other use cases.

3. On the Permissions tab, click Add inline policy.

4. On the Create policy page, click Choose a service.

5. Click the STS service.

Tip. Type STS in the search box to narrow your choices.

6. Click the arrow next to Write to expand it.

7. Select AssumeRole.

8. Click the arrow next to Resources to expand it, and then click Add ARN.

9. In the Add ARN(s) dialog box, enter the role ARN from Step 4. Create an IAM role in the Specify ARN for role box, click Add, and then click the Review policy button.

10. On Review policy page, enter name for your policy in the Name box. Review the choices you have made. If you are ready to proceed, click Create policy button.

11. Again choose user you created in Step 2. Create an IAM user. Now, On Permissions tab, click “Add Permissions“.

12. Now, click on “Attach existing policies directly”. Then, select policy that you created in Step3. Create an IAM policy, and then click “Next: Review”.

13. Click on “Add Permissions“.

​ 4. Registering your application

Before you register your application, create and configure your IAM policies and entities. We will register applications for

• Private seller applications: These are seller applications that are available only to your organization, and are self-authorized.

The following procedures show you how to register your application.

To register your application (for private seller applications)

1. Sign in to Seller Central using the credentials that you used to register as a developer.
2. In the Partner Network menu, click Develop Apps.
   The Developer Central page appears.
3. Click the Add new app client button.
   The App registration page appears.
4. Complete the form.

Important: When registering your application, the IAM ARN that you provide must be for the IAM User to which you attached the IAM policy from 

Step 3. Create an IAM policy. Since you register your application using your IAM user, be sure that the IAM policy is attached to it. Otherwise, your calls to the Selling Partner API will fail.

5. Viewing your application information and credentials

After you register your application you can view information about your application, as well as your Login with Amazon (LWA) credentials. Here, we have used :

• Private seller applications: These are seller applications that are available only to your organization, and are self-authorized.

The following procedures show you how to view your application information and credentials, depending on the application type.

To view your application information and credentials (for private seller applications)

1. Sign in to Seller Central using the credentials that you used to register as a developer.
2. In the Partner Network menu, click Develop Apps.
   The Developer Central page displays information about your application(s), including the IAM ARN associated with them.
3. Click View under LWA credentials for the application you want.

Your LWA client identifier and client secret for that application appear. You will need these credentials in module configurations: App Client ID from Seller Central, The corresponding Client Secret

Self authorization

When you create a private application for your own organization you can self-authorize it to access your account information.

Before doing this you must register as a developer and register your application. You can self-authorize your application in draft status; there is no reason to publish a private application.

To self-authorize your application (seller application)

1. Sign in to Seller Central using the credentials that you used to register as a developer.
2. In the Partner Network menu, click Develop Apps.
   The Developer Central page appears.
3. For the application that you want to authorize, click the arrow next to the Edit App button, and then click Authorize.
   The Authorize application page appears.

Note. If your selling partner account is merged with accounts in other regions, you will see an Authorize app button for each of your merged accounts.

4. Click the Authorize app button for each selling partner account that you want your application to access. The Marketplaces column indicates the marketplaces in which an account is active.

A Login with Amazon (LWA) refreshes token appears with every Authorize app button that you click.

Note:

1. Keep this LWA refresh token as this will be used in module configuration: Refresh Token

2. If you click on Authorize app button multiple times, a new refresh token is generated each time. Generating a new refresh token does not invalidate previous refresh tokens.

Export Product To Amazon

The admin can export the OpenCart products to the Amazon shop. 

While adding a new product the admin will see a new tab “Amazon “. Here, the admin can select product type,ID, then they have to select the condition and enter the requried filed.

On the basis of amazon category admin need to select the amazon child category.

The admin needs to provide a genuine Unique Identification Code which will be used while exporting the Adobe Commerce products to the Amazon shop.

After that admin can navigate to Amazon account list then click on the “Export Products To Amazon” option under Amazon Account Information.

In order to export the products to the Amazon store using the Amazon connector, the admin will:

• Select the products that the admin wants to export to the Amazon store.
• Then select the “Export as FBA To Amazon” or “Export as FBM to Amazon” option from the “Action” drop-down list.
• If selected as “Export as FBA To Amazon” then the product will be exported as FBA (Fulfillment by Amazon) product.
• If selected as “Export as FBM To Amazon” then the product will be exported as FBM (Fulfillment by Merchant) product.
• Proceed further by clicking on the “Submit” button which gets visible when selecting any of the options from the “Action” drop-down list. This will navigate the admin to the “Run Profile” page as per the image.

Once the execution is completed, the admin will click on “Back” button to navigate back.

Then, the admin will go to his Amazon seller central account page and navigate to INVENTORY>Manage Inventory.

Here, the admin can check the exported product after 15 minutes because the process of exporting products takes 10-15 minutes to reflect the exported products on the Amazon store.

Lastly, thank you for viewing this blog. If you have any queries regarding this module, please contact us at webkul.uvdesk.com.