This section is designed for customers wishing to send and receive information from their warehouse.

Key Pages in this section

Header Pages

Header Pages
Testing Inbound EDI	If you are new to sending EDI or wanting to make a change then this is the first page to start from
Inbound Specifications	Sending information to the warehouse
Outbound Specfications	Retrieving information from the warehouse
Developer API Technical	Using the API, setup information for developers.

The EDI module was designed for use with Vision warehousing to allows complete electronic trading with customers.

The current processes most customers offer is the exchange of electronic files between systems, the format of these is in XML format.

Whilst API is available we still have a number of customers sending XML files via email, however we will not support sending via email beyond 31/12/2025

Where to start

Sending to the warehouse

See the following page Testing Inbound EDI - Vision EDI

Receiving from the warehouse

In the first instance contact the warehouse directly.

1 Key Pages in this section
2 Where to start
- 2.1 Sending to the warehouse
- 2.2 Receiving from the warehouse
3 Transmission Methods
- 3.1 API (HTTP Post)
4 API Credentials
5 More Information
- 5.1 Inbound Information
- 5.2 Outbound Information

Transmission Methods

This is how files are sent and received from the system.

Direction	API	eMail to 31/12/25
Inbound (to warehouse)	Available	Restricted
Outbound (from warehouse)	Available	Available

From 01/01/2022 API will be the only transmission method for new connections

API (HTTP Post)

The API is a RESTful web service. Queries are passed via URLs constructed and submitted using the HTTP protocol (specifically the GET method), just like a web page. Results can be returned XML

You can not receive the outbound files alone, you need to send through the API to receive through the API.

FTP is no longer available (31/12/2019)

API Credentials

These are issued to warehouse customer to allow those customer to access their accounts through the API for sending information to the warehouse and also the retrieval.

API credentials are only issued to warehouse customers during the testing of EDI stages and will be required for you to complete stage 3 testing.

API tokens are limited to what they can retrieve, these are known as service limits Service Limits as such it will generally be one API token to one warehouse account however exceptions are made when a customer has a trading account and a reserve account and a single token can access up to two accounts but they are subject to the single API limits.

API tokens are only provided to warehouse customers when the warehouse customer makes the request through the testing mechanism or where they are wishing to only retrieve through the warehouse authorisation process. See Testing Inbound EDI | Step by Step Guide to Testing

An API token is granted to a single legal entity, which is either a limited company, or business of the same name with the same directors/owners/proprietors, because granting this token allows the token owner to access ALL of your information including confidential and business seneitive information which includes but is not limited to

stock holding
supplier information
purchase pricing of the stock
reserve customer information
Live delivery information and customer information

A full list of all information which could be retrieve is within the following section. EDI / API Output

Developer Information is held in its own section on this wiki Developer API Technical

More Information

More information is contained within the individual sections below.

EDI Specifications