Specific order parameters

About

• Explanation of order entry parameters that are more specific.
• These parameters are mostly related to output specifications.

Where

• Orderentry parameters can be found in: Backoffice -> Settings -> Parameters -> Order Entry

Description

cmrBlocks

• How to position CMR content, see also: cmrBlocks

cmrCarrierCode

• See 1 at above screenshot.
• Carrier code inside the CMR, default positioned top right.

CSVoutputfields

• See 2 at above screenshot.
• Order output fields and settings when parameter orderOutputType for this customer is CSV.

deliverySlots

• Available delivery slots generated by param deliverySlotsDef.
• Example of the generated content:
  #date,tripName,loadmetersAvailable,weightAvailable,timeFrom-timeTo|slotsAvailable(postcode-postcode;...),...
  2019-10-07,Maandag Rit 1,3,1500,08:00-13:00|5(8300-8879),12:00-17:00|7(8900-9159;9162-9299)

deliverySlotsDef

• Definition parameter to generate delivery slots. Example:
  #tripName,maxLoadmeters,maxWeight,timeFrom-timeTo|availableSlots(postcode-postcode;...),...
  Monday Trip 1,3,1500,08:00-13:00|5(8300-8879),12:00-17:00|7(8900-9159;9162-9299)

goodsfieldnames

• See 3 at above screenshot.
• All common used goodlines fieldnames in Cargo Office.

lastShipmentID

• See 4 at above screenshot.
• Last used shipment inside your cargoOffice.
• In most cargoOffices shipments are numbered upwards.

orderCopyEmailAddress

• See 5 at above screenshot.
• This will sent a copy of all filled orderentry-fields to a specified address.
• If you want to add more addresses, be sure to put each address on a seperated line.
• You can check your modifications when looking at the result after submitting: addresses should be seperated by a comma without blank space, e.g.: me@tst.com,you@tst.com,we@tst.com ,etc.
• If deleting addresses be sure to delete all blank space with it.
• Note: You will only receive copies of orders entered via the order entry form. If you want copies from EDI orders you can create a status action: see section Send BOL (Bill Of Lading) to an email address.

orderCopyType

• See 6 at above screenshot.
• specified template for output type.
• This could be an ordercopy template (with values similar to the booking template) read more in: OrdercopyTemplates.

orderFieldNames

• See 7 at above screenshot.
• All common used order fieldnames in Cargo Office.

orderFormType

• See 8 at above screenshot.
• specified orderentry template.
• This is often used when you have specific templates created for specific customers.

orderOutputEmailAddress

• See 9 at above screenshot.
• An order-file of all processed orderentry-fields will be sent to the here specified address.
  
  • This can be an email address.
  • You can add more than 1 email address, seperated by comma.
    Be sure not to use any blank space (around the comma).
  • This can be 'ftp' voor ftp-downloads.
    If you have access to a cargo Office FTP-account, by default these files are placed in your IN-directory.
• It is not possible to use ftp + an email address.

orderOutputType

• See 10 at above screenshot.
• You define the type of output format you want to sent to parameter: orderOutputEmailAddress
• The most easy to configurate are the Cargo Office standard outputs: CSV and XML.
• But you can also use a specified output program for your TMS-system or WMS-system, like Roadrunner, LP-Trans, Nachon, TANS, Plan & Go, Transmate, etc.
• Cargo Office programmers have created dozens of specified parsers in the past. If you want to know if an output to your TMS-system is realized than contact your supplier or ask us by using your bug tracking system.
• If you do not want to output anything, fill in value: nooutput

pickupListExcludes

• See 11 at above screenshot.
• here inserted values for deliveryType are excluded from the pickup list (which you can find in: Backoffice -> Shipments -> Print pick-up list).

pickupListOrderBy

• listing options for the pickup list.
• By default listing is provided on the Cargo Office Shipment Number. By using this parameter other options are available (if part of your pickup-template): deliveryCity, deliveryPostcode and orderReference.

shipFieldNames

• See 12 at above screenshot.
• All common used shipment field names in Cargo Office.

stickerCountType

• See 13 at above screenshot.
• Counts and prints stickers according its value.
  
  • perorder: prints 1 sticker per order
  • perpallet: prints a sticker for every pallet
  • perpalletplace: prints a sticker per pallet place (for this you may need specific adjustments programmed, first just check what it does in your surrounding).
  • Note: all above values have to be written exactly as above, in lower case.

stickerRepeat

• Defines how many stickers are printed before the next sticker.
• Note: by default this functionality is available in new order entry templates, older versions will need some extra programming for this functionality. If interested sent a request to Cargo Office programmers by using the Bug Report System.
• Note: this parameter functionality is orderentry template based, for input EDI orders a value for field stickerRepeat has to be added; for instance when using the EDI-configurator.

stickerTemplate

• See 14 at above screenshot.
• Defines the type of sticker or label that is used by this customer.
• There are also a couple of default sticker formats available.