RMS Return Flow Scenarios
Â
All the below scenarios are valid only when the processing of the forward order is also through RMS APIs.
The courier aggregators currently integrated with RMS support the below flows:
Clickpost
Shiprocket
RTO Returns : When the shipping partner initiates the return process.Â
Customer Returns : When the customer initiates the return process.
RTO Return
Integration via Omni Magic
Option 1
RMS pushes to Client system and Client system pushes to Omni Magic.Â
Â
Â
RMS receives courier return notification from courier partner/aggregatorÂ
RMS asynchronously pushes this notification to the client’s system.
Client’s system then pushes this courier return to Omni Magic.
On RMS’s UI, the client's system’s credentials will be configured.
Â
Option 2
Â
Â
Client’s system is directly integrated with courier partner/aggregator for RTO notifications.
On receiving the RTO notification from courier partner/aggregator, the client's system then pushes the RTO order to Omni Magic.
Integration via Custom Integration
Option 1
RMS receives the RTO notification from clickpost.
Here, RMS is directly integrated with the custom integration, so RMS pushes the RTO order to the custom integration.
If required, the custom integration then can send notification to the client's system about the RTO order created.
Option 2
Client’s system is directly integrated with courier partner/aggregator for RTO notifications.
On receiving the RTO notification from clickpost, the client's system then pushes the RTO order to the custom integration.
Customer Return
Integration via Omni Magic
Â
Option 1
RMS receives customer return notification from courier partner/aggregator and this is then forwarded to the client’s system.
Client’s system then pushes this customer return order to Omni Magic.
On RMS’s UI, the client's system’s credentials will be configured.
Option 2
Â
Return AWB generation is handled by the client's system only. Client’s System is integrated with RMS for return AWB generation.
Once the AWB is generated, the client's system will push the customer return order to Omni Magic.
Â
Option 3
Return AWB generation is handled by the client's system only. Client’s System is integrated with courier partner/aggregator for return AWB generation.
Once the AWB is generated, the client's system will push the customer return order to Omni Magic.
Integration via Custom Integration
Option 1
Return AWB generation is done by the client's system by direct integration with the courier partner/aggregator.
Client’s system then pushes the customer returns into Increff’s system
Option 2
Return AWB generation is done by the client's system using RMS APIs.
Client’s system then pushes the customer returns into Increff’s system
Â
Â