Tokopedia

Integration Document




About Tokopedia


Tokopedia, one of Indonesia's leading tech companies with one of the country's largest marketplace platforms, serves more than 7.3 million merchants and more than 90 million active users every month.


Tokopedia is an online marketplace center that permits people and little and mid-size entrepreneurs to open and keep up their own online store effortlessly and free while giving a superior and more secure web-based shopping experience to their customers.

It was founded in 2009 by William Tanuwijaya and Leontinus Alpha Edison. It is an Indonesian unicorn along with ride-hailing company Gojek, travel service firm Traveloka, e-commerce Bukalapak and fintech company OVO.



Business Models


1. Pickup Model: Pick-Up is a Pure Marketplace Model in which the seller must process the orders using the 3PLs assigned by Tokopedia. Courier Partner comes to the warehouse to Pick-Up the goods and the last mile delivery is done by 3PL assigned by the Marketplace.


2. Drop off Model: In Drop Off Model, Seller itself must deliver the order to the last mile delivery partner’s hub/Collection point assigned by Tokopedia. In this case, The Last Mile delivery partner i.e. JNE, SiCepat, J&T is assigned by Tokopedia only. However, these 3PLs do not come to the seller’s warehouse to pick up the orders. Here, Seller itself must drop all the orders to the Hub/Collection point of JNE, SiCepat, J&T, etc.


INTEGRATION HIGHLIGHTS

 

 In Tokopedia Integration, we have: 

 

1. SKU Pull

 

2. Order Pull 

 

3. Order Pack/Shipping Label generation 

 

4. Order Shipment 

 

5. Order Acknowledgement 

 

6. Order Cancellation

 

7. Inventory Sync

 

8. Inventory Reconciliation

 

Prerequisites

 

A. Seller must get in touch with his Tokopedia account manager to enable the APIs for the seller or to Link the seller with Vinculum’s FSID (Developer Id on Vinculum).

 

B. Below credentials are mandatory for the Channel Configuration at Vin e-retails instance:

 

• FSID: Developer Id of Vinculum (13477)

 

• Client Id: Client Id of Vinculum (6307b70e3b7646b88e3aa962e24fc766)

 

• Client Secret: Client Secret of Vinculum (a7b75edf49914c9e8edc98df36591654)

 

• Shop Id: It can be fetched from the seller Panel profile URL after login successfully in client’s seller panel or can be asked from the client directly. 

 

• Pull Orders on Invoice No.: Click “Yes” if the orders should be created based on Invoice No. If clicking “No,” it would be disabled.


 

CONFIGURING INTERFACE

 

Below is all about how to configure TOKOPEDIA in Vin-eRetail for Products Sync, Inventory Sync, and Order Fulfilment.

 

1. Once all the IDs are ready, login to Vin ERP instance and go to “Manage Channels” under Sales Section.

 

 

 

 

2. Go to the top right-hand side of the window and click on “Add New.”

 

 

3. Select the required channel from the list.

 

  

4. After selecting the correct Channel option, a “Channel Maintenance” window will appear.

 

 

5. Fill in all the details like Channel Name, order Source WH, Order Sync from date, Return Sync from Date, Inventory Sync Method, Enable Inventory Reconciliation, etc.

 

6. Click on “Configure Interface.”

 

 

 

7. Enter the FSID, Client ID, Client Secret, and Shop ID as instructed above.

 

8. Click on “OK” and Save Channel.

 


 

Channel Maintenance


Channel Maintenance setup helps the seller reduce manual intervention and avoid the multiple usages of the marketplace seller portal. With the selection of below options at the Channel Maintenance window (Sales > Manage Channels > Add New > Select Channel) in Vin E-retails instance, the User can get the advantage of using multiple features of Vin E-retail:

 

S.No.

Feature(s)

Where to Click

Dropbox/Checkbox option

Details

1.

SKU Pull

Channel Maintenance > 

Channel SKU > SKU Sync > Pull/Push

 

 

 

 

SKU Sync: SKU Sync between Channel and e-Retail can be done via PULL & PUSH.

User can choose to Pull the SKU’s from the channel to e-Retail panel.

And User can choose Push to send the SKU data or changes from e-Retail to the channel.

 

2.

Order Pull/Order Pack/Invoice/Order Shipment/Shipping label generation

Channel Maintenance > Orders > Order Sync > Yes/No

 

Order Pull: The user can choose to sync the order from the channel to e-Retail by managing this option. If this is disabled, the Order pull will not happen also the shipping label/Invoice and manifest will not get generated.

3.

Ready to Ship Status at

 

Channel Maintenance > Orders > Ready to Ship At

 

 

 

 

 

Users can choose to mark the status of ready to ship at any of the two events:

-at Manifest

or

-at Pack

 

4.

Use Market Place Shipping Label

Channel Maintenance > Orders > Use Marketplace Shipping Label checkbox

  

Users can check this option to notify the Shipping label by the marketplace and then opt from the Shipment label dropbox.

 

5.

Inventory update

Channel Maintenance > Inventory Sync

 

 

If selected "Yes," it automatically pull and update the inventory.

6.

Inventory Reconciliation

Channel Maintenance > Enable Inventory Recon

 

Despite Inventory Sync, at times, there is a possibility of Inventory mismatch. By clicking Inventory Recon as “Yes,” it enables Vin E-retail to reconcile the inventory. (* It is only scheduled for once/day)

 

 

Additional Details on Tokopedia Integration:

 

  • In the case of Drop off Model, the Shipping label generated by Tokopedia have the Shipping Reference No/Booking Reference No and not the actual AWB No. The AWB No. assignment etc. is taken care by 3PLs directly. No involvement of seller in it.
  • Channel Mappings: Tokopedia SKU code needs to be mapped in Channel SKU code and the Tokopedia Product Id needs to be mapped in Channel Product Id.
  • Tokopedia API provides the orders of the last 3 days max so order Pull from date should be selected accordingly while config the channel. In any case, it should not exceed the order pull from a date greater than 3 days else no orders will be pulled in Vin e-Retails.
  • Canceling the order from the screen will push the cancellation to Tokopedia and the order status will be updated as Cancelled on Tokopedia.


For internal use only:

 

  • Order Status Update scheduler is mandatory to be configured for Running Tokopedia and its status Also needs to be mapped in Extmapping_localDB (For Internal Team use Only). Order Status Update Scheduler includes 3 things ie. 
    1. Enabling the scheduler in Task Info. 
    2. Order Status Update Trigger is required.
    3. Make sure that the Transmitlog have the correct Date time defined for the MP_ODRSTSUPD intcode