Versions Compared

Old Version 4

changes.mady.by.user Prabal Pandit

Saved on

compared with

New Version 5

changes.mady.by.user Rahul Singh

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Flow Diagram

...

Forward Order Flow

  1. Assure Increff Omni will fetch B2C order details through Increff's VMS Integration Layer using date filters from Ajio Channel.

  2. Assure Increff Omni will soft reserve the inventory. Assure Increff Omni will send Acknowledgement Increff's VMS Integration Layer for that order. Increff’s VMS Integration layer will hold acknowledgement acknowledgment for a definite time (4 hours) and then will send it to Ajio. At this step Ajio will stop customer cancellationcancellations. Here 4 hours of window will enable customers to cancel the order.

  3. Increff's VMS Integration Layer will fetch B2B order details for which acknowledgement acknowledgment is sent.

  4. Increff's VMS Integration Layer will send B2B orders to client’s ERP via Increff’s ERP integration(Assure Increff Omni Magic/Standard ERP Integration/ Custom Integration). Here orders will have the final quantity only for which invoice is to be created.

  5. Client’s ERP will make an invoice for the final quantity submitted for B2B PO and give it to Increff's VMS Integration Layer.

  6. Order will be released for picking.

  7. During packing, for invoiced quantities Increff’s VMS Integration layer will generate B2B invoice at Ajio and other quantities will be cancelled for that order. B2B invoice will be updated with QR code and IRN number and the same will be uploaded to Ajio channel. If some items are not found in the warehouse or damaged, the whole order needs to be cancelled as the E invoice is already generated in ERPs and Increff can not cancel it partially on Ajio side.

  8. B2C Invoice and Shipping labels will be fetched for each B2C order while packing in the warehouse.

  9. At the time of handover, Increff will make a Create Manifest call to Ajio to create a manifest for shipments at Ajio channel’s end.

  10. This will end the forward order life cycle.

...

  • Article master creation - This api will be needed to automate tasks of uploading article master and listings against Assure Omni Magic 2 channel. This step can be optional if in order posting Client sku id/EAN is allowed in place of some other variant id. If some other variant id is required in order posting then please refer to below document :https://increff.atlassian.net/wiki/spaces/IOSA

  • B2B order posting - from Increff’s ERP integration layer to client ERP. If the client’s ERP is integrated to ERP via Assure Omni magic then they can refer to Order Posting from AssureOmni section in the below document: https://increff.atlassian.net/wiki/spaces/IOSA

  • B2B Order Cancellation Posting - from Increff’s ERP integration layer to client’s ERP. If the client’s ERP is integrated via Assure Omni magic then they can refer to the Order Posting from Assure Omni section in the document below. Here only Complete cancellation (OUTWARD_ORDER_CANCEL) will be sent and not the partial cancellationhttps://increff.atlassian.net/wiki/spaces/IOSA

  • B2B Invoice details posting to Increff

...

Flow Diagram

...

Forward Order Flow

  1. Assure Increff Omni will fetch B2C order details through Increff's VMS Integration Layer using date filters from Ajio Channel.

  2. Assure Increff Omni will soft reserve the inventory. Assure Increff Omni will send Acknowledgement Increff's VMS Integration Layer for that order. Increff’s VMS Integration layer will hold acknowledgement for definite time (4 hours) and then will send it to Ajio. At this step Ajio will stop customer cancellation. Here 4 hours of window will enable customers to cancel the order.

  3. Increff's VMS Integration Layer will fetch B2B order details for which acknowledgement is sent.

  4. After fetching B2B information, Increff’s VMS Integration layer will release the order for picking.

  5. Here if items are not found or damaged, order can be partially canceled.

  6. During packing, B2B invoice will be created by Increff’s RMS. The same will be generated, updated and uploaded to Ajio.

  7. B2C Invoice and Shipping labels will be fetched for each B2C order while packing in the warehouse.

  8. At the time of handover ,Increff will make a Create Manifest call to create a manifest for shipments at Ajio channel’s end.

  9. This will end the forward order life cycle.

...

  1. Increff’s VMS Integration layer will receive a return expectation from Ajio against a Forward order number. This can be a customer return or RTO. In case a warehouse has not received return expectation from Ajio for an RTO, Increff’s VMS Integration layer can generate an RTO request to Ajio through Ajio VMS RTO Generation after which Increff’s VMS Integration layer will receive return expectation as RTO in some time. 

  2. This return will be processed in the warehouse and qc updates will be shared with Ajio through Increff’s VMS Integration layer.

  3. Return order postings - from Increff’s ERP Integration layer to client’s ERP. If a client's ERP is integrated via Assure Omni magic 2 they can refer to the Return Order Posting section in the document below. Here Shipment Array will come empty: [].https://increff.atlassian.net/wiki/spaces/IOSA

  4. Credit note posting to Increff - After this client’s ERP has to generate credit note and share with Increff’s VMS integration layer via Ajio VMS Credit Note API Interface. This will send credit note information to Ajio.

  5. Any Qc bad or missing items have to be handled offline with Ajio. Qc updates will be shared through integration but settlements should be done manually.

...