OneFlo offers an ability to send order data directly which will be used for Order Lookup in the consigning screen.
When to use this?
You can use this option if the following conditions are satisfied:
If your environment does not allow an external software installed on it (eg for security reasons).
If your ERP (order management system) is capable of utilising a RESTful web service.
If your ERP (order management system) can provide a JSON payload as defined in the API documentation (see link below under Technical Details)
If you choose to use RESTful API to send your orders, we won’t be able to do further pre-processing on your order data, therefore you must adhere to the OneFlo data requirements as per point 3 above.
The following are components where you may need to have a mapping in your system:
OneFlo Account ID mapped to your warehouse locations or addresses
Cost Centre Codes and Descriptions
Carrier Service Codes when you choose to make a service decision within your business process
Requirements
Please reach out to your Account Manager or IT Implementation Consultant for the following information:
OneFlo Account Id (6-digit)
API Key
Technical Details
For UAT Swagger, visit: https://uat-apidocs.flipgroup.com.au/
Production Swagger:
Function: OrderLookup
Endpoint: https://api.flipgroup.com.au/customers/{accountId}/orderlookup
API Web Services
To learn more about our API, please see API Web Services