...
Just like how multiple invoice configurations are possible, multiple logistic aggreagator configurations are also possible. They will be identified with the help of logistic account aliases which are configured on RMS UI. This logistic account alias will then be passed in the request payload of the API call which will be used to identify the logistic configuration to be used.
For example, there are can be 2 logistic aggregator configurations
1st logistic configuration - logistic account alias:exists at same time
Configuraton 1:
Notification | Account Alias | Username | API Key |
|---|---|---|---|
Toggle Enabled/Disabled | logistic-account-1 |
...
clickpost |
...
-account-1 |
...
abcd |
...
Configuraton 2:
Notification | Account Alias | Username | API Key |
|---|---|---|---|
Toggle Enabled/Disabled | logistic-account-2 |
...
clickpost-account-2 |
...
defg |
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
|
...
|
...
|
...
|
...
|
...
|
Clickpost Integration Solution Features
...
Notifications sent by Clickpost are forwarded to the client’s systems by RMS.
Notifications can be of forward orders containing the information about statuses (DELIVERED, OUT_FOR_DELIVERY,CANCELLED etc) and about return orders (RTO, RETURN_PICKED_UP etc.) ( insert api doc link)
Upon receiving the notification from Clickpost, they are then pushed to the client systems based on the url configured.
...
Notifications sent by Shipway are forwarded to the client’s systems by RMS.
Notifications can be of forward orders containing the information about statuses (DELIVERED, OUT_FOR_DELIVERY,CANCELLED etc) and about return orders (RTO, RETURN_PICKED_UP etc.) ( insert api doc link)
Upon receiving the notification from Shipway, they are then pushed to the client systems based on the url configured.
RMS Magic Integration Solution Features
Forward AWB and Shipping Label generation
Return AWB generation
...