Versions Compared

Old Version 7

changes.mady.by.user Dennis Navarro

Saved on

compared with

New Version 8

changes.mady.by.user rossc

Saved on

Key

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

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:

  1. If

...

  1. your environment does not allow an external software installed

...

  1. on it (eg for security reasons).

  2. If your ERP (order management system) is capable of utilising a RESTful web service.

  3. Your ERP (order management system) must adhere to the Order Lookup - Information Requirements and Sample Files or as defined in the API documentation (see link below under Technical Details)

Note

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:

  1. OneFlo Account ID mapped to your warehouse locations or addresses

  2. Cost Centre Codes and Descriptions

  3. 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:

  1. OneFlo Account Id (6-digit)

  2. API Key

Technical Details:

For UAT Swagger, visit: https://uat-apidocs.flipgroup.com.au/

...