Versions Compared

Old Version 17

changes.mady.by.user rossc

Saved on

compared with

New Version 18

changes.mady.by.user Iain Shepherd

Saved on

Key

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


Table of Contents

Overview

Excerpt
Tip

POD Data is perfect for when you wish to provide POD information within your ERP or WMS or via your own portal.

Field List

Column Name

Definition

Data Type

Format

Length (max)

1

ConsignmentNumber

Connote Number

varchar


20

2

StatusDateTime

Date of POD

date 

YYYYMMDDhhmmss

-

3

PODURL

Image URL. URL leads to an image (PNG) file

varchar


-

4

Carrier

Carrier or POD provider

varchar


50

5

Reference

Reference of the Consignment

varchar

20

Format

This report can only be provided in CSV.

PODDataCSV

Requirement

The receiving system should be able to interpret this file to process it by either of the following methods:

  1. Using the link and directly loading the image from the URL provided.

  2. Processing each image by downloading the image from the URL and storing it in the receiving system's own file store.

Caveats

  • The availability of the POD is dependent on the carrier sending efm the POD image. efm is not responsible for any missing POD for an confirmed integrated carrier.

  • efm can only send these files to you and not process the information directly into your IT system.

  • This is the only option for sending POD links as we can’t guarantee the filename because PODs may contain Personally Identifiable Information so they need to be obfuscated.

Example

Code Block
languagesql
ConsignmentNumber,StatusDateTime,PODURL,Carrier,Reference
"838428","20180811132200","httphttps://datadocs.enodoflipgroup.com.au/Pods/2018/08/636705281728460335.pngfake040e84c50a60338d617d1666975f","Toll Priority",""

Sample File

Image URL change

As of 8 Nov 2022, the PODURL is now in the form https://docs.flipgroup.com.au/<random chars>

Customer_PODData_20180811142001.csv