The degree to which consignment and freight handling adds value to DUO is tempered by the functionality offered in the software provided to larger companies by their freight company. For this reason it is not initially intended to generate consignment note information within DUO but simply record it in the Exo database. 


There are multiple modes available and the mode is defined for each Courier therefore a mixture of modes is possible within a single database:

·         Manifest Only:  {Courier method:  0. No Freight (Manifest)}. This method records consignment information only and does not add any freight charges to the order.

·         Freight Billing: {Courier method:  1. Lock Freight code}. This method associates a stock code with a courier so that freight costs can be charged.  One unit of freight is charged for each consignment note / ticket.

·         Freight Billing Extra:  {Courier method:  2. Select Freight code}. This is a variation on the Freight Billing method but the freight stock code is obtained from the package definition rather than being a single stock code for the courier (requires the ticket barcode to contain a package type).

·         Prepaid Tickets: {Courier method:  3. Prepaid Tickets} This is another variation on the Freight Billing method but the freight stock code is obtained from the service code rather than being a single stock code for the courier (requires the ticket barcode to contain a service type).

·         Routing Calculation:  {Courier method:  4. Advanced} This calculates freight based on package type and destination depot (a route).  

TODO: Process freight generation for modes > 0 not yet coded

TODO: Mask recognition under development

The setup of modes is done by defining one or more couriers (ExoCfg > Admin > Courier > Courier Setup). 


Optionally it is also possible to define Dispatch Methods (Exocfg > Admin > Setup > Dispatch methods) and link each courier to one. Dispatch methods can be for any use e.g. By air and By Sea.


Note that although setup screens exist in Exocfg for most of these entities, it is often more practical to maintain them with the Quick Insert utility.  Template files for all of these are provided by DUO.

Dispatch Methods

Exocfg > Admin >  Setup > Dispatch Methods

Setup of Dispatch methods is optional.


Warehouse – Consignments – Dispatch Methods

Note: You can also use these without couriers. There is already a combo-box on the DUO > Process Sales Orders window and the same on the Exo Sales Orders > Quick Supply window.


Exocfg > Admin > Courier > Courier Setup

Warehouse – Consignments – Couriers

Courier Mode: As described in the overview

0 = No Freight Manifest

1 = Lock Freight

2 = Select Freight Code

3 = Prepaid Tickets

4 = Advanced

Prefix Size: This is not used by DUO.

Freight Stock Code: The (default) stock code required to add a line to the sales order. This is not required for Courier Mode = 0.

Consignment note (optional):  You would print and/or email this using toolbar button when scanning of all consignment information is completed.  It could contain multiple scanned consignment numbers i.e. is global for the sales order.  It could also contain product information related to the consignments if you have allocated events to tickets (a mini manifest for the order).

Trace URL: This is a link to the couriers Track and Trace web site.

We recommend activating Quick Insert for couriers using Exocfg > Utilities > Quick Insert > Tabsheets and add the two extra DUO_ columns to the template COURIERS.tem which are:

·         DUO_SUPPLIERNO – defines the creditor account for the courier. This is required if generating courier costs (see later in this section).

·         DUO_SITEID – the site id for the courier as issued by the courier company. This is required if generating your own consignment numbers.

Warehouse – Consignments – Couriers QI

TODO in Motopartz: Setup creditors for each courier and link to couriers. Put in some SiteIDs

Modify Packslip.clf

If you want the consignment information to show on the packing slip you need to add a sub-report to print minimal info from the COURIER_MANIFEST table.

DUO provides a modified version of the standard packlip.clf containing this change. If you have not already got a customised packlip.clf then you can put this in your custom Clarity folder (so MYOB won’t override it on upgrade).

Courier Masks

Courier masks (optional) allow a scanned consignment code to be deciphered into its constituent parts to populate columns in the manifest row. The consignment code in full is always stored. If a mask is not found then the derived columns remain empty.

 DUO uses a Quick Insert Template to maintain these. Some example masks are shown below.

The following characters are used in masks. Note that lower case letters are mask characters whist upper case letters plus digits are constants by which the scanned consignment number can be identified.

a =  SiteID (e.g.Couriers account code for you)

c = Parcel count

d = Destination code

w = Weight or cubic

s = Combined service code

p = Package type

Courier Packages

Courier Packages define package types. Use of these is optional but they appear in the manifest widget allowing quantity of packs to be entered.  These are maintained using the Quick Insert utility.

Warehouse – Consignments –Packages

A courier can either have a custom list of packages (CourNo > 0) or if none exist then the system will use the default set of packages (CourNo = -1).

The SupplierCode column links to Exo supplier Stock Items for the Freight Stock Code defined on the Courier master record. This determines the unit cost of freight for the package.

Warehouse – Consignments –Package Costs


Manifest Widget

This widget allows capture of consignment note and courier ticket information associated with an order.  It can be used with many different order types and will appear on the Manifest Tab of the processing screens for those order types.


There are 3 Tabs on this widget

·         View: The pre-existing grids for Tickets and Consignments and Order Line Events appear on this tab.

·         Address: This tab shows address related information including fields for barcode generation on consignment labels

·         Packages: This tab shows a grid populated with package names and associated volumetric and pricing columns. The user may enter package quantities to this tab and then use the Generate button to create manifest entries and (optionally) print consignment labels.

Manifest View Tab

Warehouse - Manifest {tab} View {sub-tab}

The top grid shows captured consignment note / courier ticket numbers which have been scanned into the omni box. These codes will be scanned from barcodes on your courier systems label or prepaid ticket.

The bottom grid shows both processed and pending supply events (obtained from sales order history in MYOB Exo). If you wish to designate which items are in which package then you can link these with the Allocate buttons as described below.

 Toolbar Buttons

         Delete selected ticket. Also removes related allocations from events.

        Print consignment note

         Email consignment note

        Allocate selected ticket (top grid) to selected event (bottom grid)

         Auto-Allocate unallocated tickets with unallocated events  (experimental)

         Open Track and Trace website (URL specified by courier)

         Open Google maps with address on ticket


Manifest Address tab

Warehouse - Manifest {tab} Address {sub-tab}

The Address tab shows the defaults used when adding a new manifest record.  Hopefully the contents of this tab are self-explanatory. Most fields on this screen may be edited i.e. overwritten from their inherited defaults.


The Barcode panel shows fields that are relevant to printing barcode labels including:

·         showing the sections of address that will be included in the two dimensional barcode

·         presenting service checkboxes that will be stored in the Flags database column(also include in two dimensional barcode)


Manifest Packages tab

Warehouse - Manifest {tab} Packages {sub-tab}

This is where you can enter package quantities against pre-defined package types and generate manifest entries.  There is also a checkbox to print courier labels at the time of generation.

Enter desired quantities against each relevant package and click Generate.  Each line with a non-zero quantity will generate an entry into the Ticket grid on the View tab. When processing concludes the Packages grid is rebuilt with zero quantities and focus moves to the View tab to show the generated entries.

If the Print Labels checkbox is checked then labels will be printed as the generate process progresses.  Labels can also be printed later from the view tab using the toolbar Print Item. This prints labels for the row in focus on the Ticket grid.

Printing of labels requires that a Clarity CLF has been defined for the selected courier in Admin > Couriers > Consignment note.  This defines the label (or consignment note) format to be printed. Dyameta has also supplied a CourierLabel.CLF (and CLS) which can be used as a generic label.

Optional Features

One or more masks can optionally be defined per courier to enable the system to recognise the constituent parts of the scanned con note / ticket. These are then used to populate the columns for Service, Item Count, Package Type, Courier Depot (city). Package types can define weight or cubic.


DUO for EXO     DUO for EXO     © Dyameta Technology Ltd                     Previous Topic           Next Topic           Home