Versions Compared

Key

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

...

Interfaces coloured in blue are Mandatory Interfaces.

Flow Name

Details

Remarks

B2B Order Posting

Omni will push B2B order details fetched from Ajio to ERP against which the ERP will generate an e-invoice.

Here the Event Type in the postings is set as OUTWARD_ORDER_CREATE.

We support two ways for this -

  1. Standard APIs - Outward

Sale
  1. Sales Posting API (For ERP systems)

  2. Custom ERP Integration

Post B2B Invoice

Once the client’s ERP generates the e-invoice it needs to pushed to Omni.

We have an API to Push B2B Invoice.
https://increff.atlassian.net/wiki/spaces/OID/pages/510853817/Ajio+VMS+Integration+Flow#Post-B2B-Invoice-API--

Cancelled Order Postings

If the customer cancels the order after the e-invoice has been generated by the client, Omni will send another posting to the client’s ERP which will cancel the order(e-invoice) in their ERP.

Here the Event Type in the postings is set as OUTWARD_ORDER_CANCEL.

We support two ways for this -

  1. Standard APIs - Outward

Sale
  1. Sales Posting API (For ERP systems)

  2. Custom ERP Integration

Complete order Postings

Once the order is completed in the warehouse, this posting is sent to Client’s ERP.

The main purpose for this posting to create a return order against a partially cancelled orders. If the order gets partially cancelled by the customer after the e-invoicing is done by the ERP, the ERP can consume this posting to create a return order for the items which were cancelled by the customer.

Here the Event Type in the postings is set as OUTWARD_ORDER_COMPLETE.

We support two ways for this -

  1. Standard APIs - Outward

Sale
  1. Sales Posting API (For ERP systems)

  2. Custom ERP Integration

Post B2B Invoice API -

Include Page
AJIO Post B2B Invoice Interface
AJIO Post B2B Invoice Interface

...

All Interfaces are mandatory.

Flow Name

Details

Remarks

Return Order Postings

After the return is processed in the warehouse, a return order posting is sent to client’s ERP.

We support two ways for this -

  1. Standard APIs - Return Order Posting API (to ERP)

    The Shipments array is always empty for this.

  2. Custom ERP Integration

Post Credit Note

After the return is processed in the ERP, the ERP will need to generate a credit note. This credit note will be uploaded to Ajio.

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.

We have an API to push credit note -

https://increff.atlassian.net/wiki/spaces/OID/pages/510853817/Ajio+VMS+Integration+Flow#API-to-Post-Credit-to-Omni

API to Post Credit to Omni

Include Page
AJIO Post Credit Note API
AJIO Post Credit Note API

Return Order Flow - Credit note via RMS

...