AJIO JIT



About AJIO

AJIO is the digital fashion extension of Reliance that was unveiled in April 2016 at Lakme Fashion Week in Mumbai. AJIO, a fashion and lifestyle brand, is Reliance Retail’s first pan-Indian e-commerce venture and is the ultimate fashion destination for styles that are handpicked, on-trend and at prices that are the best, you will find anywhere. AJIO deals in categories of women's wear, menswear, kids wear, and technology. With fashion technology, AJIO forayed into a category that combined the convenience of technology with the aesthetics of contemporary fashion by featuring a carefully handpicked selection of premium gadgets and tech accessories. With the advanced internet infrastructure built by JIO and a robust physical retail business built by Reliance Retail, creating a differentiated e-commerce model for India through AJIO.


Models of AJIO

Models of AJIO Integrated with Vin e-Retail:

  1. AJIO Dropship (B2C) 
  2. AJIO JIT (B2B) *
  3. AJIO Business (B2B)  

* JIT – Just in time

This document is all about the AJIO JIT Integration.


INTEGRATION HIGHLIGHTS

AJIO JIT Integration supports below touch points:

  1. SKU Pull (Moderation Mode) 
  2. Order Pull and Create 
  3. Order Pack i.e. Invoice/Ship Label document generation 
  4. Order Shipment
  5. Manifest Document generation 
  6. Inventory Push
  7. Inventory Reconciliation 
  8. Order cancellation Push
  9. Back Order Inventory Pull


Prerequisites

Below mentioned things are required to make AJIO Channel live for any client:

  • Username (Mandatory): (Seller Id and Password using which the API calls are made successfully, not the login credentials and the client have to get in touch with his Account Manager to share the same)
  • Password (Mandatory)
  • Is B2B flag (Mandatory): Always set this as YES for the B2B marketplace
  • Enable E-invoicing (Optional): This is to be selected as “No”.
    (It is only applicable if the seller has a multimillionaire business. It must be selected “Yes” only after checking with the client and AJIO account manager) 
  • E-Invoicing Username: Mandatory if the Enable E-invoicing is “YES” else leave it as Blank. The username of the E-invoicing portal must be mentioned in this attribute
  • E-Invoicing Password: Mandatory if the Enable E-invoicing is “YES” else leave it as Blank


CHANNEL CONFIGURATION

Below is all about how to configure AJIO 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 “Configuring Interface.”

7. Enter the mandatory details like:

  • Username (Mandatory)
  • Password (Mandatory)
  • Is B2B flag (Mandatory): Always set this as YES for the B2B marketplace

 

8. Click on “OK” and “Save.” The channel is saved in the “Manage Channel Screen” with a channel code.


Channel Maintenance


Channel Maintenance setup helps the seller to 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), get the advantage of using multiple features of Vin E-retail:

 

S.No.
Features
Where to Click on Channel Maintenance
Dropbox/Checkbox
Details
1
SKU Pull

Channel SKU >
SKU SYNC >
Pull/Push

 

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


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

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

 

SKU Create: Choose “Moderate

2

Order Pull/

Order Pack/

Invoice/

Order Shipment/

Shipping label generation


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
Order Return
Orders>

Return Order Sync

Users can click this option to sync Return Orders.


Important Note: In Return Pull Services, the “Return” is always created in Confirmed status.


Users need to do an inbound from Return Inbound functionality available on the Application.

4
Prefetch Shipment Label
Orders >
PrePack Enabled checkbox

PrePack Enabled: The user can enable prepack for the order from here.


To avoid delay in Order processing and Shipment fulfilled within a provided SLA, we have a feature to pull shipment Label and Invoice at the same time of picklist generation instead of during Pack Call. To use this functionality, we just need to enable Prepack checkbox available under the Channel Configuration setup screen and the user needs to click on Prefetch deliveries during the pending picklist status available on the Picklist enquiry screen.

5
Ready to Ship Status at
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

6
Use Market Place Shipping Label
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.

7
Inventory update
Inventory > Inventory Sync

If selected "Yes" from the dropdown box, it automatically pulls and updates the inventory

8
Inventory Reconciliation
Inventory > Enable Inventory Recon

By clicking Inventory Recon as “Yes,” it enables Vin E-retail to reconcile the inventory. (* It is only scheduled for once/day)



Channel Mappings :

 For Channel Mappings, Enabling the SKU Pull-in Moderate Mode is mandatory. 

 

The SKU code of AJIO should be mapped in ChannelSKUcode of Vin-eRetail and ProductId~VariantId needs to be mapped in ChannelProductId and channel mappings based on Pulled SKUs is mandatory.