Skip to main content

XLSX Integration

Standard Interface Overview

InterfaceDirectionFrequencyFilenameMethod Name
1. Product MasterClient > AdOr5Real timePRD_yyyyMMdd-HHmmss.xmlProductMasterSTD_XLSX
2. Purchase OrderClient > AdOr5Real timePO_yyyyMMdd-HHmmss.xmlPurchaseOrderSTD_XLSX
3. Order InstructionClient > AdOr5Real timeORD_yyyyMMdd-HHmmss.xmlOrderInstructionSTD_XLSX

Downloads

All Fields:

Required Fields Only:

Product Master

AdOr5 requires that all products are loaded into the system prior to receiving any of the units into the warehouse. Product Master records that are created or updated in the host system must be sent to AdOr5 when new products are created, modified and/or marked as inactive in the host system. Multiple barcodes can also be stored against a single product.

Available Fields:

FieldTypeNotesReq
GroupNoString (15)N
DepartmentNoString (15)Y
DepartmentDescString (50)N
TypeNoString (15)N
TypeDescString (50)N
StyleNoString (15)Y
StyleDescString (50)Y
ColourCodeString (15)N
ColourDescString (30)N
SizeCodeString (15)N
SizeDescString (30)N
SizeSortIntegerN
SKUNoString (30)Y
PackQTYIntegerN
CostPriceFloatN
SellPriceFloatN
ProductWeightFloatN
ProductLengthFloatN
ProductWidthFloatN
ProductHeightFloatN
ProductCubeFloatN
StorageTypeCodeString (20)N
StorageTypeDescString (30)N
CountryCodeString (10)N
TechIndexString (3)N
SeasonCodeString (10)N
TimePeriodString (3)N
ControllerCodeString (10)N
ControllerNameString (30)N
GradeString (10)N
SupplierTypeString (10)N
SupplierNameString (60)N
SupplierCityString (10)N
SerialControlledIntegerN
CanExpireString (15)N
Ref1String (255)N
Ref2String (255)N
BarcodeString (30)Additional barcode for a SKUN
BarcodeString (30)Additional barcode for a SKUN

Additional Notes:

  • All fields should be text fields.
  • The file name must start with “PRD_” and end with “.XLSX” e.g. PRD_20202209.xlsx.
  • If a field is not required, the header can be removed from the file

Purchase Order

The intake order interface is used to inform the warehouse of expected incoming receipts. The PO information must be sent to AdOr5 before the shipment physically arrives at the warehouse. Once the shipment arrives, the operators will compare the actual to the expected and capture any discrepancies. Updates to an intake order can be sent at any time up until receiving has begun. After this, no updates will be accepted.

FieldTypeNotesReq
POSourceString(30)Y
ClientNoString (30)Y
ClientNameString (30)N
PONoString (35)Y
PODescString (100)N
POTypeString (30)PO, Return, etcN
Ref1String (50)N
Ref2String (50)N
Ref3String (50)N
DeliveryDateDate Timeyyyy-MM-ddN
AllowPOUpdateString (1)y/n or 1/0N
AllowASNUpdateString (1)y/n or 1/0N
AllowManUpdateString (1)y/n or 1/0N
BlanketPOString (1)y/n or 1/0N
LocationNoString (10)Supplier numberN
LocationName1String (60)N
BlindReceiveString (1)y/n or 1/0N
MixedItemPalletString (1)y/n or 1/0N
CombinePalletString (1)y/n or 1/0N
AllowOverReceiveString (1)y/n or 1/0N
CustomerNoString (30)Y
SKUNoString (30)Y
QTYIntegerY
ItemAtt1-5String (40)N
ItemAttValue1-3Numeric (10,3)N

Additional Notes:

  • All fields should be text fields.
  • The file name must start with “PO_” and end with “.XLSX” e.g. PO_20202209.xlsx.
  • The first occurrence of a PONo will create the header and requires all the required fields. Any other occurrences of the PONo only requires the PONo, CustomerNo, SKUNo and QTY.
  • If a field is not required, the header can be removed from the file

Order Instruction

This interface is used to inform AdOr5 of a delivery instruction to a specified customer. Orders can be updated up until the time that allocation has occurred – thereafter no updates will be accepted. Order cancellations are handled outside of interfacing.

FieldTypeNotesReq
OrderNoString (30)Y
ClientNoString (30)Y
CustomerNoString (30)Y
DestNoString (20)Y
DestNameString (60)N
DestAddress1String (70)N
DestAddress2String (40)N
DestCityString (30)N
DestTownCodeString (10)N
DestPostalCodeString (20)N
DestContactString (30)N
DestRef1String (30)N
DestTelephoneString (30)N
SKUNoString (30)Y
OrderedQtyIntegerY
VASTextString (2048)N
ServiceLevelCodeString (10)N
OrderTypeString (10)If the order type does not exist, a new order type will be createdY
OrderTypeDescString (30)Used when creating a new order type. Will default to field OrderType if emptyN
Ref1String (30)N
Ref2String (30)N
DueDateDate TimeN
ShipFromDate TimeN
ItemAtt1-5String (40)N
ItemAttValue1-3Numeric (10,3)N

Additional Notes:

  • All fields should be text fields.
  • The file name must start with “ORD_” and end with “.XLSX” e.g. ORD_20202209.xlsx.
  • If a field is not required, the header can be removed from the file