Amazon SmartConnect - SellerFlex

Integration Overview

  • Amazon SmartConnect is a platform where the amazon APIs are hosted which can be integrated with any WMS/OMS system for order fulfilments.

  • Amazon has multiple fulfilment programs to suit different needs of different sellers. The different types of programs are as below:

    • FBA: Sellers send products to Amazon Fulfilment Centres. Amazon stores products,
      takes care of both forward leg- packing, shipping, and delivering the product to the
      customer's doorstep and return leg of the orders.

    • Seller Flex: Sellers will have to manage storage and shipping in their own warehouse
      and dedicate inventory for selling on Amazon through Seller Flex site.

    • MFN - Self Ship: Sellers to store and pack their products. Sellers can choose to deliver
      products to the customer on their own by using a third-party carrier or their own
      delivery associates.

    • MFN - Easy Ship: Seller to store and pack their products and Amazon will deliver it
      customers.

  • Geography- India

Workflow Breakdown

 

Workflow

Description

Supported

Remarks

Workflow

Description

Supported

Remarks

Inventory Sync

Update inventory of a single SKU on marketplace

Yes

Support for Bulk inventory push is not available with Amazon

Forward Orders Sync

  1. Fetch all the orders based on status ACCEPTED and on time range filter.

  2. Amazon pushes order create event to Increff system

Yes

Amazon pushes notifications and we save the notifications and asynchronously pull these orders from amazon

Routing & Splitting

Split the order across locations in OMNI

Yes

This is done only for the self ship orders as amazon doesn’t support multi warehousing for self ship

Forward Order Acknowledgement

Change order status to CONFIRMED on amazon

Yes

NA

Shipment

Multiple calls are made to Amazon in sequence:

  1. Create package: to create package on amazon

  2. Retrieve shipping options: To fetch the pick up slots from amazon

  3. Generate ship label: To generate ship label on amazon

  4. Generate invoice: To generate invoice on amazon

Yes

  1. All these calls have to be done in sequence

  2. In create package, the dimensions received from amazon is picked and if it is not in compliance with amazon’s dimension threshold(L,B<70 cm;H<45 cm; W>=11 gm) then we provide option to override(either from UI or from the master’s data uploaded)

  3. In case of self ship, tracking details are generated internally through the integration with logistic and then is passed back to amazon

Invoicing

To fetch the invoice and ship label from amazon

Yes

NA

Manifest

No call to amazon

-

Manifest limit 100

Handover

To mark orders as SHIPPED on amazon

Yes

  1. Handover limit 100

  2. This call is made only for self ship orders

Forward order update

To update order attributes

Yes

  1. Order status update when any update event comes from amazon

  2. Order SLA update when the trans capacity at amazon is breached and trans capacity event comes

Forward Order Customer Cancellation

  1. Fetch all the orders based on status CANCELLED and on time filter.

  2. Amazon pushes order create event

Yes

Amazon pushes notifications and we save and process the notifications

Forward Order Seller Cancellation

To cancel orders on amazon

Yes

NA

Replacement/Exchange Order Sync

To place a replacement of an order

Yes

  1. Replacement orders are created as separate forward orders with selling price as 1.

  2. The forward order code is added as channel meta data when the order is created in OMNI

Return Order Sync

  1. Fetch all the orders based on status CREATED and on time filter.

  2. Amazon pushes order create event

Yes

 

Return processed notification updates

To sync the return order updates

Yes

Amazon sends return update events which get synced to OMNI

Return Order Cancellation

To sync return cancellation from amazon

Yes

Amazon sends return cancellation events which get synced to OMNI

Additional Information

Workflow

API Rate Limit

Batch size of API request (if supported)

Frequency (as per standard configuration)

Workflow

API Rate Limit

Batch size of API request (if supported)

Frequency (as per standard configuration)

Inventory

6 API calls / second / merchant

1 SKU

2 sec

Get order status

6 API calls / second / merchant

1 Order

5 sec

Visualizing the Flow

Marketplace-Specific Details

Property

Value

Property

Value

Return Reasons

  • Customer return due to mismatch in size, colour and so on

  • RTO in case of three trials by the delivery partner

Cancellation Reasons

  • SELLER_REJECTED: Cancellation initiated by seller.

  • MARKETPLACE_CANCELLATION: Cancellation initiated by marketplace.

  • SYSTEM_CANCELLED: Cancellation initiated by Yojaka.

Replacement Orders

The replacement orders are placed as new outward orders with zero value and pulled in the system. For mapping it to the forward orders, we save the forward order code in the order meta data of the replacement order.

Cancellation Support

  • Customer cancellation: Supported till the order is marked as SHIPPED. In case of self ship, the order gets marked as shipped when the generate ship label call is made whereas in other models when the DA scans the courier during handover.

  • Seller cancellation: Supported till the order is invoiced

API Performance

Example: Avg time it takes to update inventory for 1000 SKUs from Increff to Marketplace.

Channel Onboarding Details

Onboarding Steps

Step 1: Generating Refresh Token and API credentials

In order to generate the refresh token, authentication code is needed for which the client needs to do a few steps:

  1. Seller need to register both on amazon seller central and complete the node registeration process for the location (warehouse/store) from where inventory is saleable. For this seller needs to reach out to the Amazon Program Manager with help of their Category account manager

  2. Once the Node onboarding is completed, node details will be shared with seller from the Program manager. These details are required to be shared with the Integrator (OMS/WMS) team

  3. The merchant_id and ARN of an AWS Key Management Service customer-managed key needs to be shared. This is received by the seller in a mail from amazon after registering.
    Merchant id can also be found on the seller account by below steps:

    1. Login to your seller account

    2. Select Settings, then Account Info on the upper right of the screen

    3. Under Business Information select "Your Merchant Token"

    4. Merchant Token will act as the Seller ID

  4. Use the below URL after changing the client_id: https://www.amazon.com/ap/oa?client_id=amzn1.application-oa2-client.e1f58c607e32437d884d05a7b8ff1b30&scope=smartconnect::inventories smartconnect::orders&response_type=code&redirect_uri=https://assure-proxy.increff.com/amazon-yojaka/swagger-ui.html

    1. The URL will first redirect to amazon seller panel where after giving access will be redirected to a different URL.

    2. This url has to be shared so that the code present in it can be used to generate the refresh token.

Information required from Brand/Seller for Channel Onboarding in Increff

Configuration Parameter

Remarks

Configuration Parameter

Remarks

merchant_id

Will be generated once seller registeration is completed on Amazon

ARN

Will be generated once seller registeration is completed on Amazon

KMS key

Will be generated once seller registeration is completed on Amazon

Code/URL

Will be generated once seller registeration is completed on Amazon

location code

Will be generated once seller registeration is completed on Amazon

Step 2: Listing Mapping

Seller can create product listings for Amazon channels in below format in Increff systems

clientSkuId

channelSerialNo

channelSkuId

Marketplace

EAN_CODE

ASINCode

Merchant SKU

Amazon SF SmartConnect

Estimated Timeline

3-4 Business Days

From the time the node details are shared with Increff Customer Success team , the necessary configurations takes a max. of 3-4 Business days from Increff’s end.

Additional Resources

For further queries and support, please reach out to the Increff Customer Support team by creating a support ticket by following steps mentioned here

FAQs

 

  1. What to do if orders are not flowing for a new customer onboarding?

    Reach out to amazon if all the details are correct, and check whether they have mapped the correct integrator with amazon.

  2. What should be the migration strategy if the client is on both the integrators(Increff and previous client’s integrator) for some time?

    1. Auto Confirmation(ack call) should be turned off from the previous integrator, so that no order gets missed in Increff’s system as we fetch new orders on ACCEPTED status and not on CONFIRMED status.

    2. While sending the inventory update for a location we send inventory update sequence no. for each sku and location. Eg. 1st time for that location and sku it will be 1 and will increment by 1 every subsequent time. Thus it is the responsibility of the client to share the latest inventory update sequence no. for all skus for that location, so that same can be updated in the proxy database after update inventory is called at least one time.

  3. Why do Listings become Inactive on Seller Portal although listings are FBA Enabled and have inventory in Seller Portal?

    Amazon expects that the product dimension received at packing time should match the product dimension defined on the Seller Portal for the respective SKU. Amazon made the listing inactive if there is a difference in both dimensions.
    The seller can make the listing active again by updating the correct dimension on the Seller Portal.

  4. Why do the sellers need to update dimensions(length, width, height, and weight) in Amazon portal listings?

    1. The dimensions uploaded by sellers in listings data are used by Amazon to create and recommend the package dimensions(using backend algorithms).

    2. The same package dimensions are fetched by Assure from Amazon.

    3. During packing, we send the dimensions back to Amazon as Amazon doesn’t allow us to pack orders without package dimensions. 

    4. There should be no empty or incorrect values in any of these 4 parameters. Otherwise, sellers can face issues while packing the orders. Hence, The seller should update all listings with the correct dimensions (length, width, height, and weight). 

  5. How to address Packing Issues because of incorrect/empty?

    1. This happens usually when the recommended packages field has some dimensions missing (length, width, height or weight). Check if all the dimensions are uploaded in the Amazon panel, if not upload the same and then retry packing. Also, check for the correctness of the dimensions.

    2. If the issue still persists, please raise the issue to assure.support@increff.com

    3. Our support team will share the logs with the Amazon team and provide you with the correct dimensions to be updated while packing.

    4. Once the recommended dimensions are received, you can enable 'Capture Packet Dimensions' in Packing screen configurations and input the dimensions while packing.

  6. What is the mechanism to identify SmartConnect orders from Seller central?

    1. Currently, there is no mechanism to identify SmartConnect Orders from Seller Central (Manage Orders) page. There are FBA reports available in Report drop-down on seller central where users can refer to AFS reports which have the warehouse id which can be used to identify SmartConnect Orders.

    2. Reports -> Fulfilled by Amazon -> Amazon Fulfilled Shipments Report

  • But this will capture only fulfilled orders. 

  • Amazon SmartConnect program team shares reports with the Integrator as well as selling partners in case orders are pending processing. You can refer to those reports to identify pending orders.

Â