Matrix® WMS CORE+ Product Description

Matrix®
Enter Warehouse
Management
System
Product Description
Release 7.1.0
CORE+
Contents
Introduction ........................................................................................... 3 Batch Management ........................................................................ 150
Business Background ............................................................................. 4 Set Up / Master Data Product Description ......................................... 152
Inbound Product Description ................................................................. 5 Set up / Master Data Overview ...................................................... 152
Inbound Perfect Transaction .............................................................. 5 Facility ............................................................................................ 153
Inbound Option Packs........................................................................ 7 SKU ................................................................................................ 162
Inbound Order Creation..................................................................... 8 Operator ........................................................................................ 170
Receive Inventory ............................................................................. 17 Documents and Reports .................................................................... 173
Putaway............................................................................................ 34 Operational Documents ................................................................. 173
HAZMAT Segregation ...................................................................... 45 Reports Catalogue ......................................................................... 205
Outbound Product Description............................................................ 49 Other Useful Information ................................................................... 271
Outbound Perfect Transaction ......................................................... 49 Picking Strategy Selection Matrix ................................................... 271
Outbound Option Packs .................................................................. 51 Cross Docking ................................................................................ 274
Picking Methods .............................................................................. 52 I2M SMART Solution Integration with Insequence & IFL.............. 276
Outbound Order Creation ............................................................... 54 Co-Pack SMART Solution Integration with Pack Manager ........... 278
Outbound Planning .......................................................................... 66 Integration Overview ...................................................................... 280
Outbound Allocation and Pick Grouping ......................................... 74 Reserved Characters ...................................................................... 285
Outbound Pick ................................................................................. 89 Barcode Parsing ............................................................................. 285
Outbound Load Preparation .......................................................... 103 Archiving Strategy Utilized ............................................................. 285
Outbound Vehicle Despatch .......................................................... 133 Sign Off ............................................................................................. 286
Inventory Management Product Description ..................................... 136 Glossary of Terms .............................................................................. 287
Inventory Management Overview .................................................. 136
Inventory Management Option Packs ............................................ 137
Inventory Relocations ..................................................................... 139
Stock Checks .................................................................................. 142
Inventory Updates .......................................................................... 145
Inventory Adjustments ................................................................... 148
Release 7.1.0 CEVA Matrix® WMS CORE+ Product Description 2

CORE+
Bookmark
Introduction
Quick links to each of the categories are available on the right of each
Introduction page. Click on the relevant icon tab to go straight to the beginning of
Your success is important to us. We want to understand and anticipate the corresponding section.
your needs and help you run smooth supply chain operations. CEVA
fulfils logistic needs of thousands of our contract logistics clients. To Further links are available within the category headers to guide to
maximize benefits, we combined our experience in warehousing and specific parts within the section.
Use the page progression arrows

CORE+ Warehouse Management System (WMS). The system with its at the bottom right-hand corner
proven and standardized processes delivers tangible benefits to our of each page to go to the next
customers in terms of efficiency and reliability over and over again.
or previous page or click on the
This document will provide a comprehensive description of the Home icon to return
functionality available within the Matrix WMS CORE+ product. It to the beginning of
provides a description of capabilities that the system offers, based on the document.
your specific requirements. By completing the grey boxes in this
document a full set of requirements will be captured. After completion,
this document will be signed off by the business and IT. It then is the Throughout the document there are elements that the reader should
input for the configuration of our WMS. complete in order to capture either operational context or decisions
about option packs and set up required. To assist in easily identifying
Once system configuration is complete, this document can be used to these elements, they have a black border and grey background and
validate system functionality. contain a combination of tick boxes, radio buttons and free text fields
(example below). Note that this document must be viewed in Adobe
How to Use This Document Acrobat Reader in order to be able to complete these elements.
This document has been split into the following categories:
Contents Set Up / Master Data

□ Tick Box Radio Button 1 Radio Button 2
Type directly into these fields

Introduction Documents and Reports
Clear Radio Button
Inbound Other Useful Information

If familiar with the Matrix WMS CORE+ Product
Outbound Sign Off
Description, click on the tick box icon at the
beginning of the relevant section to be taken
Inventory Glossary of Terms
directly to the decisions.
Record the required information and select Save within Adobe Acrobat
Reader to save the changes to this PDF document.
CORE+
Introduction
Business Background
The following short section describes at a high level the business that CEVA will perform and provides context to the product description that follows
plus the choices for option packs and set up.
Client Name Number of SKUs and anything Unique or

Noteworthy
Client Name: SKUs:
Client Primary Business Number of Inbound Orders

Client Primary Business: Inbound Orders:
Types of Products Number of Outbound Orders

Types of Products: Outbound Orders:
Facility Country Details on any Seasonality / Fluctuations

Seasonality / Fluctuation
Facility Country:
Profile:
Facility Size Inbound Goods Receipt to Putaway

Inbound Goods Receipt to Duration
Facility Size:
Putaway Duration:
Number of Warehouse Staff and Shifts Outbound Order Creation to Shipping

Covered Outbound Order Creation Duration
Warehouse Staff:
to Shipping Duration:

CORE+
Bookmark
Inbound Inbound Order Creation  Receive Inventory  Putaway  HAZMAT Segregation
Inbound Product Description

Inbound Perfect Transaction
The following high-level process flow describe the key transactions that Matrix WMS CORE+ supports, showing the expected sequence of business
activities.
1 2 3 4 5 6 7 8
Inbound Book In Inbound Unload Unloaded Receive Putaway HAZMAT
Order Vehicle Vehicle Vehicle Inventory Segregation
Creation Arrival Departure
Key:
Matrix WMS Operational

Process Process

CORE+
1. Inbound Order Creation. An inbound order is provided to CEVA.

This can be either new goods for the warehouse or returning goods.
2. Book In. The date and time of the inbound transport arriving is
agreed.
3. Inbound Vehicle Arrival. The vehicle containing the goods on the

inbound order arrives at the warehouse.
4. Unload Vehicle. The goods are unloaded from the vehicle onto the
Receiving Dock.
5. Unloaded Vehicle Departure. Following any cursory checks, the

vehicle is allowed to depart.
6. Receive Inventory. The goods on the receiving dock are positively

identified as being received in the WMS and are prepared for putaway
including applying a putaway TAG label. If the SKU is being received for
the first time, then a new SKU process is followed to capture all
necessary information. For a bonded warehouse, then customs
consignment and Invoice information is captured prior to receiving the
goods. For Handling Units (abbreviated to HU) being received, then a
unique identifier is captured.
7. Putaway. The goods are moved from the receipt dock to their
storage location, adhering to segregation rules if applicable. Goods
with an identified but empty pick face are directed there. Goods with
an identified but occupied pick face are directed to a storage location
based upon proximity putaway logic. Returns are directed to the
Returns Zone. Hazardous Goods are directed to the Hazardous Zone.
For a bonded warehouse, authorization to putaway is received prior to
performing the activity.
8. HAZMAT Segregation. If needed, hazardous goods / HUs are

assessed by a suitably qualified operative and an appropriate location is
selected for storage, prior to relocating the goods / HU to the decided
location.

CORE+
Inbound Option Packs Mobile Printing

Printing of selected operation documents to mobile printers linked to
The applicable option packs are: specific workstation(s).
Bonded Warehouse
The capture of consignment and invoice information prior to receipt; Cross Docking
bonded status upon receipt; store bonded status against inventory; The ability to move inventory from the receiving area to a temporary
identify bonded status per order line and allocate accordingly; approval holding location, post pick activity area or direct to the loading lanes,
to ship; necessary integration flows to / from a Customs Management without the need to put the items into storage. See Cross Docking for
System (CMS). more details.
Trolley Slot Receiving / Putaway DOT Management for Tires

Functionality to support the use of a trolley during pre-advised DOT Management for Tires provides functionality to receive, store,
receiving and putaway. allocate and report on the manufacturing date of a tire as well as the
DOT code (Department of Transportation).
Inventory Segregation
Segregation of inventory by owner or putaway group; identify owner Kit to Stock
per order and allocate accordingly. The ability to define a Kit or Bill of Materials (BOM) where a 'parent / kit
SKU' is made up of one or many 'child / component SKUs', Kit to Stock
enables the building and subsequent putaway of kits into stock.
Handling Unit Only Flow Includes Unkit to Stock capability which enables built kits to be broken
A simple operational flow of packages (not inventory) through the down back into component parts.
facility.
Integration with Co-Pack SMART Solution

Voice Control Matrix WMS CORE+ offers integration with Pack Manager as part of
Eyes free, hands-free voice control of all major mobile device actions -Pack SMART solution.
(Note - requires the use of suitable mobile devices and headsets).
The Pack Manager co-packing tool schedules, controls and manages
co-packing activities to facilitate building of finished goods from
Chaotic Storage component parts. See Co-Pack SMART Solution Integration with Pack
The ability to choose the final putaway location as an alternative to the Manager for more details.
location generated by the putaway algorithm.

CORE+
Inbound Order Creation Guiding Principles

• All goods entering the warehouse must be controlled by either
Diagram an Inbound Order or by using the Returns Receiving feature (to
Inbound Inbound return items previously shipped). This is to ensure a clear audit
Order Book In Vehicle trail and inventory control. Stock adjustments will not be used
Creation Arrival for this purpose; no blind receipts will be allowed.
• The default Inbound Order -
• - WMS to
inform of the pending arrival of goods to be received, which
Inbound contains a header record detailing overall information (e.g.
Order File supplier information) and then line records detailing information
per SKU (e.g. SKU ID, quantity). Whilst ideally one pre-advice
would be received per truck / shipping container and each truck
Inbound
Order Portal / shipping container would only hold one pre-advices worth of
(Form) inventory, this is not always the case. The associated receiving
process that follows is one of capturing actuals against the
Inbound
expected - the information of what has physically been received
Order Portal is identified by the operator.
(Upload) •
pending goods to be received, a header record detailing overall
information is provided with line records (and sometimes sub-
1 records) detailing the exact contents per logistics unit (pallet).
One ASN must match exactly to one truck / shipping container
and the receipt process that follows can be either one of trust,
Inbound with the simple identification of the ASN ID (or if preferred the
Order individual logistics unit), or where the values provided within the
Creation
altered during receipt, a form of receiving is available which
allows the operator to confirm what has physically been received
against what was expected. This confirmation drives the receipt
of the informed goods associated with the logistics unit(s). As
such a robust and accurate supplier is required.
• The concept of a Master Pre-Advice exists where a suitably
identified Pre-Advice (or Purchase Order) can be provided to the
CORE+
WMS (via integration) - Order and the receipt of another, correct Inbound Order. This
Pre-advices of what is expected to be received per inbound must be performed prior to any receipt confirmation / update on
arrival. the Inbound Order.
• In addition to EDI interfacing, CORE+ is API enabled for the • For Bonded Warehouse operations, only the interface can be
creation, update and cancellation of Returns Inbound Orders used for creating Inbound Orders.
and Pre-Advices. Further Inbound Status APIs provide Client • For operations using Kit to Order (Kit to Order Option Pack), Kit
visibility of the current Inbound Order (Pre-Advice and Returns to Stock (Kit to Stock Option Pack) or Bill of Material SKUs, the
Pre-Advice only) status and complete date (if present) SKU expected to be receipted will be the exact SKU stated
• Prior to Inbound Order creation, the SKU must already exist parent SKUs stated will not be broken down into child SKUs
within the WMS. records for receipt.
• Each Inbound Order must have a unique identifying Inbound • If inventory is to be reserved for a specific outbound order then
Order number. the allocation attribute(s) should be populated with a value that
• If not using the Returns Receiving feature (to return previously should be used for matching.
shipped items) returned stock should not be added to the same • Two inbound client specific references are able to be stored
Inbound Order as inbound stock. against an Inbound Order - one provided as part of Order
• Once received / created, an Inbound Order can be changed up Creation, the other captured during receipt.
to the point where it has been received against. • The Inbound Order Interface covers functionality above and
• Inbound Orders can only be cancelled providing nothing has beyond what is provided via the portal form and upload. This is
been received against it. If a cancellation is required and typically related to, but not limited to the option packs.
inventory has been received, then the inventory will need to be • If Interfaces and the portal (form and / or upload) are used, then
reverse receipted first. CEVA will perform the inbound order Receipt Confirmation for Inbound orders from all sources can be
cancellation (upon request from the client) unless the Inbound provided back via interface to the client.
Cancellation API is being used. • The Order Status API enables the inbound order status to be
• A message is able to be sent following the update of the sent from the WMS throughout inbound processing.
An APERAK message is able to be sent confirming successful

• Any alterations to inbound orders after receiving has
creation within the application of the inbound order header and
commenced are required to be dealt with by means of
associated lines not including special instructions.
cancellation and creation of appropriate, new and uniquely
identified Inbound Order(s). Business Description
• For Bonded Warehouse Operations, each Inbound Order • Prior to the capture of receipt an Inbound Order is created.
provided to CEVA needs to match to the physical contents of • It is either created by the Client (or their third Party) or
the bonded consignment received (i.e. not a purchase order). alternatively by the operation following notification.
• For Bonded Warehouse Operations, as changes to Inbound • The Inbound Order (Pre-Advice) will contain the following
Orders are not possible once received, any alterations required information:
must be made through the cancellation of the existing Inbound
CORE+
o The reference that the client is using to identify the o Batch ID (optional, to allow batch validation during
goods on the Inbound Order. inbound receiving)
o The site that the goods will be physically received at. o An indicator to identify if the SKU requires Serial Number
o The client that the goods belong to. validation against the values provided on the Inbound
o The expected due date and time of the goods to arrive Order (requires integration). Validation of the provided
at the site. Serial Number values occurs at the point of receipt.
o An indicator to identify that all the goods on the Inbound
• The Inbound Order (ASN) in addition will contain the following
Order are returns, if appropriate.
information per logistics unit:
o The suppliers name, address and contact details.
o SSCC value that will be used as the TAG ID.
o An Indicator to state it is a Master Pre-Advice (optional o Manufacturing Date (optional)
for use with Master Pre-Advice call off approach) o Expiry Date (optional)
o The VAT Number (if a bonded warehouse). o Batch ID (optional)
o The owner of the goods. o Origin (optional)
o The source / user that created the inbound order o [Valid] Pack Configuration used for the SKU
• Then per SKU (Pre-Advice Line) o [Valid] Pallet Type
o The SKU number and its description. o Serial (optional)
o The quantity expected of the SKU (expressed as eaches).
o The Qty Allocated if using Pre-Allocation as part of the • The Inbound Order number provided is then expected to be
Cross Dock Option Pack quoted / appear on the paperwork that accompanies the goods
into the warehouse for receipt.
o The condition that the goods are expected to arrive in.
o An indicator to identify if the SKU is hazardous or not.
o Supporting Matrix WMS CORE+ Functionality
o Allocation attribute(s) (1 / 2 / 3) for use reserving and The following options exist for providing information into Matrix WMS
matching inventory to outbound orders (optional). CORE+ for Inbound Order creation:
o Manufacturer information (optional for use in the
commercial Invoice). [1.1] Inbound Order via Interface
o An indicator to identify if the SKU requires the capture of Using an interface, it is possible to receive Inbound Orders [both Pre-
Unique Device Identifier (UDI) upon receipt (works in Advice and ASN] into the WMS. Any file conversion necessary from client
conjunction with flag set on SKU). If the product is UDI specific interface formats could be mapped and files converted by the
and serial controlled, then the pre-advice line should be CEVA Integration hub.
split into eaches to ensure that one UDI / serial
combination is captured per each This can be managed Characteristics
within the middleware as applicable (optional).
• Quick and labour free method of Pre-advising CEVA (once
o Inbound Client Reference 1 (captured via integration or
created and tested).
web portal) (optional).
• Removes potential for keying errors.
CORE+
• Ideal for operations with medium to-high volumes. • Simple and clear tool, with appropriate validation and control of
• Is the most functionally rich of the three options, enabling the use options and selections.
of all option packs and validated options • Ideal for operations with lower volumes and / or clients that are
unable to integrate systems.
The interface is defined in the Standard MIG document and the • Can be used in conjunction with the other methods mentioned
associated mapping document for Matrix WMS CORE+. Note that all
for situations such as Returns Inbound Order creation when the
-
clients systems does not have this ability; or a quick start up
Whereas inbound orders that are created via API
-S-21*.01-1.0.0- situation whilst the final system integration is being developed.
Additionally, if an embargoed country of North Korea, Syria, Cuba or Iran • Not compatible with the following Option Packs:
is passed the order will fail to load. o Bonded Warehouse
o Cross Docking
When Inbound Order information is passed to the WMS is will be
From the Portal form, the following will be created:
attempted yet an Inbound Order record already exists, the information Inbound Order Header
will be re-tried as an UPDATE action. Similarly, if an UPDATE is
attempted yet no inbound order record exists, the information will be • Either the Inbound Order number can be keyed in or a unique
re-tried as an ADD action. Inbound Order number can be selected to be generated by the
portal.
Inbound orders created via interface may contain special instructions • Client ID will be selected.
that can be presented to the operator at the point of receipt (if using
• Site ID will be selected.
the mobile device). Instructions can be held at both header and line
• Owner can be selected.
level.
• Inbound Order Status can be selected.
If using the Integration with Co-Pack SMART Solution Option Pack, • Due date and time are entered.
Inbound Orders will be created via ASN from Pack Manager to inform • Return indicator is to be used if the goods on the Inbound Order
the WMS of the finished (or returning component) SKUs. See Co-Pack are returns if not using the Returns Receiving feature for
SMART Solution Integration with Pack Manager for more details. previously shipped items
•
[1.2] Inbound Order from Portal (Form) reference number.
Using the CEVA Web portal, it is possible to create inbound orders [Pre- • The User ID of the person that created the Inbound Order will
Advice only] (one at a time) by entering the information into a form. be captured.
• Carrier name is entered.
Characteristics
• Carrier reference is entered.
• Available for use via the internet (in a secure manner) by clients • Supplier name, address lines 1 and 2 (optional), Town (optional),
as well as internal for CEVA colleagues. County (optional), Postcode (optional) and Country (optional) are

CORE+
entered. Note that the embargoed countries of North Korea, [1.3] Inbound Order From Portal (Upload)
Syria, Cuba and Iran are not able to be entered. Using the CEVA Web portal, it is possible to upload a document in a
• Supplier Contact name (optional), Telephone number (optional) pre-defined format to capture the information for multiple inbound
and email address (optional) are captured. orders [Pre-Advice only].
Then per Inbound Order Line Characteristics
• SKU will be selected from those already in the system • Available for use via the internet (in a secure manner) by clients
• Description will be automatically populated for the SKU as well as internal for CEVA colleagues.
selected. • Simple and clear tool, with appropriate validation to ensure that
• Tracking Level will be selected to match the lowest UoM the Inbound Orders are created correctly.
• Quantity will be entered at the lowest UoM • Ideal for operations with low-to-medium volumes and / or clients
• Condition code to be allowed to be selected if the returns that are unable to integrate systems easily but can generate
indicator has been set on the header; otherwise then the code suitable documents (in the required format). It should be noted
that the format may be subject to change as enhancements are
• Allocation Attribute (1 / 2 / 3) can be populated with up to three added to the product.
reservation references which will be held on the inventory record • Can be used in conjunction with the other methods mentioned
once received into the warehouse (the outbound order line must for situations such as Returns Inbound Order creation when the
match the attributes identically in order to allocate the reserved systems does not have this ability (or the Returns
inventory). Receiving feature is not being used for previously shipped
• If the SKU selected has a HAZMAT ID then the HAZMAT items); a quick start up situation whilst the final system
description will be automatically populated. integration is being developed.
• Batch ID which will be validated at the point of receipt.
Using the Portal upload, as a minimum the same fields will be captured
• Inbound Client Reference 1 where a client specific reference is as per the form.
required to be stored against an Inbound Order.
Upon upload to the portal of the document, the file is validated and any
Upon creation the inbound order has its source / User stamped upon it issue are identified back to the operator for correction and re-
that generated it (WPI-[portal username, logistics id for CEVA internal or submission of the whole file.
Inbound
Order Number is displayed to the operator and an email of details is Upon successful creation, each order Header will have the source / user
sent to the email address for the login. WPI-[portal username, logistics id for CEVA
internal or e

CORE+
Exceptions Exception / Failure Activity Required

Exception / Failure Activity Required Name and Description
Name and Description client and notified to CEVA. CEVA then
Inbound Order fails to Web Portal: Any incorrect population assess if the Inbound Order is at a
load of field will be identified to the suitable status for cancellation. If so the
operator by the web portal. The required ACTION report is run, (which
operator is then expected to correct one is dependent on the Inbound
appropriately. Order Type)
Note: Following cancellation, the
Web Portal to WMS: If the failure Inbound Order ID cannot be reused
occurs when processing the Inbound
Order by the WMS then a Service desk If using the Inbound Cancellation API,
call will be placed by the operation for the Client is able to cancel the Pre-
support to investigate and resolve the Advice or Returns instruction whilst it is
issue by checking connectivity and at status Released or Hold.
interface errors.
Interface conversion / movement: If Inbound Order is An inbound order may be amended if

the failure occurs as part of the required to be it has yet to be received against.
middleware conversion and move, then changed / added to. Note: if using the Bonded Warehouse
a service desk call will be placed for Option Pack then the received SKUs
support to investigate (potentially with and quantities must exactly match what
the relevant apps support teams) and is stated on the Inbound Order
resolve the issue.
Inbound Order is An inbound order may be amended if
Interface load by WMS: If the failure required to be it has yet to be received against. If the
occurs as part of the WMS load of the changed - reduction Inbound order must be amended, then
inbound order, then record(s) will be the inventory will need to be reverse
written to the interface error table for receipted first.
resolution by the operation Team Alternatively if chosen, or if receiving
Leader. Note that the embargoed has already started the Inbound Order
countries of North Korea, Syria, Cuba may be received short and then the
and Iran are not able to be entered and Inbound Order is updated to
if appear will cause the interface to fail
to load. Note: if using the Bonded Warehouse
Option Pack then the received SKUs
Inbound Order If not using APIs, the cancellation of an and quantities must exactly match what
Cancellation Inbound Order is identified by the is stated on the Inbound Order
CORE+
Exception / Failure Activity Required

Name and Description
Inbound Order Line If the inbound order line and hence the
states a different received inventory states a different
allocation attribute to allocation attribute to what is physically
what is physically on stated on the goods, then the client
the inventory should be contacted and the correct
value(s) determined.
If what appears on the physical product
is incorrect, then as guided by the
client amend what is physically
displayed on the product(s), leaving the
inventory record as is.
If what is held on the inventory record

is incorrect, update the allocation
attribute(s) using the inventory update
function, leaving the physical product
as is.

CORE+
Inbound Order Creation Decisions (for configuration / Set up)

• Will the facility be a bonded warehouse (and as such the □ Client Specific Interface [Client format mapped to the
CEVA Standard Message Master Pre-Advice] (for use
Bonded Warehouse Option Pack is used)? If so, then only Pre-
advices as the Inbound Order via an interface can be used. with the Pre-
[select one] receipt process only)
□ Yes (available as part of the initial site configuration □ Portal Upload Pre-Advice (for use with the positive
confirmation receipt process only)
not able to be applied retrospectively)
□ No □ Portal Form Pre-Advice (for use with the positive

confirmation receipt process only)
• How will the inbound orders be provided to Matrix WMS

CORE+? [select one or many]
□ CEVA Standard API (Inbound Create)
□ CEVA Standard Interface ASN

• If Portal uploads are used, who will be using it? [select one or
□ For Delivery / UPI Receiving
many]
□ For Tag Receiving

□ CEVA Employees
□ CEVA Standard Interface Pre-Advice (for use with the

□ Client Employees
positive confirmation receipt process only)
□ Other 3rd Party
□ CEVA Standard Interface
with the Pre-
Master Pre-Advice (for use
receipt process only) • If the Portal form is used, who will be using it? [select one or
□
many]
Client Specific Interface [Client format mapped to the
CEVA Standard Message ASN] □ CEVA Employees
□ For Delivery / UPI Receiving □ Client Employees
□ For Tag Receiving □ Other 3rd Party
□ Client Specific Interface [Client format mapped to the

CEVA Standard Message Pre-Advice] (for use with the
positive confirmation receipt process only)

CORE+
• On successful creation of the inbound order, is the "APERAK

Confirmation of Successful interface (generated from □ Complete
□
the WMS to the middleware layer) required to be sent? [select
one] Cancelled
□ Yes •
□ used? [select one]
□
No
Yes
• Get Status Inbound Order
to be used to view current inbound status and complete date (if
present)? [select one]
□ No
•
□ Yes
On cancellation of an Inbound Order, is an Inbound Order
interface (EDI extract generated from
the WMS to the middleware layer) required to be sent? [select
□ No one]
• □ Yes
used? [select one]
□
□
No
Yes
□ No
• If yes, which message is required? [select one or many]
□ PAHCANCELLED (Pre-Advice)
• Is the "Inbound Order Status API (S-244 POST)" interface
(generated from the WMS to the middleware layer) required □ UPICANCELLED (UPI)
□
to be sent? [select one]
□ No
ASNCANCELLED (ASN)
□ Yes, when the Inbound Order Header changes to the • Is Unique Device Identifier (UDI) capture required? [select one]
following statuses [select one or many]:
□ □ Yes
□
Hold
Released
□ No
□ In Progress Inbound Order Creation Section Complete

CORE+
Receive Inventory Guiding Principles

• Where required, it is possible to capture and store per Inbound
Diagram Order the actual date and time of arrival at the facility, as well as
the "target stock time" (the duration from point of inbound
Unloaded
order arrival at the facility until all associated receipt and
Receive
Vehicle
Departure
Inventory
Putaway
putaway activity is completed).
• The Dock Scheduler feature can be utilized for the planning and
communication of vehicle arrivals.
Customs
Receipt
Processed
• -
confirmation receipt process will be followed. The operator will
6.1 6.2 6.3 6.4 6.5 6.6 6.7 6.8 capture information pertaining to the inventory physically in
Create Create Link Identify Capture Capture Confirm Pre- C&E
front of them for the inventory record (only inheriting the SKU
C&E C&E Consignment Inbound C&E Receipt Advice Consignment
Consignment Invoice & Invoice Order Receipt Information Completion Completion
and referenced Pre-Advice).
Bon de d Warehouse Only Bon de d Warehouse Only Bon de d Warehouse Only
Information
Bon de d Warehouse Only Bon de d Warehouse Only
• - re a positive
Customs
Receipt
Label
Receipt
Confirmation Pre-advice. The operator will capture information pertaining to
the inventory physically in front of them for the inventory record
(only inheriting the SKU and referenced Pre Advice).
• two receipt processes
are available;
o Trusted Receipt - by capturing the Logistics Unit
Identifier (TAG) the information on the inbound order will
be trusted and inherited by the inventory record. For a
more streamlined receiving process all logistics units can
be received by simply capturing the ASN ID.
o Positive Confirmation Receipt by capturing the
Logistics Unit Identifier (TAG) the information on the
inbound order will be presented and is editable. When
positively confirmed it is inherited by the inventory
record.
• Inventory will only be confirmed as available (received) once it
has been receipted and putaway.
• Inventory will only be available to be allocated to orders once it
has been receipted and putaway (pre-allocation of cross dock
inventory is available if using the Cross Dock Option Pack).
CORE+
• Serial number(s) can be captured (dependent upon the serial • Returns Receiving can be completed for items previously
capture profile being used) this is information capture only and shipped, without the need for a pre-advised Inbound Order.
does not drive any processing or rules. Serial number validation • A Warehouse Dashboard is available alongside the WMS which
is required against the values sent on the Inbound Order (if the provides a real-time, single view of key metrics including
relevant flags are set against the SKU and Pre-Advice Line). outstanding inbound move tasks.
• A Batch ID is able to be captured and this may be validated
Dock Scheduler
against the Inbound Order if provided.
• A Unique Device Identifier (UDI) reference is able to be captured The Dock Scheduler feature provides the ability to plan and
(dependent upon the SKU and Pre-Advice Line set up) this is communicate vehicle arrivals.
information capture only and does not drive any processing or
The following inbound booking types can be created and amended:
rules. WMS CoE guidance is that RDT receiving is used to
receive UDI managed products, to provide the best operator • Pre-Advice
workflow. • UPI
• Forced capture of DOT code at receipt can be set if using the • Delivery
DOT Management for Tires Option Pack.
• One inbound client reference is able to be captured during The Booking Status will automatically update as the status of the
receiving and stored on the inventory record. inbound order changes. Manual updates to the Booking Status is also
• Trolley Slot receiving and putaway is available if using the possible and if required, a notification can be sent to the client at each
Trolley Slot Receiving / Putaway Option Pack. change in booking status.
• When receiving Mixed Group Pallets, care should be taken to For each Dock Scheduler booking, a log of included Pre-Advices / UPIs
not utilize SKUs that have pick faces set up or to mix hazardous / Deliveries is generated. This log can be interfaced via the middleware
and non-hazardous SKUs. Mixed group pallets should be used layer for each Pre-Advice / UPI / Delivery that is subsequently added.
for dark stores / long term storage only.
• Asset Recording provides the ability to record the count of pallet Using the Dock Door feature it is possible to link receiving locations to a
types received in or shipped out and the additional option to specific dock door and a range of standard Dock Scheduler reports are
capture individual Asset IDs at Receipt and Vehicle Loading. available from within the Reports menu.
• A message is able to be sent confirming that "Warehouse Receiving Cross Dock Inventory
Inbound activity had commenced" per pre-advice once the
receipt activity has begun. This message will be generated when If using the Cross Dock Option Pack the operator will be informed that
the Pre-Advice what they are receiving is cross dock inventory that does not require
header information only. putaway into storage. This may result in the operator segregating
• A message is able to be sent following the update of the inventory at the point of receipt depending on the type of Cross
omplete Docking being used.

CORE+
SKU Labels Business Description Positive Confirmation Receiving

• For sites wishing to receive on paper before updating the WMS,
SKU Labels are able to be used where goods are not labelled, or are
a Pre-Advice Receiving Sheet can be manually produced. The
labelled incorrectly. The following labels are available in both standard
document supports paper based receiving (non GUI / RF) for
and bespoke versions (bespoke versions if using the Flexible
Pre-
Documents Option Pack):
the manual capture of necessary information, whilst also
• Pre-Receive SKU Label manually printed prior to receipt providing a prompt to resolve SKU related information if not
• Inbound SKU Label automatically printed at receipt, and able present.
to be manually reprinted using the Reports function • For Operations using Master Pre-Advices, a Pre-Advice will be
• Outbound SKU Label automatically printed at allocation, and -advice upon
able to be manually reprinted using the Reports function notification of what is expected to be received. This Pre-advice
will then be used to receive against.
The SKU Labels value against the SKU record is used to specify if the
• Following unloading of the vehicle or container onto the dock,
SKU Labels should print per EACH or per TAG.
the goods are broken down / (re-)palletized from their travel
Asset Recording configuration if required. The goods present are also checked
against what was expected as stated on the associated Inbound
This feature provides the ability to record the count of pallet types Order(s) Pre-Advice(s).
received in or shipped out, against a Supplier / Delivery address. may be used to help determine key activities to be performed
Updated at Receipt and Vehicle Loading, the asset count is visible in such as new SKU, High Risk SKU and External test results
the WMS Asset Tracking screen. required processing.
Once enabled, this feature also provides the ability to track unique • Bonded Warehouse Option Pack: Prior to receipt of the goods,
Customs Consignment and Invoice information is captured.
the Pallet Type (held on General 2 tab). Once this flag is set, the Asset • Each pallet of goods is received, capturing information to
ID is required to be captured during Receipt and Vehicle Loading. identify the SKU, the Inbound Order it matches to, the quantity
and pack configuration received, and its attributes.
Use the Asset Details screen to view all information relating to each • If using the Trolley Slot Receiving / Putaway Option Pack, the
individual asset. Team Leaders and above can switch to Maintenance specific trolley pallet type and receiving location must be
Mode to manually create assets if required.
entered during receipt.
Returning empty assets is possible using the Asset Return feature. •
Confirmation Process, as each logistics unit is received, the
Note that Asset Recording is not compatible with Delivery Receiving. information on the Inbound Order is reviewed and amended as
required. The received inventory will be a single SKU on a tag.
• Note that for SKUs that form part of a kit (Child SKU), the receipt
will be of the SKU stated in the inbound order no conversion

CORE+
from parent SKU to the component child SKUs (Kit to Order and • The Asset Recording feature can be enabled if the count /
Kit to Stock Option Packs). tracking of pallet types / assets is required.
• The received pallets of goods will be either:
o Single SKU on a tag. The tag (and its contents) is
destined to be putaway into a single location.
Business Description Streamlined Trusted Receiving
o Multiple SKUs on a pallet. The pallet (and its contents) is • For use with extremely mature and accurate inbound orders /
destined to be putaway into a single location per SKU suppliers to allow for an even quicker inbound process.
(hence multiple locations). • After arrival of the inbound vehicle, the ASN is received in one
o Multiple SKUs on a pallet. The pallet (and its contents) is go and then the labels printed for the whole ASN.
destined to be putaway into a single location. • The labels are matched to the inventory tipped from the vehicle.
o Handling Unit Only Flow Option Pack: A single package • Note: If a pack configuration is not specified on the Inbound
is received to be put away to a single location. Order Line, the WMS will determine the pack configuration to
o Trolley Slot Receiving / Putaway Option Pack: single or use. Where there are more than one pack configurations linked
multiple SKUs on a trolley destined for a single location to a SKU, the main pack configuration to use as default must be
zone (a slot may only contain one TAG/SKU) set.
• Special instructions will be presented to the operator if held • The Asset Recording feature is not compatible with Streamlined
against the inbound order header or line(s). Trusted Receiving.
• If a GS1-128 compliant label for the goods is not provided and
used, the Putaway TAG label is produced and applied.
Supporting Matrix WMS CORE+ Functionality
• Bonded Warehouse Option Pack: As an inbound order has its
[6.1] Create C&E Consignment
receipt completed, the Customs Management System is
informed (if integrated). Via a PC only
• The Asset Recording feature can be enabled if the count / Prior to receipt of bonded goods, a Customs and Excise (C&E)
tracking of pallet types / assets is required.
key Customs related information for the Consignment of goods that are
about to be received.
Business Description Trusted Receiving
• The vehicle or container is unloaded onto the dock. The Information Comment / Description
logistics units (pallets) present are also checked against what was
expected as stated on the associated Inbound Order ASN.
C&E Consignment System generated (Mandatory). The unique
• Each logistics unit is received, capturing the identifier. This is
ID system generated reference for the
expected to be a GS1-128 compliant label.
consignment being received / declared. A
• The received pallets of goods will be a single SKU on a pallet. sequential number with a prefix of the C&E
The pallet (and its contents) is destined to be putaway into a
single location.

CORE+
Information Comment / Description Information Comment / Description
consignment prefix which is the same for the Date Mandatory. Select the date this consignment
whole WMS instance. record was registered on.
Receipt Type Mandatory. This should always be Time Optional. Select the time this consignment
"Bonded/LCP". The value selected here record was registered on.
determines the field names used for certain
fields (to make it easier to identify from the Document Number Mandatory. Used to capture the document
official document what data to enter). number - typically this is the Movement
Reference Number (MRN).
C&E Status Mandatory. The consignment is created at the
status of "Released". Note that later on once Document Type Mandatory. The Type of document received
all goods have been received and linked (along and that the Document number applies to (e.g.
with the invoice[s]) the status will be changed to MRN). Selected from the pre-populated list of
"Complete". Document type set up per country and
validated as part of initial set up with the site.
Owner ID Mandatory. Used to indicate the receipt of
stock for a particular owner (if there is only a Identity Of Optional - but strongly recommended for
single owner for the client then the value will Transport interfacing to Customs system.
default).
Expected Collis Optional.
C&E Consignor Optional. Details of the Shipper.
Collis Counted Optional.
CWC Optional. Country Whence Consigned.
Seals OK? Optional capture of Y/N.
Document Date Optional. Select the date the document was
created if desired. Mode of Transport Optional.
(border)
Document Time Optional. Select the time the document was
created if desired.

CORE+
[6.2] Create C&E Invoice Information Comment / Description

Via a PC only
Prior to receipt of bonded goods, a Customs and Excise (C&E) Invoice TOD Place Optional The Terms of Delivery place.
must be created that captures key Invoice related information for the Strongly recommended for interfacing to
consignment of goods that are about to be received. Customs system.
Invoice Value Optional - but strongly recommended for

interfacing to Customs system.
Information Comment / Description
Invoice Currency Optional - but strongly recommended for

Consignment ID Mandatory. The unique reference for the
consignment being received / declared and
that the invoice relates to.
Freight Cost Optional.
Line ID Optional. Normally left blank, this can be

Freight Currency Optional.
populated with a unique line if you wish to
enter each line of invoice information. This will
mean that each line will require linking in the Insurance Cost Optional.
next step; however it does allow for flexibility of
splitting invoices if needed (not recommended). Insurance Currency Optional.
C&E Invoice Mandatory. The unique reference for the Other Costs Optional.
Number invoice being entered.
Other Currency Optional.
Invoice Date Mandatory.
Invoice Time Optional. [6.3] Link Consignment and Invoice

Via a PC only
Terms of Delivery Optional - but strongly recommended for
The relevant Inbound Order(s) and Invoice(s) are now linked to the
Consignment for the goods that are about to be physically received.
Typically this should be a single Inbound Order and a single Invoice.
However the system allows for many Inbound Orders, many invoices or
even just some Pre-Advice lines of a Pre advice to be linked to a
consignment.
CORE+
[6.4] Identify Inbound Order - Pre-Advice ID [mandatory]

Pre-Advice / Positive Confirmation receiving Pre-Advice and Lines: Via - SKU ID [mandatory]
a PC (not using supplier affixed GS1-128 compliant labels on single SKU - Expiry Date [conditional on SKU / optional]
pallets) - Batch [conditional on SKU / optional]
- Manufacture date [conditional on SKU / optional]
Using the Basic Receiving function on the PC, the relevant Inbound
Order is entered / searched for. The relevant line is searched for if
there is only one line on the Inbound Order it is automatically identified. Pre-Advice / Positive Confirmation receiving Pre-Advice and Lines: Via
a Mobile Device (using supplier affixed GS1-128 compliant labels on
single SKU pallets)
Pre-Advice / Positive Confirmation receiving Pre-Advice and Lines: Via
a Mobile Device (not using supplier affixed GS1-128 compliant labels Using the GS1-128 receiving function on the mobile device, Barcode 1
on single SKU pallets) from the GS1-128 label is scanned. The Pre-Advice Receive function is
now displayed with the values identified in the barcode already
Using the Pre-Advice Receive function on the Mobile Device, the populated. Valid values that can be used (with the appropriate
Inbound Order number is captured. The Client ID, Inbound Order ID application identifier) are:
and Notes are displayed.
- Pre-Advice ID [mandatory]
The SKU ID is captured to identify the line being received. Special - SKU ID [mandatory]
instructions will appear if held against the Pre-Advice Header or Line(s). - Expiry Date [conditional on SKU / optional]
The Client ID, Inbound Order ID, Line ID, Notes, SKU ID, SKU - Batch [conditional on SKU / optional]
Description, Serial number(s) and Batch ID (if provided on the Inbound - Manufacture date [conditional on SKU / optional]
Order),
inventory that is the same SKU that you wish to handle together] are
displayed for the line. Pre-Advice from Master Pre-Advice(s) / Positive Confirmation receiving
Pre Advice and Lines: Via a PC (not using supplier affixed GS1-128
compliant labels on single SKU pallets) (not suitable for Bonded
Pre-Advice / Positive Confirmation receiving Pre-Advice and Lines: Via Warehouse Option Pack)
a PC (using supplier affixed GS1-128 compliant labels on single SKU
As the Master Pre-Advice (Purchase Order) cannot be received against,
pallets)
-Advices from the Master
Using the GS1-128 receiving function on the PC, Barcode 1 from the Pre Advice to use.
GS1-128 label is scanned. The Pre-Advice Receive function is now
The Team Leader will select the master Pre-Advice, then create a copy
displayed with the values identified in the barcode already populated.
of the header information as the call off Pre-Advice with a new Pre
Valid values that can be used (with the appropriate application
identifier) are:
then selected from master Pre Advices and duplicates are created on

CORE+
the Pre-advice of lesser quantity. Receiving then proceeds as described ASN / Trusted receiving Unique Pallet Identifier (UPI): Via a Mobile
for Pre-Advice / Positive Confirmation receiving Pre Advice and Lines. Device (not suitable for Bonded Warehouse Option Pack)
ASN / Positive Confirmation Receiving Tag Receiving: Via a PC (not Receipt of individual ASN pallets:
suitable for Bonded Warehouse Option Pack)
Using the UPI Receive function on the Mobile Device, the Unique Pallet
Receipt of individual ASN tags: Identifier [SSCC barcoded value on the Pallet] is captured. Special
instructions will appear if held against the UPI Header or Line(s).
Using the Tag Receiving function on the PC, the Tag is captured.
The Client ID, Inbound Order ID, Qty Due, Tracking Level, SKU, Pack
Config, Pallet Type, Expiry Date, Batch ID and Serial (if supplied) are ASN / Trusted receiving ASN Receipt: Via a PC (not suitable for
displayed. Bonded Warehouse Option Pack)
Receipt of an entire ASN (and all associated pallets):

ASN / Positive Confirmation Receiving Tag Receiving: Via a Mobile
Using the Delivery Receiving function on the PC, the ASN ID is entered
Device (not suitable for Bonded Warehouse Option Pack)
/ searched for.
Receipt of individual ASN tags:
Note: If a pack configuration is not specified on the Inbound order Line
Using the Tag Receive function on the Mobile Device, the Tag is the WMS will determine the pack configuration to use. Where there are
captured. more than one pack configurations linked to a SKU, the Pack Config
Setting screen should be used to identify the default pack configuration
The SKU, Quantity, Tag ID, Pallet Type, Expiry Date, Batch ID and Serial to use when receiving.
(if supplied) are displayed.
Note that the Delivery Management Screen can be used to view the
ASNs provided and the associated UPIs.
ASN / Trusted receiving Unique Pallet Identifier (UPI): Via a PC (not
Note that the facility to receipt whole ASNs (Delivery Receiving) in one
suitable for Bonded Warehouse Option Pack)
transaction is not provided within the mobile device application.
Receipt of individual ASN pallets:
Using the UPI Receiving function on the PC, the unique Pallet Identifier [6.5] Capture C&E Receipt information
[the SSCC barcoded value on the Pallet] is entered / searched for. Via PC or Mobile Device for Pre-Advised Receipts only
Note that the Delivery Management Screen can be used to view the Update the Customs and Excise screen / fields as needed, altering the
ASNs provided and the associated UPIs. Country of Originator and Under Bond Status if needed (these are
defaulted in from the SKU). Note that the C&E Consignment number
and CE Invoice number will be populated from the linking done
previously.
CORE+
[6.6] Capture Receipt information be putaway to a different location (based upon the putaway
Note: that this step does not apply to ASN trusted receipts as all the algorithm). If the mixed pallet flag is ticked AND the group
information for the inventory is inherited from the interface data. putaway flag is ticked, then all the TAGs on the pallet will be
Additionally no Putaway TAG label is produced; instead the GS1-128 putaway to a single location (based upon the putaway algorithm
label on the logistics unit (pallet) is used, with the SSCC barcoded value for the first TAG / product placed onto the pallet).
(bottom most barcode on the label) used as the TAG. • [capture] Inbound Client Ref 2 if a client specific reference is
required to be held on the inventory.
• [capture] Unique Device Identifier (UDI) if required for the
Via a PC for Pre-Advised Receipts only identification of medical devices within the healthcare supply
chain.
Update the General Line details screen, entering / selecting the • [capture] Asset details if using the Asset Recording feature the
number of pallets received, per type should be entered. If
tracking individual asset IDs these should be entered into the
of inventory that is the same SKU that you wish to handle together). The Individual Asset Capture screen.
default option is to receive a quantity of a single SKU that is up to one
pallets worth that will be putaway to a single location. Next the TAG number received against is displayed and the option
to continue receiving from against the Inbound Order is available
If appropriate, the following can be capture / changed to match the (returning you to step 6.4) or to finish receiving. The Putaway TAG
physical goods: label is printed (see example below and Operational Document
• [change] Pack Configuration Descriptions section for more details) based upon the printing set
• [capture] Origin (if set on the SKU not to be used in place of up configured (see facility set up). The Putaway TAG label includes
COO as part of the Bonded Warehouse Option Pack) two TAG barcodes, allowing for the label to be applied wrapping
around the edge of a pallet and hence scanned from two different
• [alter] Condition (if the goods are not in prime condition)
sides if desired. Additionally, the label includes the putaway zone,
• [capture] Notes (stored against the inventory record)
subzone and aisle allowing for presorting at the edge of the receipt
• [capture] Expiry Date (if appropriate for the SKU)
dock if desired. A High Risk SKU indicator will be displayed across
• [capture] Manufacture Date (if appropriate for the SKU) the label (left section) if the SKU is indicated as such.
• [capture] Batch ID (if appropriate for the SKU)
• [capture] Serial Numbers (if appropriate for the SKU and the
serial capture profile / for the Handling Unit Only Flow Option Via PC for ASN / Positive Confirmation Receiving
Pack used to uniquely identify the package)
• [capture] Mixed Pallet flag and with Pallet ID field used to Following the review of the pre-populated ASN data, any necessary and
indicate when multiple SKUs are being received onto a single permitted amendments are made. The Receive to Location, and the
pallet. quantity received are captured.
• [capture] Group Putaway flag if the mixed pallet flag is ticked
but the group putaway flag is NOT ticked, then each TAG will
CORE+
Example Standard Pre-Receive SKU Label (bespoke version available if Example Standard Inbound SKU Label (bespoke version available if
using the Flexible Documents Option Pack) using the Flexible Documents Option Pack)
Example Putaway TAG label

Example Pre-Advice Receiving Sheet

CORE+
Via a Mobile Device for Pre-Advised Receipts only - NOT using the • [capture] Asset details if using the Asset Recording feature the
Trolley Slot Receiving Option Pack number of pallets received, per type should be entered. If
tracking individual asset IDs these should be entered into the
Continuing within the Inbound Order Receipt function enter the
Individual Asset Entry screen.
Quantity of the unit of measure that is being received (followed by the
appropriate character(s) of the unit of measure), the Pallet Type and The Putaway TAG label is automatically printed (see previous example)
Receiving Location. based upon the Printing setup configured. This may be to a fixed
printer, a locality based printer or a mobile printer (if using the Mobile
If appropriate, the following can be captured / changed to match the
Printing Option Pack) - see facility set up.
physical goods:
• [change] Pack Configuration

• [capture] Condition (if the goods are not in prime condition) Via a Mobile Device using the Trolley Slot Receiving / Putaway Option
• [capture] Origin (if set on the SKU not to be used in place of Pack
COO as part of the Bonded Warehouse Option Pack)
The Trolley Slot Receiving / Putaway Option Pack varies to the standard
• [capture] Batch (if appropriate for the SKU)
• [capture] Expiry Date (if appropriate for the SKU)
• [capture] Manufacture Date (if appropriate for the SKU)
• [capture] Mix (Mixed Pallet Flag - used to indicate when multiple After confirming the good received the Sortation Putaway Screen will
SKUs are being received onto a pallet). allow the operator to specify the Pallet ID (Trolley) and Slot number the
• [capture] Grp (Group Putaway flag if the mixed pallet flag is goods are being received to.
ticked but the group putaway flag is NOT ticked, then each TAG Controls are in place to ensure:
will be putaway to a different location (based upon the putaway
algorithm). If the mixed pallet flag is ticked AND the group • inventory destined for different Location Zones cannot be
putaway flag is ticked, then all the TAGs on the pallet will be received to the same trolley
putaway to a single location (based upon the putaway algorithm • no mixing of Hazmat and Non-Hazmat SKUs on the same trolley
for the first TAG / product placed onto the pallet). • no more than one Tag in a single trolley slot
• [capture] Pall (captures the Pallet ID being received onto when
using mixed or grouped pallets)
• [capture] Serial Numbers (if appropriate for the SKU / Handling Via a Mobile Device for ASN / Positive Confirmation Receiving
Unit Only Flow used to uniquely identify the package)
Following the review of the pre-populated ASN data, any necessary and
• [capture] Inbound Client Ref 2 if a client specific reference is
permitted amendments are made. The Receive to Location is captured.
required to be held on the inventory.
• [capture] Unique Device Identifier (UDI) if required for the
identification of medical devices within the healthcare supply
chain (if appropriate for the SKU and Pre-Advice Line)
CORE+
[6.7] Confirm Inbound Order Completion Exceptions

Via a PC only Exception / Failure System Activity Required
For the Bonded Warehouse option pack, the Inbound Order will not Name and Description
automatically get updated to complete when Inbound Order has been Inbound Order is See exceptions in the Inbound Order
received in its entirety (unlike the normal flow). Instead it is required to required to be Creation section.
cancelled / changed /
be set manually, to allow the operation to check the information is
added to / reduced.
correct prior to any interfaces being passed to the customs
management system (in an integrated solution). Inbound Order The Team leader will use the Inbound
Using the Pre-Advice Management screen, the status is changed from Number is not stated Order Header Query screen to search
the paperwork for the Inbound Order number to use.
accompanying the The search will likely be performed
confirmation interface.
goods to be received against one or many of the following
piece(s) information:
• Address,
[6.8] C&E Consignment Completion
• Due Date,
Via a PC only • Supplier Reference.
For the Bonded Warehouse option pack, once customs have accepted
the inbound declaration / processed the receipt, the goods are allowed New SKU identified Any new SKUs following Go Live are
to be put away. Whilst this is possible via an interface, the C&E notified (along with all relevant
information) to CEVA.
The Inbound Order Creation screens
Consignment Management screen.
from the CEVAWeb Portal used for
Inbound Order Header and Line
creation will only allow the use of known
[6.9] Returns Receiving SKUs. Any new SKUs must be created
Via a PC only using either:
• New SKU form on the portal
Returned items that have previously been shipped may be returned • New SKU upload on the portal
using the Returns Receiving feature. • SKU interface
The items to be returned are entered / searched for. The quantity to
SKU receipt for the Upon first receipt of a SKU, it will not be
return (per line) is entered and the printing of tag labels is able to be
first time able to be received until the physical
specified.
details of it have been checked and the
system updated if appropriate.

CORE+
Exception / Failure System Activity Required Exception / Failure System Activity Required
Name and Description Name and Description
The SKU Maintenance screen will be set within the Pack Config Setting
used to remove the new SKU flag and screen.
enter / validate the details captured for Damaged Stock For Pre-Advice / Positive confirmation
weights and Dimensions. identified at receipt receipts: As the stock is received, the
condition code is changed to
If the Bonded Warehouse option pack is
being used then the Customs SKU directed to the QA zone for detailed
interface is generated passing the new checks to be performed as needed and
SKU information to the Customs a decision to be made as to what to do
management System. with the inventory.
SKU Details are Upon discovery of incorrect SKU details, For ASN / Trusted receipts: Immediately
required to be the details are then changed. following receipt of the stock. The
changed The SKU Maintenance screen will be condition of the inventory is changed to
used to change the SKU details.
New Pack Upon discovery of a new Pack be moved to the QA zone for detailed
Configuration Configuration for a SKU, the new checks to be performed as needed and
identified configuration is created and linked to a decision to be made as to what to do
the appropriate SKU. with the inventory.
The Pack Configuration and Pack Returns Stock As the stock is received (or after receipt
Configuration linking screens are used identified at receipt for ASN / Trusted receipt process), the
to set up the new pack Configuration. (via an Inbound Order
Unable to receive ASN If a pack configuration is not specified and not using the if it is not already set as that condition
using the Trusted on the Inbound order Line the WMS will Returns Receiving from the Inbound Order (this is the
Receipt process due determine the pack configuration to feature for previously typical way). The Putaway will then be
to pack configuration use. shipped items) directed to the Returns zone for detailed
discrepancies checks to be performed as needed and
Where there are no pack configurations a decision to be made as to what to do
set against the SKU, a new pack with the inventory.
configuration must be created and Additional Stock As additional stock is identified
linked to the SKU before receiving can identified at receipt (typically once all other items on the
occur. Inbound Order have been received) the
client / supplier is notified. If agreed
Where there are more than one pack with the client, an additional Inbound
configurations linked to a SKU, the Order is then created as needed.
default configuration to use must be Note: all inventory that is the liability of
identified with the Main Pack Config flag CEVA must be stated on the system.
CORE+
Additionally when operating a bonded Putaway TAG Label The Label is reprinted using the reprint
warehouse all inventory received must not printed function.
be stated to customs.
If the Portal is being used for Inbound

order creation, then the CEVA Web
Portal is used for Inbound Order Header
and Line creation.
Missing Stock As missing stock is identified (typically
identified at receipt once all other items on the Inbound
Order have been received) the client /
supplier is notified. If agreed with the
client The Inbound Order is then set to
Complete.
Note that for a Bonded warehouse an
alternative approach may be taken to
cancel the Inbound Order and provide
another correct one.
Receipt of Hazardous The receipt of hazardous items will be
items notified to the operator from
information captured against the
Inbound Order, on the paperwork
accompanying the items and physically
on the items themselves. Upon receipt
the Putaway TAG Label produced will
show that the items are hazardous.
Following Receipt of the Hazardous

inventory, the Putaway guides the
operator to the Hazardous zone in-stage
area. The relocates the inventory to a
suitable location within the Hazardous
zone and confirms placement there.
Incorrect Receipt Once identified the receipt is reversed
and then performed correctly.

CORE+
Receive Inventory Decisions (for configuration / Set up) • If using the Dock Scheduler feature, do you require the Booking Log
• Is the Pre-Receive SKU Label required? [select one] Interface (from the WMS to the middleware layer)? [select one]
□ No □ Yes
□ Yes [select one]: □ No
□ Standard Pre-Receive SKU Label
□ Bespoke Pre-Receive SKU Label (Flexible Documents • How will receiving be performed? [select one or many]
Option Pack)
□ On a PC
• Is the Dock Scheduler feature required to be used? [select one] □ On a mobile device without Voice
□ Yes □ On a mobile device with Voice
□ No
• Is the Trolley Slot Receiving / Putaway Option Pack required? [select
one]
• If using the Dock Scheduler feature, do you require the Booking
Status Update Interface (from the WMS to the middleware layer)? □ Yes
[select one]
□ No
□ Yes, for the following statuses:
□ Cancelled • Will single SKU or mixed SKU (or both) pallets be received onto the
system? [select one or many]
□ Scheduled □ Single SKU Pallets
□ Pending □ Mixed SKU Pallets (suitable for Long term storage only, only
□ In Progress for use with Pre-Advised / Positive Confirmation receiving)
□ Complete • Are Special Instructions required to be presented on the mobile

□ No device during receiving (available for Pre-Advised and UPI Receiving
and requires integration) ? [select one]
□ Yes
□ No
CORE+
• Is the Cross Dock Option Pack required to be used? [select one] • Is the Inbound SKU Label required? [select one]
□ Yes, for Flow-Through Cross Docking □ No

□ Yes, for Pre-Allocation Cross Docking □ Yes [select one]:
□ Yes, for full pallet SSCC Cross Docking □ Standard Inbound SKU Label
□ No □ Bespoke Inbound SKU Label (Flexible Documents
Option Pack)
• Is the DOT Management for Tires Option Pack required to be used?
[select one]
• For Pre-Advised / positive confirmation receiving of pallets of single
□ Yes SKUs only with GS1-128 compliant labels, which application
□ No identifiers will be used in addition to SSCC ID [00], Pre-Advice ID

[400] and GTIN barcode [01 or 02]? [select one or many]
• Is the Asset Recording feature required to be used (not compatible

□ Not required
with Delivery Receiving)? □ [10] Batch/Lot
□ No □ [11] Manufacture/Production Date
□ Yes [select one]: □ [15] Best Before Or Best By Date
□ To capture count per pallet type □ [16] Sell By Date
□ To capture count per pallet type AND individual asset □ [17] Use By Or Expiry Date
IDs
□ [240 / 241] SKU ID
• Will a WMS generated Putaway TAG label be used or unique (for the
site) pre-printed labels? [select one]
• Is the Putaway TAG label required? [select one]
□ Not required as GS1-128 compliant label will accompany □ No
the logistics unit (pallet of single SKU only or ASN / Trusted
Receipt)
□ Yes (specify printer requirements within the Printer Data
□ WMS Generated Putaway TAG Label (Pre-Advised / Positive Take on Spreadsheet)
Confirmation receiving only)
□ Unique pre-printed labels used (Pre-Advised / Positive

Confirmation receiving only)

CORE+
• If using the Bonded Warehouse Option Pack, do you require the

Customs Receipt Interface (from the WMS to the middleware layer)?
[select one]
□ Yes, triggered from the manual update of the Pre-Advice

□ No
• If using the Bonded Warehouse Option Pack, do you require the
Customs SKU Interface (from the WMS to the middleware layer)?
[select one]
□ Yes, triggered from the receipt of SKUs.

□ No
• Is the "Warehouse Inbound Activity Commenced" interface (EDI
extract generated from the WMS to the middleware layer) required
□ Yes
□ No
Receive Inventory Section Complete

CORE+
Putaway Guiding Principles

• Putaway location will be directed by the system.
Diagram • The putaway location is determined at the point of receipt so to
allow putaway via either the use of paper and PC or a mobile
device. Additionally it allows for pre-sorting on the receipt dock
Receive HAZMAT if desired. If using the Kit to Stock Option Pack the putaway
Putaway location is determined at the point the putaway activity is
performed.
• If using the Cross Dock Option Pack, received inventory will not
require putaway to storage.
• The Beam Weight Distribution and Pallet Type Consideration
feature ensures the consideration of the maximum weight
7.1 7.2 distribution and / or variable width pallets across a racking
beam.
• Identification of HAZMAT is against a SKU. This will only drive
Identify Perform the putaway to the Hazardous zone and nothing else. Detailed
Putaway Putaway storage, proximity or handling rules for HAZMAT will not be
controlled by the system, hence HAZMAT putaway will be
directed to an instage within the Hazardous zone from which a
qualified operator can move the inventory to a suitable location
(within the Hazardous zone).
• Return goods (by condition code) can be identified as the goods
Receipt are received, against Inbound Order Lines or against the
Confirmation
Outbound Order Lines (Qty Returned) if using Returns
Receiving. This will only drive the putaway to a location in the
Returns zone and nothing else. Detailed processing rules for
returns will not be controlled by the system.
• Damaged goods, goods for disposal, return to supplier,
retention sampling required, external testing results required,
FMD processing required, identified for destruction, isolation (by
condition code) can be identified against Inbound Order lines or
as the goods are received. This will only drive the putaway to a
location in the QA zone and nothing else. Detailed processing
rules for returns will not be controlled by the system.

CORE+
• Where sampling is required, inventory is able to be directed to Business Description

be putaway to a sampling area. The following Business Description applies to non-cross docked
• Note that for component / child SKUs that will go on to form inventory.
part of a kit, the putaway will be of the SKU stated in the
• The inventory to be putaway is located in the receiving dock and
inbound order - no conve
the unique inventory identifier (TAG) is captured.
or parent SKU (Kit to Order and Kit to Stock Option Packs).
• The location to take the goods / pallet to is informed to the
•
operator. The ability for the operator to choose the final location
will occur from parent SKU to the component child SKUs. The
is available if using the Chaotic Storage Option Pack.
generated putaway task will be for that of the built kit, (Kit to
Stock Option Pack). • The pallet is moved to the putaway location
• A message is able to be sent confirming the completion and • The pallet / goods stated are placed in the location, the TAG (if
putaway of Inbound Orders. appropriate) and the location confirmed
• A Warehouse Dashboard is available alongside the WMS which • Receipt confirmation is provided back to the client, either on an
provides a real-time, single view of key metrics including activity-by-activity basis following putaway or for the whole
outstanding inbound move tasks. Inbound Order (once complete).
If multiple SKUs are being putaway to different location (as indicated

when receiving the goods) then the above last four steps are repeated
for each location that requires to be putaway into.
The default putaway logic used to decide upon the location to place
the goods is as follows:
• If a Hazardous Flag is set, then direct the putaway to the

Hazardous Zone;
• If the condition is identified as Returns, then direct the putaway
to the Returns Zone;
• If the condition is identified as Retention Sampling Required,
then direct the putaway to the Retention Sampling Zone;
• If the condition is identified as External Testing Results Required,
then direct the putaway to the External Testing Zone;
• If the condition is identified as FMD Processing Required, then
direct the putaway to the FMD Processing Zone;
• If the condition is identified as Destruction, then direct the
putaway to the Destruction Zone;

CORE+
• If the condition is identified as Isolation, then direct the putaway between the pickface location for SKU algorithm and the pickface
to the Isolation Zone closest location (fanned putaway) algorithm.
• If sampling is enabled against the SKU or Address, then as
When assessing each suitable location as part of the putaway logic, the
determined by the frequency set, putaway will be directed to
following steps are taken, in the following order/sequence:
the Sampling area
• If the condition is identified as QA Hold, Damaged whilst in Per Location identified -
CEVA Care, Damaged by non CEVA Party, Disposal or Return to
• If using the Beam Weight Distribution and Pallet Type
Supplier, then direct the putaway to the Quality Assurance Zone;
Consideration feature, the Best Fit Beam Storage by Zone and
• If the condition is identified as Inspection, then direct the
Sub-Zone algorithm will determine the putaway location.
putaway to the storage zone identified against the SKU based
• If not using Beam Weight Distribution and Pallet Type
upon fan putaway logic from the pick face; If no pick face is
Consideration:
identified for the SKU (i.e. Dummy SKU for full pallet operations)
1. Does the location already include inventory (not applicable if
then direct the putaway within the identified zone for the SKU,
Top up being used)?
as close to the outbound Shipping Docks as possible.
2. Does the pallet footprint (width and depth) of the pallet used for
• If there is no inventory for the SKU in the pick face or storage,
the TAG fit in the location?
then direct the putaway to the pick face identified for the SKU;
3. Does the height of the inventory fit in the location?
• Else direct the putaway to the storage zone identified against
4. Does the weight of the inventory set against the SKU and
the SKU based upon fan putaway logic from the pick face; If no
physical pallet fit within the remaining weight allowance for the
pick face is identified for the SKU (i.e. Dummy SKU for full pallet
location?
operations) then direct the putaway within the identified zone
5. Does the volume of the inventory fit in the remaining volume for
for the SKU, as close to the outbound Shipping Docks as
the location?
possible.
• If there are outstanding outbound order lines identified for Pro If all of the above are identical and multiple locations are found:
Rata Allocation, then the putaway will be directed to the
6. Putaway sequence defined in the Location Data Take On (DTO)
PRORATASTAGE location.
is used to find an appropriate location
• If the putaway algorithm does not identify a suitable location
then it will be directed to a non-conformance area to alert the As such the following recommendations are offered
operator to resolve the issue.
• Location Volume should be set to the actual volume of the
By default the location searched for is an empty location; if top up of location minus a portion allowed for a pallet (or the media to be
storage and pick face locations is desired then the Inventory used) and any dead space requirements.
Segregation Option Pack must also be used. • Location Height should be set to the actual height of the
location minus any dead space requirement.
If desired the Manage Stackability feature can be enabled. Note that
• Pack Configuration TAG volume should be set to the volume of
the Block Stack best fit algorithm (predict on current receipt) sits in
a full pallet of the inventory, excluding any pallet.
CORE+
• Pack Configuration volume at eaches tick box should be set. ii. Look for generic storage by just entering the location
zone
If the Inventory Segregation Option Pack is used, then inventory is able
to be segregated by either owner or putaway group in one of the
following ways: If using the Inventory Segregation Option Pack, Team Leader access to
Putaway Group Linking provides the ability to override the stated SKU
1. Strict Segregation putaway group at a site level for multi-client sites.
a. The warehouse would need to be entirely subzoned
b. Each owner or putaway group would have a dedicated Managing Stackability
subzone(s)
c. Each owner or putaway group would have 1 rule per sub zone • Stackability controls can be set against a location and a SKU
that the product should be stored in This specifically has to
state that owner or putaway group x is putaway to a specific
subzone, or subzones if multiple are to be used
• When assessing a putaway for a full pallet of the applicable
2. Preferred segregation using prime and alternative zones (fully
zoned warehouse) location and then determines the maximum number of full
a. The warehouse would need to be entirely sub-zoned pallets of the applicable SKU that can fit into that location.
b. Each owner or putaway group would have a primary subzone, • s the number of full pallets of the SKU
but other zones could be used
c. For each owner or putaway group, algorithms would need to be
reduces the total calculated capacity of that location by that
created to direct product per zone, in order (i.e. 1st subzone A /
number of pallets.
owner or product group specific algorithm could look at specific • Two options are available:
subzones, but then to look at any remaining subzones we could o Predict on Current Receipt: The current receipt, that
state on the algorithm Location zone, plus add a wildcard (*) is pre-advice or trailer, is used looked at and the
into the subzone number of pallets is calculated.
d. Multiple owners or putaway groups could be putaway to the o Predict on Future Receipts: The pre-advices are
same subzone if required looked at to determine how many are likely to be
required. The number of days to look ahead is
3. Owner or putaway group segregation, plus generic bulk storage defined by the Best Fit Future Receipt Days field
a. The warehouse would have specific sub zones for owner or (Hold & Released).
putaway group segregation, plus generic storage within a • Note that Stackability cannot be used with the Trusted
standard location zone
receipt Process but is compatible with Pre-Advice and Tag
b. For each owner or putaway group the rules would work as
Receiving.
follows:
i. Look for a specific zone and subzone

CORE+
Beam Weight Distribution and Pallet Type Consideration DOT Management for Tires
This feature ensures the consideration of the maximum weight The DOT Management for Tires Option Pack provides added control of
distribution and / or variable width pallets across a racking beam. the maximum number of mixing days of manufacture date for the global
putaway algorithm and mixing control of DOT code (Allocation
The process involves the following:
Attribute 3) in the grouped putaway algorithm (requires use of Inventory
• Pallet Type is assigned a 'Beam Units' value Segregation Option Pack).
• Beam Maintenance holds the 'Beam ID' and beam weight
capacity Putaway of Cross Dock Inventory
• Location is assigned a 'Beam ID' and the number of 'Beam Units'
that would fit on it If using the Cross Dock Option Pack, received inventory will not require
putaway to storage. Depending on the type of Cross Docking being
During Receipt the WMS reviews pallet type Beam Units and runs the used inventory may be either putaway to a temporary Cross Dock Flow-
Best Fit Beam Storage by Zone and Sub-Zone Putaway Algorithm. The Through Zone or directed to a Post Pick Activity Zone or Ship Dock.
WMS identifies available putaway locations based on beam position
capacity and weight tolerance for the entire beam.
The Beam Maintenance screen can also be used to view a map of Free [7.1] Identify Putaway
Space for any beam.
Via a Mobile Device
Chaotic Storage
If using the Chaotic Storage Option Pack, an operator is able to guide (scanned or keyed in) that is
the final putaway to an alternative location (within a designated, pre- TAG ID, Client, SKU ID, quantity (with pack configuration hierarchy),
defined zone) than the one generated by the putaway algorithm. The SKU Description and Zone are displayed.
range of other locations is controlled by other conditions such as a limit
of the quantity of that SKU that can exist in the desired location, the Via PC
range of hazmat material, the mix of colors, sizes or styles of goods in
the location.
searched and the putaway tasks that are desired to be put on a single
ASN (Trusted Receipt) Putaway list are selected. The Move Task List will then be produced, with the
Default WMS functionality allows one operator to putaway from a pallet Task List ID also displayed on the screen (See below for an example and
at a time, however it is possible to apply the ability to allow multiple the Operational Document Descriptions section for more details).
operators to putaway TAGs from the same pallet available for goods
received using the Delivery / UPI Receiving flows.

CORE+
[7.2] Perform Putaway • Hazmat:

Via a Mobile Device Standard Putaway o If the putaway inventory has a Hazmat ID then existing
inventory must have the same Hazmat ID
o If putaway inventory does not have a Hazmat ID then
to and placed into the stated location. If the option has been selected, existing inventory must also not have a Hazmat ID
the TAG is captured and validated. If the location has a check-digit • Number of SKUs (not eaches) is less than the max set against the
value, then it is captured and validated. SKU
If any of the above is false then it is not a valid location and the
Via a Mobile Device Trolley Slot Receiving / Putaway (Trolley Slot
appropriate error message is displayed and the operator is returned
Receiving / Putaway Option Pack)
to enter a new location.
trolley and SKU are captured
If a location cannot physically
and the following information is displayed:
should be used.
• To Location (putaway location to take goods to)
• Quantity to putaway
• Tag Via PC
• Slot (the trolley slot number the inventory was received to)
Following the completion of the putaway activities as stated on the
• Pallet (trolley)
Upon confirming the putaway the operator should confirm the Tag or the system. The List ID is entered, the operator who performed the
the Slot the inventory is being taken from. If the putaway location has a tasks is captured, and the tasks completed are confirmed.
check-digit value, then it is captured and validated.
Additional Information
Via a Mobile Device Chaotic Putaway (Chaotic Storage Option Pack)
view all non-completed moves by leaving the search criteria empty. If
-
zone and the operator has the option to override with the actual
allowing for progress to be monitored and to aid with the direction of
location being used. Validation of the location is completed:
work.
• Is the location empty? If not;
• Existing inventory is not the same style
• Existing inventory is not the same colour if either size or style are Receipt Confirmation
the same; if size and style are different then the colour can be If using the positive confirmation receiving process, the Receipt
the same Confirmation interface can be provided after each putaway activity is
• Existing inventory is not the same size performed (per TAG) or once the whole Pre-Advice is set to complete
CORE+
and all receipts are now putaway, confirming all the TAGs in the Example Move Task List used for Putaway
process.
Matrix® WMS CORE+
For trusted receipts, the Receipt Confirmation interface is sent per TAG
(pallet / UPI) and can either be provided after each TAG is putaway or if
required, after the entire pallet / UPI is putaway.
It should be noted that the impact of not completing all putaway

activity prior to the stock snapshot interface being sent to the client
could lead to misinterpretation as inventory that has been received yet
has not been putaway will appear on the stock snapshot, yet will not
have been confirmed as received yet.
Sampling
Sampling of received inventory is available and controlled through the

QC Sample Frequency set against either:
• SKU number of TAGs received before sampling

• Address number of inbound orders received before sampling
A default value can be set against the Client which will be applied to
new addresses with a blank QC Sampling Frequency.
Following receipt, product is directed to be putaway into the sampling

area the location determined by the sampling type specified.
Product is held with a lock code until sampling is completed within the
Sampling web screen. During this process the next sampling action is
able to be set, for example, Disposal, Putaway.

CORE+
Exceptions Exception / Failure System Activity Required

Exception / Failure System Activity Required Name and Description
Name and Description • PC: Inventory Query
Putaway Algorithm The team Leader determines where it
Fails to determine should be and then physically relocates
location is backed out of and the issue is it to there.
investigated and resolved, prior to re- Fail Putaway location Following the location being identified
attempting Putaway. not useable as not usable, the Team Leader only (not
operator) uses the Location
digit that will not be shared with the Maintenance screen to change the lock
operation. This is so that the location
cannot be used and hence inventory Putaway task is then re-attempted,
getting stuck here or losing the ability to directing the pallet to another, usable
reverse receipt if needed. location.
Fail Putaway - Size The Team Leader (not operator)
accesses either the Mobile Device or PC Override of Putaway Not allowed.
screens for SKU and Location queries to location directed to
check the information to determine desired
what is wrong and needs correcting:
• Mobile Device: Inventory Query Non Mobile Device Putaway of goods is performed on the
• Mobile Device: Location Query Putaway (RF Failure /
• Mobile Device: Pack Config non availability) generate and print the
Query
• PC: Inventory Query
• PC: Location Query performed.
• PC: Pack Config Query
Move Task List Generation:
Once corrections have been made, the
Putaway process is then re-run. • Putaway task Type is selected to
narrow the search to relevant
Fail Putaway The inventory found in the location is
records
unexpected inventory removed and the Pallet is putaway as
in location directed. • Move tasks are selected that are
The Team Leader (not operator) uses desired to appear on a single
either the Mobile Device or PC screens list. SKU, From location and To
for inventory queries to check the location will be used to guide
correct location for the removed selection
inventory: • A Move task list ID is displayed
• Mobile Device: Inventory Query on the screen as the list is

CORE+
Exception / Failure System Activity Required Putaway Decisions (for configuration / Set up)
Name and Description • Is a receipt confirmation interface required? [select one]
created and the Move task list is
printed. □ Yes, CEVA Standard EDI Message
□ Yes, CEVA Standard API Message
Move Task List Completion:
□ Yes, Client specific message (CEVA Standard Message
mapped to a client format)
• The Move Task List ID is entered
• The operator who performed □ No
the tasks is captured and the
tasks performed confirmed. • If yes, which message is required?
For Pre-Advice / Positive Confirmation Receipt [select one]
The Putaway location directed to is
controlled by the standard Algorithms
and the Fan Putaway profile set up.
□ Confirmation per TAG Putaway (and per whole Inbound
Order received and putaway) (default type)
□ PALPUTAWAY (triggered following each putaway

task)
□ PAHPUTAWAY (triggered following Pre-Advice

completion and putaway of all inventory)
□ Confirmation per whole Inbound Order received and

putaway (carries risk of misalignment with stock snapshot if
open inbound order have been partially putaway at the time
of the snapshot running)
□ PAHPUTAWAY (triggered following Pre-Advice

completion and putaway of all inventory)
□ Confirmation per whole Inbound Order received and

complete (required for Bonded Warehouse Option Pack)
□ PAHCOMPLETE (Pre-Advice)
Continued on

CORE+
For ASN / UPI Receipt (both Trusted and Positive Confirmation • Is ASN (Trusted Receipt) Putaway with Multiple Operators required?
Receipt) [select one or many] [select one]
□ Confirmation per UPI Putaway (default type) □ No (default option)

□ UPIPUTAWAY (triggered following UPI completion
□ Yes
and putaway of all inventory)
• Is the Chaotic Storage Option Pack required to be used? [select
□ Confirmation per TAG Putaway (for multi-line UPIs) one]
□ No
□ UPLPUTAWAY (triggered following TAG completion □ Yes
□ Confirmation per ASN Putaway • Is Top-up of Storage and / or Pick Face locations required? [select
□ ASNPUTAWAY (triggered following ASN completion one]
□ No (default option)
□ Yes, (must also have Inventory Segregation Option Pack)

□ Confirmation per TAG Received (carries risk of misalignment
with customer if received TAGs have not yet been putaway
at the time of confirming the receipt to the customer and if • Is the Manage Stackability feature required to be enabled? [select
receipts are reversed) one or many]
□ UPICOMPLETE (triggered following UPI completion) □ No (default option)

□ Yes:
□ Confirmation per ASN Received (carries risk of misalignment □ As part of Global algorithm
with customer if received TAGs have not yet been putaway
at the time of confirming the receipt to the customer and if
receipts are reversed) □ As part of the Inventory Segregation Option Pack
□ ASNCOMPLETE (triggered following ASN • Is the Beam Weight Distribution and Pallet Type Consideration
completion)
feature required to be enabled? [select one]
□ Yes
CORE+
• Is a positive confirmation of the TAG being putaway required? • Voice Control

[select one] one]
□ Yes, (note this should not be used when using mixed, □ Yes
grouped Pallets, however may be used for mixed Pallets)
□ No
• Is sampling required to be completed? [select one]
• Is inventory segregation required per owner or/and putaway group?
[select one or many]
□ Yes
□ Per Owner □ No
□ Per Putaway group • Which type of segregation will be used? [select one]
□ No □ Strict
•
□ Preferred
□ Generic
If so, what are the owners or/and putaway group values?
Enter owner(s) and / or putaway group(s)

□ Other, as requested (please state logic to be used below for
validation and acceptance)
State logic here
<Enter owner(s) or/and putaway group(s)>
<State logic here>
□ Yes A4 sized output

Putaway Section Complete
□ Yes US Letter sized output
□ No
CORE+
HAZMAT Segregation Guiding Principles

• Detailed storage, proximity or handling rules for HAZMAT will
Diagram not be controlled by the system; a qualified operator will assess
and move the inventory to a suitable location (within the
Hazardous zone).
Receive HAZMAT •
Putaway code rules to move inventory to either the QA or returns areas.
The safe storage of HAZMAT items takes precedence; however
locations specifically identified for use for HAZMAT QA and
HAZMAT Return goods can be set up within the HAZMAT area.
Business Description
8.1 8.2 8.3 •
•
The goods to be relocated to their storage location are located
in the HAZMAT in-stage.
A qualified operator assesses the inventory and using the
Determine Identify Perform operational storage and handling rules appropriate for the
Suitable Relocation Relocation goods, determines a suitable location (within the Hazardous
Location zone).
• The unique inventory identifier is captured.
• The pallet is moved to the suitable location that has been
determined.
• The pallet / goods are placed in the location determined and
the location confirmed.
[8.1] Determine Suitable Location

Assessment is performed and a suitable location is decided for the
inventory.
[8.2] Identify Relocation

Via a Mobile Device

CORE+
Client, SKU ID, Quantity (with pack configuration hierarchy), SKU Exceptions
Description and Zone are displayed. Exception / Failure System Activity Required
Via PC
Putaway Algorithm
Using the Stock Relocation screen, the TAG received to the in-stage is Fails to determine
identified and the location to relocate the inventory to is entered. The location is backed out of and the issue is
investigated and resolved, prior to re-
is searched and the attempting Putaway.
relocation tasks that are desired to be put on a single list are selected.
The Move task List will then be produced, with the Task List ID also digit that will not be shared with the
displayed on the screen. operation. This is so that the location
cannot be used and hence inventory
[8.3] Perform Relocation getting stuck here or losing the ability to
Via a Mobile Device reverse receipt if needed.
Fail Putaway - Size The Team Leader (not operator)
Continuing to use th
accesses either the Mobile Device or PC
and placed into the stated location. If set up, the check-digit of the screens for SKU and Location queries to
location relocated to is captured. check the information to determine
Via PC what is wrong and needs correcting:
• Mobile Device: Inventory Query
Following the completion of the relocation activities as stated on the
• Mobile Device: Location Query
• Mobile Device: Pack Config
the system. The List ID is entered, the operator who performed the Query
tasks captured, then the tasks completed are confirmed. • PC: Inventory Query
Alternative using Inventory Segregation Option Pack • PC: Location Query
Alternatively to what is stated in this section, the order segregation
Once corrections have been made, the
option pack can be used instead to control the direction of Hazmat Putaway process is then re-run.
inventory to normal storage and pick faces based upon putaway group / Fail Putaway The inventory found in the location is
owner if desired (instead of directing to the HAZMAT in-stage). This unexpected inventory removed and the Pallet is putaway as
does not - like the default Hazmat functionality - provide product mixing in location directed.
/ placement rules. The Team Leader (not operator) uses
either the Mobile Device or PC screens
for inventory queries to check the
correct location for the removed
inventory:

CORE+
The team Leader determines where it Move Task List Completion:
should be and then physically relocates • The Move Task List ID is entered
it to there. • The operator who performed
Fail Putaway location Following the location being identified the tasks is captured and the
not useable as not usable, the Team Leader only (not tasks performed confirmed.
operator) uses the Location
Maintenance screen to change the lock The Putaway location directed to is
controlled by the standard Algorithms
Putaway task is then re-attempted, and the Fan Putaway profile set up.
directing the pallet to another, usable
location.
Override of Putaway Not allowed.
location directed to
desired
Non-Mobile Device Putaway of goods is performed on the
Putaway (RF Failure /
non availability)
performed.
Move Task List Generation:

• Putaway task Type is selected to
narrow the search to relevant
records
• Move tasks are selected that are
desired to appear on a single
list. SKU, From location and To
location will be used to guide
selection
• A Move task list ID is displayed
on the screen as the list is
created and the Move task list is
printed.

CORE+
HAZMAT Segregation Decisions (for configuration / Set up) • If Yes, What Return locations are required within the HAZMAT
• Will Hazardous goods pass through the facility? [select one] zone?
□ Yes
State HAZMAT Returns Locations here
□ No
• If Yes, what QA locations are required within the HAZMAT

zone? <State HAZMAT Return Locations here>
State HAZMAT QA Locations here
• Voice Control
Putaway? [select one]
□ Yes
<State HAZMAT QA Locations here>
□ No
HAZMAT Section Complete

CORE+
Bookmark
Outbound
Outbound Order Creation  Planning  Allocation and Pick Grouping  Pick  Load Preparation  Vehicle Load  Vehicle Despatch
Outbound Product Description

Outbound Perfect Transaction
The following high-level process flow describes the key transactions that Matrix WMS CORE+ supports, showing the expected sequence of business
activities.
1 2 4 5 6 7 8 9 10
Outbound Outbound Allocation Pick Load Outbound Vehicle Vehicle Outbound
Order Planning & Pick Preparation Vehicle Load Dispatch Vehicle
Creation Grouping Arrival Departure
3 Key:
Book In
Matrix WMS Operational
Process Process

CORE+
Outbound
Outbound Order Creation. An outbound order is provided to CEVA. Vehicle Load. The orders are loaded (in sequence if specified and
This can be for goods for delivery, returns to suppliers, goods for positively confirmed) onto the outbound vehicle. For a bonded
disposal, goods for emergency delivery and goods for collection. warehouse, a commercial invoice is obtained and a declaration made.
Once approval is received then the dispatch can occur.
Outbound Planning. Orders are grouped into consignments and
prioritized (if needed) based on when, how and with whom they will Vehicle Despatch. The vehicle manifest is produced and the vehicle is
leave the warehouse. This is performed either automatically based captured as despatched.
upon information provided on the outbound order or manually
controlled by the operation. Outbound Vehicle Departure. The outbound vehicle containing the
orders departs site.
Book In. The date and time of the outbound transport arriving is
agreed.
Allocation. Inventory is allocated to outbound order demand. Non

expiry-controlled goods are allocated on a FIFO basis; expiry-controlled
goods are allocated on a FEFO basis. For a bonded warehouse, the
bonded status of goods allocated matches that specified on the order;
if no status is specified then specific rules are followed to match the
appropriate status to the destination country first. For Handling Units /
Packages, then the unique identifier specified on the order is matched
to for allocation.
Pick. Single Orders, multiple Orders or lines of products are picked per
operative - either split by zone or across the facility and dependent
upon the pick grouping applied. The picked goods / HUs are then
taken to the stated activity zone or ship dock. Replenishment of pick
faces is triggered automatically from a minimum quantity in the pick
face being reached, or manually if triggered by an operator.
Load Preparation. If required VAS, repacking, consolidation or

bundling is performed after picking. This post pick activity is performed
in assigned areas as identified on / from the order. Shipping labels and
documents are produced as needed.
Outbound Vehicle Arrival. The outbound vehicle that will transport

the goods of the outbound orders arrives.

CORE+
Outbound
Outbound Option Packs Kit to Order

The ability to define a Kit or Bill of Materials (BOM) where a 'parent / kit
The applicable option packs are: SKU' is made up of one or many 'child / component SKUs'. Ordering
the parent SKU explodes the BOM into the child lines on the order.
Cross Docking
The ability to move inventory from the receiving area to a temporary Pick to Trolley / Slot
holding location, post pick activity area or direct to the loading lanes, The ability to enable the picking and sorting of a number of orders
without the need to put the items into storage. See Cross Docking for separately, but within the same pick run.
more details.
Locus Cobots
DOT Management for Tires Native integration framework and WMS capability to support the use of
DOT Management for Tires provides functionality to receive, store, Locus Cobots to facilitate the picking process.
allocate and report on the manufacturing date of a tire, stored as an
Allocation Attribute and stated in a week-year combination (DOT code). Geek+ Goods to Person
Native integration framework and WMS capability to support the use of
Pick Grouping Geek+ Goods to Person robots to facilitate the picking process
Pre-defined or custom-built grouping logic (subject to validation and
acceptance) to group pick tasks. Push of Pick Tasks
The ability for the system to push tasks to operators removing the
Order Grouping and Prioritization requirement to log into a specific task list and eliminating the need for
The ability to identify the consignment and drop sequence per order; paper pick lists.
identify the priority per order. [Note this requires integration and is not
possible for use via the portal] Mobile Printing
Printing of selected operation documents to mobile printers linked to
Automatic Allocation and Pick Grouping specific workstation(s).
The ability to automatically run the system allocation process and pick
grouping of pick tasks. Reducing operational intervention and reducing Replenishment Runs
the time from the order being received to being ready to pick.
to be picked for replenishment in a single run, before being deposited
SKU Substitution into the final pick face locations.
The ability to mark a SKU as a substitute that can be used as an
alternative in the event of an allocation shortage. One-Piece Flow
The ability to identify a tracking level within a pack configuration that is
Volumetric Determination for Picking considered to be of suitable design that it can be shipped in its existing
The WMS ability to calculate the type and number of containers packaging.
required prior to picking, based on a volumetric assessment.

CORE+
Outbound
Integration with CEVA Packing Application Kit to Stock

The ability to integrate with the CEVA Packing Application as an The ability to define a Kit or Bill of Materials (BOM) where a 'parent / kit
alternative to using the native WMS repacking functionality. SKU' is made up of one or many 'child / component SKUs', Kit to Stock
enables the building and subsequent putaway of kits into stock.
Post Pick Activities Includes Unkit to Stock capability which enables built kits to be broken
The ability to identify the activity zone or specific, fixed activity location down back into component parts.
for an order to be routed to following pick. Within an activity zone
packing, VAS, or when separation of order is needed for other activities Integration with I2M SMART Solution
can be performed. [Note this requires integration and is not possible for Matrix WMS CORE+ offers integration with Insequence and IFL as part
use via the portal].
drives the picking of parts in the right order at the right time to meet
Follow Me Logic production line demand and IFL manages the final distribution of
The ability to ensure that all of an order ends up in a single activity zone factory parts and the subsequent return of assets. See I2M SMART
location, regardless of one or many inventory pick path(s). Solution Integration with Insequence & IFL for more details.
Retailer Compliant Shipping Labels Integration with Co-Pack SMART Solution
The bespoke design of labels created in a format specified by the Matrix WMS CORE+ offers integration with Pack Manager as part of
Retailer to aid in their inbound receiving process. -Pack SMART solution.
Flexible Documents The Pack Manager co-packing tool schedules, controls and manages
The ability to provide a client focused layout for delivery notes and co-packing activities to facilitate building of finished goods from
packing lists. [Note that if used, Flexible Delivery Notes and / or component parts. See Co-Pack SMART Solution Integration with Pack
Packing Lists will replace the standard versions. See the Flexible Manager for more details.
Documents Spotlight Document for more information].
Handling Unit Only Flow
Post Pick Grid Sortation A simple operational flow of packages (not inventory) through the
Improvements to the batch picking and sortation activities completed facility.
within the WMS, providing simplified process flows to drive
productivity. Voice Control
Eyes free, hands free voice control of all major mobile device actions
Bonded Warehouse (Note requires the use of suitable mobile devices and headsets).
The capture of consignment and invoice information prior to receipt;
bonded status upon receipt; store bonded status against inventory;
identify bonded status per order line and allocate accordingly; approval Picking Methods
to ship; necessary integration flows to / from a Customs Management
System (CMS). [Note this requires integration and is not possible for use Decisions on configuration will be driven by the chosen method(s) of
via the portal] picking. Throughout the document, the following methods will be
referred to:
CORE+
Outbound
Full Pallet Picking the picking of full pallets. and / or there are a number of extreme dimensions on products
hence the volumetric version of this method cannot be used.
• Why use Full Pallet Picking? When you have sufficiently large
volumes of a SKU required for an order line that you would end Pick & Pack with Volumetric Assessment the two-step process of
up picking full pallets of a SKU frequently. As such it makes picking inventory into containers that have been volumetrically
more sense in terms of operational efficiency to pick these determined and then repacking separately.
directly from bulk storage rather than pick from a pick face and
• Why use pick & pack with volumetric assessment? When you will
then have to also replenish.
be picking one order at a time, the order once picked will
Pick-Pack the picking of inventory into its final shipping containers. require further activity (post pick activities) and you have a lots of
different container sizes (with no real extreme single dimension
• Why use pick-pack? When the entirety of an order will be sizes on products) so wish to tell the operator which container
picked in one pick run (not multiple) directly into the shipping size to use. Getting the container size correct is more important
container; the order size is also sufficiently large that a trolley during pick (better pack efficiency), than picking lots of broadly
wouldn't be used. Additionally, multiple picking methods are to correct container sizes and then re packing (better pick
be used for the site and / or there are a number of extreme efficiency).
dimensions on products hence the volumetric version of this
method cannot be used. Picking to Trolley / Slot where the picker is directed to pick in to pre-
defined slots on a trolley.
Pick-Pack with Volumetric Assessment the picking of inventory into
final shipping containers that have been volumetrically determined. • Why use Trolley Slot Picking? When you wish to pick a number
of orders separately but at the same time. Picking lots of orders
• Why use pick-pack with volumetric assessment? When the into the broadly correct container sizes and then optionally re-
entirety of an order will be picked in one pick run (not multiple) packing (better pick efficiency) is more important that getting
directly into the shipping container and you have a lots of the exact container size correct during pick (better pack
different container sizes (with no real extreme single dimension efficiency).
sizes on products) and wish to tell the operator which container
size to use. Getting the container size correct is important Batch Picking the consolidated picking of a single SKU across one or
during pick (so you can avoid a packing process). many orders.
Pick & Pack the two-step process of picking inventory and then • Why use Batch Picking? When you have sufficiently large
repacking separately. volumes of a SKU required for an order line that you would end
up picking small quantities of a SKU frequently. As such it makes
• Why use pick & pack? When the entirety of an order will not be more sense in terms of operational efficiency to pick these as
picked in one pick run; the order once picked will require further one single pick task (rather than pick separately) and then
activity (consolidation of pick flows and/or post pick activities). perform a secondary sort into the quantities per order required.
Additionally multiple picking methods are to be used for the site
Refer to the Picking Strategy Selection Matrix for further details.

CORE+
Outbound
Outbound Order Creation Guiding Principles

• Each Order created must have a unique identifying order number.
Diagram • All inventory leaving the warehouse must be driven / controlled
Outbound Allocation & by an order to ensure a clear audit trail and inventory control.
Outbound Stock adjustments will not be used for this.
Order Pick
Planning
Creation Grouping • The Outbound Order Interface covers functionality above and
beyond what is provided via the portal form and upload. This is
typically related to, but not limited to the option packs.
• If reserved inventory is to be allocated for a specific outbound
order then the allocation attribute(s) should be populated with a
value that will be used for matching.
Outbound
Order File • In addition, and as an alternative to EDI interfacing, CORE+ is
API enabled for outbound order creation, order updates, order
cancellations and further Order Status APIs provides Client
Outbound
Order Portal
visibility of the current order status and shipped date (if present).
(Form) • If interfaces and the portal (form and / or upload) are used then
Order Status Confirmations for Outbound Orders from all
sources will be provided back via interface to the client.
Outbound
Order Portal • The creation of Back Orders can be automated for orders where
(Upload) the ordered quantity does not match the shipped quantity.
• Validation of addresses on outbound orders is possible through
Outbound the integration with the CEVA Address Validation tool.
Order From SPS • Carrier selection rules and logic are not part of the standard
Commerce Order creation process of Matrix WMS CORE+. A carrier and
service level can however be stated on the outbound order
received.
1 • Integration with the CEVA GetCarrier tool enables a quick and

easy determination of the appropriate carrier and service level.
• It is possible to automatically select the most cost-effective
Outbound carrier and service level if integrated with an external Transport
Order or Carrier management system with Rate Shopping capability.
Creation • Unless using APIs, once received, an outbound order cannot be
changed (with the exception of Ship by Date and Time), only
cancelled by CEVA (upon request from the client).

CORE+
Outbound
• If using APIs, the Order Update API allows changes to outbound o Carriers Shipment Tracking ID (optional Interface only. In
orders up to the point of order allocation, and the Order NORTAM this is the PRO#. Applicable if transport planning
Cancellation API allows the cancellation of outbound orders performed prior to passing the order to the WMS)
whilst at the status of Released or Hold. o Transport Booking ID (optional Interface only, applicable if
• The Order Status API enables the outbound order status to be transport planning performed prior to passing the order to
sent from the WMS throughout outbound processing. the WMS)
• An APERAK message is able to be sent confirming successful o Customers Transport Authorization ID (optional - Interface
creation within the application of the outbound order header only)
and associated lines not including special instructions. o Palletise Indicator (optional Interface only)
o Source / User (that generated the outbound order)
• Prior to picking of inventory an Order is received (created). Then per Order Line
• The Order will contain the following information: o SKU
o Unique Order Number o Quantity
o CEVA Site reference o Tracking Level
o CEVA Client reference o Lock Code (for expired inventory)
o Delivery Note Information (optional) o Condition code (optional)
o Ship date and time o Serial Number
o Customers own reference (optional) o Batch
o Delivery name, address and contact details o Bonded Status (Bonded Warehouse Option Pack Interface
o Inventory Owner only)
o Order Type o Origin
o Work Order Type (Kit to Stock Option Pack) o Country of Originator (Bonded Warehouse Option Pack)
o Grouping reference for grouping multiple orders into a o Allocation Attribute(s) (1 / 2 / 3)
shipment o Shipment Shelf Life
o Consignment reference (Order grouping and Prioritization o Pick Circuit Indicator (Interface only)
Option Pack Interface only) o Grid Picking Indicator (Post Pick Grid Sortation Option Pack)
o Priority (Order Grouping and Prioritization Option Pack o Outbound Client Reference 1 (captured via integration or
Interface only) web portal)
o Activity Zone/Activity Location (Post Pick Activity Option Pack) o FMD flag, if Falsified Medical Directive processing is
o Disallow Short Shipment Indicator (optional) required
o Split Tasks into Shipping Units indicator (One-Piece Flow o Suitable for Back Orders flag
Option Pack)
o FMD (Falsified Medical Directive) Reason (optional)
o Transport Planning Indicator (optional Interface only).

CORE+
Outbound
Then per Special Instructions [1.2] Outbound Order from Portal (form)
o Special Instructions Type Code indicating use for VAS Using the CEVA Web portal, it is possible to create outbound orders
(Post Pick Activity Option Pack), Picking label, Container (one at a time) by entering the information into a form.
Label, Commercial Invoice information, Returns Note Characteristics
Information, Transport Instructions (optional)
• Available for use via the internet (in a secure manner) by clients
o The text to display / use (optional)
as well as internal for CEVA colleagues.
Supporting Matrix Functionality • Simple and clear tool, with appropriate validation and control of
options and selections.
The following options exist for providing information into Matrix WMS • Ideal for operations with lower volumes and / or clients that are
CORE+ for Outbound Order creation:
unable to integrate systems.
• Can be used in conjunction with the other methods mentioned
[1.1] Outbound Order via Interface
for situations such as Disposal order creation when the clients
Using an interface, it is possible to receive Outbound Orders into the
systems does not have this ability; or a quick start up situation
WMS. Any file conversion necessary from client specific interface formats
whilst the final system integration is being developed.
could be mapped and files converted by the CEVA Integration hub.
• Not compatible with the following Option Packs:
Characteristics o Bonded Warehouse
o Order grouping and Prioritization
• Quick and labour free method of providing orders to CEVA (once
created and tested). o Post Pick Activity
• Removes potential for keying errors. Using the Portal form, the following will be created:
• Ideal for operations with medium to-high volumes.
• Is the most functionally rich of the three options, enabling the use Order Header
of all option packs.
• Either the Order number can be keyed in or a unique order
The interface is defined in the Standard MIG document and the number can be selected to be generated by the portal.
associated mapping document for Matrix WMS CORE+. Note that all EDI • Client ID will be controlled by the login used.
interfaced orders will have the source - • Instructions field will be displayed on the Delivery Note. This
Whereas orders that are created via API will have shall be used to capture any free text instructions for the delivery
the source / user field populated wit API-S-220.01-1.0.0- . partner (up to 180 Characters) or other information desired to
Additionally, if an embargoed country of North Korea, Syria, Cuba or Iran appear on the delivery note not for warehouse use.
is passed the order will fail to load. •
• Move Task Status will be defaulted automaticall
Outbound orders created via interface may contain special instructions • Owner selected from those available.
that can be presented to the operator at the point of picking and • Order Type required for the order.
packing (if using the mobile device). Instructions can be held at both • From Site ID will be controlled by the login used.
header and line level.
CORE+
Outbound
• Shipment group (optional) will allow the capture of a unique • Allocation Attribute(s) (1 / 2 / 3) used to specify the exact
reference for grouping orders together into a shipment. inventory that is to be allocated to the order (the inventory must
• Ship by date and time are entered. have been received with identical reservation references to
• Deliver By date and time (optional). ensure it matches during allocation).
• Terms of Delivery (optional). • Serial Number:
• Terms of Delivery Place (optional). o is required if the SKU selected is part of the Handling
• Language determines the language in which the field headers Unit flow (Handling Unit Only Flow) this will be used to
within the Delivery Note and / or Pack Contents List will be uniquely identify the exact pallet / package required.
printed. If left blank English will be defaulted. o Is optional (none Handling Unit Only Flow) if the SKU
• Create shipping units indicator (One-Piece Flow Option Pack) selected need to be allocated a specific serialized item.
• • Batch will be entered if the SKU allocated needs to be from a
functionality (optional). specific batch.
• Work Order Type is required if using the Kit to Stock Option • Override Shelf Life allows for inventory past the minimum
Pack. Select Kit to Stock if building kits, or Unkit to Stock if shipment shelf life, but yet to expire, to be ordered.
breaking down kits into component parts. • Allocate Expired Inventory allows for expired inventory to be
• Customer ID, Delivery name, address lines 1 and 2 (optional), ordered.
Town, County (optional), Postcode and Country are entered. • Grid Picking Indicator (Post Pick Grid Sortation Option Pack)
Note that the embargoed countries of North Korea, Syria, Cuba • Outbound Client Reference 1 where a client specific reference is
and Iran are not able to be entered. required to be stored against an Outbound Order.
• Delivery Contact name, Telephone number and email address • Suitable for Back Orders to automatically create a Back Order
(optional) are captured. for short-shipped order lines
• Customer Order ID field (populating the Purchase Order field in • Delivery Transport Instructions, which if captured are stored in
Matrix WMS CORE+) will be used to capture the Clients own
the Special Instructions table
reference number.
• Carrier and Service Level to be used for the order. Upon creation the order has its source / User stamped upon it that
generated it (WPI-[portal username]). Upon successful creation, an on-
Then per Order Line screen message notifies the operator.
• SKU will be selected from those already in the system.
• Description will be automatically populated from the SKU
[1.3] Outbound Order from Portal (Upload)
selected.
• Quantity will be entered at the lowest UoM. For the Pallet only Using the CEVA Web portal, it is possible to upload a file in a pre-
Flow the quantity should always be 1. defined format to capture the information for multiple outbound orders.
• Tracking Level will be selected to match the lowest UoM.
Characteristics
• Condition code to be allowed to be selected if a particular
condition of inventory is to be picked; the default selection is • Available for use via the internet (in a secure manner) by clients
as well as internal for CEVA colleagues.

CORE+
Outbound
• Simple and clear tool, with appropriate validation to ensure that Integration with Co-Pack SMART Solution
the Inbound Orders are created correctly.
If using the Integration with the Co-Pack SMART Solution Option Pack,
• Ideal for operations with low-to-medium volumes and / or clients
outbound orders will be provided to Matrix WMS CORE+ by Pack
that are unable to integrate systems easily but can generate
Manager to request the component parts that it requires according to
suitable spread sheets (in the required format).
its scheduled activity. See Co-Pack SMART Solution Integration with
• Can be used in conjunction with the other methods mentioned Pack Manager for more details.
for situations such as Disposal order creation when the clients
systems do not have this ability; quick start up situation whilst Ship in Full
the final system integration is being developed.
The Ship in Full feature provides the ability to ensure that orders are
Using the Portal upload, as a minimum the same fields will be captured shipped with no shortages occurring during the outbound process.
as per the form. During allocation if a shortage does occur then the entire order is
deallocated. In addition, if an order that is allocated in full, is
Upon upload to the portal of the document, the file is validated and any subsequently picked short it will not be possible to Vehicle Load.
issue are identified back to the operator for correction and re-
submission of the whole file. Upon successful creation, an on-screen This functionalit
message notifies the operator.
Remove Ship in Full
han Shipped or
[1.4] Outbound Order from SPS Webshop Platform
Cancelled.
Working with SPS Commerce a client may choose for them to provide
webshop (e-commerce) facilities on their behalf. As such CEVA will using the Ship in Full feature, the Shorted
receive outbound orders for the Client from SPS Commerce. Orders Overview Report is available, and in further support of this
Specific integration is used enabling the C -commerce orders to is cancelled within the Order Management screen.
be picked, packed and shipped by CEVA.
Please note that the Ship in Full feature may not be used alongside the
SKU Substitution Option Pack.
Integration with I2M SMART Solution
Back Order Processing
If using the Integration with the I2M SMART Solution Option Pack,
sequenced demand orders will be provided to Matrix WMS CORE+ by Back Orders can be automatically generated for Order Lines where the
Insequence via API, although non-sequenced outbound orders can be shipped quantity does not match the ordered quantity.
processed using existing CORE+ processes. See I2M SMART Solution
Integration with Insequence & IFL for more details.
Call Manage Back

CORE+
Outbound
The Back Order ID will be the original Order ID prefixed with a B Exceptions
followed by a two-digit sequence (up to 99) and a hyphen e.g.: Exception / Failure Related System Activity Required
• Original Order: ABC12345
Outbound Order fails Web Portal: Any incorrect population of
• Back Order: B01-ABC12345 to load field will be identified to the operator by
Note that if the original Order ID is greater than 16 characters then the the web portal. The operator is then
expected to correct appropriately.
preceding characters are removed e.g.:
• Original Order: ABCDEFGH1234567890 Web Portal to WMS: If the failure occurs

• Back Order: B01-CDEFGH1234567890 when processing the Outbound Order
by the WMS then a Service desk call will
The original Order / Line ID can be viewed on the Back Order in the be placed by the operation for support
Host Order ID and Host Line ID fields. to investigate and resolve the issue by
checking connectivity and interface
errors.
Interface conversion / movement: If

the failure occurs as part of the
middleware conversion and move, then
a service desk call will be placed for
support to investigate (potentially with
the relevant apps support teams) and
resolve the issue.
Interface load by WMS: If the failure

occurs as part of the WMS load of the
outbound order, then record(s) will be
written to the interface error table for
resolution by the operation Team
Leader. This includes the failure to load
any orders that contain an embargoed
country (North Korea, Syria, Cuba and
Iran).
Returning Inventory to Typically this will be a change from a

Suppliers
products that have been returned and
are not of sufficient quality to go back
CORE+
Outbound
Exception / Failure Related System Activity Required Exception / Failure Related System Activity Required
into pristine inventory. Alternatively the into pristine inventory, nor require
products could be changed directly Supplier investigation. Alternatively the
from a condition products could be changed directly
(meaning pristine) or DAM in the event
of a recall or following direction from (meaning pristine) or DAM following
the client. direction from the client.
The Inventory Update screen on PC is The Inventory Update screen on PC is

used to change the condition code (by used to change the condition code (by
the Team leader only) the Team leader only)
• Select Type as Condition Code • Select Type as Condition Code
Update Update
• Identify the inventory you wish • Identify the inventory you wish
to alter the condition code of to alter the condition code of
by entering combination of one by entering combination of one
or many of TAG ID, SKU or or many of TAG ID, SKU or
location, and also Client ID location, and also Client ID
(mandatory). (mandatory).
• Select the Tags that you wish to • Select the Tags that you wish to
update. update.
• •
and enter the reason and and enter the reason and
authorizing person for the authorizing person for the
condition code in the Note condition code in the Note
field. field.
The condition is then set on the order The condition is then set on the order
as per the normal outbound order as per the normal outbound order
creation description. The order then creation description. The order then
follows the outbound flow. follows the outbound flow.
Disposing of Inventory This could be a change from a Outbound Order If not using APIs, the cancellation of an
Cancellation Outbound Order is identified by the
products that have been returned and client and notified to CEVA. CEVA then
are not of sufficient quality to go back assesses if the Outbound Order is at a

CORE+
Outbound
Exception / Failure Related System Activity Required Outbound Order Creation Decisions (for configuration / Set up)
Name and Description • How will outbound orders (normal, Return to Supplier & Disposal)
suitable status for cancellation (prior to be provided to Matrix WMS CORE+? [select one or many]
allocation) if so the Team Leader
updates the Outbound Order Header to □ Portal Upload
and the client is
notified via the same way CEVA was □ Portal Form
notified of the desire to cancel, or via
message if enabled. □ CEVA Standard Interface
If using the Order Cancellation API, the □ Client Specific Interface (Client Format mapped to the
CEVA Standard Message)
Client is able to cancel the order whilst
it is at status Released or Hold.
□ CEVA Standard API (Order Create)
Outbound Order is
required to be
If not using APIs, no changes are
permitted to a created Outbound Order □ SPS Webshop Platform (information flows throughout the
process will differ per Webshop)
changed / added to / (with the exception of Ship by Date and
reduced. Time) instead the old Outbound Order
is cancelled and a new, correct one is • If integrating with an SPS Webshop please specify the platform(s).
created.
List the platform(s) here
If using the Order Update API, the Client
is able to update the order (prior to
allocation). Upon submitting an
updated order (with the original order < List the platform(s) here>
reference), the original order is removed
(if at a permitted status) and replaced
with the updated order.
Urgent Orders Same as the normal process outlined

for Goods out, but with a focus on
individually identifying the order or • Is integration with the I2M SMART Solution required (Integration
order preparation, allocation, picking with I2M SMART Solution Option Pack)? [select one]
and loading and pushing it through
quickly. □ Yes
□ No

CORE+
Outbound
• Is integration with the Co-Pack SMART solution required (Integration • If using the Kit to Stock and / or Kit to Order Option Pack are
with Co-Pack SMART Solution Option Pack)? [select one] confirmation messages (generated from the WMS to the middleware
□
layer) required to be sent? [select one]
Yes
□
□
No
No
□ Yes, CEVA Standard Message
• If Portal uploads are used, who will be using them? [select one or Message Trigger Moment
many] Level (Un)Kit Build (Un)Kit Putaway
□ CEVA Employees
Only Kit to Order Per Order 
 
Only Kit to Stock
[select only one per
trigger moment]
Per Order
Per Tag  
□ Other 3rd Party Kit to Order and
Kit to Stock
Per Order 
• If the Portal form is used, who will be using it? [select one or many]
□ CEVA Employees
mapped to a client format)*
Message
Level
Trigger Moment
(Un)Kit Build (Un)Kit Putaway
□ Other 3rd Party

Per Order  
Per Tag  
*Please discuss with your Product Consultant on exact extract and trigger
• Is the Kit to Stock or Kit to Order Option Pack required to complete moments.
kitting activity? [select one]
•
□
Will the Ship in Full feature be used? [select one]
Yes
□
□
Yes
No
□ No
• Will the Back Order Processing feature be used? [select one]
□ Yes
□ No

CORE+
Outbound
• Is integration with the CEVA Address Validation tool required:

[select one] □ In Progress
□ Yes □ Picked
□ No □ Packed
• Get Status Outbound Order □ Ready to Load

be used to view current outbound order status and shipped date (if
present)? [select one] □ Complete
□ Yes □ Shipped
□ No □ Cancelled
• Standard API required to be used? • What Carrier and Service Level combinations will be used? Please
[select one] state them below:
□ Yes
Enter Carrier and Service Level combination(s) here
□ No
• Is the "Outbound Order Status API (S-244 POST)" interface

(generated from the WMS to the middleware layer) required to be
sent? [select one]
□ No < Enter Carrier and Service Level combination(s) here>
□ Yes, when the Outbound Order Header changes to the

following statuses [select one or many]:
□ Hold
□ Released
□ Allocated

CORE+
Outbound
• How will Carrier and Service Level be determined / provided on the

Order interface [select one]? □ By applying defined logic in the integration layer. Please
□ Not applicable as only the portal will be used for orders to

the WMS.
provide the business rules / logic to be used below (Note -
only for use when Client Specific Interfaces are used):
Insert structured logical statement of how to construct the

□ The agreed carrier and service levels stated in the WMS will
be provided by the Client in the outbound order interface.
Consignment value from the fields on the Order Header
□ The carrier and service levels will be determined later in the

process via integration with a transport planning / carrier
management / GetCarrier tool.
□ By applying structured logic in the integration layer using a

combination of the following fields (please state the
<Insert structured logical statement of how to construct
the Consignment value from the fields on the Order
structured logic to apply using the allowed fields listed): Header>
□ Creation Date
□ Dispatch Date
□ Delivery date
□ Order Type
□ Owner
•
□
Will Order Grouping or Prioritization values appear on the order via
Country the interface? [select one]
□ Hub Name □ Yes please see the Outbound Planning section for details.
Insert structured logical statement of how to derive the

Carrier and Service Level from the fields above
□ No
<Insert structured logical statement of how to derive the • Will Special or VAS instruction codes and descriptions appear on the
Carrier and Service Level from the fields above> order via the interface? [select one]
□ Yes please see the Load Preparation section for details.
□ No

CORE+
Outbound
• On successful creation of the outbound order, is the "APERAK

Confirmation of Successful interface (generated from the
WMS to the middleware layer) required to be sent? [select one]
□ Yes
□ No
•
[select one]
□ Yes
□ No
• On cancellation of an outbound order, is an outbound order

cancellation interface (generated from the WMS to the middleware
layer) required to be sent? [select one]
□
□ No
Outbound Order Creation Section Complete

CORE+
Outbound
Outbound Planning Business Description

• The operation determines consignments or loads to be built
Diagram based upon how / when the orders will leave the warehouse.
These orders may or may not be grouped into Shipments. If this
Outbound Allocation &
Outbound information is already determined prior to the warehouse
Order Pick
Planning receiving the orders, then the Order Grouping and Prioritization
Creation Grouping
Option Pack can be used to reflect this on the orders. If
integration with a TMS is being used, then an indicator on the
Planned order will allow for information required for planning to be
Orders (from provided from the WMS and then planned order information to
TMS) be received back and reflected on the WMS order. If these
options are used then there will be a need to build
consignments manually and may need to create shipments if
2.1 2.2 •
appropriate.
Booking in of outbound vehicles may be required; similarly
booking in of Deliveries may be required; both of which may
impact the contents and sequence of the consignments / loads
Build Sequence
built.
Shipment / Consignment
• Orders are grouped into consignments. Some scenarios
Consignment
envisaged are
o Per Vehicle. Building a consignment for everything that is
going out of the dock door in one go; i.e. everything
going out with a Parcel carrier on one vehicle, everything
going out as a vehicle load.
Unplanned o Per Order. Building a consignment per order for
Order TMS everything that a carrier will collect; i.e. parcel flow.
o Per Order Type. Building a consignment for a particular
order type; i.e. emergency orders.
Guiding Principles
o Per Day. Building a consignment for everything that is due
• An order must belong to a consignment prior to picking. out on a specific day.
• A consignment ID is unique to the Site. Supporting Matrix Functionality
• For shipment level operational documents (some Carrier labels),
shipment groups must be used. It should be noted that if the Order Grouping and Prioritization Option
• Shipment Groups must be unique to the Site. Pack is selected then the consignment number and load sequence are
• A Consignment may hold one or many Shipment Groups; a able to be provided on the Outbound Order interface. Similarly,
Shipment Group may have one or many Orders. Shipment group may also be provided on the Outbound Order
interface.
CORE+
Outbound
The values on the interface will either be provided by Upon being built into a consignment with its load sequence, the
• the client when they create the interface based upon agreed Consignment ID populated.
business logic; or
• the CEVA Integration hub added during the interface conversion Use of a Transport Planning Tool
process based upon agreed business logic and able to be
If the information flows with a TMS or planning tool have been selected
determined by the information contained on the order alone.
for use on the product, then manually building and sequencing
As such the process steps described below does not need to be consignments can be skipped, with the planning tool providing this
performed as the interface will have automatically updated the (and other) services.
relevant information to have this affect.
When using a TMS alongside CEVA Matrix WMS CORE+ the order is
[2.1a] Build Shipments expected to have the following fields populated (in addition to /
Normally this is populated on the interfaced order or via transport different to the normal requirement):
planning integration. However, for orders created in the portal on a
• Transport Planning Indicator. Used to indicate (or not) If
solution that does not use a transport planning tool this option may
be used with care.
• Carrier. Used to indicate the desired Carrier (from those set up)
for planning purposes or alternatively / more likely left blank.
orders to use are searched for, typically using either order date or • Service Level. Linked to the carrier, used to indicate the desired
ship by date. A unique Shipment Group ID is entered and then Service Level (from those set up for the Carrier) for planning
orders are selected from those searched for to add to the Shipment purposes or alternatively / more likely left blank.
Group. • Consignment
from the planning performed.
[2.1b] Build Consignment
• Original Ship By Date. A duplicate of the Ship By Date
provided on the order, to preserve the value should it be
changed during planning.
orders to use are searched for, typically using either order date or
• Original Deliver By Date. A duplicate of the Deliver By Date
ship by date. A unique Consignment ID is entered and then orders
provided on the order, to preserve the value should it be
are selected from those searched for to add to the consignment.
changed during planning.
drop-down menu.
All orders received with a Transport Planning indicator set to
[2.2] Sequence Consignment
order status ON-HOLD, an Unplanned
Continuing from process step 2.1, the sequence of the orders to Order message generated out of the WMS and the Transport Planning
load in is manipulated as needed.

CORE+
Outbound
The order will now remain ON-HOLD until a Planned Order message is Transport Planning Indicator Status can be viewed upon each Order
received by the WMS which updates the order and notifies of the Header via the normal enquiry.
completed planning activity. Note that it is possible, if desired, to
If for some reason an order gets stuck within the transport planning
update the order planning information multiple times only setting the
process (or as an emergency needs to be re-planned after resolving
transport planning status to COMPLETED and setting the order status
any already performed picking activity), then two reports exist to assist
to RELEASED on the final update. Possible updates to the order
in resolving the issue. One report allows for the re-set of the Transport
include:
-
• Consignment thus allowing for another message to be set to the planning
• Deliver By Date tool. Another Report allows for the Transport Planning Indicator to be
• Hub Name, Full Address and contact details thus
• Hub Carrier ID moving the order past the planning stage (albeit potentially without
• Load Sequence Consignment, Stage Route ID, Repack Location and other associated
information). It should be noted that these reports should only be used
• Carrier
in conjunction with a thorough understanding of the implications of
• Service Level
doing so and the follow-on actions that are required (not just in the
• Ship By Date
WMS).
• Shipment Group
• Post Pick Activity Zone (Stage Route ID) / Post Pick Activity Address Validation and Carrier and Service Level Determination
Location (Repack Location) (Only in use with the Post Pick Where outbound orders are created via interface the Transport Planning
Activities Option Pack, with the integration layer applying the Indicator on the Order Header can be used to indicate the requirement
same logic that is shared for used on new order creation) and status of Address Validation and / or GetCarrier and / or Carrier
• Carriers Shipment Tracking ID (in NORTAM this is the PRO#) Rate Shopping processing.
• Transport Booking ID
Address Validation provides validation of an Outbound Order address
• Customers Transport Authorization ID
by referring to a pre-configured matrix of values containing acceptable
At this point the order will be set to a status of RELEASED, and hence address information set in the integration layer.
be available for allocation.
CORE+ allows for integration with the CEVA GetCarrier tool which
An Audit trail is kept of updates from the TMS to the WMS; this is enables operations that are not using a full transport planning tool to
request a Carrier and Service Level for a supplied Order (and associated
information) and have it returned (and updated for use) by the WMS.
Transport Planning Dashboard & Troubleshooting
CORE+ also allows for integration with a Transport Management
A Transport Planning Dashboard is available for use that provides an System / Carrier Management System utilizing Rate Shopping
overview of how many orders are currently at each Transport Planning functionality. Using a client provided or GetCarrier provided Rate Shop
Indicator status and for how long they have been there. Individual group, the Carrier and Service Level providing the best and most cost-

CORE+
Outbound
efficient option given the shipment characteristics and Deliver-By date the rate shopping engine and when successfully returned the
is chosen. order is set to Release status
When utilizing Address Validation and / or Get Carrier and / or Rate- The Transport Planning Indicator on the Order Header will present the
Shopping Integration, the order will enter the WMS at the status of appropriate value depending on the current Address Validation and / or
Hold and a scheduled job will initiate one of the following processes: GetCarrier and / or Carrier Rate Shopping status.
1. Address Validation only - after successful validation of the

address, the order is set to Released status
Order Grouping using the Automatic Allocation and Pick Grouping
2. GetCarrier only - after a carrier and service level have been
Option Pack
returned the order is set to Released status
3. Rate-Shopping only - after a carrier and service level have been The Automatic Allocation and Pick Grouping Option Pack offers the
returned the order is set to Released status ability to pre-define the orders that are to be automatically grouped;
4. Address Validation and then GetCarrier - Address Validation is some examples being grouping of whole orders by carrier, and / or
completed and after successful validation of the address, the number of order lines and / or specific order type; i.e. emergency
order remains at Hold status. A carrier and service level is then orders. Note that the applicable orders will be grouped in their entirety.
requested and when successfully returned the order is set to
Release status. Further grouping rules can be applied, some examples are:
5. Address Validation and then Rate-Shopping - Address Validation • Stating the maximum numbers of orders within the order group
is completed and after successful validation of the address, the • Updating the Order Header(s) with a specific Ship Dock, Carrier
order remains at Hold status. A carrier and service level is then Service Level, Move Task Status etc
requested and when successfully returned the order is set to
• Setting the automatic allocation of the grouped order(s)
Release status
• Setting the automatic clustering of the grouped order(s)
6. GetCarrier and then Rate Shopping - GetCarrier is used to either
find a suitable rate shop group and/or modify or transport The facility to view the configured order grouping rules is possible
related details. Once completed, the order remains at Hold through use of the Order Group Selection and Order Group Building
status. A carrier and service level is then requested through the screens.
rate shopping engine and when successfully returned the order
The report (Action) Order Group Maintenance provides visibility of the
is set to Release status
7. Address Validation then GetCarrier and then Rate Shopping - existing order grouping rules configured for the site, and the current
status of each rule (Enabled: Y/N). This report also allows the enabling
Address Validation is completed and after successful validation
of the address, the order remains at Hold status. GetCarrier is or disabling of those rules.
used to either find a suitable rate shop group and/or modify
transport related details. Once completed, the order remains at
Hold status. A carrier and service level is then requested through

CORE+
Outbound
Exceptions the desire to cancel, or via message if

Exception / Failure Related System Activity Required enabled, or via message if enabled.
Name and Description Address Validation If the address stated on the Outbound
Order placed on If an order is placed (or is received) Failure Order fails the validation process, the
Incorrect Consignment with a consignment ID that is now reason why should be investigated. If a
needed to be changed, then following different address is required, the
a check that the order is at a status Outbound Order should be cancelled
where it makes sense to allow this and a new uniquely identified
change to happen, the consignment ID Outbound Order submitted.
is changed.
Using the Order Preparation Function GetCarrier Failure Use the TMS Planning Indicator for an
the order is searched for. The indicator as to why the process has
consignment displayed against the failed.
order is removed, and the correct one
is entered.
Order with an If an order has been set an incorrect
incorrect load load sequence that is now needed to
sequence be changed, then following a check
that the order is at a status where it
makes sense to allow this change to
happen, the load sequence is changed.
Using the Order Preparation Function
the consignment that the order
belongs to is searched for. The
consignment is displayed and after
navigating to the load sequence
screen, the sequence is altered as
needed.
Outbound Order The cancellation of an Outbound Order
Cancellation is identified by the client and notified
to CEVA. CEVA then assesses if the
Outbound Order is at a suitable status
for cancellation (prior to allocation) if
so the Team Leader updates the
Outbound Order Header to the status
via the same way CEVA was notified of

CORE+
Outbound
Outbound Planning Decisions (for configuration / Set up)

• How will orders be grouped into consignments prior to picking □ By applying defined logic in the integration layer. Please
[select one]?
□ Manually, using the Order Preparation screen in Matrix
WMS CORE+ [not using the Order Grouping and
Consignment value from the fields on the Order Header
Prioritization Option Pack].
□ Using a CEVA Transport Management System or planning

tool via integration.
□ The unique consignment value will be provided by the

Client in the outbound order interface.
□ By applying logic in the integration layer using a

combination of the following fields (please indicate desired
fields and their sequence of concatenation, noting that the
value used can only be up to 20 characters long):
□ Creation Date <Insert structured logical statement of how to construct
□ Dispatch Date
the Consignment value from the fields on the Order
Header>
□ Delivery date
□ Carrier
□ Service Level
□ Order Type
□ Country
□ Hub Name

CORE+
Outbound
• How will orders be grouped into Shipments prior to picking [select

one]? □ By applying defined logic in the integration layer. Please
□ Shipment Group will not be used (nor any

documents that rely on it).
□ Manually with care, using the Order Preparation screen in

Matrix WMS CORE+ (for non-interfaced orders and no
Shipment Group value from the fields on the Order Header
transport planning tool integrated as part of the solution).
□ Using a CEVA Transport Management System or planning

tool via integration.
□ The unique Shipment group value will be provided by the

Client in the outbound order interface.
□ By applying logic in the integration layer using a

combination of the following fields (please indicate desired
fields and their sequence of concatenation, noting that the
value used can only be up to 20 characters long): <Insert structured logical statement of how to construct
□ Creation Date
the Shipment Group value from the fields on the Order
Header>
□ Dispatch Date
□ Delivery date
□ Carrier
□ Service Level
□ Customer ID
□ Delivery Name
□ Delivery Postcode
□ Hub Name

CORE+
Outbound
• How will orders be prioritized prior to picking [select one]?
□ They will not they will be provided for picking in the

sequence that they are allocated [not using the Order
Grouping and Prioritization Option Pack].
□ The priority value will be provided by the Client in the

outbound order interface. Please provide the business rules
/ logic that the client will used to determine the priority
value:
Insert structured logical statement of how the Priority value
will be determined
<Insert structured logical statement of how the Priority

value will be determined>
□ By applying defined logic in the integration layer. Please

Priority value from the fields on the Order Header
<Insert structured logical statement of how to construct

the Priority value from the fields on the Order Header>
Planning Section Complete

CORE+
Outbound
Outbound Allocation and Pick Grouping Guiding Principles

• Available to promise (stock availability) is controlled by the
Diagram client.
Allocation & • Inventory cannot be pre-allocated prior to receipt into the facility
Outbound
Planning
Pick Pick unless using the Cross Dock Option Pack
Grouping
• The following business process applies when allocating
inventory that is not pre-allocated as part of the Cross Dock
4.1 4.2 •
Option Pack
The operation determines consignments that they wish to
allocate. Typically this is left as close to the time for picking as
Perform Group po
Allocation Picks • Automatic allocation of orders is possible through the use of the
Automatic Allocation and Pick Grouping Option Pack.
• The ship dock that the consignments are to be loaded from is
determined manually, unless using the Automatic Allocation and
Pick Grouping Option Pack which allows the Ship Dock and
Allocated Move Task Status to be pre-determined and automatically
Orders List Header Volumetric applied to the move tasks of the order header.
Notification Label Label
• Allocation processes are run, with the appropriate grouping
selected, hard allocating inventory to orders.
Pallet o Either the system is left to perform the allocation process,
Pick Media Shipping
Label Label
using the allocation rules in place [preferred / normal
operation]; or
o The operator intervenes in the process by selecting the
Container
exact inventory to allocate in each case.
Shipping
Pick List Label • If using the Batch Pick - Then Put to Wall feature the consolidated
allocation process will be completed before (and separately to)
other non-consolidated allocations.
Pick Label Carrier Own • If using the Kit to Order Option Pack, the system will first try to
Header Label
system will attempt to allocate the component SKUs.
• If using the Kit to Stock Option Pack, for both Kit to Stock and
Unkit to Stock order types, the system will attempt to allocate the
Pick Label Delivery Note K

CORE+
Outbound
• If using the Ship in Full feature any partially allocated orders will slots) on a trolley, allowing for multiple orders to be
be entirely deallocated in full. picked at once (suitable for Trolley Slot Picking).
• The SKU Substitution Option Pack enables substitute SKUs to be
allocated as an alternative in the event of an allocation shortage 6 Group all pick tasks within a zone for picking to
(not compatible for use with the Ship in Full feature). volumetrically determined container sizes; (one or many
• If using the Pro Rata Allocation feature the system will allocate containers per order, but no mixing of orders in each
inventory only from the PRORATASTAGE location, and will container), (suitable for Volumetric Picking).
consider the Allocation Priority against the order(s) to determine
• Note - A custom built grouping logic may be provided if needed
how the available inventory is divided.
subject to validation and acceptance.
• If required when using the Vendor Managed Inventory Option
• Note If predefined pick grouping 4 is to be used, or a custom
Pack, the inventory owner can automatic transfer in the event of
grouping logic that involves grouping pick tasks by product,
an allocation shortage. This allows the transferred inventory to
then the Post Pick Activity Option Pack must be used.
be used to fulfil the order.
• Note The Pick Grouping Option Pack is an essential element
• If the Pick Grouping Option Pack has been selected, then either
for the Locus Cobot and Geek+ Goods to Person Option Packs.
triggered immediately, or run separately, a pre-defined set of
As part of those option packs, custom built grouping logic is
grouping rules can be applied to the pick tasks to optimize pick
required to build the orders which need be transferred over to
efficiency.
Locus or Geek+. A unique Pick Grouping Prefix will identify such
• The Pre-defined pick groupings available are: Pick Lists.
1 Group all pick tasks for each single order (suitable for • Once run, the pick groupings will product Pick Lists that have a
Pick-Pack and Pick-&-Pack picking methods). unique ID. The List ID is then used to control the pick tasks
being worked on as part of the picking process.
2 Group all pick tasks within a zone for each single order
• Where no post pick activity is required, it is possible to generate
(suitable for Pick-Pack, Pick-&-Pack and Pallet Pick
documentation at the point of order allocation.
picking methods).
Pro Rata Allocation
3 Group all pick tasks within a zone for an agreed number
of orders, allowing for multiple orders to be picked at Pro Rata Allocation enables inventory to be allocated proportionally
once (suitable for Pick-&-Pack and Pallet Pick picking across a set of orders when there is insufficient stock to fulfil the orders
methods). in their entirety.
4 Group all pick tasks within a zone for each SKU (suitable The following must be set via integration:
for Batch picking method).
Order Header:
5 Group all pick tasks within a zone for an agreed number
• Order Type = PRO
of slots (fixed single size slots; order into one or many
• Allocation Priority = A numeric value. Allocation prioritises
higher values first and will evenly split available inventory across
CORE+
Outbound
orders with the same Allocation Priority value before moving group all pick tasks for a SKU (also known as pick by line, or product
down to the next Allocation Priority value
Note -
Order Line:
automatically run through all the pick groupings set up that are
• Max Qty Ordered applicable for the Site following allocation this is required if using an
• Rule ID = PRORATA1 option pack that groups picks (Pick Grouping Option Pack / Pick to
Trolley Slot Option Pack).
During Putaway a check is made for any outstanding (not fully tasked)
PRO order lines requiring that SKU. If there are outstanding order lines System Allocation - Batch Pick - Then Put to Wall
the inventory is directed to be putaway to the PRORATASTAGE If using the Batch Pick - Then Put to Wall feature, search for the eligible
location. It is from this location only that pro rata inventory can be SKUs (identified by an Allocation Group of ) and during
allocated. allocation ensure is checked. Note
Supporting Matrix Functionality that SKUs marked as 'BATCHPICK' can also be allocated normally and
[4.1] Perform Allocation will abide with existing algorithm rules by simply not checking the
'Consolidate Allocation' checkbox.
Allocation using the Automatic Allocation and Pick Grouping Option
Pack Pro Rata Allocation
If using automatic allocation as part of the Automatic Allocation and If using the Pro Rata Allocation feature, search for the applicable orders
Pick Grouping Option Pack, the process steps described below do not
need to be performed as allocation will take place automatically.
The Allocation process is then triggered, which will utilize an
Please note that the Automatic Allocation and Pick Grouping Option appropriate allocation rule plus any overriding attributes.
Pack is not compatible with the Batch Pick - Then Put to Wall or Pro
Allocation Rules
Rata Allocation features.
There are a range of allocation rules available that are applied during
System Allocation
the allocation process. The rules to apply during this process are
tion is used. The orders that determined by the allocation group held on the SKU record. Each SKU
you want to allocate are first searched for, typically by any combination should be linked to at least one of these rules; if no allocation group is
of the following consignment, priority, order date, Stage Route ID / present, then the default set of rules will be applied (Set 3).
Repack Location (if the Post Pick Activity Option Pack has been
The allocation group can be specified at the point of SKU creation, or at
selected). From the returned orders, the desired orders to allocate are
a later stage through an amendment to the SKU record (either through
selected. The Ship dock that you wish the orders to be taken to for
SKU Maintenance (best used for updates to single SKUs), or by using
loading is selected. Additionally, the ability to consolidate order lines
the Allocation Group Linking screen (best used for updating multiple
being picked from a single location into a single pick is available for
SKUs at a time)).
selection. If you are using the Pick Grouping Option Pack and desire to

CORE+
Outbound
The allocation rules available are: Set 5
Set 1: "Strict Pick Face" Per circuit:
This rule will generate replenishment tasks using FEFO/FIFO from bulk 1. First, look for a full pallet that matches the quantity desired in
locations in the warehouse and direct these to the pick face. relation to FEFO / FIFO.
Allocations are then made directly from the pick face. This setup 2. Then, Look to the pick face.
bypasses the existing Global Allocation rules utilizing Full and then Full
Prioritize
Part Pallets first before allocations from the pick face are made. This
then adheres more closely to strict FEFO/FIFO controls. Allocation of returned goods from the override zones will be prioritized
above other locations. It is also possible to detail the preferred tracking
level for allocation for the assigned SKU, which the WMS will attempt to
This rule will generate allocation tasks using FEFO/FIFO from bulk prioritize first, above other options from a pick face.
locations in the warehouse. This setup bypasses the existing Global
If the applied allocation rules do not identify suitable inventory, then an
Allocation rules utilizing Full and then Full Part Pallets first before
error alert is issued.
allocations from the pick face are made. This then adheres more closely
to strict FEFO/FIFO controls for picking from bulk where no pick face is If using the SKU Substitution Option Pack this feature will be invoked in
required. the event of an allocation shortage for a SKU that has one or more
active SKU Substitutions assigned. Where a substitution has taken place
Set 3 → Part Pallet → Default rules
an additional Order Line for the substituted SKU is created including
1. First, look for a full pallet that matches the quantity desired in the Original Line ID and Substituted For quantity. The original Order
relation to FEFO / FIFO. Line will be flagged as Line Substituted.
2. Then, look for a less than full pallet (part pallet) that is equal to
Note that FIFO / FEFO (depending on the inventory) on replenishment
or less than the desired quantity in relation to FEFO/FIFO. If
is used to drive the appropriate flow through the pick faces.
part of the desired quantity is found, then repeat this rule for the
remainder [loop]. Overriding Attributes
3. Then, Look to the pick face.
The presence of allocation attribute(s) on an order line will make the
Set 4 → allocation rules look to identically match a piece of inventory with the
same allocation attribute(s).
1. First, look for a full pallet that matches the quantity desired in
relation to FEFO / FIFO. If using the DOT Management for Tires Option Pack, the DOT code can
2. Then, Look to the pick face. be stored in the Allocation Attribute 3 field.
Allocation algorithm will be replaced by FMFO (First Manufactured,

First Out) allocation algorithm for that specific SKU.

CORE+
Outbound
The presence of a serial number on an order line will make the warehouses only, the system can operate without a specified bonded
allocation rules look to identically match to a piece of inventory with the status on the order line, instead using a hierarchy to decide based upon
same serial number. This is used as part of the Handling Unit Only Flow the country of delivery and available inventory bonded status.
Option to match the specific pallet / package to the order needed; for
Delivery Location First choice Second choice
EU Free Bonded
allocation. Non EU Bonded Free
The presence of Batch on an order line will make the allocation rules User Allocation
look to identically match to inventory with the stated Batch only.
The presence of an owner value on the order header will make the system allocation function, the order(s) you want to allocate are
allocation rules look to identically match to inventory with the same searched for, then selected and a ship dock entered. However rather
owner for all pick tasks created against that order. than then letting the system choose the inventory; the matching
The presence of a condition code on the order line will make the applicable inventory is displayed for the operator to the select what to
allocation rules look to identically match to inventory with the same be allocated.
condition code for all pick tasks created against that order line. Following allocation a pop up window appears to ask if TAG swapping
The presence of a COO on an order line will make the allocation rules TAG identified
look to identically match inventory with the stated Origin (or Country of must be picked.
Originator for sites using the Bonded Warehouse Option Pack) [4.2] Group Picks (Pick Grouping Option Pack / Pick to Trolley Slot
Shipment shelf life validation upon allocation, if set on the SKU, requires Option Pack)
the goods allocated to have their expiry date validated as being at least Note: If using automatic pick grouping as part of the Automatic
the number of days into the future as specified. For orders that are Allocation and Pick Grouping Option Pack, the process steps described
specifically for expired inventory, then the presence of the Lock Code below do not need to be performed as pick grouping will take place
rules look to identically automatically.
match to a piece of inventory with the same Lock Code. For orders that
are specifically for inventory past their minimum shipment shelf life but
is selected as well as the Site, Client (if needed) and the clustering
are yet to expire, then the presence of the order shelf life days value on
group to use. Note that any allocated, yet not clustered move tasks will
the order line (typically combined with an appropriate condition code)
be attempted to be clustered. The clustering is then attempted, with a
will make the allocation rules look to match to a piece of inventory that
final screen showing how many tasks were clustered and how many lists
is not yet expired, but bypassing the min shelf life value set on the SKU.
were created.
As part of the Bonded Warehouse Option Pack, the presence of an
The default clustering groups / configurations provided are:
bonded status value on the order line will make the allocation algorithm
look to identically match to inventory with the same bonded status (for • Single Order Cluster group
all pick tasks created against that order). Alternatively, for EU
CORE+
Outbound
• Single Order and Zone Cluster group are directed to the same repacking location regardless of one or many
pick paths.
• Multi Order Cluster group
Please liaise with your WMS CoE Implementation Consultant to ensure
that a suitable set of clustering rules (derived from your best practice /
o Note that Rule 4 within this group can be swapped out
solution design approved picking strategy) is requested.
for other rules restricting the number of orders to a
different value. SKU Labels
• By Product Cluster group
SKU Labels are able to be used where goods are not labelled, or are
• Pick to Trolley / Slot Cluster group multi order picking for one
labelled incorrectly. The following labels are available in both standard
or many zones limited by the number of trolley slots and trolley
and bespoke versions (bespoke versions if using the Flexible
volume
Documents Option Pack):
Additionally custom clustering rules can be set up as part of this option
• Pre-Receive SKU Label manually printed prior to receipt
pack, subject to approval. This includes adding a 4 character prefix for
• Inbound SKU Label automatically printed at receipt, and able
each List ID defined per clustering rule.
to be manually reprinted using the Reports function
[zero] will automatically produce picking labels; all other starting
• Outbound SKU Label automatically printed at allocation, and
characters will produce a pick list.
able to be manually reprinted using the Reports function
For example, clustering rules could be set up so that different pick lists
value against the SKU record is used to specify if the
are generated to match the picking strategy for the site; with one or
SKU Labels should print per EACH or per TAG.
many different picking methods utilized across the multiple outbound
flows within the warehouse. Example Standard Outbound SKU Label (bespoke version available if
using the Flexible Documents Option Pack)
Additionally, clustering rules could be set up so that pick lists are
limited to a stated number of lines (which the operation has determined
will give say, 30 minutes of work) hence allowing work load control by
the team leader over the picking operators.
It should be noted that mixing priorities in a clustered group is not

advised as the higher priority tasks will get performed separately and in
effect negate the clustering performed.
Similarly, if you are using the Post Pick Activity Option Pack you should
not mix different end Activity Zones associated to the pick tasks that are
clustered, unless also using the Follow Me Logic Option Pack which
ensures that all parts of an order, or all orders for the same customer

CORE+
Outbound
Document Generation at Order Allocation Dynamic Pick Faces
It is possible to generate documentation at the point of order allocation The Dynamic Pick Face feature allows operations with fast rotating
where no post pick activity is required. products to set and use pick faces dynamically to fulfil open orders
within a specific work zone.
The following documents can be generated at order allocation and will
be produced in a single output headed by the List Header Label which Within Pick Face Maintenance, the selected SKUs can be allocated a
provides summary details of the documents generated: pick face type of Dynamic and the Location Zone 53DYN01 is
specified. This process can be automated if using the Automatic Pick
• List Header Label Face Creation and Control feature see SKU Set up for more details.
• Pick Media Label*
• Pick List Furthermore, it is possible to assign the specific range of locations
• Pick Label (and Pick Label Header)* within the Dynamic Pick Face Zone, although please note that it is not
• Volumetric Picking Label possible to further subzone the 53DYN01 Location Zone.
• Pallet Shipping Label On allocation of the selected SKUs, both a replenishment and pick task
• Container Shipping Label* are generated to firstly move the product from a bulk location into the
• Carrier Own Label dynamically assigned pick face, after which the pick task can be
• Pack / Contents List executed.
• Delivery Note
If inventory remains in the Dynamic Pick Face and has no further
* Separate, enhanced version of the standard document when demand, a system generated relocate task will be created to move the
generated at order allocation remaining inventory back into bulk storage.
Retailer Compliant Shipping Labels Option Pack used to manually trigger the generation of the relocate tasks, as and
The Retailer Compliant Shipping Labels Option Pack enables the when required.
bespoke design of labels that are created in a format specified by the The Dynamic Pick Face Details report can be used to check fill level,
Retailer to aid in their inbound receiving process. These labels are able and demand for SKUs within the Dynamic Pick Face zone.
to be triggered when the container and / or pallet reaches the status
required, labels can be

triggered after completion of the allocation process.
For more information please liaise with your WMS CoE Implementation
Consultant.

CORE+
Outbound
Document Generation at Order Allocation Example Documents

Example List Header Label Example Pick List Example Pick Label*
Example Pick Label Header*

Example Pick Media Label* Example Volumetric Label
* Separate, enhanced version of the standard document when generated at order allocation
•
CORE+
Outbound
Example Pallet Shipping Label Example Pack / Contents List Example Delivery Note
Example Container Shipping Label* Example Carrier Own Label
* Separate, enhanced version of the standard document when generated at order allocation
•
CORE+
Outbound
Exceptions Exception / Failure Related System Activity Required

Exception / Failure Related System Activity Required Name and Description
Failed Allocation Orders that fail allocation are shown on client is notified via the same way
the Finish [Shortages] tab in the System CEVA was notified of the desire to
allocation screen at the end of running cancel, or via message if enabled.
allocation. The order will not change Post allocation (prior to pick) The
status it will simply remain at its Team Leader deletes the move tasks
current state. created using the Move Task Update
screen. The Team Leader updates the
Once the shortage is resolved (receipt Outbound Order Header to the status
of suitable inventory / correction of of
issue), the allocation process can be re- via the same way CEVA was notified of
run for the previously failed order. the desire to cancel, or via message if
Alternatively, if the inventory is not enabled.
going to be available then the order Notification of Carriers that are able to receive voiding
may be decided to be cancelled. Differences between confirmations will receive notification of
und Order Planned and Shipped containers that are no longer planned
to be despatched (triggered by the
Incorrect Clustering Move task list generation, use the deallocation process).
group selected
selected tab, identify the tasks you no
longer wish to be associated to the
entered list ID (hence remove
clustering) then use the remove button.
Incorrect Inventory The Team Leader deletes the move
allocated using User tasks created using the Move Task
Allocation Update screen. The User Allocation
process is then performed again
correctly.
for cancellation.
Prior to allocation The Team Leader
updates the Outbound Order Header

CORE+
Outbound
Outbound Allocation Decisions (for configuration / Set up) • Will the Dynamic Pick Faces feature be used? [select one]
• Will the Automatic Allocation and Pick Grouping Option Pack
be used? [select one] □ Yes
□ No □ No
□ Yes, by applying the following order grouping rules: • How is the bonded status of inventory to allocate determined?
[select one]
State the order grouping rules here:
• Orders
<Stateto group?
the order grouping rules here:
□ Not applicable as not using the Bonded Warehouse
Option Pack
• Auto Allocate?
• • Orders to group
Auto Pick Group?
• Auto Allocate?
□ Received in outbound order from the client
• Auto Pick Group? > □ Derived by CEVA Matrix WMS CORE+ based upon a
hierarchy related to the country of Delivery [EU
warehouses only]
• If the operation is working off paper, do the pick lists require to

• Will the Pre-Allocation feature for Cross Dock be used (Cross
be automatically printed (note you cannot print both pick lists
Dock Option Pack)? [select one]
AND picking labels for a single list)? [select one]
□ No □ Yes A4 sized output
□ Yes □ Yes US Letter sized output
• Will the Pro Rata Allocation feature be used? [select one] □ No
□ No • Are (bespoke) Retailer Compliant Shipping Labels required
□ Yes (Retailer Compliant Shipping Labels Option Pack)? [select one]
• Is the Outbound SKU Label required? [select one]

□ Yes
□ No □ No
□ Yes [select one]: • Where will the Pick List be printed to (if required)? [select one]
□ Standard Outbound SKU Label □ Pick List not required

□ Bespoke Outbound SKU Label (Flexible Documents □ Printer requirements specified within the Printer Data
Option Pack) Take on Spreadsheet

CORE+
Outbound
• Do the pick labels require to be automatically printed (note you Picking Method: Pallet Pick
cannot print both pick lists AND picking labels for a single list)?
[select one] □ PM01 - Full Pallet Pick - No Post Pick Activity
(documents generated at order allocation)
□ Yes □ PM02 - Full Pallet Pick - With Post Pick Activity
□ No (documents generated post-picking)
Select the required Pick Grouping logic to support this

• Where will the Picking Label be printed to (if required)? [select
picking method:
one]
□ Picking Label not required □ Group all pick tasks within a zone for each single order.
□ Printer requirements specified within the Printer Data □ Group all pick tasks within a zone for an agreed number
of orders, allowing for multiple orders to be picked at
Take on Spreadsheet
once. Please state the number of orders.
• Is Pick grouping logic required? [select one] State the number of orders
<State the numberhere
of orders here>
□ No, the Pick Grouping Option Pack will not be used □ Custom built grouping logic (subject to validation and
picking will be performed for a whole single order at a
acceptance). Please state the logic to be used below
time (if selected, skip the following questions relating to
including the prefix to be used per list (note a '0' [zero]
Picking Methods).
prefix will automatically print picking labels else picking
□ Yes. (Use the following questions to specify the picking
lists will be generated):
methods and required pick grouping logic)
Enter here the structure logic of what is required
to be grouped and how
<Enter here the structure logic of what is required

to be grouped and how>
Clear Radio Button

CORE+
Outbound
Picking Method: Pick-Pack Picking Method: Pick-Pack with Volumetric Assessment (Volumetric
□ PM03 Determination for Picking Option Pack)
□ PM05
Pick-Pack in to Shipping Container - No Post
Pick Activity (documents generated at order allocation) Pick-Pack in to Shipping Container with
□ PM04 Pick-Pack in to Shipping Container - With Post volumetric assessment - No Post Pick Activity (all
documents generated at order allocation)
□ PM06
Pick Activity (documents generated post-picking)
Pick-Pack in to Shipping Container with
Select the required Pick Grouping logic to support this volumetric assessment - With Post Pick Activity
picking method: (volumetric documents generated at order allocation,
□ Group all pick tasks for each single order. other documents generated post-picking)
□ Group all pick tasks within a zone for an agreed number

picking method:
once. Please state the number of orders. □ Group all pick tasks for each single order.
State the number of orders
<State the numberhere
of orders here> □ Custom built grouping logic (subject to validation and
□ Custom built grouping logic (subject to validation and
acceptance). Please state the logic to be used below lists will be generated):
lists will be generated): Enter here the structure logic of what is required

<Enter here the structure logic of what is required to be grouped and how>
Clear Radio Button Clear Radio Button

CORE+
Outbound
Picking Method: Pick & Pack Picking Method: Pick & Pack with Volumetric Assessment (Volumetric
□ PM07 Determination for Picking Option Pack)
□ PM08 - Pick & Pack in Post Pick Activity Zone with

- Pick & Pack in Post Pick Activity Zone
(documents generated post-picking)
volumetric assessment (volumetric documents
Select the required Pick Grouping logic to support this generated at order allocation, other documents
picking method: generated post-picking)
□ Group all pick tasks for each single order. Select the required Pick Grouping logic to support this
□ Group all pick tasks within a zone for each single order. picking method:
□ Group all pick tasks within a zone for an agreed number □ Group all pick tasks for each single order.
once. Please state the number of orders.
State thethe
<State number of orders
number herehere>
of orders prefix will automatically print picking labels else picking
□ Custom built grouping logic (subject to validation and Enter here the structure logic of what is required
including the prefix to be used per list (note a '0' [zero] to be grouped and how



CORE+
Outbound
Picking Method: Trolley Slot Picking (Pick to Trolley / Slot Option Picking Method: Batch Picking
Pack)
□ PM11
□ PM09 - Trolley Slot Picking No Post Pick Activity - Batch Picking - No Post Pick Activity
□ PM12 - Batch Picking - With Post Pick Activity
□ PM10 - Trolley Slot Picking With Post Pick Activity (documents generated post-picking)
(documents generated post-picking)
□ PM13 - Batch Picking - Then Put to Wall (documents
Select the required Pick Grouping logic to support this generated post-picking)
picking method:
□ Group all pick tasks within a zone for an agreed number picking method:
of slots (fixed single size slots; order into one or many
slots) on a trolley, allowing for multiple orders to be □ Group all pick tasks within a zone for each SKU (Note
picked at once. Please state the number of slots per that the Post Pick Activity Option Pack must also be
trolley. selected for use with this option).
State <State
the number of slotsof
the number per trolley
slots perhere
trolley here>
□ Custom built grouping logic (subject to validation and including the prefix to be used per list (note a '0' [zero]
acceptance). Please state the logic to be used below lists will be generated):
prefix will automatically print picking labels else picking Enter here the structure logic of what is required



Allocation Section Complete

CORE+
Outbound
Outbound Pick Guiding Principles

• Fixed pick faces will be used unless using the Dynamic Pick Face
Diagram feature which allows operations with fast rotating products to set
Allocation &
and use pick faces dynamically to fulfil open orders within a
Load specific work zone.
Pick Pick
Preparation
Grouping • A single pick sequence will be used to cover the entire site. As
such the placement locations for heavy goods should be
included earlier in the pick sequence than lighter ones, unless
using the Pick Face Circuits feature.
• Pick sequences defined must contain suitable gaps (100)
5.1 5.2 5.3 •

between each value to allow for future growth or alteration
without the need for redoing the whole sequence.
Picking can be performed at a Pallet, Case, Pack or Each level.
Issue Pick Perform Deposit For the Handling Unit Only Flow the Pallet level is only
applicable.
Tasks Picks Pick(s)
• The pick quantity presented is dependent on the tracking level
specified as being 'required for display' from the associated
pack configuration, unless using the UOM Pick Face feature,
which will display the quantity in multiples of the tracking level
associated with the location.
• The picking of a full pallet pick will be directed to Bulk Storage,
Picking Shipping
not the pick face if there is suitable inventory.
Media Label Label
• Short shipping will be allowed if no suitable inventory is
available
which prevents short shipping.
Picking Label Delivery Note
• Serial or Handling Unit reference numbers can be captured at
pick if the SKU is specifically flagged as requiring this this is
information capture only and does not drive any processing or
rules, except in the case of the Handling Unit flow.
Bill of Lading • Replenishment of fixed Pick Faces will be automatically
triggered when a minimum quantity is passed (not equal to). The
minimum quantity is recommended to be an amount easily
determined from a visual check.
Returns Note

CORE+
Outbound
• Manual triggering of replenishment tasks for fixed Pick Faces is WMS to the respective system. All picking functionality and
- Report/Create PF Top exceptions will be handled by the Locus and Geek+ systems.
• If using the One-Piece Flow Option Pack it is possible to identify
• Multiple replenishment tasks are able to be grouped together a tracking level (and its dimensions) within a pack configuration
into a single run if using the Replenishment Runs Option Pack. that is considered to be of suitable design that it can be shipped
• If using the ABC Analysis Option Pack the replenishments will be in its existing packaging.
prioritized as follows:
o The ABC ranking of the Location (if applicable). Locations
priorities, a E ranked location being the lowest.

• The replenishment of a Dynamic Pick Face is generated prior to
each pick task, unless inventory remains in the location. Where
there is no longer demand for inventory sat in a Dynamic Pick
Face, a relocation task will be generated to move the inventory
back into Bulk storage.
• A location count is automatically triggered within a fixed pick
face when the quantity reaches zero.
• If required when using the Vendor Managed Inventory Option
Pack, the inventory owner can automatic transfer when a pick-
face trigger level has been reached.
• Bespoke trigger quantities per SKU are able to be set so when
the count on a pick face falls below the stated quantity, the
operator is presented with a request to stock check the location.
• Picking location will be directed by the system.
• A message is able to be sent confirming that "Warehouse
Outbound Activity had commenced" per order once the picking
activity has begun. This message will be generated when the
status and contains
header information only.
• A Warehouse Dashboard is available alongside the WMS which
provides a real-time, single view of key metrics including
outstanding outbound move tasks.
• If using the Locus Cobot or Geek+ Goods to Person Option
Packs, picks identified through the Pick Grouping functionality to
be executed by Locus or Geek+ will be transferred from Matrix
CORE+
Outbound
Business Description ▪ SKU/EAN/UPC barcode may be confirmed

• If using User Directed picking, the Picker is informed of the pick (optional)
activity to perform by the team Leader. Following the picking ▪ TAG confirmation when picking whole pallet
strategy for the site, the Picker will be tasked with using a quantities (optional)
particular pick method for the pick tasks assigned. ▪ The label of the Media picked into may be
• If using the Push of Pick Tasks Option Pack, the System Directed captured (optional)
Picking function will present the Picker with their assigned tasks. ▪ One or many orders may be chosen to be
• Picking may be directed to occur within just a single zone, sub- allowed into the pick media (optional)
zone or the whole facility; for part of an order (if split by zone), a ▪ Serial Number(s) may be captured (optional)
whole order individually, a number of whole orders one by one • When the pallet (or trolley) is full or all picking is completed, the
(within a consignment for example) or a number of orders at the picker moves to deposit location identified.
same time; batches of single SKUs for multiple orders or • Deposit picks and confirm location check-digit (only if the
individual order SKUs. location has one).
• The Pick Face Circuit feature allows multiple pick faces for the • Special instructions will be presented to the operator if held
same SKU, for use in up to ten different pick circuits. against the outbound order header or line(s).
• The determination of the type and number of containers • Picking is then resumed if picks remains in the picking activity
required for certain pick methods is possible (Volumetric assigned.
Determination for Picking Option Pack). • Replenishment of fixed pick faces occurs when a minimum
• For picking multiple orders in one pick run, the use of a trolley is trigger quantity is reached in the pick face. If this occurs during
possible (Pick to Trolley / Slot Option Pack). picking the picker may either chose to wait for the
• Picking Media Labels are produced (if needed) which allows for replenishment to then pick the remaining quantity needed or
the unique identification of the media being picked onto. continue with other pick tasks returning to complete the pick
• Picking Labels are produced (if needed and not generated at the later.
point of order allocation) which allow for physical identification • The Replenishment Runs Option Pack provides the ability to
of the items picked per order line. group replenishment tasks into a single run, allowing multiple
• The picker obtains pick media if needed. Labels are applied to SKUs to be picked for replenishment in a single run before being
the media (pallet / trolley / container / boxes) as needed. deposited into the final pick face locations. The Replenishment
• Prior to picking SKUs within a Dynamic Zone a replenishment Runs Option Pack can work in conjunction with the Push of Pick
task will be generated to move the required quantity from Bulk Tasks Option Pack for the most efficient grouping and issuing of
storage into a dynamically assigned pick face location (if no grouped replenishment tasks.
inventory remains in the Dynamic Pick Face at the time of order • The Pick Face Throughput report provides visibility of the speed
allocation). at which SKUs move through fixed pick faces. A classification can
• Per pick task: be held against the pick face location record to represent this
o Locate Pick location and confirm location check-digit speed. This classification can be used when / if completing
(only if the location has one). manual top up of pick faces and is a useful tool when analyzing
o Physically perform pick
o Confirm pick
CORE+
Outbound
the most efficient warehouse configuration. Categories range The Push of Pick Tasks Option Pack allows the assignment of configured
from AA (fastest moving) to C (slowest moving). work lists (consisting of one or many pick grouping list prefixes) to be
• The Dynamic Pick Face Details report can be used to check fill assigned to specific users or workstations.
level, and demand for SKUs within the dynamic pick face zone.
Cascade Replenishments nction on the PC.
An optional cascade replenishment feature is available if a

warehouse operation is using multiple tracking level specific
Example Move Task List for Picking
Pickfaces for a SKU. Cascade Replenishment is a process where the
replenishments for a SKU containing multiple pick faces (where each
pick face holds a different tracking level) cascades through from the
highest to the lowest tracking level.
For example:
• Three tracking levels of pick:

o EA eaches
o SL sleeves
o CA cases
o The remainder of inventory stored in bulk locations
• Replenishments are triggered:
o To the eaches pick face from the sleeve pick face
o To the sleeve pick face from the case pick face
o To the case pick face from the bulk location
Supporting Matrix Functionality

[5.1] Issue Pick Tasks
The Team leader will inform the Picker of what pick activity to perform.
This can be through verbal communication or from within the
application. The direction will reflect the operations pick strategy [5.2] Perform Pick(s)
(including timing of departure vehicles, SLAs, workforce planning
If desired the Standard Picking Media Labels are triggered manually
performed, etc.) and hence may have involved some previous pick
from the PC only in the User Reports screen to the selected label
grouping (if the Pick Grouping Option Pack is being used).
printer. The barcode for the label can be set to be either a generated
TAG ID or SSCC.

CORE+
Outbound
Example Standard Picking Media Label for the Site UK-WAR-01 If using the Volumetric Determination for Picking Option Pack, the
Volumetric Picking Labels must be generated at the point of order
allocation.
Example Volumetric Picking Label
If desired the Standard Picking Labels are triggered manually from the
PC through the Move Task List Generation option. A Picking Label
Header will be produced displaying overall details for the pick list. The
Header label will display key components for the pick run. Pick Label(s)
will follow for each corresponding pick task to be completed.
Example Standard Picking Label Header
Via Mobile Device - Container Picking
Used for the following Picking Methods:

Example Standard Picking Label
• PM01 Full Pallet Picking No Post Pick Activity
• PM02 Full Pallet Pick - With Post Pick Activity
• PM03 Pick-Pack in to Shipping Container - No Post Pick Activity
• PM04 Pick-Pack in to Shipping Container - With Post Pick
Activity
• PM07 Pick and then Pack in Post Pick Activity Zone
• PM11 Batch Picking - No Post Pick activity
• PM12 Batch Picking - With Post Pick Activity
CORE+
Outbound
It is possible for Team Leaders to issue pick tasks manually to Operators this is able to be set against the component SKU and / or kit SKU.
through the distribution of pick lists. The Push of Pick Tasks Option Pack Serial capture is also used as part of the Handling Unit Option Pack to
allows pick tasks to be sent the Operator within the RDT application capture the unique identifier of the Handling unit picked.
and upon starting this System Directed picking process, a pick list
Upon picking the location to zero, a stock check task may be
summary will be displayed.
automatically created which the operator must complete to confirm
there is no further inventory within that location.
directed to guide them to the activity desired. Presented in the screen
This process then continues to loop around back to showing the next
for this aim are the fields for Container, Task ID (enter order number)
all of the order / list is complete. If at any point
and List ID. To work with the next order enter
work with the next List enter ith the
are able to use a function key to perform, confirm the check digit and
next pick task leave all fields blank.
then resume the picking on new media (following capture of the pallet /
If required, the pallet / container details are captured. The Task ID is container ID[s]).
displayed.
-digit is captured to
Via Mobile Device - Volumetric Picking
confirm presence (if the location has one). Special instructions will be
presented to the operator if held against the outbound order header or Used for the following Picking Methods (however, not recommended
line(s). The details of what to pick are then displayed from location, for use in conjunction with the Push of Pick Tasks Option Pack):
client, SKU, Quantity (with pack configuration hierarchy), SKU
Description, to location. • PM05 Pick-Pack in to Shipping Container with Volumetric
Assessment - No Post Pick Activity
The quantity picked is confirmed. The TAG picked from may be • PM06 Pick Pack in to Shipping Container with Volumetric
directed to be captured, dependent upon the location you are picking Assessment - With Post Pick Activity
from, if it has TAG merging enabled, the number of TAGs it contains • PM08 Pick and then Pack in Post Pick Activity Zone with
and if full pallet TAG confirmation is enabled. Per client you may choose Volumetric Assessment
to:
Using the List Header Label, the operator is able to see the number and
• scan the SKU/EAN/UPC barcode for all SKUs; type of containers required together with the List ID for the pick run.
• scan the container you have picked the goods into;
• scan the TAG when picking full pallet quantities (supersedes the operator enters the List ID.
SKU/EAN/UPC barcode scanning if both are enabled). The pallet type, pallet ID, container type and container ID, are pre-
populated. -digit is
If the goods are serialized and the serialization profile for the SKU is set captured to confirm presence (if the location has one). The details of
for capture at Pick, then the serial number/s of each item will need to what to pick are then displayed. The container ID used, and quantity
be captured, unless this feature has been suppressed (available for full
TAG movements). If using the Kit to Stock or Kit to Order Option Packs
CORE+
Outbound
picked is confirmed. Per client you may choose to scan the [5.3] Deposit Pick(s)
SKU/EAN/UPC barcode for all SKUs. Via Mobile Device
This process then continues to loop around back to showing the next Either from completing the picking of the order / List or by using a
displayed. This will either be the assigned Ship dock for the
consignment they relate to or, if the Post Pick Activity Option Pack is
Via Mobile Device Trolley / Slot Picking being used, then the assigned post pick activity zone or post pick
Used for the following Picking Methods: activity location for the order. If using the Follow Me Logic Option Pack
alongside the Post Pick Activity Option Pack, it is possible to prompt
• PM09 Trolley Slot Picking - No Post Pick Activity the operator to deposit the pallet either directly into the Post Pick
• PM10 Trolley Slot Picking - With Post Pick Activity Activity Zone / Location, or to a holding location if required.
List ID. If using either the Kit to Order or Kit to Stock Option Pack, component
(List SKUs will be directed to be deposited at the Kitting Location.
ID) . T -digit is captured
Once the deposit has been made, the check digit is captured (if one
to confirm presence (if the location has one). The details of what to pick
exists for the location).
and the slot to be picked in to, is displayed. The quantity picked is
confirmed. Per client you may choose to scan the SKU/EAN/UPC Via paper & PC
barcode for all SKUs.
As the Picker deposits the picked inventory (in media) to the stated
This process then continues to loop around back to showing the next location on the Pick List, they tick off the activity on the sheet. When all
deposits have been done the picker then signs and date / time stamps
ion, they the sheet then passes it to the Team Leader. The Team Leader will
are able to use a function key to perform, confirm the check digit and
then resume the picking on new media. List ID is entered, the operator who performed the tasks captured, then
the tasks completed are confirmed.
Additional Information
Via paper & PC
Upon being given a move task list from the Team Leader, the picker
view all non-completed moves by leaving the search criteria empty. If
then proceeds to pick what is stated on the list from the stated
ks are shown allowing
locations, writing down how many was picked and to what pallet ID /
for progress to be monitored and to aid with the direction of work.
container ID it was put into / onto. Note that picking via paper & PC is
Similarly, Replenishment tasks can be filtered and shown on their own.
not applicable for volumetric picking (Volumetric Determination for
Picking Option Pack) or for trolley / slot picking (Pick to Trolley / Slot
Option Pack).
CORE+
Outbound
Upon the first quantity of an item picked being captured the order Replenishment
header status will change to
Replenishment of pick faces will be automatically triggered when a
picked for the order has been transferred to the container being picked
minimum quantity is passed (not equal to). The value recommended to
use is one that is easily determined from a visual check. This value is
order has been put to the in-stage for the ship dock the order header
defined as part of SKU pick face setup. If a replenishment is triggered
Upon the failure to pick any
whilst an operator is picking, then a message will be displayed to the
inventory for an order,
picker informing them and the operator can move to the next task.
. If required, can be updated to
When all the remaining pick task have been completed, then the
Cancelled or Shipped Update Zero Picked
replenishment related pick task will be presented again.
Manual triggering of replenishment tasks for Pick Faces is possible

Production of Pallet Shipping labels can be triggered from the Mobile
- Report/Create PF Top Up
Device upon drop of Pallet (Marshall complete to in-stage) into the
picking to location. This may be to a fixed printer, a locality based
generated, at a time suitable to the operation and works outside of the
printer or a mobile printer (if using the Mobile Printing Option Pack) -
minimum quantity triggers.
see facility set up.
Replenish Part Tag functionality is available that will provide the
Production of Delivery and / or Return Notes is triggered from the
operator with the instruction to take a full pallet, replenish part of the
Mobile Device upon drop of the last Pallet (Marshall complete to in-
pallet into the pick face, and then relocate the remaining balance into a
stage) into the picking to location for the order. One Delivery Note will
suitable storage location.
be printed per Order; One Returns Note will be printer per Order. This
is covered in more detail in the Load Preparation section. The replenishment tasks generated can be seen by the Team Leader in
Retailer Compliant Shipping Labels Option Pack
resource to meet the demand if operators are not dedicated to the task.
The Retailer Compliant Shipping Labels Option Pack enables the
Via Mobile Device
bespoke design of labels that are created in a format specified by the
Retailer to aid in their inbound receiving process. These labels are able
to be triggered when the container and / or pallet reaches the status similar to the pick process described above but without needing
labels, media and it being a single move as default. Where the option
to replenish part tag is taken, the operator will be provided with the
the Close Container
instruction to take a full pallet, replenish part of the pallet into the pick
option on the mobile device should be used after depositing the pallet.
face, and then relocate the remaining balance into a suitable storage
For more information please liaise with your WMS CoE Implementation location.
Consultant.
The initial screen allows the workzone, location or SKU to narrow
applicable replenishment tasks to perform, however typically the fields

CORE+
Outbound
are left blank to let the tasks appear in the system generated sequence. Replenishment Runs Option Pack
-digit is captured to
As an alternative to the native replenishment functionality detailed
confirm presence (if the location has one). The Task REPLENISH, From
above, the Replenishment Runs Option Pack allows multiple SKUs to be
Location, The Tag, Client, SKU ID, SKU Description, Qty, To Location,
picked for replenishment in a single run before being placed into a
Final Destination are all displayed. If SKU confirmation is enabled, then
holding location (REP-STOP). The replenishments are then collected
the SKU is scanned (for validation). The operator performs the
and deposited into the final pick face locations.
replenishment as directed and then confirms the check-
location (if the location has one). This two-step process can provide efficiencies by allowing one operator
to complete the collect task and another operator to complete the
Via Paper and PC
deposit task.
The collection element of the replenishment run utilizes the picking

type is searched and the relocation tasks that are desired to be put on a
functionality on the mobile device and can be completed using the
single list are selected. The Move task list will then be produced, with
following methods:
the Task List ID also displayed on the screen.
The list is then given to an operator to perform. • User Directed Container Picking
• System Directed Picking (if used in conjunction with the Push of
Following the completion of the relocation activities as stated on the Pick Tasks Option Pack)
the system. The List ID is entered, the operator who performed the Following the collection and subsequent deposit of the replenishments
tasks captured, then the tasks completed are confirmed. into the temporary holding location (REP-STOP), using the Marshall
functionality on the mobile device, the inventory is collected and placed
Via Geek+ Goods to Person into the final pick face location.
If replenishing towards the Geek+ Goods to Person system, the Some additional things to note regarding the Replenishment Runs
replenishment will comprise of two parts. The first part (towards an In- Option Pack:
Stage location - representing the Geek+ Workstation) will be performed
as described above in the Via Mobile Device or Via Paper and PC. Once • If used in conjunction with the Pick Grouping Option Pack,
the first part of the Replenishments is completed, Matrix WMS will replenishment tasks can be grouped together in to lists through
transfer the second part of replenishment task to the Geek+ Goods to the use of clustering. Within the cluster rules it is also possible to
Person system. The last step of the replenishment (to the final Pick Face default the pallet and container types used.
location) will be performed in the Geek+ Goods to Person system. One-Piece Flow Option Pack
Upon completion, is the result of the Replenishment will be
communicated back to Matrix WMS which will in turn finalize the The One-Piece Flow Option Pack offers the ability to identify a tracking
Replenishment. level within a pack configuration that is considered to be of suitable
design that it can be shipped in its existing packaging (so does not
need to be picked into a larger shipping container).
CORE+
Outbound
The Split Tasks into Shipping Units indicator on the Order Header can Exceptions
be set via the portal or integration and one or many tracking levels can Exception / Failure Related System Activity Required
be set as shippable units using the Shipping Unit Level indicator(s) Name and Description
within the Pack Configuration. Where a TMS is used to communicate an Attempt to Pick an A message is displayed to alert the
update back to an Order, an allowance is made for the TMS to be able Order that is not part operator that they are starting an order
to identify that Shippable Units is applicable. This means that the client of a Consignment that has not been prepared correctly.
does not have to identify this on the initial submission of the Order to The order should not be picked until
the WMS, and that the TMS is able to make a decision based on order preparation has been used to
planning. add a consignment value.
Fail Pick short / nil Pick as per the defined Pick process
The dimensions used within documentation and extracts will be those above, capturing the actual amount
recorded against the relevant tracking level within the Pack picked.
Configuration. Prompted for a reason for the pick Qty
being less than requested reason
codes available to select are: damaged
Picking when Integrated with the I2M SMART Solution Stock, Not Enough, or Split Pick.
For Not enough reason code, The
If using the Integration with the I2M SMART Solution Option Pack, a operator is then taken to the Stock
pick notification API will be sent to Insequence to inform of allocated check function to confirm the quantity
pick tasks. that remains. The operator is then
prompted to re-confirm (as different to
Insequence is used for picking onto racks and the production of what is expected). The suspense
paperwork. account (location) is updated with
reduction of inventory.
A pick confirmation API will be sent to Matrix WMS CORE+ to confirm
the picking activity and the container.
If replenishment is generated then it
Insequence will confirm the completion of picking activity for an order follows the previously described
and its location using the move confirmation API to Matrix WMS process. Automatic allocation with
CORE+. See I2M SMART Solution Integration with Insequence & IFL occur if possible and a task created to
pick the remainder, which is performed
for more details.
as per a normal pick.
Fail Pick damage Pick as per the defined Pick process

above, capturing the actual amount
picked.
Prompted for a reason for the pick Qty
being less than requested reason

CORE+
Outbound
Exception / Failure Related System Activity Required Exception / Failure Related System Activity Required
codes available to select are: damaged Fail Pick unexpected As per a short pick, but then with an
Stock, Not Enough, or Split Pick. inventory in location inventory query to determine what to
For damaged reason code, The do with the discovered inventory (such
operator is then taken to the Stock as relocate as needed).
check function to confirm the quantity Outbound Order The cancellation of an Outbound Order
that remains. The operator is then Cancellation is identified by the client and notified
prompted to re-confirm (as different to to CEVA. CEVA then assesses if the
what is expected). The suspense Outbound Order is at a suitable status
account (location) is updated with for cancellation.
reduction of inventory and the During / after Pick [High Risk]
used on the affected Pallets /

A manual relocation task is created by Containers, then the inventory is
the Team Leader and performed by an relocated back to storage. The Team
operative to relocate the damaged Leader deletes the move tasks created
stock to the QA Hold area. using the Move Task Update screen.
IMPORTANT: This must be performed The Team Leader updates the
in a timely manner as a replenishment Outbound Order Header to the status
task will also have been triggered to
place pristine stock into the pick face via the same way CEVA was notified of
failure to relocate the damaged stock the desire to cancel, or via message if
prior to the replenishment being enabled.
completed will result in the replenished Notification of Carriers that are able to receive voiding
inventory being concatenated to the Differences between confirmations will receive notification of
damaged inventory and a cycle of Planned and Shipped containers that are no longer planned
replenishments will be created (until to be despatched (triggered by the
the damaged inventory is moved or deallocation process).
resolved).
If replenishment is generated then it

follows the previously described
process. Automatic allocation with
occur if possible and a task created to
pick the remainder, which is performed
as per a normal pick.

CORE+
Outbound
Outbound Pick Decisions (for configuration / Set up) • Is Replenish Part Tag required? [select one]
• Push of Pick Tasks
[select one] □ Yes
□ Yes □ No
□ No • Will serialized SKUs require their serial number(s) captured
during pick? [select one]
• If Yes, please provide the Work List data take on spreadsheet.
□ Yes
Enter link link
< Enter to completed data data
to completed take take
on spreadsheets here here>
on spreadsheets
□ No
• Will scanning of the SKU / EAN / UPC barcode be required for • If Yes, which default serial capture profile is required (see Set
every pick? [select one] Up / Master Data section to view default profiles)? [select one]
□ Yes I confirm that every SKU has a barcode with this □ Inbound and Outbound Pack
value
□ Inbound and Outbound Pick
□ No □ Outbound Only Pack
• Will TAG confirmation of full pallet picking be required? [select
one]
□ Outbound Only Pick
□ Yes □ Inbound and Outbound Pick and Pack
□ No □ Custom per SKU (configured per SKU on import into
the WMS)
• Are Special Instructions required to be presented on the mobile • For full TAG movements should serial scanning be suppressed
device during picking (requires integration) ? [select one] for multi-serial TAGs? [select one]
□ Yes □ Yes
□ No □ No
• Will the container ID be required to be scanned on the deposit
• Are automatic Stock Check Tasks required to be generated into it for every pick? [select one]
when a location is picked to zero? [select one]
□ Yes (default) □ Yes

□ No □ No
CORE+
Outbound
• Will the Follow Me Logic Option Pack be required? [select one] • Is integration with Insequence required as part of the I2M
□ Yes SMART Solution (Integration with I2M SMART Solution Option

Pack)? [select one]
□ No □ Yes
• Will consolidated picking of SKUs (grouping of all pick tasks for □ No
a single SKU into one pick task) be used? [select one]
□ Yes I will also be using the Post Pick Activity option •

one]
Pick Face Circuits feature be used for Picking? [select
pack; I will not be using serial capture at point of pick.
□ Yes - I will also be using the 'Post Pick Grid Sortation' □ Yes
option pack. □ No
□ No • Cascade Replenishment feature be used for Picking?
[select one]
Voice Control
□ Yes
•
one]
□ Yes □ No
□ No • Replenishment Runs
Replenishment picking? [select one]
Locus Cobot
□ Yes
•
one]
□ Yes □ No
□ No • Where will the Picking Media label (and what barcode type) be
printed to? [select one]
• GEEK+ Goods to Person
Picking? [select one] □ Picking Media Label not required
□ Yes □ Printer requirements specified within the Printer Data
□ No Take on Spreadsheet

CORE+
Outbound
• Is Mobile device picking consolidation of order lines within a

single order at a single pick location required to be turned off?
[select one]
□ [Default] Yes, turn this particular consolidation off.

□ No, turn it on.
• Is the One-Piece Flow Option Pack required for shipping units?
[select one]
□ Yes
□ No
• Are (bespoke) Retailer Compliant Shipping Labels required
(Retailer Compliant Shipping Labels Option Pack)? [select one]
□ Yes
□ No
• Is the "Warehouse Outbound Activity Commenced" interface
(EDI extract generated from the WMS to the middleware layer)
required to be sent - IDEALLY FOR EXTERNAL SYSTEMS?
[select one]
□ Yes
□ No
Pick Section Complete

CORE+
Outbound
Outbound Load Preparation Guiding Principles

• For Ship As Is items being picked and despatched with no
Diagram physical change (no repack or consolidation), the SKU
Pick
Load
Outbound
Vehicle
dimensions will be used as the container dimensions. This works
Preparation
Arrival
for repacked items of a quantity of 1 (EA) in a single container
Carrier
that has the Ship As Is flag indicator enabled.
Consignment #
Interface • If consolidated pick per SKU for many orders is performed, then
a secondary activity of sorting to the relevant order must be
6.1 6.2 6.3 6.4 6.5 performed as part of Load Preparation.
Arrival at Perform Move to Arrival at Manual • The separation of orders for different post pick activities is
Activity / Activites Ship Dock Ship Dock Consolidation
Grid Zone controlled per order.
• Each order may only be directed to one of the following post
CEVA
pick activity areas:
Packing
Report
Container
Label
Shipping
Label
Consolidation
Report o Post Pick Activity Zone dynamic areas not specific to
Carrier Label Ready To Load /
any order / customer that are good for multiple picking
Request
Interface
Customs Decl.
Interface
flows through the facility.
o Post Pick Activity Location fixed locations specific to an
Receiver
Compliant
Label Delivery Note
order / customer that support multiple picking flows
through the facility.
Carrier
Container
Label Bill of Lading
o Grid Zone ideal for operations that use 'batch' picking
(large volume of a single SKU for many different orders)
for a fixed customer (delivery location) base.
Packing List
o Kitting Location used to build kits from picked
Packed / Invoice
Request component parts (Kit to Order and Kit to Stock Option
Interface
Packs)
Shipping • Integration with an external weigh scale is available to accurately
Label
calculate the weight of pallets.
• Integration with the CEVA Packing Application is available and
Delivery Note
enabled at Client level as an alternative to using the WMS
repacking functionality. If enabled, all repack tasks will be
Bill of Lading
directed to the CEVA Packing Application, and therefore will not
be available to be completed within the WMS.
Returns Note
• The same ID may not be used for multiple media this includes
CEVA
Commercial
the ID for a container on top of a pallet (they cannot be shared).
Invoice

CORE+
Outbound
• A message is able to be sent confirming that "Warehouse • Repacking from a single pick container to multiple shipping
Outbound Activity has completed" per order once the order is containers
ready to be loaded. This message will be generated when the • Repacking from multiple pick containers to multiple shipping
containers
header information only. • Repacking and consolidating from multiple pick containers to a
• A Warehouse Dashboard is available alongside the WMS which single or fewer multiple shipping containers
provides a real-time, single view of key metrics including • Building Kits (comprising of 2 or more component SKUs) (Kit to
outstanding outbound move tasks. Order and Kit to Stock Option Packs)
• Performing VAS
• Performing outbound quality check(s) / inspections
Following picking, if additional activities are required prior to loading
• Producing Packing lists either CEVA standard or bespoke
(or prior to putaway if using the Kit to Stock Option Pack) then the order
version (Flexible Documents Option Pack)
arrives at one of the following:
• Preparing Hazardous labelling / paperwork prior to shipping
• Weigh Scale Location (if integrated) (away from the WMS)
• The relevant Post Pick Activity Zone (Post Pick Activities Option • Preparing Freight paperwork prior to shipping (away from the
Pack) WMS)
• The relevant Post Pick Activity Location (Post Pick Activities • Triggering the production of and applying container or pallet
Option Pack) labels either CEVA standard ones or Carrier specific ones.
• The relevant Grid Zone (Post Pick Grid Sortation Option Pack) • Consolidating and/or bundling many shipping containers into a
• The Kitting Location (Kit to Order and Kit to Stock Option Packs) single Transport container
• Put To Wall Sort Area (Batch Pick - Then Put to Wall) • Consolidating and/or bundling many shipping containers into
many Transport containers
A dashboard is available within the WMS to view live details of • Triggering the production of and applying CEVA standard
outstanding post pick/grid activities. Access to the Ready for Post Pick transport labels to the transport containers.
Activity Dashboard is through a dedicated user account and allows • Outbound FMD processing for identified Order Lines.
viewing as and when required, or ideally set up as a fixed dashboard
within the warehouse see an example at the end of the section and
section for more details. Following the performance of the required activities, or if none are
being used then following pick, the order(s) is moved to the stated ship
Additional activities can include one or many of the following: dock. If required, and not already produced, the Shipping labels and
Delivery Note are printed and applied either CEVA standard or
• Validation of the picked weight based on the provided SKU
bespoke version (Flexible Documents Option Pack). For Bonded
master data (if integrated with weigh scale)
Warehouses, an interface for customs declaration is created where
• Repacking from a single pick container to a different single
applicable (Bonded Warehouse Option Pack). Minor manual (off
shipping container

CORE+
Outbound
system) consolidation for a better fit on the outbound truck / container • Commercial Invoice
may be performed in preparation for loading.
This feature allows the suppression of the physical print whilst retaining
the PDF, or the suppression of both. Please liaise with your Technical
Production of Bill of Lading documentation is triggered when the
Consultant to enable this feature.
con
produced per consignment; one Bill of Lading is produced per Supporting Matrix Functionality
shipment and where the amount of data exceeds one page (of either
the Master, or Bill of Lading document), a Supplement to the Bill of What are Grid Zones?
Lading will be produced.
As part of the Post Pick Grid Sortation Option Pack, the use of grid
zones is provided. This is to support the sorting activity that occurs after
Retailer Compliant Shipping Labels Option Pack picking has been completed. It is useful to use where you have
The Retailer Compliant Shipping Labels Option Pack enables the reoccurring shipments to the same group of customers. An example
bespoke design of labels that are created in a format specified by the might be an automotive manufacturer who needs to separate out
Retailer to aid in their inbound receiving process. These labels are able deliveries to specific dealerships each day. This option pack works
to be triggered when the container and / or pallet reaches the status particularly well with batch picking, where the picking of the same or
many SKUs for multiple orders, and then sorting between pre-defined
customers is required.
triggered after repacking on the PC or mobile device. A flag set against the order line combined with the family group
specified on the SKU are the controlling items that direct the picked
For more information please liaise with your WMS CoE Implementation goods to the grid zone.
Consultant.
Grid zones comprise of dedicated customer subzones which contain
one or many grid locations. It is recommended that only one pallet is
Prevent Unnecessary Printing of Paperwork open per grid location at any one time.
It is possible set qualifiers to prevent the unnecessary printing of certain A subzone containing one grid location will offer only one / put
types of documentation. Available qualifiers: location, whereas multiple locations within a customer subzone will
prompt the operator to specify the required location and allows for
• Site / Client
goods to be placed in to multiple locations for the same customer at
• Order Type
the same time.
• Delivery Point (EU / Non-EU)
High-Level Process
Available for the following documents:
• Once picked, the inventory is deposited into the grid in stage
• Pack / Contents List
location
• Delivery Note

CORE+
Outbound
• Using the Grid Picking screen on the mobile device, the picked Following picking, component SKUs will be deposited at the Kitting
pallet ID is scanned into the Grid Pick Entry screen Location where the building of the Kit is completed using the Kitting
• The operator enters the grid pick start location function within the PC application.
• The operator scans the SKU(s) required for post pick grid If using the Kit to Stock Option Pack a move task will be generated to
sortation, and presses enter after scanning the final SKU putaway the completed Kits (or component parts if processing an Unkit
• The operator is directed to the first location to Stock order). If using the Kit to Order Option Pack a move task will
• The pallet type is entered if there is no pallet yet in the location be generated to move the completed Kits to the required Ship Dock, or
• The SKU and quantity required are displayed to the relevant Activity Zone / Location (if using the Post Pick Activities
• The operator places the goods into the location and presses Option Pack).
enter to confirm
If using the Kit to Stock Option Pack it is possible to set a pickface
• If further SKUs are to go to this grid location, the next SKU and
trigger which will generate replenishment tasks to move component
quantity required is displayed, otherwise the next location is
parts to the kitting location. Once kit building is complete the built kit is
presented
relocated to the pickface.
• After confirming the last SKU into its location, the Grid Pick Entry
screen will reappear and the process can be repeated for the
next Post Pick Grid Sortation activity Batch Pick Put to Wall
• Once the entire order is within the grid and all goods have been If using the Batch Pick Put to Wall feature, consolidated pick runs
sorted in to the correct location(s), the pallet can be closed using enable multiple orders to be picked into one or many picking media.
the Pallet Closure screen within the mobile device. Picked goods are deposited into a sortation area where orders are
sorted using a putwall.
Outstanding move tasks within the grid can be viewed within the Grid
Management Screen which is visible only to those sites utilizing the Post High-Level Process
Pick Grid Sortation Option Pack.
• Picked inventory is deposited into a Put to Wall Sort area
Note: Activation of the Post Pick Grid Sortation Option Pack will apply • Using the Pick and Sort feature on the mobile device, the picked
site wide changes to the Container Picking screen within the mobile Container or Trolley and Slot is entered into the Sort Pick Entry
device application, however it is not mandatory that all orders are screen
processed using the Post Pick Grid Sortation activity. • The Sort to Location is displayed:
Kitting o If already populated this indicates that part of that
Shipment Group has already been sorted and these
Kitting, or Bill of Materials (BOM) processing through parent (kit) / child
goods must be directed into the same putwall location
(component) association is possible if using either of the Kit to Stock or
o
Kit to Order Option Packs.
location is entered
• The SKU and quantity to be placed into the putwall location is
displayed
CORE+
Outbound
• The goods are placed into the location and confirmed on the There are two variations available:
mobile device
1 - Directed to an Activity Zone with the
• The Sort Pick Entry screen will reappear, and the process can be
repeated for the same container / trolley until it is empty
• If required repack can be completed within the putwall location; The entire order is directed to a specific activity zone and on deposit,
inventory will not be directed to a Post-Pick Activity Zone. Items the operator may overwrite the specified activity zone with the
that have been placed in to the putwall will be directed to the appropriate activity location that they wish to use.
instage of a shipdock next.
The controlling item is the Stage Route ID that is passed on the Order
Header (via interface or upload only) which is then used to direct the
Post Pick Weight Validation entirety of the order to a specific activity zone.
Integration with an external weigh scale provides weight validation to -
ensure correct weight values are captured. The overriding of weight
validation failures or discrepancies is possible when configured with the status Hold or Released.
pallet type tolerances.
2 - Directed to a fixed Activity Location which is not able to be altered
The entire order is directed to a specific activity location. The activity

Co-Packing Using Co-Pack SMART Solution location is fixed and cannot be changed by the operator.
the Pack Manager application will be used to perform the co-packing The controlling item is the Repack Location that is passed on the Order
Header (via interface or upload only) which is then used to direct the
activity, production of finished goods including controlling QA process
and pallet labelling. Finished goods are received back into the WMS entirety of the order to a specific activity location.
using an Inbound order from Pack Manager. See Co-Pack SMART If using Repack Locations, it is possible to use the Repacking Overview
Solution Integration with Pack Manager for more details. screen to see an overview of the workload at the Repacking Locations.
It is possible to update the Repack Location vi -

What are Activity Zones?
status Hold or Released.
As part of the Post Pick Activity Option Pack, the use of post pick
activity zones and post pick activity locations is provided. Activity zones
and activity locations are designated areas where a specific post pick operation deciding (and visually managing) what they will use each zone
activity can be performed, or simply used to segregate certain groups used for. Each zone has 20 predefined locations (AZONE01-AZONE20
of orders. for example) of which as few or as many can be used to represent
marked areas on the warehouse floor for when orders (or parts of
orders) are deposited to the activity Zone.

CORE+
Outbound
Examples of Different Activity Zones / Activity Location set ups are: placed into on the sheet. When all deposits have been done the picker
then signs and date / time stamps the sheet then passes it to the team
• An activity zone per carrier
• An activity zone per geographical region, area or country screen to update the system. The List ID is entered, the operator who
• An activity zone per bonded / non bonded containing performed the tasks captured, the correct locations used captured, then
• An activity zone for HAZMAT / Non HAZMAT the tasks completed are confirmed.
• An activity zone for packing
• An activity zone for FMD processing [6.2] Perform activities
• An activity zone per type of VAS It should be noted that the contents of the Activity Zones can be
• An activity location by order viewed from the Move Task Management Screen. To focus attention on
• An activity location per customer the Activity Zones, any fields not required within the Move Task
Management screen should be removed from view to ensure a much
• An activity location per dealer
shorter and more meaningful selection of columns are presented. The
[6.1] Arrival at Activity Zone check boxes can also be ticked to ensure that when there are no tasks
Via Mobile Device in the work zone, the work zone is not shown.
For the Post Pick Activity Option Pack only - either from completing the Via a PC: Repacking function
picking of the order / list or by using a function key to enable an early
or activity Using the Repacking function on a PC, the operator is able to work at a
location is displayed. Note that if only the zone is displayed (i.e. bench to perform the activities as needed. Using the Repacking
AZONE); the operator is to choose the appropriate location within the function gives access to all of the Matrix WMS CORE+ functionality
zone that they wish to use. If the activity location is displayed (i.e. available within an activity zone. Using the PC function, the operator
AZONE01); the operator must use the location presented. can:
Once the deposit has been made into one of the locations within the - Confirm repacking at a SKU by SKU level from one or many
activity zone, the check digit is captured for the location (a check digit containers to one or many containers (which could be the same
must exist for each location within the activity Zone). containers).
- Have displayed the Special Instructions which detail the VAS to
be performed.
ready for Post Pick Activiti see - View the system or external weigh scale calculated weight and
dimensions on the containers and override the values if required
. and within tolerance (see Pallet Config DTO for tolerances).
Via paper & PC - Generate either the CEVA Standard Container Shipping label or
Carrier specific Container label based upon the Carrier and
As the Picker deposits the picked inventory (in media) to the stated Service level stated on the order (interface out to the carrier
Activity Zone on the Pick List, they write down the actual location label creation tool; return output of the label; return interface of
CORE+
Outbound
tracking reference) - see examples at the end of the section and populated. If required, the system calculated weight can be manually
. overridden; with the new value being presented as the container gross
Generate the Packing / Contents List for the container in the weight in any relevant documents. If appropriate for the order line,
language indicated on the order - either CEVA standard special instructions will be displayed in a pop up window for the
document or bespoke version (Flexible Documents Option Pack) operator. The option to close the pallet/container is available, and as
see example of standard document at the end of the section the task is updated to say that it is complete, the relevant labels (for the
. carrier / service level) packing list and delivery note are printed.
-
Alternatively, if a container or pallet is desired to simply be closed, the
hence generate the invoice request interface (Bonded
pallet or container ID can be entered and then confirmed to close
Warehouse Option Pack), Returns Note (with locations for client
(hence producing the relevant labels and documents).
Commercial Invoice (note both documents require information Via a PC: CEVA Packing Application
that is only available to be provided when interfacing is used)
when all of the order has been packed - see document examples If integration to the CEVA Packing Application is enabled, all repacking
tasks for the Client will be directed to the application. The status of the
section for more details on the Returns Note and Commercial move task within the WMS will be set to In Progress, and the User ID
Invoice. will be updated to PACKAPP.
- Generate the Delivery Note for the Order in the language Using the CEVA Packing Application the operator performs all
indicated on the order - either CEVA standard document or necessary repacking. Upon completion, the move task is updated within
bespoke version (Flexible Documents Option Pack) - see the WMS to say that it is complete, and the relevant documentation is
example of standard document at the end of the section and generated.
.
Mobile Device: Order Repacking
If the container type the SKUs are being packed into is not held against
the container (e.g. boxes are being re-used from within the operation), The Order Repacking function allows for the contents of an entire
then the repacking function on the PC must be used instead of the container to be transferred to a new or existing container, on a new or
Mobile Device to allow the capture of correct weight and dimensions existing pallet.
for population on the appropriate labels and delivery documents. To use the function, is identified. Next a
Using the Repack function, the operator enters the location they are container or pallet ID is entered into the ID field.
field is an existing container or pallet,

the container will be repacked.
Pallet ID, Pallet Type, Container ID and Container Type being used are
entered. As the records are moved (dragged or selected and click If repacking into a new container, the container type must be entered in
areas, the current volume, current weight and container height are co

CORE+
Outbound
completed. From the Order Repacking screen, enter the newly created Special Instructions
container
Special instructions will be presented to the operator on the mobile
a new or existing pallet ID. If repacking onto a new pallet, the pallet
device if held against the outbound order header or line(s). These
type must be confirmed in the next screen. Note: if this second repack
instructions are available for both Pallet and Order Repacking.
activity is not completed both the container and pallet ID will be the
same which can cause issues with integration.
Mobile Device: Close Container
Using the Close Container screen, the container / pallet ID is entered
can be overridden by entering a new value in

field. One confirmed a message will appear stating that the container /
pallet has been closed.
Mobile Device: Pallet Repacking
Using the Pallet Repacking function allows for the contents of an entire
container or pallet to be transferred to another pallet, then
automatically close the pallet (and container) and print out the required
labels and documents.
To use the function, first the destination pallet is identified and if not
already known, the pallet type is entered. Next the source container /
pallet is identified. The destination container details are entered and if
required the type and weight may be amended. This last step is then
repeated for as many pallets / containers you wish to consolidate or add
to the destination pallet. When you are complete you then use a
function key to exit the function and trigger the closing of all pallets /
containers, plus print all labels and documents. If required, the operator
may be prompted to enter the pallet height.
It is possible to palletize repacked containers without triggering repack

messages and / or labels. This is Carrier specific, controlled at Carrier
level and allows for mixing of service levels on the same pallet for the
same Carrier. Please note that this feature cannot be used in
conjunction with Force Single Carrier per Pallet.
CORE+
Outbound
Example of the Ready for Post Pick Activity Dashboard Available within the WMS for dedicated dashboard accounts (Post Pick Activity Option Pack
Only).
CoE – Matrix® WMS CORE+

CORE+
Outbound
Example of a Ready for Post Pick Activity Report Automatically printed once all of an order is picked (Post Pick Activity Option Pack Only).

CORE+
Outbound
Example CEVA Standard Container Shipping Label (Post Pick Activity Option Pack Only).

CORE+
Outbound
Example of a CEVA Standard Pack / Contents List (Post Pick Activity Option Pack Only).

CORE+
Outbound
Example of a CEVA Standard Delivery Note

CORE+
Outbound
Example Bill of Lading Documents
Master Bill of Lading Bill of Lading Supplement to the Bill of Lading

CORE+
Outbound
Example of a CEVA Standard Commercial Invoice

CORE+
Outbound
Example of a CEVA Standard Returns Note

CORE+
Outbound
Example of a CEVA Standard Pallet Shipping Label

CORE+
Outbound
Via PC: Capture Tracking References the Pack Configuration web screen. All applicable documents and
labels will be triggered at this point.
After packing the containers but prior to moving to the ship dock, it is
possible to capture the Carriers Shipment Tracking ID (in NORTAM this As this feature requires use of t on the RDT
is the PRO#), the Transport Booking ID and the Customers Transport it is not compatible with Mobile Device: Capture Carrier Tracking
Authorization ID - all per order (if not provided on the interfaced order Reference.
ION - Update Carrier Tracking
[6.3] Move to Ship Dock
Via Mobile Device
Mobile Device: Capture Carrier Tracking Reference
res the pallet ID and is
After packing the containers but prior to moving to the ship dock, it is
not integrated via a CEVA Carrier Integration Tool). This is performed

location and the check digit is confirmed (if the location does not have a
Container ID and then the tracking ID. check digit then the move is simply confirmed).
Note that Carrier Tracking References captured / integrated into the [6.4] Arrive at Ship Dock
WMS are visible -
Upon arrival at the Ship Dock, if the Pallet Shipping Label (per pallet
Batch Generation of Container Shipping Documentation deposited) and Delivery Note (as the full order is present in the ship
dock) have yet to be printed then they will be triggered see examples
This feature is designed to generate a number Shipping Unit quantities
for a single SKU from one full picked pallet. more details
Unlike other Shipping Unit solutions, the Shipping Units for this process the full order is present on the ship dock; for the Bonded Warehouse
are not generated at the point of allocation. Option Pack only this status progression is used to trigger the customs
declaration interface.
Importantly this process makes use of some standard Shipping Unit
configuration data that is managed on the Pack Configuration web [6.4] Manual Consolidation
screen. Please note that only 1 shipping unit level may be used per If desired manual consolidation can be performed without interaction
pack configuration with this feature e.g. cases (CA). and update of the WMS at this point. Typically this is done to better
assist vehicle or container fill or for safety during transit.
Users will pick full pallets of a single SKU and deposit a pallet to an
Activity Zone location. The operator will then access the Reprint
Shipping Label RDT menu and follow the on-screen instructions, which that shows what pallets for each orders are in the ship dock.
will require them to capture the pallet ID that they are working with and
the target locality. Once this information has been captured Shipping
Units will be generated automatically, to the build as specified within

CORE+
Outbound
Exceptions Exception / Failure Related System Activity Required

Exception / Failure Related System Activity Required Name and Description
Name and Description During post pick activity [High Risk]
Multiple Orders are If the need to pack multiple orders into
desired to be packed a single container exists, then this is used on the affected Pallets /
into a single container possible with the labels, documents Containers, then the inventory is
and interfaces fully supporting it. relocated back to storage. The Team
Leader deletes the move tasks created
Re-packing identified If the need for repacking is discovered, using the Move Task Update screen.
as required, prior to such as poor original packing or The Team Leader updates the
marshal to the ship additional items to pack, then the Outbound Order Header to the status
dock Repacking function on the PC is used
to repack as necessary. via the same way CEVA was notified of
the desire to cancel, or via message if
If marshalling to the ship dock has enabled.
occurred, then using the repacking Notification of Carriers that are able to receive voiding
function again is not possible. Differences between confirmations will receive notification of
Planned and Shipped containers that are no longer planned
Carrier label fails to be to be despatched (triggered by the
produced function can be used, deallocation process).
CEVA labels and Packing List.
For Labels that are Carrier specific (and

hence printed out of CarCon) a
helpdesk ticket is logged to resolve the
issue.
Reprint required for The operator would run the user report
the Delivery Note -STN-
the document.

for cancellation.

CORE+
Outbound
Outbound Load Preparation Decisions (for configuration / Set up) • How will the Repack Location be populated on the order when
• If additional activities are required prior to loading, which it is received into the WMS? [select one]
features are required? [select one or many]
□ No Repack Location to be populated
□ Post Pick Weight Validation (Integration with external □ By the client on their order file
weigh scale)
□ Post Pick Activity Option Pack □ BytheCEVA applying simple structured business logic in
Integration layer?
□ Post Pick Grid Sortation Option Pack Please define below the business rules / logic that will
be used to derive each choice of Repack Location value
□ Kit to Order and hence drive orders post pick to a matching Activity
Location. Allowed fields for use in the logic are -
□ Batch Picking - Then Put to Wall Creation Date, Dispatch Date, Delivery Date, Carrier,
□ No additional activities are required Service Level, Order Type, Country, Hub Name,
Customer ID, Shipment Group.
• How will the Stage_Route_ID be populated on the order when Enter business rules / logic here
it is received into the WMS? [select one]
□ No Stage_Route_ID to be populated Post Pick

Activity is not to be used
□ By the client on their order file

□ By CEVA applying simple structured business logic in
the Integration layer?
Please define below the business rules / logic that will
be used to derive each choice of Stage_Route_ID value
<Enter business rules / logic here>
and hence drive orders post pick to a matching Activity
Zone (these are pre-populated in the system and
Enter business values
applicable rules / are
logic here through to ZZONE).
AZONE
Allowed fields for use in the logic are - Creation Date,
Dispatch Date, Delivery Date, Carrier, Service Level,
Order Type, Country, Hub Name, FMD Reason.
<Enter business rules / logic here>

CORE+
Outbound
• Will the consignment be sequenced for load? [select one] • If you have chosen to use the Post Pick Activity Option Pack, is
□ Yes - this will be performed by an operator in the Order the capturing of pallet height at RDT Repack required? [select
one]
□ Yes
Preparation screen whilst building a consignment
□ Yes - the sequence will be received on the order

interfaced into the WMS □ No
□ No • Is integration with the CEVA Packing Application required?
[select one]
•
□ No
If you have chosen to use the Post Pick Activity or Post Pick
Grid Sortation Option Packs, will carrier labels be triggered
from CEVA Carrier integration tool? Please note that it is not
responsibility of the Matrix WMS CORE+ team to provide the □ Yes All required repacking activities will be
setup in the external label tool. [select one or many] completed within the CEVA Packing Application
(outside of the WMS):
□ The CEVA Standard Container and / or Pallet Shipping
label from Matrix WMS CORE+ will be used, using • If you require integration with the CEVA Packing Application,
Container / Pallet ID as the barcode please provide the following information:
□ The CEVA Standard Container Shipping label from Average number of orders processed per day:
Matrix WMS CORE+ will be used, using an SSCC / GS1 Add maximum number
< Add average of orders
number per day
of orders (peak season)
per day>
Barcode
Average number of order lines per order:
□ Atonon-integrated external tool / web page will be used
Add<average number
Add average of orders
number processed
of order per day
lines per order>
produce carrier labels
□ Yes Integration will be used between the WMS and

Maximum number of orders per day (peak season):
Add average number number
< Add maximum of orderoflines perper
orders order
day>
the external label tool to request a label, receive back a
consignment number and then confirm shipment of the daydayofbenches:
Number of packing packing benches>
package.
Add number of packing
< Add benches
number of packing benches>
• If you have chosen to use the Post Pick Activity Option Pack,
are Special Instructions required to be presented during • If you require integration with the CEVA Packing Application,
packing (requires integration) ? [select one] please specify the following functional requirements:
[Packing App] Display proposed box type?
□ Yes □ Yes
□ No □ No
CORE+
Outbound
[Packing App] Validate Batch? [Packing App] Pallet Building?
□ Yes (When enabled ALL containers need to be placed on a

pallet)
□ No □ Yes
[Packing App] Validate Expiry Date? □ No
(Available when Shipment Shelf Life is set on SKU. This is
developed to validate the Shelf Life not to confirm the [Packing App] Only display special instructions with
Expiry Date) the 'use RDT' flag?
□ Yes □ Yes
□ No □ No
[Packing App] Weight Validation?
• Is the Prevent Unnecessary Printing of Paperwork feature
□ No required to be used (available for the Pack / Contents List,
□ Yes: Delivery Note, Commercial Invoice)? [select one]
□ Yes (details to be provided to your Technical

Positive Allowed Percentage:
Consultant)
Enter positive
< Addpercentage allowed
Positive Allowed Percentage>
Negative Allowed Percentage: □ No
Enter negative percentage
< Add Negative allowed
Allowed Percentage>
• Will the Delivery Note, Container Shipping Label [Post Pick
[Packing App] Piece Scanning? Activity or Post Pick Grid Sortation Option Packs only] and
(Available for SKUs that have the 'Repacking by Piece' flag Packing List [Post Pick Activity or Post Pick Grid Sortation
enabled) Option Packs only] use the CEVA logo or the client logo (please
provide)? [select one]
□ Yes □ CEVA logo
□ No □ Client Logo
[Packing App] Blind Quantity Check? Provide link<toProvide
logo tolink
useto the logo to use>
□ Yes
□ No
CORE+
Outbound
• If you have chosen to use the Post Pick Activity Option Pack, • If you have chosen to use the Post Pick Activity Option Pack,
where will the Ready for Post Pick Activity Report be printed to? will the manual capture of the Shipment Item IDs be required
[select one] (Mobile Device: Capture Carrier Tracking Reference (café
□ Ready for Post Pick Activity Report not required model))? Please note this is not compatible with Batch
Generation of Container Shipping Documentation.
□ Printer requirements specified within the Printer Data □ Yes

Take on Spreadsheet
□ No
• If you have chosen to use the Post Pick Activity or Post Pick
Grid Sortation Option Pack, is the Ready for Post Pick Activity • Is Batch Generation of Container Shipping Documentation
Dashboard Report required? [select one] (creation of shipping units from bulk full pallets after picking)
□ Yes required?
□ No □ Yes
□ No
• If you are using Container Labels, list the carrier / service level
combinations that you wish the Container label to be produced • If you have chosen to use the Post Pick Activity Option Pack,
for? [select one] where will the Container label be printed to? [select one]
□ Container Label not required □ Container Label not required
□ Container Labels to be produced for: □ Printer requirements specified within the Printer Data
Enter the Carrier(s) / service(s) here Take on Spreadsheet
• If you are using Packing Lists, which Packing List is required?

[select one]
<Enter the Carrier(s) / Service(s) here>

□ Packing List not required
□ CEVA Standard Packing List
□ Bespoke
Pack)
Packing List ( Flexible Documents Option

CORE+
Outbound
• If you have chosen to use the Flexible Documents Option Pack • If you have chosen to use the Flexible Documents Option Pack
to create one or many bespoke Packing Lists, which template is to create one or many bespoke Delivery Notes, which template
required? [select one or many] is required? [select one or many]
□ A6 Label Packing List □ A4 Portrait Delivery Note

□ A4 Portrait Packing List □ A4 Landscape Delivery Note
□ A4 Landscape Packing List □ US Letter Portrait Delivery Note
□ US Letter Portrait Packing List □ US Letter Landscape Delivery Note
□ US Letter Landscape Packing List
• If you have chosen to use a Delivery Note. When should the
Delivery Note be triggered to be printed? [select one or many]
Grid Sortation Option Pack, where will the Packing List be □ At the point of allocation (as part of the set of
printed to? [select one] Allocation documents when using picking methods
□ Packing List not required without Post Pick Activities)
□ Printer requirements specified within the Printer Data

□ When the entire order has been grid picked and sorted
Post Pick Grid
Take on Spreadsheet Sortation Option Pack]
□ When the entire order: [select one]

• Which Delivery Note is required? [select one]
□H Post Pick
□ Delivery Note not required Activity Option Pack only]
□ CEVA Standard Delivery Note per Order □I

□ CEVA Standard Delivery Note per Shipment Group
□ Bespoke Delivery Note ( Flexible Documents Option • If you have chosen to use a Delivery Note. Where will the
Delivery Note be printed to? [select one]
Pack)
□ Delivery Note not required
Take on Spreadsheet

CORE+
Outbound
• If you have chosen to use the Post Pick Activity or Post Pick • At what point is the Pallet Shipping Label required to be
Grid Sortation Option Pack (and are using the order Interface), triggered? [select one]
where will the Returns Note be printed to? [select one]
□ Pallet Shipping Label not required
□ Returns Note not required □ In conjunction with Repacking
□ Direct at Ship Dock In-Stage
Take on Spreadsheet
□ In conjunction with Repacking AND also direct at Ship

Dock In-Stage
Grid Sortation Option Pack (and are using the SKU, Pre-Advice
and Order Interface), where will the Commercial Invoice be
printed to ? [select one]
Grid Sortation Option Pack, Is an Invoice Request interface (to
□ Commercial Invoice not required the client) required? [select one]
□ Printer requirements specified within the Printer Data □ Yes, gen (after packing
Take on Spreadsheet - Note: this needs to occur and the invoice produced
and included with the goods, prior to moving the
inventory to Ready to Load [which would trigger
another interface for bonded warehouses see below])
• If you require Bill of Lading documentation, where will the
Master Bill of Lading, Bill of Lading and the Supplement to the
Bill of Lading be printed to when the consignment reaches
□ No
? [select one]
□ Bill of Lading documentation not required • If the Bonded Warehouse Option Pack is being used, is a
Customs Declaration interface required (to be sent from the
WMS to the Middleware)? Please note, that if you are taking
Take on Spreadsheet shipped as the positive confirmation of the goods being
despatched) [select one]
• Are (bespoke) Retailer Compliant Shipping Labels required
(Retailer Compliant Shipping Labels Option Pack)? [select one]
□
□ No
□ Yes
□ No

CORE+
Outbound
• If CEVA internal systems are being used (e.g. OMS or TMS), is
them (to be sent from the WMS to the Middleware; NOT FOR
EXTERNAL SYSTEMS)? Please note, that if you are taking
shipped as the positive confirmation of the goods being

despatched) [select one]
□ Yes, CEVA Standard EDI Message

□ No
• Is the "Warehouse Outbound Activity Completed" interface
(generated from the WMS to the middleware layer) required
□ Yes
□ No
Load Preparation Section Complete

CORE+
Outbound
Outbound Vehicle Load Guiding Principles

• For Bonded Warehouses, loading is not performed until customs
Diagram clearance is given.
Outbound • The task of physically loading the vehicle crosses the
Vehicle management boundary of the warehouse and as such capturing
Vehicle Vehicle Load
Despatch
Arrival accurately when the task occurs is important for audit purposes.
• The ability to record a pre-vehicle load check is available at site
level.
• If using the Ship in Full feature any short-picked orders will be
prevented from being vehicle loaded.
Customs
• Asset Recording provides the ability to record the count of pallet
Approval types received in or shipped out and the additional option to
capture individual Asset IDs at Receipt and Vehicle Loading.
• A Warehouse Dashboard is available alongside the WMS which
8 provides a real-time, single view of key metrics including

Vehicle
Load • For Bonded warehouses only, approval is given for all the orders
to be loaded (i.e. all have been customs cleared).
• The consignment(s) for loading is identified.
• The Pre-Vehicle Load check is confirmed if configured for the
site.
• Loading is performed.
• Loading is confirmed.

CORE+
Outbound
Supporting Matrix Functionality Via a PC
[8] Vehicle Load

entered. From the lines displayed (pallets / TAGs) for the consignment
When using the Bonded Warehouse Option Pack, each order that select those that have been loaded. The trailer loaded onto is captured
contains bonded inventory will need to have been updated via the user and if using Asset Recording then the number of pallets loaded, per
type should be entered. If tracking individual asset IDs these should be
to identify the order and update the approval [once provided by the entered into the Individual Asset Entry screen. Once all information is
customs department]. Note that a failure to receive this update yet the entered the task confirmed as completed.
order is attempted to be shipped will result in the order going to the
Once successfully loaded the order header status will change to Ship in Full
If using the Ship in Full feature any attempt to load a pallet for a short-
Via a Mobile Device picked order will be prevented within both the PC and Mobile Device
applications.
consignment to load from a Delivery Note (each Delivery Note has the
consignment number displayed as a barcode) or as informed. The trailer
Asset Recording
field can be used to capture the trailer ID, or if required can be used
instead to record the vehicle registration and/or driver name. If the This feature provides the ability to record the count of pallet types
capturing of a pre-vehicle load check is configured for the site, the received in or shipped out, against a Supplier / Delivery address.
mobile device will require confirmation that this check has been Updated at Receipt and Vehicle Loading, the asset count is visible in
completed. The Pre-Vehicle Load Check Report provides details per the WMS Asset Tracking screen.
trailer of each pallet loaded.
Once enabled, this feature also provides the ability to track unique
Prior to each pallet loaded, an information message will be displayed
detailing the total number of pallets in the consignment, and the total the Pallet Type (held on General 2 tab). Once this flag is set, the Asset
number of pallets in the consignment left to be loaded. The operator ID is required to be captured during Receipt and Vehicle Loading.
will read the information presented and press enter to continue. The
Use the Asset Details screen to view all information relating to each
pallet to load is displayed on the device (with the order sequence pre-
individual asset. Team Leaders and above can switch to Maintenance
determined from what was captured during consignment build) and the
Mode to manually create assets if required.
loading position is confirmed. If optional positive confirmation at
loading is required, a further screen prompts the operator to enter the Returning empty assets is possible using the Asset Return feature.
pallet ID. The ability to capture a seal is available at site level, and if
enabled will prompt the operator to enter a seal value in the Load Seal
Capture screen.
CORE+
Outbound
Exceptions then followed to produce the paperwork

Exception / Failure Related System Activity Required and Trailer Shipping is performed.
Name and Description Outbound Order The cancellation of an Outbound Order
Fail Load not enough Whilst using the Vehicle Load Function Cancellation is identified by the client and notified to
space on vehicle on the Mobile Device, at the point of CEVA. CEVA then assesses if the
When vehicle capacity not loading pallet(s) onto a vehicle is Outbound Order is at a suitable status
is reached and yet for cancellation.
there is still pallets to the screen. The normal process is then Loaded [High Risk]
load, those loaded are followed to produce the paperwork and
confirmed and Trailer Shipping is performed. affected Pallets / Containers, then the
paperwork is Once the alternative vehicle / trailer is inventory is relocated back to storage.
produced. Another sourced, the vehicle Load function is The Team Leader deletes the move
Trailer / Vehicle is then used once again to then load the tasks created using the Move Task
sourced and the remaining pallet and the remainder of Update screen. The Team Leader
remaining pallets are the normal process is followed to updates the Outbound Order Header to
load confirmed onto complete the process.
the alternative vehicle, notified via the same way CEVA was
with the appropriate notified of the desire to cancel, or via
paperwork then also message if enabled.
produced. Notification of Carriers that are able to receive voiding
Fail Load damage Whilst using the Vehicle Load Function Differences between confirmations will receive notification of
identified during on the Mobile Device, at the point of Planned and Shipped containers that are no longer planned to
loading be despatched (triggered by the
If Damaged pallet(s) pressed to skip the offending pallet(s). deallocation process).
are discovered during The Team Leader deletes the associated
loading then the move task and creates a relocation of
damages are moved to the damaged pallet(s) to the QA area.
the QA Area and An operative then re-locates the pallet(s)
marked as Damaged. from the instage to QA location,
Re-allocation is then changing the condition code of the
performed against the
inventory needed to The Team leader then performs a re-
obtain the items for the allocation of the parts of the order(s)
order. These are then that had damages to generate the
picked and loaded as appropriate pick tasks. The inventory is
normal (time now picked and loaded as per the
permitting). normal process. The normal process is

CORE+
Outbound
Outbound Vehicle Load Decisions (for configuration / Set up)

• Voice Control
one]
□ Yes
□ No
• Is positive confirmation at loading required? [select one]
□ Yes
□ No
• Is seal capture at the point of loading required? [select one]
□ Yes
□ No
• Is a pre-vehicle load check at the point of loading required?

[select one]
□ Yes
□ No
• Is the Asset Recording feature required to be used?
□ No
□ Yes:
□ To capture individual asset IDs
□ To capture the count per pallet type
Vehicle Load Section Complete

CORE+
Outbound
Outbound Vehicle Despatch Guiding Principles

• Shipping shall be performed at the point of the good actually
Diagram leaving the facility, unless using the Kit to Stock Option Pack
Outbound
where goods are automatically shipped once the order moves to
Vehicle status complete.
Vehicle Load Vehicle
Despatch
Departure • A Warehouse Dashboard is available alongside the WMS which
provides a real-time, single view of key metrics including
• Despatch Manifest / Notes obtained.
9 •
•
Driver performs acceptance and security checks.
Paperwork is completed and keys are issued.
• Vehicle drives to the gatehouse.
Vehicle
• Consignments / Orders are confirmed as shipped including the
Despatch
generation of dispatch / ASN interfaces.
Supporting Matrix Functionality
[9] Vehicle Despatch

When vehicle departure is about to occur, the load manifest is
Load produced (manually triggered user report that can be printed after
Manifest loading but prior to dispatch). The Load Manifest is produced per
specified Trailer ID and contains Trailer ID, Total Weight of load then
Despatch
each Consignment, Pallet, Pallet Weight, Order Number, (all in the
Confirmation
Interface sequence loaded), and the Printed Date & Time.
(Client)
Despatch
Confirmation
Interface
(Carrier)
Despatch
Confirmation
Interface
(Customs)

CORE+
Outbound
Example Load Manifest Additional

Following dispatch
then used to produce the dispatch confirmation, carrier dispatch
confirmation and customs dispatch confirmation interfaces. For Bonded
Warehouse Option Pack check that all orders are at the status of
Receiver compliant ASNs are able to be generated at the point the
will require a period of approximately 4-6 weeks for onboarding.
Integration with I2M SMART Solution
If using the Integration with the I2M SMART Solution Option Pack,
following dispatch, a Despatch Advice API is able to be sent from
Matrix WMS CORE+ to notify IFL of the orders to be delivered to the
manufacturer. See I2M SMART Solution Integration with Insequence &
IFL for more details.
.
Integration with Co-Pack SMART Solution
The departure of the goods picked against orders is confirmed and
recorded on the system. Whilst typically this is done per Vehicle or
following dispatch a Despatch Advice API is able to be sent from Matrix
trailer, it is also able to be performed per Consignment or per order.
WMS CORE+ to inform Pack Manager of the handover of requested
• The most common use is dispatch per Vehicle / trailer. inventory. See Co-Pack SMART Solution Integration with Pack
• Dispatch per consignment has a potential use in situations Manager for more details.
where the dispatching of the vehicle / exit of goods is entirely
Exceptions
outside of the control of CEVA such as carrier collection of
Exception / Failure Related System Activity Required
stand trailers outside of operating hours.
• Dispatch per order has a potential use in situations such as
Goods are not customs A check is performed to confirm that the
customer collections or emergency orders. cleared at point of order is customs cleared, then the
Via a PC updating the trailer as approval is recorded and the order re-
shipped [Bonded shipped.
Using the Trailer Shipping function, the operator enters the trailer warehouse option pack
number. The action status is displayed whilst it is in progress, then only]
confirms it is complete. Consignment shipping and order shipping the order is shipped.
work in the same manner, but with identifying the relevant identifier.
CORE+
Outbound
Outbound Vehicle Despatch Decisions (for configuration / Set up) • Is integration with IFL required as part of the I2M SMART Solution
• Is a Despatch confirmation interface required (to be sent from the (Integration with IFL Option Pack)? [select one]
WMS to the Middleware? [select one]
□ Yes
□ Yes, CEVA Standard EDI Message □ No
□ Yes, CEVA Standard API Message • If CEVA internal systems are being used (e.g. OMS, TMS or Planning

interface required for
them (to be sent from the WMS to the Middleware; NOT FOR
EXTERNAL SYSTEMS)? [select one]
□ No □ Yes
• If yes, which message is required [select one]? □ No
□ Yes • If the Bonded Warehouse Option Pack is being used, is a Despatch
□ Yes per trailer

confirmation interface required for the CMS (to be sent from the
WMS to the Middleware? [select one]
• Is a Receiver compliant ASN required? [select one]

□
□ Yes □ No
□ No Vehicle Despatch Section Complete
• If Yes please list the Receivers required.
List Receiver(s) required here
<List the Receivers required>

CORE+
Bookmark
Inventory
Inventory Relocations  Stock Checks  Inventory Updates  Inventory Adjustments  Batch Management
Information Queries
Inventory Management Product Description
In addition to the above, the ability to query many different sets of
The following section details the activities that CEVA are able to be
information exists, such as the inventory, locations, move tasks, pack
performed using Matrix WMS CORE+.
configurations, and many more.
Inventory Management Overview Where possible, querying should be limited to small amounts of data,
which returns less than 500 records. If more than 500 records are
Diagram 500
-run and the records
1 2 3 4 5 6 will include any transactions that have been completed since the initial
Inventory Stock Inventory Inventory Batch Information query was run.
Relocations Checks Updates Adjustments Managment Queries
It should also be noted that the ability to query inventory exists within
the portal (alongside Order, Pre-Advice, SKU, Customer and Supplier
creation). Where a client exists in more than one site, it is possible to
Inventory Relocations allow a single web portal user account to view inventory across multiple
The ability to relocate inventory from one location to another, without sites.
direction from the inbound or outbound process.
Matrix WMS CORE+ is API enabled offering real-time inventory visibility
Stock Checks to clients and other applications such as Insequence (Integration with
The ability to perform periodical Wall to wall or specific group of the I2M SMART Solution Option Pack).
location stock counts, performed blind, then with the discrepancies
investigated.
Inventory Updates
The ability to capture a change in condition of the inventory using pre-
defined condition codes and descriptions. Also the ability to capture a
change in batch code, expiry date, origin, pack configuration, lock
status, pallet type, owner or allocation attribute(s).
Inventory Adjustments
The ability to adjust the quantity of the inventory should stock be
damaged, go missing or be found.
Batch Management
The ability to control processing and movement of inventory identified
by a Batch (lot).
CORE+
Inventory
Inventory Management Option Packs

ABC Analysis Option Pack Vendor Managed Inventory Option Pack
Guiding Principles: Guiding Principles:
• Provides calculation of the shipment velocity of SKUs allowing • The ability to transfer the ownership of Vendor Managed
putaway and storage of inventory to be optimized. Inventory (VMI) from one owner to another owner.
• ABC analysis tool calculates the ranking of each SKU based on
velocity of shipment tasks completed within a defined time Business Description:
window, updates the ranking on the SKU record and generates • VMI Mapping is completed to indicate which client/owner can
relocation tasks. transfer stock to another client/owner.
Business Description: • A SKU may be configured to automatically transfer in one or
more of the following scenarios:
• Five categories of ABC frequency can be defined (A-to-E) and o VMI transfer aging days: The period after the SKU has
applied to both a SKU and Location. been received into the warehouse. Upon reaching the
• Frequencies are site, client and owner specific. number of days specified all the stock will be transferred
• Two models are available for assigning a category to each SKU: following VMI mapping.
o Percentage of SKUs per frequency category. o VMI transfer shortage: This option can be set to allow
o Number of SKUs to be included in each frequency inventory to be transferred in the event of an allocation
category. shortage.
• The ACTION Call ABC SKU Ranking Functions Report updates o VMI transfer replenish: This option can be set to allow
the ranking (slotting) requirement for each SKU. This can be run inventory to be transferred if there is a replenishment
manually by a CEVA operator or automatically at a specific time shortage.
each day; relocation tasks will not be created by the automatic • A VMI transfer may also be completed manually within the PC
process. application .
• A range of reports can be used to analyse the current ABC • Two VMI Transfer types exist:
position see Reports section for more details. o Receipt where the specified client is in receipt of the
• Relocation tasks for the highest priority SKUs are generated up transfer resulting in an increase of the stock quantity of
to the maximum task count entered previously. the requested SKU. Allocation shortage and
• Relocation tasks are set to status Hold and must be manually replenishment transfers are Receipt types.
updated when required to be completed or deleted if no longer o Shipment where the specified client is effectively
required. shipping the transferred SKU resulting in a decrease of
• Please note that if pick faces are required the ABC Analysis the stock quantity of the concerned SKU. Aged receipt is
Option Pack must be used in conjunction with the Dynamic Pick a hipment transfer type.
Face feature, otherwise bulk locations must be used.
CORE+
Inventory
Inventory Management Option Pack Decisions (for configuration /

Set up)
• ABC Analysis Option Pack be required? [select one]
□ Yes
□ No
• Vendor Managed Inventory

[select one]
□ Yes
□ No
Inventory Management Option Packs Section Complete

CORE+
Inventory
Inventory Relocations Guiding Principles

• Relocations can only be created by a Team Leader.
Diagram • Relocations are not to be used instead of the normal putaway
task, as to do so will not allow for capture of the activity being
1.1 1.2 performed for KPI / SLA / Invoicing purposes.
• The Team leader is able to identify inventory that is required to
Identify Perform be moved.
Relocation Relocation
• The Team Leader release the task for an operator to perform.
• An Operator performs the relocation as requested and confirm
completion.

CORE+
Inventory
Supporting Matrix Functionality Stage location - representing the Geek+ Workstation) will be performed
as described above in the Via Mobile Device or Via Paper and PC. Once
the first part of the Replenishments is completed, Matrix WMS will
[1.1] Identify Relocation transfer the second part of replenishment task to the Geek+ Goods to
On a PC, the Stock Relocation screen is used to create a move task. Person system. The last step of the replenishment (to the final Pick Face
First identify any search criteria such as SKU or Tag ID that will enable location) will be performed in the Geek+ Goods to Person system.
you to correctly identify the inventory that you wish to relocate. Select Upon completion, is the result of the Replenishment will be
the inventory that is desired to be moved. State the location for them communicated back to Matrix WMS which will in turn finalize the
to be moved to. Set as released for someone to now be able to Replenishment.
perform the relocation (If the task is being performed from paper and
out the Move task list)
[1.2] Perform Relocation

Using an Mobile Device
directed to the first relocation; alternatively enter the Tag ID to drive

the activity. Client, SKU, Qty, From Location, To Location are
displayed. The move is performed and the check string is captured to
confirm.
Paper & PC
Following the completion of the relocation activities as stated on the
the system. The List ID is entered, the operator who performed the
tasks captured, then the tasks completed are confirmed.
Via Geek+ Goods to Person
If replenishing towards the Geek+ Goods to Person system, the

replenishment will comprise of two parts. The first part (towards an In-

CORE+
Inventory
Exceptions Exception / Failure System Activity Required

Exception / Failure System Activity Required Name and Description
Name and Description and the relocation process is started
Fail Relocation - Size The Team Leader only (not operator) again.
has access to Mobile Device and PC
screens for SKU and Location queries to The Team Leader only (not operator)
check the information to determine uses the Location Maintenance screen
what is wrong and needs correcting: to change the lock status of the location
• Mobile Device: Location Query
• Mobile Device: Pack Config Override of Relocation Not allowed.
Query location directed to
• PC: Inventory Query desired
• PC: Location Query
Inventory Relocations Decisions (for configuration / Set up)
Once corrected, the relocation process • Voice Control
is then followed. [select one]
Fail Relocation
unexpected inventory
The inventory found in the location is
removed and the Pallet is relocated as
□ Yes
in location directed. The removed inventory is then

queried by the Team Leader to
□ No
determine where it should be and then

physically relocated to there. Inventory Relocations Section Complete
The Team Leader only (not operator)

has access to Mobile Device and PC
screens for inventory queries to check
the correct location:
Fail Relocation Following the location being identified

location not useable as not usable, the location is updated to

CORE+
Inventory
Stock Checks Guiding Principles

•
Diagram response (actual performance of the check) is achieved.
• Any discrepancies where stock is less than expected are shown
2.1 2.2 2.3 •

as positive amounts in the suspense account
Any discrepancies where stock is more than expected are shown
as negative amounts in the suspense account.
Create Perform Resolve Business Description
Stock Stock Discrepancies • Stock checks are able to be created automatically (on a cycle) or
Check Check manually
• The Team Leader is able to create a stock check specifying the
Aisles, bays and location to be included.
• Operators performing the stock check are directed to locations
to perform the count.
• Any differences are double checked with confirmed differences
written to a suspense account for resolution.
• After completing the stock check updates to inventory records
are made as necessary, with reporting available to show what
occurred.
• Forced capture of DOT code during stock checks can be set if
using the DOT Management for Tires Option Pack.

CORE+
Inventory
Supporting Matrix Functionality [2.2] Perform Stock Check

Via a Mobile Device
[2.1] Create Stock Check
Automatically created of the stock check to be performed. The location checkstring is then
required to be captured to confirm the check is being performed at the
For automatically created stock checks, the count frequency in days is correct location. Stock check details for the first location to check will
set on the SKU. Matrix WMS then generates the checks and creates appear (location, SKU, Tag and Pack Config) with the operator
expected to key in the quantity. The operator will key in the quantity. If
the quantity does not match what is expected, then the operator is
prompted to re-confirm the quantity (following physically counting
again). SKU confirmation may be enabled to confirm the SKU that has
Manually Created
been counted. This loop is repeated until two consecutive quantities are
ption entered that are the same. When all known inventory has been checked
to generate by location is used (although it is possible to do this by for a location the operator is prompted to state if any more inventory
inventory, but not preferred). The range of the stock check is entered exists in the location if it does then it can be captured.
The locations that match the range searched for are displayed; the
locations desired for the stock check are then selected and added. Via Paper and PC
Finally the list is generated, with the List number displayed. An option
to print the stock check list is also presented. The stock check list that is issued is completed by the operator as they
physically count at the locations. To update the information captured,
Example Stock Check List
for and the locations displayed. The quantities for existing inventory
Matrix® WMS CORE+ are updated as per the information captured on the paper list; new
inventory is added as required. Any variances (discrepancies) against
what the system records currently holds have a record written to the
suspense account (for validation).
[2.3] Resolve Discrepancies

If a second check is desired to be performed by another operator, then
check List ID is searched for and variance checks are able to be

CORE+
Inventory
identified. The Perform Stock Check process can then be repeated with Stock Checks Decisions (for configuration / Set up)
this information to complete and update the secondary checks. • Voice Control
[select one]
Discrepancies identified via the stock check (or other means) have a
□ Yes
show all suspense records. □ No
To resolve these discrepancies, after physically determining that the • Will the automatically created stock checks be used? [select
variances identified are true (you can re-run the stock check using the one]
variances only), please follow the inventory adjustments process in
Inventory Management [4] Inventory Adjustments. □ Yes
□ No
Exceptions • Will scanning of the SKU / EAN / UPC barcode be required for
Exception / Failure System Activity Required every stock check? [select one]
Stock check created in
error
Using the Stock check Task Status
change function, the stock check is
□ Yes I confirm that every SKU has a barcode with this
value
The stock check is
deleted if not required.
identified and then deleted. Note that
it is able to be restored if deleted in □ No
error.
Stock check errors Using the Stock check process but for
If a stock check error the required location only, the stock
Stock Checks Section Complete
has been made with an check is performed again capturing the
incorrect discrepancy correct value. The correct value being
identified, another captured will remove the value from
stock check is appearing in the suspense location.
performed on the
location in questions
to capture the correct
value.

CORE+
Inventory
Inventory Updates Guiding Principles

-
Diagram
As the condition of inventory changes, the new condition is recorded.
3.1 3.2 Also the ability to capture a change in batch code, expiry date, lock
status, origin, pack configuration, pallet type, owner or user defined
Identify Perform values (e.g. allocation attribute(s), Import Document ID / Date).
Update Update Forced capture of DOT code can be set during Inventory Updates if
using the DOT Management for Tires Option Pack.
Inventory
Update
Interface

CORE+
Inventory
Supporting Matrix Functionality enter the reason and authorizing person for the new code in the Note
[3.1] Identify Update field. Click Done.
Typically following discussion with the client, some inventory is agreed Expiry date
to have an attribute changed (condition code, batch code, expiry date,
origin, pack configuration, lock status, pallet type or owner) either for Select T
performing a correction, to assist in segregating and facilitating either a alter the expiry date of by entering a combination of one or many of
follow on action or exit from the warehouse. The inventory being TAG ID, SKU or location, and also Client ID (mandatory). Select the
updated is often also moved to another location, where it will reside on Tags that you wish to update. Enter the expiry date you desire and
a TAG for just these concerned goods. enter the reason and authorizing person for the new date in the Note
field. Click Done.
Lock Status
[3.2] Perform Update
alter the lock status of by entering a combination of one or many of

Condition Code TAG ID, SKU or location, and also Client ID (mandatory). Select the
Tags that you wish to update.
For changes to the condition code (by the Team leader only) valid
(Status Locked will require a Lock Code to also be selected) and enter
Condition codes can be used as stated in the facility master data
the reason and authorizing person for the change in lock status in the
section of this document.
Note field. Click Done.
Origin
wish to alter the condition code of by entering a combination of one or
many of TAG ID, SKU or location, and also Client ID (mandatory).
Select the Tags that you wish to update. Select the condition code you the value in the origin field (no Country of Origin field) of by entering a
desire and enter the reason and authorizing person for the condition combination of one or many of TAG ID, SKU or location, and also Client
code in the Note field. Click Done. ID (mandatory). Select the Tags that you wish to update. Enter the
Origin you desire and enter the reason and authorizing person for the
The alteration of condition of inventory will generate an interface from
new origin in the Note field. Click Done.
the WMS stating the inventory changes.
Pack Configuration
Batch code
wish to alter the Pack Configuration of by entering a combination of

alter the batch code of by entering a combination of one or many of
one or many of TAG ID, SKU or location, and also Client ID (mandatory).
TAG ID, SKU or location, and also Client ID (mandatory). Select the
Select the Tags that you wish to update. Enter the Pack Configuration
Tags that you wish to update. Enter the Batch code you desire and
you desire and enter the reason and authorizing person for the new
configuration in the Note field. Click Done.
CORE+
Inventory
Pallet Type • If yes, which message is required? [select one or many]
□ Batch Update
alter the pallet type of by entering a combination of one or many of
TAG ID, SKU or location, and also Client ID (mandatory). Select the □ C&E COO Update (Bonded Warehouse Option Pack)
Tags that you wish to update. Enter the pallet type you desire and
enter the reason and authorizing person for the new pallet type in the
□ Condition Code Update
Note field. Click Done. □ Lock Status Change Update
Owner □ Origin Update
alter □ Owner Update
the expiry date of by entering a combination of one or many of TAG ID,
SKU or location, and also Client ID (mandatory). Select the Tags that
□ User Defined Update
you wish to update. Enter the owner you desire and enter the reason □ Allocation Attribute 1, 2, 3
and authorizing person for the new owner in the Note field. Click Done.
□ Import Document ID
User Defined (E:g Allocation Attribute, Import Document ID/Date)
□ Inbound Client Ref 2
Search for the inventory you wish
to alter the allocation attribute(s) of by entering a combination of one or □ Import Document Issue Date
many of TAG ID, SKU or location. Select the inventory that you wish to
update and enter the updated values in the relevant field(s) and click
□ SKU Hazardous Class
Done. □ UDI
Exceptions
None Inventory Updates Section Complete
Inventory Updates Decisions (for configuration / Set up)

• Is an Inventory Update interface required (to be sent from the
WMS to the Middleware)? [select one]
□ Yes, CEVA Standard EDI Message

□ No
CORE+
Inventory
Inventory Adjustments Guiding Principles

• None.
Diagram
As stock checks identify misalignment of inventory, the inventory is
4.1 4.2 checked and adjustments made as needed.
Identify Perform
Adjustment Adjustment
Inventory
Adjustments
Interface

CORE+
Inventory
Supporting Matrix Functionality Inventory Adjustments Decisions (for configuration / Set up)
• Is an Inventory Adjustment interface required (to be sent from
the WMS to the Middleware)? [select one]
[4.1] Identify Adjustment
Adjustments identified via the stock check (or other means) have a □ Yes, CEVA Standard EDI Message
record written to th □ Yes, CEVA Standard API Message
show all suspense records. □ Yes, Client specific message (CEVA Standard Message
[4.2] Perform Adjustment

□ No
To resolve these Adjustments, the suspense records need to be written
Inventory Adjustments Section Complete
off which c
along with selecting the reason and entering any pertinent notes.
Exceptions
None

CORE+
Inventory
Batch Management Guiding Principles

Restrictions to the processing of inventory identified by a specific batch
Diagram / Lot is controlled by the operation in consultation with the client and
impact analysis by the operation.
Inventory Batch
Update Removal of restrictions can be made via client interface or manually by
Interface the operation.
5.1 5.2 Business Description

As identified by the client, restrictions in processing may be placed
upon one or many batches / lots of inventory.
Identify / Perform
Following any additional activity associated to the restriction, the
Analyse Alteration
Alteration inventory, or alternative restrictions put in place.
Inventory
Update
Interface

CORE+
Inventory
Supporting Matrix Functionality Exceptions

[4.1] Identify / Analyze Alteration None
Assessment of the impact of making the restriction is performed,
considering impact upon layout, locations used, existing inventory and Batch Management Decisions (for configuration / Set up)
orders, etc. None
[4.2] Perform Update

Using an EDI message from the Client to the WMS, the Quality Control
Hold (QCHOLD) status may be updated to either Released or Rejected
together with the option to update the Lock Code and Lock Status from
Locked to Unlocked.
Using the ACTION - Batch Update report via a PC, a Team Leader may
set the change the QC status from Hold to Released or Rejected only,
they may also update the restrictions flags (e.g., Allow Picking, Allow
Packing, Allow Loading, Allow Shipping).
Manual updates of the Lock Status should be completed using the

Inventory Update (batch) process.
QC Status / locked status

If QC Status = 'Released', then the SKU requires batch capture at
receipt.
If QC status = 'Hold', then the SKU requires batch capture at receipt
then automatically set Lock code to 'Locked' for inventory. The
assumption is that the batch will later be changed to either 'Released'
or 'Rejected'.
If QC status = 'Rejected', then the SKU requires batch capture at receipt
then automatically set lock code to 'Locked'.

CORE+
Bookmark
Set Up / Master Data

Facility  SKU  Operator
Guiding Principles
Set Up / Master Data Product Description
• Each Facility will utilize the same standard set of zones.
The following section details the set up activities that CEVA perform
• Each facility will use the same units of measure for length,
using Matrix WMS CORE+.
volume and weight.
Set up / Master Data Overview • All required Facility and Product set up must be populated in
the system prior to the first Inbound Order and Receipt.
Diagram • Each SKU will have a single (only one) unique inventory code.
This will be the sole ID used to identify the product during the
1 2 3 •
process and also to the Client and Customer, appearing on any
documentation.
For operations utilizing the Handling Unit Only Flow
SKU will be used with a unique reference to identify the handling
Facility SKU Operator
unit of items to allow them to be treated as a single piece of
inventory.
• The unit of measure for any SKU will always be positive integer
and will be used for receiving and ordering.
• Inventory will be managed at the SKU level only, no Bill of
Materials (BOM) or kitting references will be managed.
Facility
• An operator will be tied to a single site; they may however have
Information related to the physical warehouse that is either pre- access to one or more clients.
configured in the system or is required as part of set up.
• All Mobile Devices are configured to meet standard screen sizes
SKU of 10 x 20 or 16 x 20.
Information related to the products and their storage that is either pre- • Manual and scheduled anonymizing of data.
configured in the system or is required as part of set up.
Operator
Information related to the operators of the system and associated IT
tools they will use that is either pre-configured in the system or required
as part of set up.

CORE+
Facility potentially). If found to not be pristine the code would

then be changed to DAM, NCD, DIS or RTS.
Diagram o INS Inspection. The condition code to be used when
the inventory requires inspection. Typically this will be
used when goods arrive in the warehouse and require
Standard inspection prior to being made available as pristine
Base Data Set goods.
o DAM - Damaged whilst in CEVA Care. The condition
code to be used when inventory is found to be damaged
Data Take On
after CEVA has taken ownership / whilst in CEVA control.
XLS o NCD - Damaged by non CEVA Party. The condition code
to be used when inventory is found to have damaged by
a party other than CEVA. The notes field can be used to
1 o
identify the other party if required.
DIS Disposal. The condition code to be used when
goods have been identified for disposal. An outbound
order (rather than stock adjustment) will then be used to
Facility pick and dispatch the goods to the disposing party /
location.
o RTS - Return to Supplier. The condition code to be used
when goods have been identified for return to the
supplier. An outbound order (rather than stock
adjustment) will then be used to pick and dispatch the
goods to the supplying party.
Description
o RET- Returns. The condition code to be used for
Facility Set-up: Automatically provided for all and fixed as part of the returned goods if it is desired for them to be putaway to
solution the returns area (for assessment).
• Client Group used to control access to the functionality that is o RSR - Retention Sampling Required. When inventory
provided. received is required to have retention sampling
• Function Access a single set of Function access to control performed, and so needs to be taken to the specific area
functionality to use and its behavior. in the warehouse where this is done
o ETR - External Testing Results Required. When inventory
• Condition Codes a single set of condition codes for use
received is required to have had testing performed prior
o <Blank> - the normal condition code that is used to to storage, and so needs to be taken to the specific area
identify pristine inventory. in the warehouse where the results are obtained / waited
o QAH - QA Hold. The condition code to be used when for.
inventory requires to not be used as it is pending o DES - Identified for Destruction. When Inventory is
assessment (suspected to not be pristine, or a recall designated for destruction it is putaway / relocated to
CORE+
the specific are of the warehouse where it awaits the • Origins a single set of (CEVA standard) inventory country of
matching order for its destruction. When the condition Origin codes for use.
code of 'DES' is stated on an order line, only inventory • Location zones - a single set of standard location zones.
with the matching condition code from the Destruction
• Work zones a single set of standard work zones.
Area Zone (not in-stage if present) will be allocated.
o FMD Falsified Medicines Directive. When inventory is • Merge Rules a single system-wide merge rule to control the
designated for FMD processing it will be putaway to the identification of hazardous inventory.
FMD Zone for processing. Following processing the • Fan Putaway Profile a single Fan putaway profile for use that
condition is updated and the inventory relocated to drives the putaway of inventory as close to the pick face as
normal storage. Note that some inventory for an possible.
applicable FMD SKU may NOT require processing due to • Default Putaway Algorithm a single set of default putaway
where they are being shipped to. As such the identifier Algorithms for use that controls the direction of inventory once
cannot be determined solely from the SKU record but received to their storage location (if client stock segregation is
will use this condition code not being used).
o ISO Isolation. Where inventory is required to be
• Order Types a single set of order types for reporting /
isolated it will be putaway to the Isolation Zone.
charging purposes and associated inventory condition setting
• Inventory Lock Codes a single set of inventory lock codes that
will be used by the WMS. These are not for operator use o CEO - C&E Order Type
(instead condition or location lock codes should be used). o COL - Collect Order Type
• Location Lock Codes - a single set of location lock codes for use: o CPK - Co-Pack Order Type (Integration with Co-Pack
SMART Solution Option Pack)
o LOCKED (blocks both inbound and outbound moves o CUS - Customer Order Types (Note - only this type can
from occurring) utilize a returns Note)
o UNLOCKED (inventory can go freely in or out of the o DES - Destruction Order Type
location) o DIR - Direct Delivery Order Type
o INLOCKED (blocks inbound moves from occurring) o DIS - Disposal Order Type
o OUTLOCKED (blocks outbound moves from occurring) o EMR - Emergency Order Type
• HAZMAT codes a single set of compliant hazardous material o KTO - Kit to Order, Order Type (Kit to Order Option
Pack)
o KTS - Kit to Stock Order Type (Kit to Stock Option Pack)
• Adjustment Reason Codes a single set of adjustment reason o PRO - Pro Rata Allocation Order Type
o REL - New Release Order Type
codes for use
o REP - Replenishment Order Type
o DMGD - Damaged, o RTS - Return to Supplier Order Type
o LOSS - Loss in Store, o STN - Standard Order Type
o GAIN - Gain in Store. o STO - Store Order Type
o UTS - Unkit to Stock (Kit to Stock Option Pack)

CORE+
o VAS - Order with Value added Services o VARICONT Variable container that when used during
o XDC - Cross Dock Order Type (Cross Dock Option Pack) repacking allows the operator to override the dimension
• Pre-Advice Types a single set of Pre-Advice types for reporting [and hence match the physical container being used].
/ charging purposes This must be combined with the VARIABLE pallet type to
trigger the sending of updated dimensions.
o CPF Co-Pack Finished Goods Pre-Advice type
(Integration with Co-Pack SMART Solution Option Pack) • Trailer Type a single standard Trailer type.
o CPR Co-Pack Returns Pre-Advice Type (Integration with • Document Types - These are defined per country and are
Co-Pack SMART Solution Option Pack) selected when creating the C&E Consignment, with a document
o RET Return Pre-Advice type number recorded against it (typically, but not always, the MRN).
o STN Standard Pre-Advice type • Serial Number Capture Groups A series of Serial capture
o MST Master Pre-Advice type groups are defined allowing for one to be selected as the
o TAG Tag Receiving Pre-Advice type default group for
o XDC Cross Dock Pre-Advice type (Cross Dock Option The valid profiles are:
Pack)
• Default Carrier & Service levels 2 default Carrier/ Service level Serial Capture SERIAL_AT
_RECEIPT
SERIAL_AT
_PICK
SERIAL_AT
_PACK
SERIAL_AT
_STOCK_A
SERIAL_AT
_STOCK_C
combinations are provided as part of Matrix WMS CORE+ Group
DJUST HECK
INBOUNDANDOUTB Y Y Y Y
o CEVA / Standard, OUND-PACK
INBOUNDANDOUTB Y Y Y Y
o Customer Collect/None. OUND-PICK
• Allocation Algorithm a single set of allocation Algorithms for OUTBOUNDONLY- Y
PACK
use that controls the allocation of inventory to orders (By FEFO if
OUTBOUNDONLY- Y
expiry dates exist, if not then FIFO) prior to being picked. PICK
• Certain locations INBOUNDANDOUTB Y Y Y Y Y
OUND-PICKPACK
system directed putaway to prior to being relocated to an • FMD Reasons (for outbound processing, stated on the order line
[optional])
system to use when goods are being moved between locations; o Dispensed
o Sample
o Destruction
suspense account for resolution; All the locations within the Post o Export
Pick Activity Zones used by the Post Pick Activity Option Pack.
• Default Pallets (and containers) the following default pallet Facility Set-up: Provided by the Business (in the data take on
types and container are provided as part of CORE+ spreadsheets provided to IT)
o EUR1 Euro Pallet 1 / ISO1 [0.8 x 1.2 x 0.14] • Site The Site to be used (if not already set up) and associated
o EUR2 Euro Pallet 2 / ISO2 [1.2 x 1.0 x 0.14] visibility group. Address details for the Site are captured that
o EUR3 Euro Pallet 3 [1.0 x 1.2 x 0.14] will be used for printing out on documents where appropriate;
o EUR6 Euro Pallet 6 / ISO0 [0.8 x 0.6 x 0.14]
CORE+
the time zone for the site is also set. If Customs functionality is DHLEXPRESS MAIL
DHLEXPRESS P09
also the Site address needs to reflect what is expected to be
passed to Customs for the operational Site. Against the Site the DHLEXPRESS P12
time zone (it resides in) is stored - this is used for all display NIGHTSTAR P08
information via the application to operators and also for stating
on all relevant documents. POSTNL P10
• Client the Client that CEVA will perform warehousing activities POSTNL P12
on behalf of and associated visibility group. Each Site can have
POSTNL STN
one or many clients associated to it; a client can belong to one
or many sites. If Customs functionality is to be used then the TNT DOM
address needs to reflect what is expected to be passed to TNT ECO
Customs for the operational Client, including the VAT number. A
TNT EXP
client, to allow for automatic population of the valid serial TNT P09
capture points to set against SKUs that identify that they will use
TNT P10
serial capture.
• Additional Carrier & Service levels Carrier/ Service level TNT P12
combinations over and above the standard two, plus attributes UPS EXPRESS
for Carrier Account ID, Client ID in the supporting Transport or
UPS P09
label tool, SCAC, Shipping System, Carrier Electronic Pre-
notification required (Y/N), Print Carrier tracking Number on UPS SAVER
Delivery Note (Y/N), label generation tool identifier, Carrier • Location Sub Zones Sub zones within the bulk storage zone
GLN, parsing schema. Current combinations present in Matrix that are set up if stock segregation is required.
WMS CORE+ include: • Locations The locations to be used for the Site (per Location
and Work Zone), complete with dimensions and weight
CARRIER_ID SERVICE_LEVEL
restrictions, (plus Aisle side, Aisle, Level, Position, X co-ordinate,
CEVA OCEAN Y co-ordinate, Z co-ordinate, pick sequence, Put sequence,
CEVA PREMIUM check sequence, check string where appropriate), flag to
CEVA STANDARD
with the Picking Activity report)
CEVA VALUE stackability controls.
• In and Out Stages The in and out stages to be used for the
DHLEXPRESS DOM
Site (per Location and Work Zone), complete with dimensions
DHLEXPRESS ECX and weight restrictions, (plus Aisle side, Aisle, Level, Position, X
CORE+
co-ordinate, Y co-ordinate, Z co-ordinate, pick sequence, Put

sequence, check sequence, check string where appropriate). in the pick face location.
In stages are typically (but not always) used as a drop off point • One option to vastly reduce occurrence of multiple TAGs in a
before using different equipment or process to the pick / pick face location is to lower the replenishment trigger quantity
storage locations they serve such as very narrow aisles or to be set to less than one. This effectively means the pick face
mezzanines. The naming of the in stage will be INLNN where gets reduced to zero before the replenishment is triggered. This
LNN is the aisle identifier used for every location. Out stages does not however address the issue of top up from putaway and
serve the same role but in reverse for when inventory leaves the potentially introduces waiting time at the pick face whilst waiting
pick / storage locations. The naming of the out stage will be for replenishments activities to be performed.
OUTLNN where LNN is the aisle identifier used for every • However, In relation to this there is also the option to set the
location. location and then also specified SKUs to allow TAG merge. This
• Pick Faces The Pick Face to use (plus minimum replenishment then merges the inventory deposited into the location into the
quantity that will be defaulted to 5) with the SKU identified. A original TAG that exists there. This functionality would allow the
report exists that provides the data to use with the CEVA
slotting tool for assessment of pick faces / locations to use on an serial tracked products (however note that this cannot be
applied to inventory that has batch and expiry control needs).
correctly identified. • Replenishment For replenishment, amongst the attributes
• available to be set per pick face are: trigger quantity,
placed into it so all details in reference to the inventory are replenishment tracking level, minimum replenishment quantity
stripped (not just the tag). Essentially all you have is a SKU and and maximum replenishment quantity.
a quantity. •
• It is therefore not advised to use this type if you wish to utilize replenishments are executed the displays shows Each, Carton
this information at any point after deposit to the pick face (as and Pallet level where appropriate. The tracking level used for
this information is cleared along with the tag). Such situations replenishment is governed by the 'Replenishment Tracking
are likely to be: Level' setting. Maximum quantity can be set on fixed pick face
o configuration (using the Maximum Replenishment Quantity
o batch controlled inventory, where strict batch knowledge setting) limiting the stock being allocated and later moved by an
is desired to be maintained; operator. All pick face limits are represented in eaches; limits
o inventory with expiry dates, where validations are applied must be set based on the SKU Pack configuration accordingly -
on the outbound process; hence filling the pick face whilst respecting the whole units of
o conditioned inventory; Measure of what is set up is possible.
o Inventory which requires distinct separation between • Replenish Part Tag is available as an option to provide the
bonded and non-bonded goods; operator with the instruction to take a full pallet, replenish part
• When a pick face is set to the type of TAG, then the inventory as of the pallet into the pick face, and then relocate the remaining
it is deposited into the pick face maintains its tag information; balance into a suitable storage location.
CORE+
• The ability to change the priority for Replenishment tasks is • Clustering rules if being used as part of the Pick Grouping
possible if desired via the Move Task Management Screen. Option Pack or Pick to Trolley / Slot Option Pack.
• When a replenishment is due to the pick face and picking is • Pick Circuit requirements.
actioned from said pick face, the operator is informed that a • Unit of measure pick face requirements.
replenishment is due. • Site Units of Measure (if a new Site) a single set of units of
• Replenishment tasks are not able to be skipped; they do measure are used by the facility for all clients operating out of it
however include exception processes that mirror those used for length, volume and weight. The values used should be the
during picking for short or null. Exceptions performed during short code stated and part measures will always be base10.
replenishment are able to be viewed via the movement Note that if a client is at multiple sites then consideration needs
discrepancy screen. to be had for the UoM(s) involved. Valid Units of measure are:
• Pallets (and other containers) Specific to the Client, these are o Length Centimeters (CM), Meters (M), Inches (IN), Feet
required to be set up (over and above a base set of Euro 2, etc), (FT)
including accurate descriptions, dimensions, volume, weights, o Volume Centimeters cubed (CM³), Meters cubed (M³),
pallet group (valid GS1 entries are PLT Pallet; BAG bag; BOX Inches cubed (IN³), Feet cubed (FT³)
Carton, or box; CAG Roll Cage or Cage; ENV Envelope) o Weight Grams (G), Kilograms (KG), ounces (OZ),
Pounds (LB)
of volumetric calculations and displayed on container labels,
carrier labels, pallet labels, and Delivery Notes as well as data
SSCC Client Specific Values
exchanges to other parties so accuracy is of upmost
importance. A Client level company prefix can be defined, along with a serial
• Printers The Printers (Name, Type, IP Address,) to be used by reference range, to generate SSCC values within the WMS based on
the operation and hence require setting up (if not already done). this criteria. This ensures the WMS generates appropriate SSCC
Includes the specification of which fixed, locality based and /or compliant IDs for Containers and/or Pallets to meet SSCC standards.
mobile printers (linked to specific workstation(s) to use - mobile
printing available for some operational documents if using the
Mobile Printing Option Pack. GDPR
• Site Systems contact Name, Telephone numbers and email • Personal data can be anonymized after 30 days from all of the
address for notification of system related issues and following records:
troubleshooting if required. The email address (which can be a o Orders at Shipped status
pre set-up distribution list in Exchange) will also be used to o Pre-Advices at Completed status
receive email alerts from the WMS for interface errors. o UPIs at Completed status
• WMS interface failures can be sent to an email address or • Available through a request to Support (manual), or as a
distribution list per site / client configuration. Please liaise with scheduled / reoccurring activity (automatic).
your Technical Consultant to enable this feature. • The automatic purge method is applied at Site / Client level and
will remove personal data for all customers / suppliers.
CORE+
• The manual purge method can also be applied at Site / Client • The default setting for all sites and clients is to anonymize GDPR
level but offers further opportunity to filter the records the personal data sent from the WMS to the Flexible Reporting tool,
anonymization is applied to. An example would be to anonymize however it is possible to opt out of this option to permit them.
all records for an individual customer / supplier. • For more information on Flexible Reporting please contact your
• The manual purge method allows the opportunity for Support to in-country Report Server Owner.
instruction should be given to Support to proceed with Facility Decisions (for configuration / Set up)
anonymization. This is recommended, as data cannot be • Provide the completed Client and Site Questionnaire
retrieved after being purged. Enter link to completed questionnaire here
• Scheduled (automatic) purging runs daily and does not offer the < Enter link to completed questionnaire here>
• Anonymized data will be replaced within the application with

• Provide the time zone that will be used for interface messages
• If sending WMS data to the Flexible Reporting tool the default to and from the WMS?
setting for all sites and clients is to anonymize GDPR personal
data, however it is possible to opt out of this option to permit Time zone to use for interface messages to WMS from client?
Enter timezone here
them.
< Enter timezone here>
Warehouse Dashboard
• A Warehouse Dashboard is available alongside the WMS and
provides a real-time view of key metrics enabling the Time zone to use for interface messages from WMS to client?
monitoring, control and management of warehouse processes.
Enter timezone here
Outstanding move tasks will be visible providing direct insight to
< Enter timezone here>
the current operational status.
• Full guidance on the use of the Warehouse Dashboard can be
obtained by referring to the Product Spotlight document,
available on the Matrix WMS Knowledge Centre.
• Provide the Printer, Location, Pick Face, Pallet Type, Carrier,
Service Level, master data details.
Flexible Reporting
Enter link to completed data take on spreadsheets here
• Accessible alongside the WMS, access to a stand-alone < Enter link to completed data take on spreadsheets here>
reporting warehouse is available which provides local operations
the data and ability to complete their own operational queries.

CORE+
• Select the Units of Measure that will be used across the whole
facility (site) and hence all clients operating out of it: [select □✔ NCD - Damaged by non CEVA Party
□
one]
✔ QAH - QA Hold
□
□
Length: Centimeters (CM)
Volume: Centimeters cubed (CM ³) ✔ RET - Returns
Weight: Grams (G)
□ RSR - Retention Sampling Required (optional)
□ Length: Meters (M)

Volume: Meters cubed (M ³)
□✔ RTS - Return to Supplier
Weight: Kilograms (KG)

• What Bonded Warehouse Document Types will be used?
□ Length: Inches (IN)

[select one]
Volume: Inches cubed (IN ³)

Weight: Pounds (LB)
□ None this is not a bonded warehouse
□ I have detailed them here:
□ Length: Feet (FT)

Volume: Feet cubed (FT ³)
Enter document type(s) here
Weight: Ounces (OZ)
• In addition to the standard Condition Codes, which optional

Condition Codes will be used? [select one or many]
□
✔ DAM - Damaged whilst in CEVA Care
< Enter document type(s) here>
□ DES - Identified for Destruction (optional)
□
✔ DIS - Disposal
□ ETR - External Testing Results Required (optional)
□ FMD - Falsified Medicines Directive (optional)
□
✔ INS - Inspection
□ ISO - Isolation (optional)

CORE+
• Are Client specific SSCC values required to be generated? • Is access to the Warehouse Dashboard required? [select one]
[select one]
□ Yes
□ Yes, using the following Company prefix and Serial

Number range:
□ No
Enter GS1 Company

< Enter GS1 Company prefixprefix
and Serial Number
and Serial Range
Number
here Range
(this should equate to 17 numeric characters) • Is access to the Flexible Reporting Warehouse required? [select
here (this should equate to 17 numeric
one]
characters)>
□ Yes
□ No □ No
• Will the Handling Unit Flow be used? [select one] • If using Flexible Reporting is GDPR sensitive data required to
□ Yes
be sent to the Report Server tool:
□
□ No
□
No (default)
Yes
• Is scheduled (automatic) GDPR purging required?
Facility Section Complete
□ Yes
□ No
• If using Client Specific References, what is the name of the data

each of the following fields will hold?
For example:
Inbound Client Ref 2 = GRN
• Inbound Client Ref 1 Enter the data

< Enter name
the data herehere>
name
• Inbound Client Ref 2 Enter the data

< Enter name
the data herehere>
name
• Outbound Client Ref 1 Enter the data

< Enter name
the data herehere>
name
• Outbound Client Ref 2 Enter the data

< Enter name
the data herehere>
name

CORE+
SKU Description
SKU Set-up: Automatically provided for all and fixed as part of the
Diagram solution
• Units of Measure
Standard o
Base Data Set o
o Case (entered as C on the Mobile Device).
o
Data Take On o
XLS o
• Certain SKUs
hazardous version of the previous SKU.
• Certain Pack Configurations
SKU Interface with the HU and HUHAZ SKUs.
SKU Set-up: Provided by the Business (in the data take on spreadsheets
2 provided to IT)
• SKUs The SKUs to be used for the Client complete with
dimensions and weigh per each, HAZMAT ID (if appropriate), if a
SKU serial number capture is required (the capture points will be
automatically set based upon the Serial Capture Group set
against the client), serial format (if capturing (no more than) one
serial it is possible to specify, per SKU, the format that must be
adhered to at the point of serial capture), if Batch is to be
captured at receipt, if Expiry and/or manufacture date is to be
captured at receipt (note that if a shelf life is set for the SKU, and
no expiry date is provided, then manufacture date will be used
SKU Interface to determine the expiry date; if no expiry date nor manufacture
date is provided then receipt date will be used to determine
expiry date), if a minimum number of days (now until expiry
date) must be available on the product on receipt, and if a
minimum number of days (now until expiry date) must be
available on the product on allocation / picking. If Origin is
required to be captured for inventory received (Note this must
not be used if using the Bonded Warehouse Option Pack). If
CORE+
automatic creation of stock checks is required then a count Inventory of the same SKU can have different owners, which
frequency can be set. The Pick Count Quantity can be set so would drive it to be stored separately. Owner is used to drive
when a pick face falls below this number a stock check is stock segregation and putaway rules to follow (if desired). Please
triggered. If the SKU is a high risk SKU (or not). If the SKU see putaway for more information on stock segregation. At
requires external testing results to accompany the inventory, If allocation an exact match against SKU, condition and owner
Customs functionality is to be used, then C&E Warehouse type specified is used; there is no standard substitution hierarchy or
needs to be set, C&E SKU set, [initial] Country of Originator set, logic applied.
C&E Commodity Code set and the C&E VAT Code set. Each compatible if owner functionality is used then the Kit to Order
SKU provided will also state its source / User that generated it and Kit to Stock Option Packs cannot.
(EDI-[host system of client]; DTO; WPI-[portal username, logistics • Putaway Groups Inventory per SKU can belong to different
putaway groups, which would drive it to be stored in locations
external users]; WPM-[portal username, logistics id for CEVA specific to that putaway group.
• Allocation Group the rules to be applied during allocation.
users]). • TAG Merge Criteria - For Inventory to merge, the locations tag
• Supplier (alternative) SKU IDs Additional SKU identifiers for a merge flag and the impacted SKUs tag merge flag must both be
SKU which allow the alternative SKU ID to be linked to the enabled. Available valid matching criteria (at inventory level and
set per client/site) set to control the merge are: Condition,
across SKU, EAN, UPC and supplier SKUs then the operator is Manufacture date, Pack Config, Pallet Type, Batch ID, Origin,
displayed the choices so to make a selection. Supplier, and Expiry Date.
• Pack Configuration Pack configuration for use complete with • FMD Indicator An Indicator to show that this SKU is part of the
pallet volume, layer height, eaches per layer, volume per each, Falsified Medicines directive programme of the client. Note that
ratio of eaches-to-cases-to-Pallet and the Shipping Unit Level some inventory for an applicable FMD SKU may NOT require
indicator(s) if using the One-Piece Flow Option Pack. processing due to where they are being shipped to. As such the
• Pack Configuration Linking Which Pack Configuration(s) each need for action cannot be determined solely from the SKU
SKU will use. record and will be used in conjunction with condition code on
• Site specific Putaway Algorithms to honour inventory inbound and an FMD processing indicator on outbound.
segregation (by owner or Putaway group) a single set of site • Kits (Bill of Materials) SKUs can be set up as indicated to be a
specific putaway Algorithms, selected from a set choice of 4 Kit SKU (the parent). Kit lines can then be set up to function as
types [strict segregation, Preferred then alternate segregation, component parts of the SKU. A kit line will state the SKU, the
segregated with generic bulk storage, no segregation], that
controls the direction of inventory once received to their storage not compatible
location and respecting the segregation rules identified. (Kit to Order and Kit to Stock Option Pack).
• Owner one or many inventory owners for use, used to drive • Capture UDI An indicator can be set to identify if the SKU
segregation rules and / or VMI. By default the Client ID will be requires the capture of Unique Device Identifier (UDI) upon
set up as an owner and used if no other owners are specified. receipt (works in conjunction with flag set on Pre-Advice Line).
CORE+
This is used for the identification of medical devices within the UPDATE action. Similarly, if an UPDATE is attempted yet no
healthcare supply chain. SKU record exists, the information will be re-tried as an ADD
• Ship As Is action.
• stops
packaging. SKU dimensions will be used instead of container any inventory for the SKU being received until the indicator has
dimensions for all documentation and extracts related to been removed. The indicator is removed by a Team Leader as
container level packing, where the quantity of the container part of completing the new SKU process when the physical
does not exceed 1 SKU (EA). goods have been inspected, accurate details determined the
• Stackability controls system updated accordingly (typically SKU, pack config and pick
pallets of that SKU that can be stacked on top of each other, face information). SKU record specific information that is able to
be captured is (* denotes cannot change if existing Stock or
location storing this product by that number of full pallets and transactions exist).
o Description,
• Serial Format the format that serials must adhere to when o Product Group,
captured. Format can comprise of: o Putaway Group,
o A (alphabetical characters) o Allocation Group,
o N (number characters) o Family Group (Post Pick Grid Sortation Option Pack),
o * (wildcard characters) o Hazmat ID,
For example AAAANN would allow the o TAG Merge,
capture of serial TEST01. Note not compatible when capturing o Count Frequency,
more than one Serial Per Each (see below) o Max Stack,
• Serial Per Each the number of serials that will be captured per o Stack Limitation,
each (use in conjunction with the Serial Type data take on sheet) o Stack Description,
o Always Full Pallet,
o Commodity Code,
SKU Set-up: Additions, Updates and Deletions o Hazmat,
• SKUs can be added using either the portal or an EDI or API o HTS,
interface. o ECCN,
• If created via EDI interface, an APERAK message is able to be o XDC Attribute*,
sent confirming successful creation within the application of the o High Security / Risk Indicator,
SKU. o External Test Results required Indicator,
• When SKU information is passed to the WMS from either the o Force Capture of Allocation Attribute 3* (DOT Management
portal or an EDI interface, it will be accompanied by an indicator for Tires Option Pack),
a SKU o FMD applicable indicator,
record already exists, the information will be re-tried as an o Kit flag (Kit to Order and Kit to Stock Option Packs),

CORE+
o Split Kit flag (Kit to Order and Kit to Stock Option Packs), o Serial Capture Required?
o New Product, o Bonded Warehouse Option
o Count frequency Pack only)
o Obsolete Product, o Bonded Warehouse Option Pack only)
o Origin Required, o Country of Originator set to which ever country the SKU is
o Repacking by Piece (when using the CEVA Packing first supplied from. (ISO2 code) (Bonded Warehouse Option
Application) Pack only)
o 2man lift (indicates too heavy for a single operator to move o C&E Commodity Code set to the commodity
can be used in pick grouping logic), (Harmonization) code applicable. (Bonded Warehouse
o Size, Option Pack only)
o Each Quantity, o C&E VAT Code set ero. (Bonded
o Each Height, Warehouse Option Pack only)
o Each Width, o Ship as Is
o Each Depth, o Capture UDI
o Each Volume [if left empty this can be automatically • ABC Ranking is held against the SKU and is automatically
calculated if height, width and depth are populated and updated based on the ABC Analysis outcome (ABC Analysis
then pressing execute]*, Option Pack).
o Each Weight*, • Once added, the only updates available to be made via EDI
o Serial Capture at Receiving, interface are to the SKU description, Commodity Code, HTS
o Serial Capture at Picking*, Code, ECCN, C&E Commodity Code (used as part of the
o Serial Capture at Packing*, Bonded Warehouse Option Pack
o Serial Capture at Stock Check, • Updates are available to be made via the Item Master Update
o Serial Capture at Stock Adjust, API when the New SKU flag is checked.
o Serial Format, • The Item Master Delete API is able to be used to set an existing
o QC Status*, SKU to obsolete.
o Min Expiry Days*, • All other changes will need to be manually communicated to the
o Return Min Expiry Days*, operation from the client to allow for proper consideration and
o Shelf Life*, the impact understood (to inventory, facility set-up, operational
o Shipment Shelf Life*, process or contract terms, etc). Once the actions required are
o Expiry Required*, determined then the operation can co-ordinate the operational
o Manufacture Date Required* (DOT Management for Tires activity alongside a helpdesk ticket to make the appropriate
Option Pack - activates First Manufactured, First Out changes to the SKU record / inventory / locations, etc.
Allocation (FMFO) algorithm), • If the SKU is marked as obsolete, note that this will stop the
o Max Mixing Manufacture Days (DOT Management for Tires
receipt (including Return receipt) of the SKU.
Option Pack) ADD*?

CORE+
• Client visibility of the following SKU details is available using the o Supplier ID
Item Master Status API. o Batch ID
o Client ID o Allocation Attribute 1
o SKU ID o Allocation Attribute 2
o SKU Description o Allocation Attribute 3
o Family Group
Automatic Pick Face Creation and Control
o Product Group
o Putaway Group The Automatic Pick Face Creation and Control feature offers the ability
o Count Frequency to assign SKUs a Pick Face Type of either Fixed or Dynamic which in
o Hazmat ID turn drives the following behaviour:
o Each Value Pick Face Type Fixed:
o C&E Currency
o Barcodes • Users are prevented from deleting the last fixed pick face
▪ UPC ensuring there is a fixed pick face at all times
▪ EAN • Upon setting a SKU with a Pick Face Type of Fixed, any empty
o Each weight and dimensions Dynamic pick faces will be deleted
o Commodity Code • Controls to ensure receiving is prevented until at least one fixed
o Shelf Life pick face is set up
o Minimum Expiry Days
Pick Face Type Dynamic:
o Shipment Shelf Life
o Pack weight and dimensions\ • A dynamic pick face will be automatically created in the dynamic
o Supplier SKU pick face zone 53DYN01. Default pick face settings are applied
o ECCN and can be updated if required.
o HTS Code
• An Inventory Report API is available to be used to provide Client
visibility of the following inventory details (per SKU): SKU Substitution Option Pack
o Site ID The SKU Substitution Option Pack provides the ability to mark one or
o SKU ID many SKUs as a substitute that can be used as an alternative SKU
o UOM during an inventory allocation shortage.
o Quantity On Hand
This feature is controlled through the SKU Substitution screen which
o Quantity Allocated
allows users to setup substituted SKU values. Included within this screen
o Condition Code
is the ability to specify the following:
o Owner ID
o Origin • The Substitute SKU (more than one may be added per original
o Under Bond? SKU)
CORE+
• The Start and End Date and Time that the substitution is in SKU Decisions (for configuration / Set up)
effect (only required for temporary substitutions) • Provide the SKU, Pack Config, SKU-SKU Pack Config master
• Priority, where more than one substitution is required these will data.
be assigned based on Priority Enter link to completed data take on spreadsheets here
• Conversion Factor used to specify the quantity of the substitute
SKU required to replace the original SKU
Please note that the SKU Substitution Option Pack may not be used
alongside the Ship in Full feature. < Enter link to completed data take on spreadsheets here>
• Will Supplier SKU functionality be used?
□ Yes
□ No
• Will the SKU Substitution Option Pack be used? [select one]
□ Yes
□ No
• (Kit to Order and / or Kit to Stock
Option Pack)? [select one]
□ Yes I accept that this is not compatible with the use of

owner functionality and as such will only use one
□ No

CORE+
• How will the SKUs be provided to Matrix WMS CORE+? [select • Is a SKU Advice interface required (to be sent from the WMS to
one or many] the Middleware)? [select one]
□ CEVA Standard Interface □ Yes, CEVA Standard EDI Message

□ Client Specific Interface (Client format mapped to the □ Yes, CEVA Standard API Message
CEVA Standard Message)
□ Yes,
□ Portal Upload Client specific message (CEVA Standard Message
□ Portal Form □ No
□ CEVA Standard API (Item Master Create) • Is
used? [select one]
• If Portal uploads are used, who will be using it? [select one or
many] □ Yes
□ CEVA Employees □ No
□ Client Employees •
□ Other 3 Party
rd used? [select one]
•
□ Yes
□ No
If the Portal form is used, who will be using it? [select one or
many]
□ CEVA Employees •
□ Client Employees used? [select one]
□ Other 3 Party
rd □ Yes
• On successful creation of a SKU, is the "APERAK Confirmation
□ No
interface (generated from the WMS to •
the middleware layer) required to be sent? [select one] used? [select one]
□ Yes □ Yes
□ No □ No

CORE+
• Is an Inventory Reconciliation interface required (to be sent

from the WMS to the Middleware)? [select one]
□ Yes
□ No
• If Yes, at what time each day is the Inventory reconciliation
interface required to be sent?
Enter the time and time zone

< Enter the time and time zone>
• Is the Automatic Pick Face Creation and Control feature

required to be used? [select one]
□ Yes
□ No
SKU Section Complete

CORE+
Operator o Team Leader

o Customs Team Leader
Diagram o Site Manager
o Stock Operator
o Stock Administrator
Standard o Dashboard Viewer
Base Data Set
• Trained and authorized Global Matrix WMS Super Users are
provided with Super User accounts. These accounts grant access
above and beyond that provided within operational user groups
Data Take On • Investigator accounts are available for colleagues, typically in IT /
XLS National roles, to have a view (only) of selected information for
all sites and clients within one Region
• CEVA Corporate IT Policy for passwords is adhered to
3 o Users need to change their password every 90 days
o Users will (when possible) get a warning 14 days prior to
expiration
Operator o Users are disabled when they have not logged in for 90
days
o Users can have 6 tries when logging in to use the correct
password, otherwise they are disabled
o The policy for new passwords is:
▪ Must be at least 8 characters
▪ Must contain at least one upper case character,
one lower case character and numeric characters
▪ Must not contain any special words, like a
workstation name, a user name, a day of week, or
a month of year
Description ▪ Must not be used in the last 92 days
Operator Set-up: Automatically provided for all and fixed as part of the ▪ Must not be the same as the last 12 passwords
solution used
• Workstation Groups • New Operators created using the in-product tool (report) will
group are provided for assigning to a workstations to control
how they behave. • Sites using the Push of Pick Tasks Option Pack can specify a
• The following operational user groups are provided for
assigning to a user account to control the access allowed:
o Operator

CORE+
The following description provides an overview of tasks that will be performed by each of the identified operational roles.
Tasks Operator Team Leader Customs Team Leader Site Manager Dashboard User Stock Operator Stock Administrator
New SKU Completion       

Inbound Task Management       
Receiving and Reverse Receiving       
Customs Consignment and Invoice Creation       
Customs Completion of Inbound Order Receipting       
Putaway       
Outbound Task Management       
Outbound Preparation       
Allocation       
Picking       
Loading and Unloading       
Customs Update of Outbound Declaration Approval       
Shipping       
Create Relocations       
Performing Relocations       
Discrepancy investigation and Adjustments       
Inventory Updates       
Create Stock Checks & Cycle Counts       
Perform Stock Checks & Cycle Counts       
Reprint of Labels       
General Enquiries       
Interface investigation and Correction Activities       
Static data Management i.e. pick faces, locations       

Dashboard Visibility (General)       
Dashboard Visibility (Ready for Post Pick Activity)       
KPI / MI Report Generation       
User Query / Creation       
Update of User Shift       

®
Release 7.1.0 CEVA Matrix WMS CORE+ Product Description 171
CORE+
Operator Set-up: Provided by the Business (in the data take on Operator Decisions (for configuration / Set up)
spreadsheets provided to IT) • Provide the Operators and Printers master data.
• Operators The users of the system for this Site / Client. Enter link to completed data take on spreadsheets here
• Workstations The Mobile Devices that will be used for this Site
/ Client.
• Printers The Label and Report printers that will be used for this
Site. Which reports will be outputted by what printer(s).
< Enter link to completed data take on spreadsheets here>
Operator Section Complete

CORE+
Bookmark
Documents and Reports Operational Documents  Reports Catalogue
Documents and Reports

Operational Documents
Pre-Advice Receiving Sheet
The Pre-Advice Receiving Sheet provides the facility to perform the receiving process on paper before being recorded electronically within the WMS.
The document will display:
Document Header:
• Site
• Client
• Document Date [DD-Mmm-YYYY]
• Page X of Y
Pre-Advice Header information:
• Pre-Advice ID
• Pre-Advice ID; in barcode format
• Number of Pre-Advice Lines
• Owner ID
• Return (Y/N)
• Due Date
• Supplier Reference
• Supplier Name
By Each Pre-Advice Line: • Hazardous Goods (Y/N)
• SKU ID; readable text • Serial Required (Y/N)
• SKU ID; Barcode format • Expiry Required (Y/N) blank space below for Expiry Date capture
• SKU Description • Origin Required (Y/N) blank space below for Origin capture
• • Batch ID Required (Y/N) blank space below for Batch ID capture
• Primary Pack Config (for SKU) • Expected Qty Eaches (Tracking Level 1) blank space below for capturing actual
• Alternative Pack Configurations for the SKU quantity in eaches
• Pre-Advice Line ID • Expected Qty (Tracking Level 2) blank space below for capturing actual quantity in
• SKU EAN; Blank if not populated tracking level 2 [if appropriate]
• SKU UPC; Blank if not populated • Expected Qty - (Tracking Level 3) blank space below for capturing actual quantity in
• New Product (Y/N) tracking level 3 [if appropriate]
• Pick Face exists (Y/N) • Expected Qty (Tracking Level 4) - blank space below for capturing actual quantity
• Minimum expiry date allowed before we can receive in tracking level 4 [if appropriate]

CORE+
CEVA Standard Pre-Receive SKU Label

The Standard Pre-Receive SKU Label is manually printed prior to receipt. Please refer to the Receive inventory process step for an example label.
Select either the Pre-Receive SKU Label Pre-Advice or the Pre-Receive SKU Label ASN. Use the report parameters to specify if the label should be
generated for the whole Pre-Advice / ASN or for an individual SKU.
Each label will display:
• Client Name, SKU ID, SKU (barcode), SKU Description, Net Piece Weight.
• roduced per EACH or per TAG.
• Label format (70x50mm):
CEVA Pre-Receive SKU Label Flexible Documents Option Pack

A bespoke version of the Pre-Receive SKU Label is available if using the Flexible Documents Option Pack.
The Design Template allows the building of a customized Pre-Receive SKU Label using the existing data fields as per the Standard Pre-Receive SKU
Label.
Each label may display a customized layout using the following fields:
• Client Name, SKU ID, SKU (barcode), SKU Description, Net Piece Weight.
•
• Label format (70x50mm)

CORE+
CEVA Standard Putaway TAG Label

Upon confirming receipt of a quantity of goods a Putaway TAG label is automatically generated. Please refer to the Receive inventory process step for
an example label.
The label will display:
• Data related to receipt transaction per TAG label

• Each label will include SKU, SKU Description, Pallet ID, Pallet Type, Handling Unit reference (only displayed for SKUs identified as a Handling
Unit), Resv. ID 1 / 2 / 3 (only displayed if an Allocation Attribute is populated on the Pre-Advice), Putaway Zone for the determined putaway
location, Putaway Subzone (if present) for the determined putaway location, Putaway Aisle (if present) for the determined putaway location,
Putaway Sequence, TAG ID Barcode and number, High Risk SKU Indicator (only displayed for SKUs that are indicated as such), Hazmat Code
(only displayed for hazardous goods), Client Name, Receipt ID, Receive Dock, Receive Date & Time (in the time zone of the Site), Batch (if
appropriate), Expiry Date (if appropriate), Receive Quantity, Receive Weight (UoM) (including weight Unit of Measure stored against the Site
record), Receipt Volume (UoM) (including volume Unit of Measure stored against the Site record), Origin, Manufacture Date, TAG ID Barcode
(vertical), Environment produced from and document version number displayed vertically in the label margin.
• Label format (6 inches by 4 inches in size) -
Putaway TAG Label

SKU: 999999999999999999999999999999999
XXXSKUDESCRIPTIONHEREXXXXXXXXXXXXX Client Name:
XXX XXXX XXXXX XXXX XXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Receipt ID:
XXXXXXXXXXXXXXX
### HIGH RISK SKU CONTAINED ###
999 99999 999999 999999

Pallet ID: XXXXXXXXXXXXXXXXXXX Receive Dock:
Pallet Type: XXXXXXXXXX XXX XXXX XXXXX XXXX XXXX
*999999*
HU Reference: XXXXXXXXXXXXXXXXXXXXXXXXXXXX Receive Date & Time:
Resv. ID 1: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 99-XXX-999 9 9 9:99:99
HAZMAT Code: 9999
Resv. ID 2: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX Batch:

Resv. ID 3: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXX XXXX XXXXXX XX
Expiry Date:
Putaway Zone: XXXXXXXXXX
99-XXX-999 9
Putaway Subzone: XXXXXXXXXX Receive Qua ntity:
Putaway Aisle: XXXXXXXXXXXXXXXXXXX 999 99999 99999 99,999 999
Putaway Sequence: 99999999,99 Receive Weight (UoM):
*999999*
999 99999 99999,999 999
TAG:
Receive Volu me (UoM):
999 99999 99999,999 999
Orig in:
XX
PRD – 6.0.0.0
Manufactu re Date:
99-XXX-999 9
999999
CEVA LOGISTICS IN TER NAL USE – DATA CORREC T AT POINT OF PU TAWAY ON LY

CORE+
CEVA Standard Inbound SKU Label

The Standard Inbound SKU Label is automatically printed at receipt, and able to be manually re-printed if required. Please refer to the Receive
inventory process step for an example label.
• Client Name, SKU ID, SKU (barcode), SKU Description, Country of Origin, Net Piece Weight, Serial Number.
• he SKU Label should be produced per EACH or per TAG.
CEVA Inbound SKU Label Flexible Documents Option Pack

A bespoke version of the Inbound SKU Label is available if using the Flexible Documents Option Pack.
The Design Template allows the building of a customized Inbound SKU Label using the existing data fields as per the Standard Inbound SKU Label.
• Client Name, SKU ID, SKU (barcode), SKU Description, Country of Origin, Net Piece Weight, Serial Number.
•

CORE+
Move Task List

To aid paper based operations (i.e non RDT) a Move Task List can be generated to aid the movement of inventory, typically for putaway or picking).
Please refer to the Putaway process step for an example Report.
The Report will display:
• Data related to a single List

• Each report contains a header displaying the List ID number, total volume, total Weight, Number of Tasks, Total Quantity, Number of Orders,
Number of Customers, Timezone and List ID as a Barcode. The environment produced from and document version number will be displayed
vertically in the document margin.
• Each record displayed over two lines on the sheet relates to a single move task
• Each move task will include Task ID, Client ID, SKU, SKU Description, Consignment, Shipment Group (if populated), From Location, To Location,
Tag ID, Owner ID, Quantity to move and Pallet ID.
• Report format (A4 or US Letter in size)
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29
MATRIX® WMS CORE+

8 20
Move Task List

<<Logo, bottom right justified>>
19
List ID: <List ID>

Volume (UoM): Calc # Tasks: Calc # Orders: Calc
18
Barcode <List ID>

Weight (UoM): Calc # QTY (EA): Calc # Customers: Calc
177
Task ID Client ID SKU Consignment From Location Tag ID Qty to Move

SKU Description Shipment To Location Owner ID Pallet ID
16
<Task ID> <Client_ID> <SKU.SKU_ID> <Order_Header.Consi <???.From_Location> <???.Tag_Id> <???.Quantity>

15
gnment>
Order_Header.Shipm <???.Owner_Id>
6
<SKU.Description> ent_Group> <???.To_Location> > <???.Pallet_ID>

14
XXXXXXXXXXXXXXXXX XXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXX XXXXXXXXXXXXXXX

XXX XXX X XXXXXXX
13
XXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXX XXXXXXXXXX XXXXXXXXXXXXXXX

XXXXXXXXXXXXXXXXXXXXXXXX XXX X XXX
12
4
9
85
11
10
37
<<Env>> <<Version>>
6
5
2
4
3
12
DD/Mmm/YYYY HH:MM:SS Page X of Y

1
<Timezone>
0
0

CORE+
List Header Label

If generating documents at the point of order allocation, the documents will be produced in a single output headed by the List Header Label which
provides summary details of the documents generated.
• Data related to a single list

• Each label will include a header displaying the List ID number, the Client ID, Site ID, Label Count in the print run, Consignment, Activity Zone,
Date, Volumetric Allocation section detailing the Container Type and Count required for the pick run.
• Label format (6 inches by 4 inches in size)

CORE+
CEVA Standard Outbound SKU Label

The Standard Outbound SKU Label is automatically printed at allocation, and able to be manually re-printed if required. Please refer to the Allocation
and Pick Grouping process step for an example label.
• Client Name, SKU ID, SKU (barcode), SKU Description, Cou X of Y.

• must be set to TAG for Outbound SKU Labels to generate.
CEVA Outbound SKU Label Flexible Documents Option Pack

A bespoke version of the Outbound SKU Label is available if using the Flexible Documents Option Pack.
The Design Template allows the building of a customized Outbound SKU Label using the existing data fields as per the Standard Outbound SKU Label.
• bel Count X of Y.
•

CORE+
Picking Media Label

Picking media labels may be printed prior to picking. Either manually through the user report (standard), or automatically if set to generate at the point
of order allocation.
• Data for a sequential system generated TAG ID that is unique to the Site
• Each standard label will include Site ID and the media TAG ID (number & Barcode). Note that the TAG ID can be set as a SSCC if required. If
generating this document at the point of order allocation the label will also show Client ID, plus the container and slot ID if using the Pick to
Trolley / Slot Option Pack.
Picking Media Label (standard) Picking Media Label (if generated at order allocation)

CORE+
CEVA Picking Label

Prior to picking, picking labels may be printed. A Picking Label Header will be produced displaying overall details for the pick list. The Picking Label
Header will be followed a Picking Label for each individual pick within the list. Please refer to the Picking process step for example labels.
• Each Picking Label Header will include Client Code, List ID, List ID (barcode format), Label Count (number of Pick Labels to follow), Customer
this pick list this pick list), Task
in this pick list), Qty Count (the total number of EA (Eaches) on all Move Tasks that are included
on the Pick List), Order Type, Consignment, Activity Zone that the picked goods should be taken to once picked, Date the pick task was
allocated (in the time zone of the Site), Volume.
• Each Picking Label will include Client, Customer ID, Order Qty, Order ID (quantity allocated to be picked), SKU, SKU Description, (Pick)
Location, Activity Zone (that the picked goods should be taken to once picked), Date the pick task was allocated (in the time zone of the site),
Name (Customer name stated on the order), Order Type, List ID, Info (Special Instructions).
• Environment produced from and document version number will be displayed vertically in the label margin.
• Label format:
Standard (100 - 105mm x 45mm in size) When generated at order allocation (6 inches by 4 inches in size)
Picking Label Header Picking Label Header Picking Label

List ID:
XXXXXXXXX
CLIENT: XXXXXXXXX
XXXXXXXXXXXXXXX
Label Count: XXX
Customer Count: XXXX Consignment: XXXXXXXXXX

Order Count: XXXX Activity Zone: XXXXXXXXXX
Task Count: XXXX Date: XXXXXXXXXXX
Qty Count: XXXX Volume (UoM): XXXXXXXXXX
Order Type: XXX Weight (UoM): XXXXXXXXXX
Picking Label
Customer ID: Order ID:
XXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXX
CLIENT: XXXXXXXXX
SKU:XXXXXXXXXXXXXXXXXXXX Qty: XXXXXXXXXXXXX

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Location: XXXXXXXXXXXXXXXXXXXX Activity Zone: XXXXXXXXXX
Name: XXXXXXXXXXXXXXXXXXXX Date: XXXXXXXXXXX
List ID: XXXXXXXXXXXXXXXXXXXX Order Type: XXXXXXXXXX
Info: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

CORE+
Volumetric Picking Label

At the point of order allocation, Volumetric Picking Labels may be printed. Please refer to the Picking process step for an example label.
• Each Volumetric Picking Label will include Client Name, Site Name, List ID, List ID Barcode, Order Type, Order ID(s), Consignment, Shipment
Group, Activity Zone, Ship Dock, Pallet ID Barcode, Pallet Type, Pallet ID, Last 4 Characters or Pallet ID, Container Type, Container ID, Last 4
characters of Container ID.
• Environment produced from and document version number will be displayed vertically in the label margin.

CORE+
Ready for Post Pick Activity Report

Upon the entirety of an order being picked and placed into the relevant activity zone, the Ready for Post Pick Activity report is automatically triggered
to be printed. Please refer to the Load Preparation process step for an example report.
The report will display:
• Data for the entire order

• Order ID Number and Barcode, Shipment group, order Type, Consignment ID for
the order, Ship dock assigned to the order, Client name, FMD reason for the Order, the date and Time printed (in the time zone of the Site),
page number of total pages and a space for the signature or stamp of the person performing the repack or other VAS activity.
• r Location ID of where the stated
combination of SKU/pallet/container resides within the activity zone, the pallet ID for the goods, the container ID for the goods, the order line
that the goods relate to on the order, the SKU, the EAN (if present), the UPC (if present), the description of the SKU, the quantity, a check box
for operator use, FMD Flag from the SKU record and a space to record the FMD Result.
• The Environment produced from and document version number will be displayed vertically in the document margin.
• Note that a SKU may be picked into multiple containers and/or be on multiple pallets and/or in multiple locations.

CORE+
• Document format (A4 or US letter in size)

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29
8 20
Document Date: <DD-MMM-YYYY>

Ready for Post Pick Activity Logo
19
Page: <XXX(YYY)>
<Order_Header.Name>
18
Order Type: <Order_Header.Type>

Order ID: <Order_Header.Address1>
<Order_ID> Consignment: <Order_Header.Consignment>

177
<Order_Header..Address2>
Ship Dock: <Ship_Dock>
<Order_Header.Town>
<Order_Header.PostCode>
<Order_ID>
16
Client Name: <Order_Header.Client>

<Order_Header.County
FMD Reason: <Order_Header.FMD_Reason?> <Order_Header.Country
Shipment ID: <Shipment_ID>
15
Palletise? <Order_Header.UserDefCheck2>
6
Location Pallet ID Container ID Order Line ID SKU SKU Description Quantity Check Box
14
TAG Batch Expiry UPC EAN FMD? FMD Result

13
Location Pallet ID Container ID Order Line ID SKU <SKU Description> <Quantity> []

12
5
<TAG> <Batch> <Expiry> <UPC> <EAN> <FMD_Flag>

11
10
4
9
8
37
6
5
2
4
3
Special Instructions: Signed / Stamp:

12
<Special Instructions Code> <Special Instructions text>

1
Dates/times are in time_zone

0
0

CORE+
CEVA Standard Container Packing / Contents List

Upon the container completing repacking or at the point of order allocation, the Packing / Contents List may be triggered to be printed. Please refer
to the Load Preparation process step for an example document.
The Document will display:
• Dependent upon the language value passed on the Order Header, the Field text will be displayed in the appropriate language. Available
languages are English, French, Italian, German, Slovak, Czech, Dutch, Danish, Spanish, Arabic, Swedish, Finnish, Norwegian, Polish &
Portuguese.
• Data for the entire contents of the container which may be part or whole of one or many orders.
• The default is to use a CEVA logo, however a logo [Minimum 300 dpi and preferably in jpeg format] for the client can be used instead if
provided.
• Document Date (in the time zone of the Site), Page x (of y), Delivery Address,
Delivery Postcode, Delivery Country, Client Name, Site Address, Site Post Code, Site Country, Site Phone, Site Fax, Client ID, Consignment ID
number and Barcode, Container ID, Gross Weight (including weight Unit of Measure as stored on the Site Record), Nett Weight (including
weight Unit of Measure as stored on the Site record), Order reference (Purchase Order Number from Order Header)
• Order ID the SKU belongs to, Purchase Order
Number (if provided on the Order Line), Order Line ID for the SKU, SKU ID, Customer SKU ID (if provided), SKU Description, Quantity of the
SKU in the container, Reserve Inventory ID (allocation attribute(s) if provided), Host Order & Line ID (if provided), The Hazardous material code
for the SKU (if relevant). In addition below the SKU line the Manufacture Date, Origin/Country of Origin and a list of the Batches, Expiry and
Serial Numbers is provided (if relevant).
• The Environment produced from and document version number will be displayed vertically in the document margin.
• In the footer of the document it displays the time zones that all dates / times are in.
CEVA Container Packing / Contents List Flexible Documents Option Pack

Upon the container completing repacking, the Packing / Contents List may be triggered to be printed.
Bespoke Packing / Contents List are available if utilizing the Flexible Document Option Pack. Design templates are available in A4 and US Letter sizes,
and in both portrait or landscape orientation. The design templates allow the building of the customized Packing / Contents List by selecting from the
available data fields. Note, the available data fields are aligned with the Standard Packing / Contents List. Please liaise with your WMS CoE
Implementation Consultant for further details.

CORE+
• CEVA Standard Pack / Contents List document format (A4 or US Letter in size)
0
8 20 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29
Document Date: <DD-MMM-YYYY>

Pack/Contents List Logo
19
Page: <XXX(YYY)>
<Order_Header.Name> <Site.Address_Name> Client ID: <Client.Name>

18
Consignment <Order_Header.Consignment_ID>
<Order_Header.Address1> <Site.Address1>
177
<Order_Header..Address2>
<Order_Header.Town>
<Order_Header.PostCode>
<Site.Address2>
<Site.Town>
<Site.PostCode>
<Consignment_ID>
16
<Order_Header.County <Site.Country
<Order_Header.Country Container ID <Container_ID>
Phone: <Site.Contact_Number> Gross Weight: <Gross_Weight><UOM>
15
Fax: <Site.Fax> Net Weight: <Net_weight><UOM>

6
Order ID PO Number Line ID SKU Description Hazmat QTY

14
<Order ID
<SKU.Haz
<Order_Header.Order_ID> <Order_Line.Purchase_Order> _Line.Li <Order_Line.SKU_ID> <SKU.Description> mat_ID> <Qty>
ne_ID> Customer SKU: <Order_Line.Customer_SKU>
Host Order (& Line) ID: <Order_Line.Host_Order_ID>(<.Host_Order_Line_ID>)
13
Reserved Inventory ID: <Inventory.User_Def_Type_1>, <Inventory.User_Def_Type_2>, <Inventory.User_Def_Type_3> Sub Qty:

Origin / CoO: Batch: <Inventory.Batch_ID> Expiry: <Expiry> Manuf: <Manufa> Serials: <Serial_Number> <Qty>
12
5
11
10
4
9
8
37
6
5
2
4
3
12
1

0
0

CORE+
CEVA Container Shipping Label

Upon the container completing repacking, the CEVA standard Container Label may be triggered to be printed (dependent upon carrier set up). If no
post pick activity is required the Container Label is able to be generated at the point of order allocation. Please refer to the Allocation and Load
Preparation process steps for example labels.
• Data related to the container and its contents

provided.
• Each label will include Client Name, Carrier Name, Service, Site Address, Site Town, Site County Site Postcode, Site Country, Order Name,
ht
(including weight unit of measure from the Site record), Product group (Product groups from the SKUs contained), Hazardous Class (HAZMAT
ID), Container ID, Barcode (either Container ID or SSCC Barcode dependent upon settings), Trolley Slot ID and Trolley Slot Barcode (if using the
Pick to Trolley / Slot Option Pack and the label is generated at order allocation), Customer Address (Special Instructions at the order level with a
location qualifier of PRN-LBLADR using values corresponding to Name1, Address1, Address2, City, Postal Code, CountryName), Environment
produced from and document version number will be displayed vertically in the document margin.
• If used, the SSCC/GS1 barcode [which will then also be the Tracking NR displayed on the Delivery Note] is managed against the combination of
Site and Client and controlled using defined values for the front digit, Base ID, Range Start, Range Length and Last SSCC ID used. If a record
exists then the SSCC number will be used, if no record exists then the Container ID is used. The SSCC / GS1 barcode value is constructed as
follows - Application Identifier [(00) indicates a SSCC-18 structure to follow], Extension digit [no defined logic], GS1 Company Prefix [7-10 digits
Base ID value], Serial Number [6-9 digit reference assigned by the holder of the GS1 prefix to uniquely identify the logistics unit. Cannot be
reused for a minimum of 12 months. Combined length of the GS1 prefix and the Serial number is always 16 digits], Check digit [calculated
using modulo 10 algorithm]. Client specific SSCC values are able to be set based on a specific client data range see the Facility section for
more details.

CORE+
• Label format (6 inches by 4 inches / 101mm by 152mm in size):
Standard Container Shipping Label Container Shipping Label if generated at order allocation

CORE+
CEVA Standard Pallet Shipping label

Upon the drop off of a pallet in the ship dock, on demand during load preparation, or at the point of order allocation, the Pallet Shipping Label is
triggered to be printed. Please refer to the Load Preparation process step for an example label.
• Data related to the pallet and its contents

• Each label will include Client Name, Consignment, Carrier ID, Ship Dock, Carrier Service Level (If all order do not have the same then display
MULTI), Ship By Date [in the time zone of the Site] (if all orders do not have the same then display MULTI), Load sequence (if populated), Order
IDs (display up to 5 order IDs if more, then display MULTI), Order Name / Address / Town / County / Postcode / Country (if not all the same
then display MULTI in Name field and rest are left blank), Hub Name / Address / Town / County / Postcode / Country (if not all the same then
display MULTI in Name field and rest are left blank), Gross Weight for the pallet (including display of the weight Unit of Measure from the Site
record), Gross Volume for the pallet (including display of the volume Unit of Measure from the Site record), Hazardous flag (Y/N
C, Pallet ID, Environment produced from and

document version number will be displayed vertically in the document margin.

CORE+
• Label format (6 inches by 4 inches / 101mm by 152mm in size)

CORE+
CEVA Standard Delivery Note

Upon the drop off of the last pallet in the ship dock for an order, on demand during load preparation or at the point of order allocation the Delivery
Note is triggered to be printed. Please refer to the Load Preparation process step for an example Delivery Note.
• Dependent upon the

• value passed on the Order Header, the Field text will be displayed in the appropriate language. Available languages are English, French,
Italian, German, Slovak, Czech, Dutch, Danish, Spanish, Arabic, Swedish, Finnish, Norwegian, Polish & Portuguese.
• Data for the entire contents of the order which may be one or many containers and / or pallets.
provided.
• Document Date (in the time zone of the Site), Page x (of y),
Delivery Address, Delivery Postcode, Delivery Town, Delivery County, Delivery Country, Delivery Phone, Client Name, Site Address, Site Post
Code, Site Town, Site Country, Client ID, Order ID, Consignment ID number and Barcode, Terms of Delivery, Carrier, Carrier Service Level,
Purchase Order Number, Deliver By date, Pallet count for Order, Container Count for Order, Item Quantity count for Order, Lines count for the
order, Total Volume of the order (including volume unit of measure from the Site record; displayed to three decimal places), Gross weight
(including weight unit of measure from the Site record; displayed to two decimal places), Nett Weight (including weight unit of measure from
the Site record; displayed to two decimal places).
• Pallet ID, Pallet Tracking ID, Container ID, Container Dimensions (from
the corresponding pallet record set up for the container if pallet type is VARICONT then the dimensions will be those captured during
repacking; dimensions displayed to three decimal places), Volume of the Container Gross Weight (including weight Unit of Measure as stored
on the Site Record; dimensions displayed to two decimal places)
container, Nett Weight (including weight Unit of Measure as stored on the Site record; dimensions displayed to three decimal places), total
Carton quantity of items.
• - Order Line ID, Order Line Purchase Order Number,
SKU ID, Customer SKU ID, SKU Description, Quantity ordered on the line, Quantity shipped for the line, Host Order & Line ID (if provided),
Quantity within the container.
• Note that if generating the Delivery Note at the point of order allocation the entire order should fit on a single Pick List / Move Task List.
• The environment produced from and document version number will be displayed vertically in the document margin.
• Instructions (as provided on the Order Header) and also the time
zones that all dates / times are in.

CORE+
• CEVA Standard Delivery Note document format (A4 or US Letter CEVA Delivery Note Flexible Documents Option Pack
in size) Upon the drop off of the last pallet in the ship dock for an order, or on
0
1 1 1 1 1 1 1 1 1 1 2
demand during load preparation, the Delivery Note is triggered to be
0 1 2 1 3 4 52 6 7 3 8 9
04 1 2 5 3 4 5 6 6 7 7 8 9 0 8
printed.
2
9
2
8
<Client Logo> DELIVERY NOTE CEVA Logo A bespoke Delivery Note is available if utilizing the Flexible Document
710
2
Document Date: DD-Mmm-YYYY

<Site Address>
Page: XXX(XXX) Option Pack. Design templates are available in A4 and US Letter sizes,
Client ID XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
2
6
Shipment ID
Consignment
XXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXX and in both portrait or landscape orientation. The design templates
2
5
Barcode <Consignment> allow the building of the customized Delivery Note by selecting from
9
<Delivery Address>
2
4
Terms of Delivery: INCOTERM INCOTERM NAMED PLACE (If present)

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX the available data fields. Note, the available data fields are aligned with
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
the Standard Delivery Note. Please liaise with your WMS CoE
2
3
Carrier XXXXXXXXXXXXXXXXXXXX
Service Level: XXXXXXXXXXXXXXXXXXXX
Delivery Reference: XXXXXXXXXXXXXXXXXXXX
28
Implementation Consultant for further details.

2
Deliver By Date DD-Mmm-YYYY
Total Pallets: XXXXXXXXXXXXXXXXXXXX Total Lines: XXXXXXXX Gross Weight (kg): XXXXXXXXXXXXXXXXXXXX
2
1
Total Containers: XXXXXXXXXXXXXXXXXXXX Total (m3): XXXXXXXX Nett Weight(kg): XXXXXXXXXXXXXXXXXXXX

Total Qty Shipped: XXXXXXXXXXXXXXXXXXXX
Delivery Details:
2
0
Pallet ID: XXXXXXXXXXXXXXXXXXXX Container ID: XXXXXXXXXXXXXXXXXXXX

7
Pallet Tracking ID: XXXXXXXXXXXXXXXXXXXX Tracking NR: XXXXXXXXXXXXXXXXXXXX m3

Dimensions (m): XXXXXXXXXXXXXXXXXXXX GWT/NWT (kg)
1
9
Order ID Line: SKU: Description Ordered QTY Shipped QTY Container QTY
Customer SKU: PO Number:

1
8
Substitute SKU: Description Shipped QTY Container QTY
Customer SKU: PO Number: Host Order (& Line) ID:

1
6
7
1
6
1
5
Total Container QTY

5
1
4
1
3
1
42
1
1
1
03
9
8
27
6
5
4 1
3
Delivery Instructions:
0 2

1
0

CORE+
CEVA Standard Returns Note

Upon completion of packing during the Load Preparation phase for an order, the Returns Note is triggered to be printed for orders with the order type
eturns Note. The design of the Returns Note allows for the use of Pre-
printed stationary with a peel-
Returns Note the Order Interface is required to be used so to allow the passing of required information.
• 0 dpi and preferably in jpeg format] top left, top right and bottom right of the
document.
• Carrier ID, Service Level, the date printed, the Order ID, the Purchase Order from the Order header and an X of
Y page count.
• Invoice Name, Invoice Address line 1, Invoice Address line 2, Invoice Post Code, Invoice Town, Invoice
Country, Invoice VAT Number (all from the order header via the Order interface).
• ntaining Customer ID, Name, Address line 1, Address line 2, Postcode, Town and Country from the order
header.
• An Order Line section containing SKU ID, SKU Description, Quantity ordered on the Order Line and quantity picked / packed.
• A peel-able label section containing Order ID, Name, Address Line 1, Address Line 2, Postcode, Town, Country then a Return Address
(Special Instructions at the order level with a location qualifier of PRN-RETADR using values corresponding to Name1, Address1, Address2, City,
PostalCode, CountryName).
• A Return Instructions Text (Special Instructions with a location qualifier of PRN-RETTXT for the Order).
• Each documen - the time zones that all dates / times are in.

CORE+
• Document format (A4 or US Letter in size)

CORE+
CEVA Standard Commercial Invoice

Upon completion of packing during the Load Preparation phase for an order, the Commercial Invoice is triggered to be printed. Please refer to the
Load Preparation process step for an example Commercial Invoice. To use the Commercial Invoice the capture of
upon receipt must be set on every SKU; additionally the following interfaces must be used so to provide necessary information:
• SKU Interface to the WMS able to include a HTS (Harmonized Tariff Schedule for the United States) and ECCN (Export control Classification
Number).
• Pre-Advice Interface to the WMS able to include a Manufacturers Name, Address and Country for stamping on the inventory received.
•
Invoice Specific Instructions and various freight terms and values.
• The optional output of a Client logo top left and a CEVA logo top right [Minimum 300 dpi and preferably in jpeg format].
• Site Name, Site Address line 1, Site Address line 2, Site Town, Site County, Site Postcode and Site Country.
• Invoice reference from the Order Header, date of print, Order ID, Order reference from the Order Header,
Purchase Order from the Order Header and an X of Y page count.
• Client Name, Client Address line 1, Client Address line 2, Client Town, Client County, Client Post Code, Client
Country, Client VAT Number.
• - Special Instructions at the order level with a location qualifier of PRN-IORADR using values corresponding to
Name1, Address1, Address2, City, County, PostalCode, CountryName, VatId.
• Invoice Name, Invoice Address line 1, Invoice Address line 2, Invoice Town, Invoice County, Invoice
Country, Invoice VAT Number (all from the order header via the Order interface).
• Customer ID, Name, Address line 1, Address line 2, Town, County, Postcode, Country from the
order header.
• ing Carrier ID, Despatch method, Terms of delivery, Terms of delivery Place, Payment Terms, General LIC
Number [User_Def_Type_7], C.I. Special Instructions up to a max of 200 characters [User_Def_Note_1], Count of containers, Count of pallets,
Total Gross weight.
• Quantity Shipped, SKU ID, SKU description, HTS code for the SKU, ECCN code for the SKU, Origin, Product
Price from the order line, Value for the line determined by qty x product price.
• Total of all qty values, Freight Currency on the order header, Freight Cost from the order header, Freight Terms
from the Order Header, Freight Insurance from the Order Header, Other Fees from the Order Header, Invoice Currency from the Order Header,
a total of the all the values.

CORE+
• - the time zones that all dates / times are in.


CORE+
CEVA Standard Master Bill of Lading

One Master Bill of Lading will be produced per Consignment. A consignment will contain many Shipments and a Shipment can consist of one or many
orders for the same site/client, tied together as a Consignment by the same unique value in the OrderHeader.Consignment field.
The output(s) for the Master Bill of Lading document will be triggered per consignment upon completion of packing of the last container for the
consignment. This will be via Inventory_Transaction_Code_Report.
To populate the Master Bill of Lading with the required data the following interfaces must be used to provide the necessary information:
• Order Interface to the WMS able to include Bill of lading number.
• Data for the entire contents of the consignment.

• A statement on document GS1 compliance.
• Site Name, Site Address line 1, Site Address line 2, Site City, Site State, Site Zip Code, FOB check box -
• not populated on Master Bill of Lading.

• - not populated on Master Bill of Lading.
• Bill of Lading Number section containing a Bill of Lading number (unique value for entire consignment) in text and barcode format (GS128
standard).
• Carrier Name Displays carrier name where Carrier_ID and Service level match. If all order headers for every shipment on the consignment do
• Trailer Number only to be used if consignment is full truckload, will be hand written on if used.
• Seal Number and SCAC
r header for every shipment for the consignment. If there are variations
in service level, but all carrier IDs match then SCAC value will be displayed if they match for every order within the shipment. If there are
variations in the carrier ID between orde
• Pro Number Not populated on Master Bill of Lading
• Special instructions section containing list of Bill of Lading numbers tied to this Master Bill of Lading.
• Freight Charge Terms Three options, rd
rd
Note if orders within the same
shipment have differing values then no check box will be selected.
• Check box indicating if the document is Master Bill of Lading or not (will be unchecked for Bill of Lading).
•

CORE+
• Not populated on Master bill of Lading.

• - Not populated on Master bill of Lading.
• COD section - Not populated on Master bill of Lading.
• Liability statement containing GS1 standard statement on liability of carrier and carrier charges, signature box for acknowledgement of
statement.
• Signature/Date section containing
lations.

CORE+

CORE+
CEVA Standard Bill of Lading

One Bill of Lading will be produced per Shipment and a Shipment can consist of one or many orders, tied together as a Shipment by the same value in
the OrderHeader.Shipment_Group field. If the number of orders within the shipment exceeds the amount that one Bill of Lading document can
display, a Supplement to the Bill of Lading Document will be produced.
The output(s) for the Bill of Lading document will be triggered per consignment upon completion of packing of the last container for the consignment.
This will be via Inventory_Transaction_Code_Report.
To populate the Bill of Lading with the required data the following interfaces must be used to provide the necessary information:
• SKU Interface to the WMS must include commodity code (for correct grouping of SKUs on carrier info section).
• Order Interface to the WMS able to include Terms of Delivery, Bill of Lading of number, Pro number, bill to address.
• Data for the entire contents of the shipment which may be one or many orders.
• A statement on document GS1 compliance.
• Site Name, Site Address line 1, Site Address line 2, Site City, Site State, Site Zip Code, FOB check box -
• section containing Site Name, Location number (the location number assigned to the ship to address by the consignee), Site
Address line 1, Site Address line 2, Site City, Site State, Site Zip Code. FOB check box - where the ORDER_HEADER field TOD contains data
• Site Name, Site Address line 1, Site Address line 2, Site City, Site State, Site
Zip Code. This section will only be populated if the Freight Charge Terms = 3rd Party (taken from order interface, order.specialinstructions type
PRN-INVFRT).
• Bill of Lading Number section containing a Bill of Lading number (taken from interface = shipment_item_id) in text and barcode format (GS128
standard).
• Carrier Name Displays carrier name where Carrier_ID and Service level match. If all order headers for this shipment do not contain the same
• Trailer Number only to be used if shipment is full truckload, will be hand written on if used.
• Seal Number and SCAC
header for the shipment. If there are variations in service level, but all
carrier IDs match then SCAC value will be displayed if they match for every order within the shipment. If there are variations in the carrier ID
between orders on a single shipment
• Pro Number ber
barcode will be displayed in GS1-128 format.

CORE+
• Special instructions section containing - if there are any variances between the
• Freight Charge Terms Three options paid (If the

box will be checked), 3rd
rd
party (If Note if orders within
the same shipment have differing values then no check box will be selected.
• Check box indicating if the document is Master Bill of Lading or not (will be unchecked for Bill of Lading).
• Customer Order number, number of packages (containers), weight,
Pallet/slip selection (Y/N, this will be manually
order_header), grand total section summarising total number of packages of shipment, total weight of shipment. Note if there are more than
5 orders on a shipment none of the orders will be displayed, but will appear on the Bill of Lading Supplement. There will be one line on the
•
of the same commodity code handling unit quantity and type, package quantity and type, weight, HM (if commodity is hazardous this field will
be marked with X) , comm
(requires SKU.nmfc_number to be populated) (requires SKU.Commodity_code to be populated). Note if there are more than 5
orders on a sh ne line
• GS1 standard statement on total value of goods.

• COD (cash on delivery?) section containing
'Collect', th cked). Note if
COD_type value does not match on every order, this field will be blank).
• Liability statement containing GS1 standard statement on liability of carrier and carrier charges, signature box for acknowledgement of
statement.
• Signature/Date section containing

CORE+

CORE+
CEVA Standard Bill of Lading Supplement

One or many Bill of Lading Supplements will be produced where the total number of orders on a shipment exceeds five.
The document will display:
• Bill of Lading number this value will equal the Bill of Lading • Document format (A4 or US Letter in size)
number this supplement appends.
• Page count o
appends.
•
containing (line per order) Customer Order number, number of
packages (containers), weight, Pallet/slip selection (Y/N, this will
be manually circled by operation), additional shipper info (display
section summarising total number of packages of shipment, total

weight of shipment.
•
for groups of the same commodity code handling unit quantity

and type, package quantity and type, weight, HM (if commodity is
hazardous this field will be marked with X) , commodity
description (requires SKU.Commodity.description to be

CORE+
CEVA Standard Load Manifest

When vehicle departure is about to occur, the load manifest is produced (manually triggered user report). Please refer to the Vehicle Despatch process
step for an example document.
• Data for the entire contents of the Trailer

• The Load Manifest is produced per specified Trailer ID and contains Trailer ID, Total Weight of load, Total Volume of the Load and the Printed
Date & Time (in the time zone of the Site). Then for each pallet loaded (in load sequence) it states the Client, the Consignment, the order, the
Pallet ID , Pallet Weight, Pallet Volume and if hazardous. In the footer of the document it displays a Pallet count and also the time zones that all
dates / times are in. The environment produced from and document version number will be displayed vertically in the document margin.

CORE+
Reports Catalogue
The below reports exist within the Matrix WMS CORE+ application. For reporting capability outside of the WMS application please refer to the Facility
section for details on Flexible Reporting.
Inbound Related Reports Outbound Related Reports Inventory Management Related Reports
• ASN Summary* • Completed Orders* • ABC Dynamic Pick Face Mismatch

• Completed ASNs* • Detailed Order Receipt to Shipped • ABC Inventory Location Mismatch
• Completed Pre-Advices* Performance* • ABC Putaway Algorithm Mismatch
• Customs Document Reference Details • Kitting Activity • ABC SKU Ranking
• Detailed Receipt to Putaway • Outbound Consignment Planning • Adjustments*
Performance* • Outbound Order Performance • Clear Floor Check
• Inbound Workload Planning* • Outbound Workload Planning* • Consolidated Transactions*
• Open Putaway Tasks • Packing Activity* • Cross Dock Pallets
• Pre-Advice Summary • Pick Face Throughput • Daily Inventory Recording for Billing
• Putaway Activity* • Picked Quantity Summary • Expiring Inventory
• Receipt Activity* • Picking Activity* • Inventory Age Analysis
• Receipt to Bin • Pre-Vehicle Load Check • Inventory Condition Code History
• Serial Numbers Shipped • Inventory Details*
Other Reports • Shipped Order Details • Inventory Summary
• Shipped Order Summary • Inventory Updates
• Dynamic Pick Face Details • Shipping Activity* • Number of Replens per SKU
• Management Dashboard • Shipping Contents • Slotting Tool
• Ready for Post Pick Activity Dashboard • Shorted Orders Overview • Stock Check Details*
• Site Activity by Hour • Tracking References* • Stock Check Summary
• TMS Planning Dashboard • Trailer Shipping Notification • Warehouse Occupancy*
• Updates from TMS to WMS • Weekly Stock Summary
*Reports available in CSV format.
The CSV file will be emailed as an attachment to the specified email address.
If the CSV file is bigger than 10 Mb the attachment will be zipped.
When a zipped attachment is bigger than 10 Mb it will not be emailed. Contact Support for retrieval of the file.
Note that the date format within the CSV file will be presented as DD-MMM-YY.
include data from the Live and Archive tables.
For reporting purposes serialization is restricted to single record entries for consistent results.

CORE+
Operational Documents  Reports Catalogue
Inbound - ASN Summary

The ASN Summary (By Date Range) report is a historical report to show inbound activity related to ASNs.
This report is available in CSV format only.
Selection criteria for the report:

Criteria Mandatory (Y/N)? Description / Comment
Site Y Each operator will be assigned to a single site ID which will be defaulted in.
Client Y If an operator has access to more than one client they will be required to select one; otherwise the client the operators
login is tied to will be defaulted in.
From Date Y The earliest date to use for data included in the report.
To Date Y The latest date to use for data included in the report.
Email Address Y The email address to send the CSV report to.
• One line per combination of Site, Client and date that matches the selection criteria entered.
• Each line will show data for Site ID, Client ID, Date, ASNs Completed, UPI Headers Received, UPI Lines Received, Tags Received (related to
ASNs)
• Report sortation is ascending by date.
Click here to view a sample REPORT output.

CORE+
Inbound - Completed ASNs

The ASN Summary (By Date Range) report is a historical report to show ASNs that were completed in the date range specified.
This report is available in CSV format only.

From Finish Date Y The earliest completion of receiving date to use for data included in the report.
To Finish Date Y The latest completion of receiving date to use for data included in the report.
From Receipt Date Y The earliest start receiving date to use for data included in the report.
To Receipt Date Y The latest start receiving date to use for data included in the report.
Email Address Y The email address to send the CSV report to.
• One record per ASN that matches the selection criteria entered.
• Each line will show data for Site ID, Client ID, ASN ID, Status, Inventory Owner, Freight Container ID, Due Date, Due Time, Receipt Date,
Receipt Time, Finish Date, Finish Time, Created By, Creation Date, Creation Time, Number of UPIs, Number of UPI Lines, Returns Flag, Customs
Consignment Number, Customs Invoice Number, Putaway Date, Putaway Time.
• Report sortation is ascending by finish date and time.
Click here to view a sample REPORT output.

CORE+
Inbound - Completed Pre-Advices

The Completed Pre-Advices (By Date Range) report is a historical report to show Pre-Advice receipt and putaway completion.
Note that one pairing of either the finish from / to or the Receipt from / to selection criteria must be entered.
There are two versions of this report available:
• REPORT Completed Pre-Advices by Date Range - to print direct to a printer or view and print from screen.
• CSV REPORT - Completed Pre-Advices by Date Range - to generate and receive a CSV file via email.

From Finish Date N The earliest completion of receiving date to use for data included in the report.
To Finish Date N The latest completion of receiving date to use for data included in the report.
From Receipt Date N The earliest date to use for data included in the report.
To Receipt N The latest date to use for data included in the report.
Date
Email Address Y If the CSV report type has been selected, an email address must be entered.
• One line per Pre-Advice

• Each line will show data for Site ID, Client ID, Pre-Advice ID, Status, Inventory Owner, Freight Container ID, Due Date, Due Time, Receipt Date,
Receipt Time, Finish Date, Finish Time, Created By, Creation Date, Creation Time, Number of Lines, Returns Flag, Customs Consignment
Number, Customs Invoice Number, Putaway date, Putaway Time, Pre-Advice Type (CSV only).
• Report sortation is ascending by Finish date and time.
• A report summary is shown, displaying a total for each column
Click here to view a sample REPORT output (the report is designed for print to screen, then direct print or extract for use if needed).

CORE+
Inbound - Customs Document Reference Details

The Customs Document Reference Details report shows a summary of customs related information to support local compliance requirements.

From Receipt Date N The earliest receipt date to use for data included in the report.
To Receipt Date N The latest receipt date to use for data included in the report.
Import Document ID N If populated, then only show records with the specified Import Document ID
Pre-Advice ID N If populated, then only show records with the specified Pre-Advice ID
From Shipped Date N The earliest shipped date to use for data included in the report.
To Shipped Date N The latest shipped date to use for data included in the report.
Export Document ID N If populated, then only show records with the specified Export Document ID
Order N If populated, then only show records with the specified Order ID
SKU N If populated, then only show records with the specified SKU
• One record per (grouped) match, that matches the selection criteria entered, shown in the following data:
• Site ID, Client ID, SKU, SKU Description, Commodity Code, Sum ( Inbound QTY ), Inbound Gross Weight (SKU * QTY), Import Document ID,
Import Document Issue Date, Pre-Advice ID, Receipt Date, Sum ( Export QTY ), Export Gross Weight (SKU * QTY), Export Document ID, Export
Document Issue Date, Order ID, Shipped Date
• Records will be grouped by Export Document ID, Import Document ID, SKU
• Sorted by Shipped Date (new to old), Receipt Date (new to old)
Click here to view a sample REPORT output (the report is designed for print to screen, then direct print if needed).

CORE+
Inbound - Detailed Receipt to Putaway Performance

The Detailed Receipt to Putaway Performance (By Date Range) Report is a historical report that shows detailed information about what has been
received and putaway which may be useful for invoicing / KPI purposes.
• REPORT - Detailed Receipt to Putaway Performance by Date Range - to print direct to a printer or view and print from screen.
• CSV REPORT - Detailed Receipt to Putaway Performance by Date Range - to generate and receive a CSV file via email.

Include Y Whether to include data from the Archive Tables (data older than 35 days).
Archive
Tables
• One line per TAG putaway

• Each line will show data for Site ID, Client ID, TAG, SKU, SKU Description, Released Date, Released Time, Received Date, Received Time,
Putaway Date, Putaway Time, Qty, Location, Condition Code, Lock Code, QC Status, User, Pallet Type, Pallet Config, Line, Reference, Elapsed
Receipt to Putaway Time, Elapsed Released to Putaway time, Allocation Attribute 1, Allocation Attribute 3, Allocation Attribute 3, Client
Reference 1, Client Reference 2, Target Stock Date, Target Stock Time, Arrival Stock Date, Arrival Stock Time.

CORE+
Inbound - Inbound Workload Planning

The Inbound Workload Planning (By Date Range) report shows details of identified Pre-Advices to allow for operational assessment of effort and
activities required upon its arrival at the warehouse.
• REPORT - Inbound Workload Planning by Date Range - to print direct to a printer or view and print from screen.
• CSV REPORT - Inbound Workload Planning by Date Range - to generate and receive a CSV file via email.

Pre-Advice ID N State a specific Pre-Advice ID to only show data for the identified Pre-Advice
ASN ID N State a specific ASN ID to only show data for the identified ASN (ASN related information available in CSV version only)
• One line per Pre-Advice / ASN

• Each line will show data for Site ID, Client ID, Pre-Advice ID or ASN ID, Host ID, Freight Container ID, Status, Returns Flag, Inventory Owner,
Due Date, Due Time, Receipt Date, Receipt Time, Creation date, Creation Time, Number of UPIs (ASN only), Number of Pre-Advice / UPI Lines,
Customs Consignment Number, Customs Invoice Number, Line Number, Host Line ID, SKU, SKU Description, Quantity Due, Quantity Received
so far, Under Bond Flag, Product Group, Expiry Date required?, Expiry Date, Batch, Hazmat Code, New Product Flag, QC Status, Customs and
Excise Flag, Serial Number Capture Required, Pack Configuration Tracking level 1, Ratio of tracking level 1 to 2, Pack Configuration Tracking
level 2, Ratio of tracking level 2 to 3, Pack Configuration Tracking level 3, Ratio of tracking level 3 to 4, Pack Configuration Tracking level 4, High
Risk SKU (CSV only), External Testing Results (CSV only), Import Document ID, Import Document Issue Date, Manufacture Date (CSV only),
Allocation Attribute 3 (CSV only).
• Note that ASN related information will appear in the CSV version only.

CORE+
Inbound - Open Putaway Tasks

The Open Putaway Tasks (By Pre-Advice) report shows details of open putaways to allow for operational review of outstanding inbound tasks.
• REPORT - Open Putaway Tasks By Pre-Advice - to print direct to a printer or view and print from screen.
• CSV REPORT - Open Putaway Tasks By Pre-Advice - to generate and receive a CSV file via email.

Pre-Advice ID N If populated, then only show open Putaway tasks for the stated pre-advice; else show for all Pre-Advices.
Due Date N If populated, then only show open putaway tasks for Pre-advice Headers that have a matching Due Date.
Older Than N If populated, only
Hours value entered.
• One line per putaway task

• Each line will show data for Site ID, Client ID, TAG ID, Pallet ID, Pallet Type, Mixed? Y/N, Grouped? Y/N, Pre-Advice ID, Pre-Advice Receipt
Date, Pre-Advice Due Date, Current Location, To Zone, To Subzone, To Location, Above Ground?, Owner, Hazmat ID, Condition, Bonded
Status, Age of Task.
• Grouped by Pre-Advice ID, then by TAG ID within Pre-Advice ID,
• Sorted by oldest to youngest Pre-Advice Due Date

CORE+
Inbound - Pre-Advice Summary

The Pre-Advice Summary (By Date Range) report is a historical report to show inbound activity.

• One line per combination of Site / Client / Date.

• Each line will show site and client ID, plus data for counts of Pre-advices completed, lines received and tags received, split by client.
A report summary is shown, displaying a total for each column.

CORE+
Inbound - Putaway Activity

The Putaway Activity (By Date Range) report is a historical report to show details of the putaway tasks performed. Please note that this does not
include any associated receipt activity.
• REPORT Putaway Activity by Date Range - to print direct to a printer or view and print from screen.
• CSV REPORT Putaway Activity by Date Range - to generate and receive a CSV file via email.

Client Y If an operator has access to more than one client they will be required to select one; otherwise the client the
operators login is tied to will be defaulted in.
• One line per putaway task, report sortation is ascending by date and time.
• Each line will show data for Site ID, Client ID, Transaction Code, Tag ID, SKU, SKU Description, Pre-Advice (Putaway relates to), Line ID,
Quantity, Transaction Date, Transaction Time, Inventory Condition, Inventory Lock Code, QC Status, Batch, Expiry Date, User, Pallet Type, Pack
Config, Customs Consignment, Customs Invoice, Under Bond flag, Product group, Size, Each Height, Each Width, Each Depth, Each Weight,
Customs Commodity Code, Nett Weight, Nett Volume, Hazardous Class, Tracking Level 1, Ratio of 1 >2, Tracking Level 2, Ratio 2>3, Tracking
Level 3, Ration 3>4, Tracking level 4, Import Document ID (CSV Only), Import Document Issue Date (CSV Only), Manufacture Date (CSV only),
Allocation Attribute 3 (CSV only).
Field Details: • Line ID is the pre-advice line ID the receipt relates to.
• Transaction Date is the date the activity was performed.
From the Inventory transaction record -
• Transaction Time is the time the activity was performed.
• • Update QTY is the amount of inventory received for that line.
• SKU is the SKU ID. • Condition is the condition of the inventory (blank is pristine)
• Tag ID is the Tag received against. • Lock Code is any lock code assigned to the inventory.
• SKU Description is the Description stored against the SKU • QC Status is the QC status of the inventory
• Reference displays the unique pre-advice number provided in • Batch is the batch captured if applicable.
the Pre-Advice interface; if the pre-advice was generated by the • Expiry Date is the expiry date captured if applicable.
Portal then it would be a CEVA generated number. • User ID is the operator account that performed the activity.
CORE+
• Pallet Type is the pallet type used for the receipt. From the Pack Configuration record (for the SKU) -
• Pack Config is the pack configuration used.
• Tracking level 1 The lowest tracking level for the SKU which
• C&E Consignment ID associated to the inventory.
will typically be eaches (EA).
• C&E Invoice Number associated to the inventory
• Ratio 1 to 2 The quantity of the lowest tracking level that are
• Under Bond status for the inventory. able to be stored in the 2nd tracking level.
From the SKU record - • Tracking Level 2 The second lowest tracking level for the SKU.
If the SKU only has two tracking levels then this will be pallet
• Product Group displays the product group stored for the SKU (PL), otherwise it might me cases (CA) or packs (PK)
• Each Height a single SKUs height in Meters • Ratio 2 to 3 The quantity of the 2nd tracking level that are able
• Each Width a single SKUs width in Meters to be stored in the 3rd tracking level - if used.
• Each Depth a single SKUs depth in Meters • Tracking Level 3 The 3rd tracking level for the SKU if used.
• Each Weight a single SKUs weight in Kilograms • Ratio 3 to 4 The quantity of the 3rd tracking level that are able
• C&E Commodity Code for the SKU. to be stored in the 4th tracking level - if used.
• Nett Weight the nett weight of the single SKU if provided • Tracking Level 4 The 4th tracking level for the SKU if used.
• Nett Volume the nett volume of the single SKU if provided
Note - If the SKU has multiple pack configurations associated it will
• SKU Hazardous Class the hazardous class of the SKU if
applicable.

CORE+
Inbound - Receipt Activity

The Receipt Activity (By Date Range) report is a historical report to show details of the receipt tasks performed. Please note that this does not include
any associated putaway activity.
• REPORT Receipt Activity by Date Range - to print direct to a printer or view and print from screen.
• CSV REPORT Receipt Activity by Date Range - to generate and receive a CSV file via email.

Client Y If an operator has access to more than one client they will be required to select one to view records for a specific
client, or leave blank to view records for all clients; otherwise the client the operators login is tied to will be
defaulted in.
Owner N If a value is entered then only receipt tasks that involve the Owner ID entered shall be returned; if left blank then no
owner ID selection / restriction is made.
Include Serials N Selecting this will display serial numbers on the report (if known)
• One line per receipt task (within the selection criteria), showing the following data:
• Each line will show data for Site ID, Client ID, Transaction Code, ASN (CSV only) / Pre-Advice Number, Line Number, Tag ID, SKU, SKU
Description, Quantity, Transaction Date, Transaction Time, User ID, Pallet Type, Pack Configuration, Expiry Date, Condition Code, Lock Code,
Batch Code, QC Status, Customs Consignment Number, Customs Commodity Code, Customs Invoice Number, Customs Under Bond Flag,
Product group, Each Width, Each Depth, Each Height, Each weight, Nett Weight, Nett Volume, Hazardous Code, Serial reference (if selected in
search criteria), Import Document ID, Import Document Issue Date, Manufacture Date (CSV only), Allocation Attribute 3 (CSV only), Pallet ID
(CSV only), Owner ID (CSV only).
• Note that ASN related information will appear in the CSV version only.

CORE+
Field Details
From the Inventory transaction record - From the SKU record -

•
• ASN / Pre-Advice displays the unique pre-advice number • C&E Commodity Code for the SKU.
provided in the Pre-Advice interface or unique ASN in the ASN • Product Group displays the product group stored for the SKU
interface; if the pre-advice was generated by the Portal then it • Each Height a single SKUs height in Meters
would be a CEVA generated number. • Each Width a single SKUs width in Meters
• UPI / Line No. is the pre-advice line ID the receipt relates to; or • Each Depth a single SKUs depth in Meters
the UPI and UPI Line ID the receipt relates to • Each Weight a single SKUs weight in Kilograms
• ASN Pallet ID is the unique identifier for the handling unit, if • Nett Weight the nett weight of the single SKU if provided
provided, on an ASN. • Nett Volume the nett volume of the single SKU if provided
• Tag ID is the Tag received against. • SKU Hazardous Class the hazardous class of the SKU if
• SKU is the SKU ID. applicable
• SKU Description is the Description stored against the SKU
• QTY is the amount of inventory received for that line.
• Transaction Date is the date the activity was performed.
• Transaction Time is the time the activity was performed.
• User ID is the login of the operator that performed the receipt.
• Pallet Type is the pallet type used for the receipt.
• Pack Config is the pack configuration used.
• Expiry Date is the expiry date captured if applicable.
• Condition Code is the condition of the inventory (blank is
pristine)
• Lock Code is any lock code assigned to the inventory.
• Batch is the batch captured if applicable.
• QC Status is the QC status of the inventory
• C&E Consignment ID associated to the inventory.
• C&E Invoice Number associated to the inventory
• Under Bond status for the inventory.
• Owner ID for the TAG of inventory (if one is present).

CORE+
Inbound - Receipt to Bin

The Receipt to Bin (By Date Range) report shows putaway performance for the date range selected

Client Y If an operator has access to more than one client they will be required to select one; otherwise the client the operators login
is tied to will be defaulted in.
Threshold Y Will include only TAGs greater than the value entered in the report
• One line per combination of Site / Client / Date.

• Each line will show the site and client ID, plus data for a count of TAGs, the minimum time taken, the average time taken, and the maximum
time taken.
• A second section detailing each TAG that is over the stated threshold with its time taken.

CORE+
Outbound - Completed Orders

The Completed Orders (By Date Range) report is a historical report to show orders that were shipped within the selected date range.
• REPORT Completed Orders by Date Range - to print direct to a printer or view and print from screen.
• CSV REPORT Completed Orders by Date Range - to generate and receive a CSV file via email.

• One line per order

• Each line will show data for Site ID, Client ID, Status, Order ID, Number of Lines, Order Type, Owner, Consignment ID, Shipment group, Terms
of Delivery, Created by, Creation Date, Creation Time, Ship By Date, Ship By Time, Shipped Date, Shipped Time, Deliver By Date, Deliver By
Time, Drop Point, Carrier, Service Level, Customer ID, Postal Code, Country, Pallet Weight, Pallet Volume, Container Weight, Number of
Pallets.
• Report sortation is ascending by date and time shipped.

CORE+
Outbound - Detailed Order Receipt to Shipped Performance

The Detailed Order Receipt to Shipped Performance (By Date Range) Report is a historical report that shows detailed information about what has been
shipped which may be useful for invoicing / KPI purposes.
• REPORT Detailed Order Receipt to Shipped Performance by Date Range - to print direct to a printer or view and print from screen.
• CSV REPORT Detailed Order Receipt to Shipped Performance by Date Range - to generate and receive a CSV file via email.

Include Prev N
Shipped Lines status during the date range specified
• One line per order line shipped, sortation is ascending by date and time shipped.
• Each line will show data for Site ID, Client ID, Owner, Order Type, WMS Order ID, Customer Order ID, Number of Order Lines, Order
Reference, Carrier, Service Level, Consignment ID, Shipment Group, Terms of Delivery, Creation Date, Creation Time, Ship By date, Ship By
Time, Shipped Date, Shipped Time, Deliver By date, Deliver By Time, Elapsed Time, Created By, Customer ID, Customer Name, Postal Code,
Country, Delivery Point, WMS Line ID, Customer Line ID, SKU, Description, Product Group, Size, Customs Commodity Code, Hazardous Class,
Quantity Ordered, Ordered Tracking Level, Tracking Level 1, Ration 1>2, Tracking Level 2, Ratio 2>3, Tracking Level 3, Ratio 3>4, Tracking
Level 4, Quantity Shipped, Allocation Attribute 1, Allocation Attribute 2, Allocation Attribute 3, Client Ref 1, Client Ref 2, Import Document ID
(CSV only), Import document Issue Date (CSV Only), Export Document ID (CSV only), Export document Issue Date (CSV only), Manufacture Date
(CSV only).
Click here to view a sample REPORT output (the report is designed for print to screen, then extract for use).

CORE+
Outbound - Kitting Activity

If using the Kit to Order or Kit to Stock Option Packs, the Kitting Activity Report is used to show details of all kitting and unkitting activity completed
within the specified timeframe.

To Time Y The latest time to use for data included in the report.
• One line per transaction.

• Each line will show data for Site ID, Client ID, Task Type, Kit SKU ID, Kit SKU Description, Batch ID, Expiry, Reference (Order Number), Original
Qty and Update Qty.

CORE+
Outbound - Outbound Consignment Planning

The Outbound Consignment Planning (By Date Range) report is used to show expected consignments of order that are due to be shipped.

To Time Y The latest time to use for data included in the report.

• Each line will show data for Site ID, Client ID, Consignment ID, Carrier, Service level, Order ID, Order Type, Order Status, Number of Lines,
Creation Date, Creation Time, Ship By Date, Ship By Time, Deliver By Date, Deliver By Time, Customer ID, Customer Name, Customer Address
1, Customer Address 2, Customer Town, Customer County, Customer Postcode, Customer Country, Drop Point, Hub ID, Hub Name, Hub
Address 1, Hub Address 2, Hub Town, Hub County, Hub Postcode, Hub Country, Terms of Delivery, Contains Hazmat, Order Volume, Order
Weight.

CORE+
Outbound - Outbound Order Performance

-
report.

Criteria Mandatory Description / Comment
(Y/N)?
Client Y If an operator has access to more than one client they will be required to select one; otherwise the client the operators login is tied
to will be defaulted in.
Mode Y Choose between running a Detailed or Non-Detailed report.
Order N To view details for an individual order.
The report will display one line per transaction and each line will show:
Detailed Report:
• Order ID • Line ID • Expiry Date

• Host Order ID • Purchase Order Line ID • Picked to Container ID
• Purchase Order ID • Host Order Line ID • Picked to Container Type
• Customer ID • Order Qty • Picked to Pallet ID
• Customer Name • SKU • Picked to Pallet Type
• Delivery Postcode • SKU Description • Packed (Date and Time)
• Delivery County • Allocated (Date and Time) • Packing Activity Zone
• Delivery Country • Allocated Qty • Packed Qty
• Order Type • Allocation Location • Packed to Container ID
• Order Created (Date and Time) • Allocation Work Zone • Packed to Container Type
• Ship By (Date and Time) • Picked (Date and Time) • Ready to Load (Date and Time)
• Deliver by Date • Picked Qty • Loaded (Date and Time)
• Consignment • Pack Config • Trailer ID
• Shipment Group • Tracking Level • Shipped (Date and Time)
• Batch ID

CORE+
Non-Detailed Report:
• Order ID • Order Created (Date and Time) • Ready to Load (Date and Time)
• Host Order ID • Order Ship By (Date and Time) • Earliest Load Task (Date and Time)
• Purchase Order ID • Deliver by Date • Latest Load Task (Date and Time)
• Customer ID • Allocated (Date and Time) • Earliest Ship Task (Date and Time)
• Customer Name • Earliest Pick Task (Date and Time) • Latest Ship Task (Date and Time)
• Delivery Postcode • Latest Pick Task (Date and Time) • Order Qty
• Delivery County • Earliest Pack Task (Date and Time) • Shipped Qty
• Delivery Country • Latest Pack Task (Date and Time) • Shipped Nett Weight
• Order Type • Packed Container Qty • Shipped Gross Weight
Sample Outputs:
Click here to view a sample Detailed REPORT output (the report is designed for print to screen, then direct print if needed).
Click here to view a sample Non-Detailed REPORT output (the report is designed for print to screen, then direct print if needed).

CORE+
Outbound - Outbound Workload Planning

The Outbound Workload Planning (By Date Range) report shows details of identified Orders to allow for operational assessment of effort and activities
required.
• REPORT - Outbound Workload Planning by Date Range - to print direct to a printer or view and print from screen.
• CSV REPORT Outbound Workload Planning by Date Range - to generate and receive a CSV file via email.

Order N State a specific order ID to only show data for the identified order.
• One line per Order Line.

• Each line will show data for Site ID, Client ID, Consignment, Order ID, Ship by Date, Ship by Time, Delivery Date, Line ID, Special Instructions,
SKU, SKU Description, Putaway Group, Qty Ordered, QTY Tasked, Order Creation Date & Time, Each Weight, Expected Weight, Each Volume,
Expected Volume, Pack Config, Tag Volume, Eaches Per Layer, Layer Height, Pack Configuration Tracking level 1, Ratio of tracking level 1 to 2,
Pack Configuration Tracking level 2, Ratio of tracking level 2 to 3, Pack Configuration Tracking level 3, Ratio of tracking level 3 to 4, Pack
Configuration Tracking level 4, Condition Code, HazMat Class, Allocation Attribute 2 (CSV only).

CORE+
Outbound - Packing Activity

The Packing Activity (By Date Range) Report is a historical report to show details of the orders that have packed.
• REPORT Packing Activity by Date Range - to print direct to a printer or view and print from screen.
• CSV REPORT Packing Activity by Date Range - to generate and receive a CSV file via email.

• One line per pack task performed

• Each line will show data for Site ID, Client ID, Transaction Code, Tag ID, SKU, SKU Description, Order ID, Line ID, Host Order ID, Host Line ID,
Number of Lines, Quantity, Transaction Date, Transaction Time, Condition Code, QC Status, Notes, Container ID, Pallet ID, User ID, Batch,
Expiry Date, Pallet Type, Customs Under Bond Flag, Customs Commodity Code, Product Group, Each Width, Each Depth, Each Height, Each
Weight, Nett Weight, Nett volume, Hazardous Class, Order Type, Creation Date, Creation Time, Shipped Date, Shipped Time, Country, Special
Instructions, Manufacture Date (CSV only), Allocation Attribute 3 (CSV only).
• Report sortation is ascending by date and time.
Field Details • Number of Lines

• Quantity packed
• Code shows the transaction record code which will all be
• Transaction Date of the pack activity
• Transaction Time of the pack activity
• Tag ID for the goods
• Condition code on the inventory
• SKU ID for the goods packed
• QC status of the inventory when packed
• SKU Description for the goods packed
• Notes
• Order ID of the goods packed
• Container ID the inventory was packed into
• Line ID of the goods packed
• Pallet ID the inventory was packed onto
• Host Order ID
• User ID is the operator who packed the goods
• Host Line ID
CORE+
• Batch is the batch reference associated with inventory • Nett Weight for the SKU
• Expiry Date is the expiry date associated with the inventory • Nett Volume for the SKU
• Pallet Type is the type of pallet the goods were packed onto • Hazardous Class for the SKU
• Customs Under Bond is the bonded status of the goods • Order Type on the Order Header for the goods packed
• Customs Commodity code for the SKU • Creation date of the related Order
• Product Group for the SKU • Creation Time of the related Order
• Each Height from the SKU record • Shipped date of the related order
• Each Width from the SKU record • Shipped Time of the related order
• Each Depth from the SKU record • Country of delivery as stated on the Order
• Each Weight from the SKU record • Text in the special instructions for the order
• C&E Commodity is the customs commodity code for the SKU
Click here to view a sample REPORT output (the report is designed for print to screen, then either direct print or extract for use if needed).

CORE+
Outbound - Pick Face Throughput

The Pick Face Throughput report is used to provide visibility of the speed at which product is moving through pick faces.

Site Y If an operator has access to more than one site they will be required to select one; otherwise the site the operators
Client N Visible if an operator has access to more than one client. Select the required client, or leave blank to view details for
all clients.
• One line per pick face

• Each line will show data for Site ID, Client ID, SKU ID, SKU Description, Location ID (pick face), Quantity picked, Number of picks, Location
Classification, Location Zone, Subzone, Pick Sequence.

CORE+
Outbound - Picked Quantity Summary

The Picked Quantity Summary (By Date Range) report is used to show a summary of what has been picked.

Site Y If an operator has access to more than one site they will be required to select one; otherwise the site the operators
• One line per combination of Site / Client / SKU

• Each line will show data for Site ID, Client ID, SKU ID, SKU Description, Quantity Picked, Number of Pick Tasks, Pick face location for the SKU,
Pick Face Zone, Pick Face Subzone 1, Putaway group, From Date, To Date, XDC? (Cross Dock).

CORE+
Outbound - Picking Activity

The Picking Activity (By Date Range) Report is a historical report to show details of the orders that have picked.
• REPORT Picking Activity by Date Range - to print direct to a printer or view and print from screen.
• CSV REPORT Picking Activity by Date Range - to generate and receive a CSV file via email.

Above N
Ground Level
selected then all picks are shown
• One line per pick task performed

• Each line will show data for Site ID, Client ID, Transaction Code, SKU, Tag ID, SKU Description, Inventory Condition, Order Number, Quantity
Picked, Line ID, Transaction Date, Transaction Time, QC Status, Container ID, Pallet ID, User ID, Batch ID, Expiry, Pallet Type, Under Bond Flag,
Product Group, Each Height, Each Width, Each Depth, Each Weight, Customs Commodity Code, Nett Weight, Net Volume, Hazardous Class,
Current Pick Face, From Location, Above Ground Flag, Sub Zone, Location Zone, Manufacture Date (CSV only), Allocation Attribute 3 (CSV
only).
Field Details • Condition is the condition code on the inventory

• Reference is the Order ID
• Code shows the transaction record code which will all be
• Update Qty is the quantity picked
• Line is the line number on the order
• SKU is the SKU ID
• Date is the date shipped
• Tag is the Tag ID that the goods
• QC Status is the QC status of the inventory when picked
• Description is the SKU Description
• Container is the container ID the inventory was picked into
CORE+
• Pallet is the pallet ID the inventory was picked onto • Each Width from the SKU record
• User ID is the operator who picked the goods • Each Depth from the SKU record
• Batch is the batch reference associated with inventory • Each Weight from the SKU record
• Expiry is the expiry date associated with the inventory • C&E Commodity is the customs commodity code for the SKU
• Pallet Type is the type of pallet the goods were picked onto • Nett Weight
• Under Bond is the bonded status of the goods • Nett Vol
• Product Group for the SKU • Haz Class is the Hazardous class for the SKU
• Each Height from the SKU record
Click here to view a sample REPORT output (the report is designed for print to screen, then either direct print or extract for use if needed.

CORE+
Outbound - Pre-Vehicle Load Check

The Pre-Vehicle Load Check report provides a summary, per trailer, of the loaded pallets that had confirmed pre-vehicle load checks.

Trailer Y The trailer to use for data included in the report.
• One line per loaded pallet.

• Each line will show data for the Order ID, Consignment, Pallet ID, Pallet Type, Container ID, Container Type, Loading Date and Time, User that
completed the loading activity.

CORE+
Outbound - Serial Numbers Shipped

The Serial Numbers Shipped (By Date Range) report is a historical report to show details associated to the serial numbers that have been shipped.

Order N If populated, only serial numbers for the stated order number will be displayed
• One line per serial number

• Each line will show data for Site ID, Client ID, Serial Number, SKU, SKU Description, Order ID, Line ID, Shipped date, Owner ID, Consignment,
Order Type, Order Date, Seller Name, Terms of Delivery, Carrier, Service level, Customer ID, Country, Customer Order Number.

CORE+
Outbound - Shipped Order Details

The Shipped Order Details (By Date Range) Report is a historical report to show the identified details per order that has been shipped.


• Each line will show data for Site ID, Client ID, Order ID, the date shipped, the delivery address ID (within Standard WMS), the customer name,
the number of pallets, the Net weight in kilograms, the Gross weight in kilograms, the volume in cubic meters.

CORE+
Outbound - Shipped Order Summary

The Shipped Order Summary (By Date Range) Report is a historical report to show the orders that have been picked and shipped.

• One line per combination of Site ID / Client ID / Date

• Each line will show data for the count of orders picked, count of order lines picked, count of orders shipped and count of order lines shipped.

CORE+
Outbound - Shipping Activity

The Shipping Activity (By Date Range) Report is a historical report to show details of the orders that have shipped.
• REPORT Shipping Activity by Date Range - to print direct to a printer or view and print from screen.
• CSV REPORT Shipping Activity by Date Range - to generate and receive a CSV file via email.

Include Serials N Selecting Y will display serial numbers on the report (if known)
• One line per shipped order line

Each line will show data for:
• Code shows the transaction record code which will all be • Date is the date shipped
• Time is the time shipped
• SKU is the SKU ID • QC Status is the QC status of the inventory when shipped
• Tag is the Tag ID that the goods • Container is the container ID the inventory was shipped in
• Description is the SKU Description • Pallet is the pallet ID the inventory was shipped on
• Condition is the condition code on the inventory • Consignment is the consignment reference associated to the
• WMS reference is the Order ID order
• Purchase Order is the Customer Reference • User is the operator who shipped the goods
• Customer ID is the ID for the Customer • Batch is the batch reference associated with inventory
• Name is the Customer Name • C&E Consignment (Bonded Warehouse Option Pack)
• Update Qty is the quantity shipped • C&E Invoice (Bonded Warehouse Option Pack)
• Line is the line number on the order • Expiry is the expiry date associated with the inventory
CORE+
• Pallet Type is the type of pallet the goods were shipped on • Nett Vol
• Under Bond (Y / N) • Haz Class
• Product Group for the SKU • Host Order ID
• Each Height from the SKU record • Host Line ID
• Each Width from the SKU record • Purchase Order Line ID
• Each Depth from the SKU record • Shipment Group
• Each Weight from the SKU record • Import Document ID
• Commodity Code • Import Issue Date
• Plt Weight is from the shipping manifest • Export Document ID
• Plt Volume is from the shipping manifest • Export Issue Date
• Contr Weight is from the shipping manifest • Serial reference (if chosen in report selection)
• Contr Height is from the shipping manifest • Manufacture Date (CSV only)
• Contr Depth is from the shipping manifest • Allocation Attribute 3 (CSV only)
• Nett Weight
Click here to view a sample REPORT output (the report is designed for print to screen, then either direct print or extract for use if needed).

CORE+
Outbound - Shipping Contents

The Shipping Contents Report is a historical report to show details of the orders that have shipped on a specified trailer.

Trailer Y State the required trailer to show data for.
• Ship From, Ship Via and Ship To.

• Trailer Details Trailer ID, Total Containers, Total Pallets, Total Nett Weight (UOM), Total Gross Weight (UOM), Total Volume, Seal Number(s).
• Pallet Details Pallet ID, Consignment, Volume, Client ID, Shipment Group, Gross Weight, Nett Weight, No. of Containers.
• Order Details Order ID, Line ID, SKU Description, Nett Weight Client Order ID, Client Line ID, SKU, Qty Shipped, Qty @ Tracking Level 2, Qty
@ Tracking Level 3, HazMat, Gross Weight.

CORE+
Outbound - Shorted Orders Overview

The Shorted Orders Overview Report shows details of active short allocated or short picked orders where Ship in Full is set on the Order Header.

Order N State the required order to show data for.
Consignment N State the required consignment to show data for.
Ship Dock N State the required ship dock to show data for.
Status N State the required order status to show data for.

• er), Order Lines within
Order, Lines Short, Consignment, Ship Dock.

CORE+
Outbound - Tracking References

The Tracking References reports are used to show a related tracking references captured / provided.
There are various versions of this reports available:
Tracking References by Period use to report by date range. Also available as a CSV Report:

From Label Date N The earliest date to use for data included in the report.
To Label Date N The latest date to use for data included in the report.
Tracking References by Container / Pallet / SSCC / BOL use to report by container / pallet / SSCC / BOL.
Pallet N Pallet ID to be searched for
Container N Container ID to be searched for
SSCC or BOL N SSCC or BOL to be searched for
Tracking References by Consignment / Shipment Group/ Order ID use to report by consignment / shipment group / order ID.
Consignment N Consignment ID to be searched for
Shipment Group N Shipment group to be searched for
Order N Order ID to be searched for

CORE+
• One line per record

• Each line will show data for Consignment, Shipment group, Order ID, Carrier Shipment Tracking Reference, Transport Booking Reference,
Customer Transport Authorization reference, Carrier, Service Level, Pallet, Container, Package Code, Shipment Item Label Type, Reference (this
will be the SSCC, BoL or MBoL reference for example), Nett Weight, Gross Weight, Width, Length, Height, Volume, Label Date, Label Time,
Hashcode.
• To interpret the values use the following:
Package Shipment Item

code Label Type
C WHS_REC Retailer Label SSCC number for the label
BOL WHS_BOL BOL number BOL Number as appearing on the BOL document and the Retailer label
MBOL WHS_MBOL MBOL number MBOL Number as appearing on the MBOL document
Valid 'Pallet CAR_DST Container Tracking Reference as shown on the Carriers container label either provided by the carrier
Type' reference number integration tool or captured manually (depending on setting for the Carrier/Service
Level).
Click here to view a sample Tracking References by Period REPORT Output.
Click here to view a sample Tracking References by Container / Pallet / SSCC / BOL REPORT Output.
Click here to view a sample Tracking References by Consignment / Shipment Group/ Order ID REPORT Output.

CORE+
Outbound - Trailer Shipping Notification

The Trailer Shipping Notification (By Date Range) report is used to show a summary of what has been shipped per trailer.

Location N Allows for selection of the trailer value captured, and hence to only display information for the desired trailer.
• One line per pallet

• Each line will show data for Site, Client, Shipped Date, Trailer, Carrier, Customer ID, Customer name, Consignment, Pallet ID, Order(s), Count of
Containers, Pallet weight, Pallet Volume, Putaway group(s), Hazardous Class(es).
• Total Pallets, Containers and Pallet Volume per trailer.

CORE+
Inventory Management - ABC Dynamic Pick Face Mismatch

A report to show Pick Face ABC rank vs the current SKU ABC rank where the ranks differ for use with the ABC Analysis Option Pack.

Owner ID N The Owner to use for data included in the report.
• One record per combination of Site, Client, Owner ID, SKU, and Location that matches the selection criteria entered
• Each line includes information on the:
o Site ID
o Client ID
o Owner ID
o SKU
o Description
o Location
o ABC Frequency:
▪ Actual Current ABC ranking of the dynamic pick face
▪ Required Current ABC ranking of the SKU in that pick face
• Sortation is ascending by alpha numeric sequence within data grouping

CORE+
Inventory Management - ABC Inventory Location Mismatch

A report to show Pick Face ABC rank vs the current TAG ABC rank where the ranks differ for use with the ABC Analysis Option Pack.

• One record per combination of Site, Client, Owner ID, SKU, and Location and TAG that matches the selection criteria entered
o Site ID
o Client ID
o Owner ID
o SKU
o Description
o Location
o TAG ID
o ABC Frequency:
▪ Required Current ABC ranking of the TAG in that pick face

CORE+
Inventory Management - ABC Putaway Algorithm Mismatch

A report to show Pick Face ABC rank vs the current receipt awaiting putaway for use with the ABC Analysis Option Pack.

• One record per combination of Site, Client, Owner ID, SKU, and Location that matches the selection criteria entered
o Site ID
o Client ID
o Owner ID
o SKU
o Description
o ABC Frequency:
▪ Required Current ABC ranking of the SKU awaiting putaway

CORE+
Inventory Management - ABC SKU Ranking

A report to show current SKU ranking information for use with the ABC Analysis Option Pack.

• One record per combination of Site, Client, Owner ID and SKU that matches the selection criteria entered
o Site ID
o Client ID
o Owner ID
o SKU
o Description
o ABC Frequency:
▪ Required Current ABC ranking of the SKU in that pick face
o ABC Count (the number of transactions in the ITL table or Shipping Manifests, based on how ABC Analysis is run)

CORE+
Inventory Management - Adjustments

A Historical view of adjustments made (to sense check for excessive adjustments or using adjustments rather than using an order to drive stock out of
the warehouse).
• REPORT Adjustments by Date Range - to print direct to a printer or view and print from screen.
• CSV REPORT Adjustments by Date Range - to generate and receive a CSV file via email.

Owner N An owner can be selected to narrow down the displayed data if desired.
Include Serials N Selecting this will display serial numbers on the report (if known)
• One line per adjustment

• Each line includes information on the Site ID, Client ID, Date, Time, Location, Owner, SKU, SKU Description, Condition Code, Update Quantity,
Reason Code for the adjustment, Customs Under Bond Y/N, User, Notes, Capture Serials flag, Serial Number, Import Document ID, Import
Document Issue Date, Manufacture Date (CSV only), Allocation Attribute 3 (CSV only).
• Sortation is by SKU then Date
• A Summary is included that shows the total of increases, total of decreases, balance per SKU.

CORE+
Inventory Management - Clear Floor Check

The Clear Floor Check report is used to show a summary of stock not in a suitable storage location and a count of open orders, by status.

Client N Visible if an operator has access to more than one client. Select the required client, or leave blank to view details for all
clients.
Ship by N A Ship by Date can be specified to view open orders in relation to a specified Ship by Date.
Date
• A count of outstanding move tasks grouped into the following categories (the count is grouped by the age of the move task, calculated at the
point the report is run):
o Warehouse Floor Inbound:
▪ Receiving Dock
▪ Return Dock
▪ NCA
▪ INHAZ Location
o Warehouse Inventory:
▪ Suspense
▪ Open Stock Checks
▪ Open Relocations
o Warehouse Floor Outbound:
▪ Replen Tasks (only of
▪ Pick Containers (when still an open move task)
▪ Post Pick Activity Zones
▪ Ship Dock
▪ Allocation Shortages
• A summary of all open orders and order lines that match the status of either Hold, Released, Allocated, In Progress, Picked, Packed, Ready to
Load, Awaiting (Bonded Warehouse Option Pack only) and Complete together with a count of the number of days the orders have been open
(timings = time/date the report was run vs order creation date/time).
• If a Ship by Date has been specified, a summary of all open orders and order lines that match the status of either Hold, Released, Allocated, In
Progress, Picked, Packed, Ready to Load, Awaiting (Bonded Warehouse Option Pack only) and Complete together with a count of the number
of days the orders have been open (timings = time/date the report was run vs specified Ship by Date date/time).

CORE+
Inventory Management - Consolidated Transactions

A Historical view of transactions, often used for troubleshooting.
• REPORT Consolidated Transactions by Date Range - to print direct to a printer or view and print from screen.
• CSV REPORT Consolidated Transactions by Date Range - to generate and receive a CSV file via email.

Transaction N Select a transaction type to narrow the data returned.
SKU N Select a SKU to narrow the data returned.
• One line per transaction sorted by date (if using the Replenishment Runs Option Pack, two transactions will be displayed per replenishment; one
from the originating location to the REP-STOP location, and a second from the REP-STOP location to the final location).
• Each line includes information on the Site ID, Client ID, SKU, Date Time, Reference, User, Customer Name, Customer Order ID, Qty, Transaction
Type, Consignment, Each Length, Each Height, Each Width, Each Volume, Each Weight, Total Volume, Total Weight, EAN, Hazmat Y/N, Serial
Y/N, Batch Y/N, Ship Shelf Life, SKU Description, Owner ID, Tag ID, From Location, Location Zone From, Sub Zone 1 From Loc, To Location,
Location Zone To, Sub Zone 1 To Loc, Line ID, Pallet, Batch ID, Product Group, Putaway Group, Pack Config ID, Tracking Level 1, Ratio 1 to 2,
Tracking Level 2, Ratio 2 to 3, Tracking Level 3, Origin, Bonded Status, Country of Originator, Import Document ID (CSV only), Import
Document Issue Date (CSV only), Manufacture Date (CSV only), Allocation Attribute 3 (CSV only).

CORE+
Inventory Management - Cross Dock Pallets

A view of outstanding SSCC cross dock pallets and age in warehouse. Applicable to SSCC pallets as part of the Cross Dock Option Pack.

• One line per SSCC pallet, sorted by earliest storage date.

• Each line includes information on the Site ID, Client ID, Owner ID, Handling Unit (Pallet ID), Location ID, Storage Date, Days in Cross Dock,
Number of Lines, Contains HAZMAT?, Contains Expiry Controlled Goods?.

CORE+
Inventory Management - Daily Inventory, Recording for Billing

A snapshot view of inventory, designed for use if needed when billing.

Client Y If an operator has access to more than one client they will be required to select one; otherwise the client the operators login is
tied to will be defaulted in.
Email Y The email address to send the output file to.
• One line per SKU

• Each line includes information on the Site ID, Client ID, Date, Site, Client, SKU, SKU Description, Quantity on Hand, Each Depth, Each Width,
Each Height, Each Weight, Each Volume, Volume on Hand, Weight on Hand, Pallet Equivalent, Number of Tags, Hazardous flag, EAN, Serial
flag, Batch flag, Shipment Shelf life.
• Sortation is by SKU
Below shows a sample output (the report is designed for print to screen and direct email of the file to address entered).

CORE+
Inventory Management - Expiring Inventory

The Expiring Inventory (By Date Range) Report is a report to show expired inventory either at the point in time of running the report, or at a stated
future point in time (if inventory levels did not change).

Expired N
Expiry Date N Enter a date to show inventory with an expiry date up to and including the date entered
• One line per Tag of inventory

• Each line will display Site ID, Client ID, Tag ID, SKU, Description, Location, Quantity on hand, Lock Status, Condition code, QC Status, Batch ID,
Product Group, Hazmat ID, Expired flag, Under Bond Flag, Customs Commodity Code, Customs Consignment Reference, Customs Invoice
Reference, Shelf Life, Shipment Shelf life, days (difference to expiry date).

CORE+
Inventory Management - Inventory Age Analysis

A snapshot of inventory showing its age, grouped into the specified intervals.

Intervals Y The intervals in days to use for the report
• One line per SKU / Condition / Lock Code

• Each line includes information on the Site, Client, SKU, SKU Description, Condition code, Lock Code, intervals
• Sortation is by SKU

CORE+
Inventory Management - Inventory Condition Code History

A historical view of the inventory identified and the condition codes it has had.

SKU Y Enter the SKU the report is to present data for.
Include Archive N Include the archive data in the report?
Condition N If entered only inventory with the current status of this condition will be returned.
The report will display for the stated SKU / Condition code (optional):
• One line per group of inventory at the stated condition code.

• Each line includes information on the Site ID, Client ID, TAG ID, Location, Quantity on Hand, Lock Status, Condition Code, Condition Code
Date From, Condition Code Date To.
• Sortation is by SKU then Date then condition.

CORE+
Inventory Management - Inventory Details

The Inventory Details (By date range) report shows all inventory that is within the site, for the client stated
• REPORT Inventory Details by Date Range - to print direct to a printer or view and print from screen.
• CSV REPORT Inventory Details by Date Range - to generate and receive a CSV file via email.

From Date N The earliest receipt date to use for data included in the report.
To Date N The latest receipt date to use for data included in the report.
Include Serials N
Hazardous N
• One line per Tag of inventory

• Each line includes information on the Site ID, Client ID, Owner ID, Tag ID, SKU, Description, Batch, Location, Zone, Subzone, Qty On Hand, Qty
Allocated, Expired, Expiry, Origin, Condition, QC Status, Shelf Life, Product Group, Putaway Group, Pack Config, Full Pallet?, Pallet, Lock Status,
Lock Code, Hazmat, Hazardous Class, Last Movement Date, Container, Pallet Type, "Width (M)", "Depth (M)", "Height (M)", "Volume (M3)",
Track Level 1, Ratio 1 to 2, Track Level 2, Ratio 2 to 3, Track Level 3, C&E Consignment ID, C&E Document Number, C&E Invoice Number,
Country of Originator, Pre-Advice ID, Received Date, Line ID, Notes, Allocation Attribute 1, Allocation Attribute 2, Allocation Attribute 3, Serial
(if Y was selected in Report Selection (available in CSV only)), Import Document ID (CSV only), Import Document Issue Date (CSV Only),
Manufacture Date (CSV only).

CORE+
Inventory Management - Inventory Summary

A high-level Snapshot of inventory levels, typically used for ATP, info for triggering RTS / Disposal orders from clients.

Owner N An owner can be selected to narrow down the displayed data if desired.
• one line per combination of Site ID, Client ID, SKU, location zone, condition and Hazardous ID
• Each line includes information on the SKU, Owner ID, SKU Description, Under Bond Flag, Location Zone, Condition code, Hazardous ID,
Quantity (of lowest level held).
• Sortation is by SKU, Condition, Hazardous ID

CORE+
Inventory Management - Inventory Updates

The Inventory Updates (By Date Range) report shows a historical view of updates made (to sense check for excessive or incorrect updates).

Owner N Allows for a specific owners inventory to be reported on if specified, otherwise all owners will be shown.
• One line per update

• Each line includes information on the Site ID, Client ID, Date, Code (type of update), Tag ID, Location, Owner, SKU, SKU Description, Update
Quantity, Batch, Lock Status, Condition code, Reason Code, Notes entered, Under Bond Flag, User ID, Import Document ID, Import Document
Issue Date, Manufacture Date, Allocation Attribute 3.
• Sortation is by Date

CORE+
Inventory Management - Number of Replens Per SKU

The Number of Replens Per SKU Report is a historical report to show the amount of times SKUs have been replenished over the stated time interval
(Days). Excessive replenishment within an operationally defined time period would indicated that the pick face size and/or inventory levels needs to be
reviewed so to reduce replenishment activity.

Interval Y The report will show five columns increasing by this interval and then a final sixth column of anything else over
• One line per SKU

• Each line includes information on Site, Client, SKU, SKU Description, Pick face Location, Intervals in days (for count of Replens per SKU)
• Sorted by SKU in ascending sequence
• Note: if using the Replenishment Runs Option Pack, two transactions will be counted per replenishment; one from the originating location to
the REP-STOP location, and a second from the REP-STOP location to the final location
Click here to view a sample REPORT output (the report is designed for print to screen, then direct print or extract if needed).

CORE+
Inventory Management - Slotting Tool

An extract that is provided to allow the (re-)optimization of the pick faces in use [by a tool separate to the WMS].

SKU N Enter a SKU to refine the output to a single SKU.
Email Y The email address to send the created csv file to
The file will contain:
• Report Header to show selection criteria for the report as a single row at the top of the report. Also includes the Units of Measure used.
• No Report Footer
• Report Body to show a record per active SKU (that is not a handling Unit SKU) / Pack Configuration. If multiple Pack Configurations are being
used for the SKU (i.e. inventory exists using that Pock Configuration) then a record will appear for each one.
• The fields (columns) for use are:
o Item. Populate with SKU ID from SKU record.
o Supplier. Populate with Supplier name from the SKU record.
o
o Description. Populate with SKU Description from SKU record.
o Prod_Fam. Populate with the Family Group from the SKU record (if value exists)
o Ave_Activity. Populate with the number of Pick tasks for the SKU. Data is pulled from the live tables (not yet archived).
o Balance on Hand. Populate with the total quantity of eaches of the SKU that exists in the Warehouse for the Owner and bonded Status
selected. Do not include suspense account records.
o
o
o
o Pick Face
o Pick Face
o M_Case_Height. Populate with Each Height from SKU record.
o M_Case_Length. Populate with Each Length from SKU record.
o M_Case_Width. Populate with Each Width from SKU record.
o P_Height. Populate with Pallet Height from the Pallet Type associated with the inventory in the pick face for the SKU.

CORE+
o P_Width. Populate with Pallet Height from the Pallet Type associated with the inventory in the pick face for the SKU.
o P_Length. Populate with Pallet Height from the Pallet Type associated with the inventory in the pick face for the SKU.
o Stack_Height. Popul
o
o
o Layers_Pallet. Populate by determining the eaches per pallet, then dividing by the eaches per layer value.
o Toxicity. Populate with the Hazmat Code from the SKU record.
o M_Case_Weight. Populate with the Each weight from the SKU record
o
o Item_Ranking_Expression. Do not populate.
o
o Preferred_Zone_Id. If the Hazmat code is
o Location_ID. Populate with the Pick Face location ID (if one exists) for the SKU. If multiple pick faces for the SKU exist then populate the
field with each one separated by a space.
Below shows a sample output (direct output is a file sent to the email address entered).

CORE+
Inventory Management - Stock Check Details

The Stock Check Details (by Date Range) Report is a historical report to show the results of stock checks completed.
• REPORT Stock Check Details by Date Range - to print direct to a printer or view and print from screen.
• CSV REPORT Stock Check Details by Date Range - to generate and receive a CSV file via email.

Show only variances Y
• One line per count task performed

• Each line includes information on Site ID, Client ID, SKU, Description, Product Group, TAG ID, List ID, Pack Configuration, Location, HazMat
indicator, Count Date, Expected Quantity, Counted Quantity, Variance, Expiry Date (CSV only) and Expiry Time (CSV only).
• Sorted by location in ascending sequence, grouped by SKU
• Locations with no inventory will not be published in the report

CORE+
Inventory Management - Stock Check Summary

The Stock Check Summary (By Date Range) is a historical report to show Stock Check activity.

• One line per Site / Client / Date / Location Zone / Subzone combination that a stock check was performed
• Each line includes information on the Site ID, Client ID, Date, Location Zone, Subzone 1, Number of stock checks completed, % accuracy, count
of accurate tasks, % inaccurate, count of inaccurate tasks, quantity of inventory added, quantity of inventory removed.
• Note that this report will not show empty location checks where a client ID has been specified as empty locations do not relate to a client, only a
site.

CORE+
Inventory Management - Warehouse Occupancy

The Warehouse Occupancy Details Report provides details of the inventory currently within the selected Site for the client(s) chosen.
• REPORT Warehouse Occupancy - to print direct to a printer or view and print from screen.
• CSV REPORT Warehouse Occupancy - to generate and receive a CSV file via email.

• One line per TAG

• Each line includes information on the Site ID, Client ID, Tag ID, SKU ID, SKU Description, Obsolete flag, Location, Location Zone, Subzone,
Quantity on Hand, Pallet Type, Move Date, Condition ID, Lock Code, QC Status, Batch ID, Expiry Date, Pack Configuration, Customs Under
Bond flag, Product Group, SKU Each Height, SKU Each Width, SKU Each Depth, SKU Each Weight, Customs Commodity Code, SKU Nett
Weight, SKU Nett Volume, SKU Hazardous Code, SKU Hazardous Group, Location Weight, Location Height, Location Width, Location Depth,
Location Current weight, Location Current volume, Allocation Attribute 1, Allocation Attribute 2 Allocation Attribute 3, Manufacture Date (CSV
only).

CORE+
Inventory Management - Weekly Stock Summary

The Weekly Stock Summary is a historical report to show activity and stock holding for the previous full week. It can be used for invoicing the client if
the metrics detailed are part of the contract; alternatively it can be used for management assessment of contract performance (particularly in a multi-
client site).

• Data for the last full week Sunday midnight to Sunday midnight [UTC]
• One line per unique SKU and pack configuration
• Each line includes information on the Site ID, Client ID, SKU, Description, Owner, Pack Configuration, Number of Part Pallets received, Total
Part Pallet Cases received, No Full Pallets received, Total Part / Full Cases received, Total Receipt, Total Pallets In, Total receipt adjusted, Total
Pallets adjusted, No Container Picks, Total Cases Container, No Full Picks, Total Cases Full, Total cases out, Total Pallets Out, Adjustments,
Closing Stock, Current Stock, Current Pallet, Full, Part.
• Total per column.
Click here to view a sample output (the report is designed for print to screen, then direct print or extract if needed).

CORE+
Dynamic Pick Face Details

The Dynamic Pick Face Details report shows the current location, fill level, and demand for SKUs within the dynamic pick face zone.

• One line per SKU.

• Each line includes information on the Site ID, Client ID, SKU, SKU Description, Location, Location Zone, Qty on Hand, Qty Allocated and Qty
Due.
• Sorted by SKU.

CORE+
Management Dashboard
The Management Dashboards provides a high level overview of key information pertaining to the Site set up for.
The Outstanding Tasks dashboard will display:
• A count of outstanding Marshall (vehicle load), Order (pick), Putaway, Relocation, Replenishment tasks and Suspense account records.
• The number of tasks outstanding less than 24 hours will be shown in green, those more than 24 hours old will be shown in red.
The Warehouse Stats dashboard will display:
• Warehouse Utilization expressed as a percentage

• The average receipts to bin time for today
• The average receipts to bin time for the last 7 days
Sample Output
The dashboard is designed to be run to the screen only and automatically refreshed on a timer basis. Dashboards will pause if not used for more than
2 days and will require manually refreshing.

CORE+
Ready for Post Pick Activity Dashboard

The Ready for Post Pick Activity Dashboard provides details of outstanding post pick activity tasks and is only visible to Dashboard user accounts.
The dashboard will display:
• Client ID, Consignment, Shipment Group, Order ID, Location, Carrier, Service Level, Ship Dock, Number of Tasks.
• Tasks sorted in priority order, then by ship date.
Sample Output
CoE – Matrix® WMS CORE+
The dashboard is designed to be run to the screen only and automatically refreshed on a timer basis. Dashboards will pause if not used for more than 2
days and will require manually refreshing.

CORE+
Site Activity By Hour Report

The Site Activity By Hour Report provides details of activity for the Site(s) chosen.

Date From Y The earliest date to use for data included in the report.
Date To Y The latest date to use for data included in the report.
• A top section showing a summary of activity per day of the week, split per hour.
• A second section showing per identified day, the activities that were performed and the hour they occurred within. Both the number of tasks
and the quantity of inventory affected is displayed.

CORE+
TMS Planning Dashboard

The TMS Planning Dashboard provides a high level overview of the number of orders at key Transport planning stages.
The dashboard will display:
• status (no status on

the order typically orders that are not being planned or have the planning status missing)
• The number of tasks outstanding less than 24 hours will be shown in green, those more than 24 hours old will be shown in red.
Sample Output
The dashboard is designed to be run to the screen only and automatically refreshed on a timer basis. Dashboards will pause if not used for more than 2
days and will require manually refreshing.

CORE+
Updates from TMS to WMS

The Updates from TMS to WMS reports provides visibility of updates made to orders from the TMS to the WMS.

Order N* The order for which update information should be presented within the report.
Consignment N* The consignment for which update information should be presented within the report.
*Enter either Order or Consignment reference.
• One line per update.

• Each line includes information on the Site ID, Client ID, Date of Update, Time of Update, Transport Planning Indicator, Order ID, Consignment,
Shipment Group, Deliver by Date, Load Sequence, Carrier, Service Level, Hub Carrier ID, Ship by Date, Stage Route ID, Carrier Shipment
Tracking ID, Transport Booking ID, Customers Transport Authorization ID.
• Sorted by update date and time.

CORE+
Bookmark
Other Useful Information Picking Strategy Selection MatrixCross DockingI2M SMART SolutionCo-Pack SMART Solution
Integration OverviewReserved CharactersBarcode ParsingArchive Strategy
Other Useful Information

Picking Strategy Selection Matrix
Pick Method Attributes
Applicable to one or many orders in
(used in conjunction with other pick

method(s) for the rest of the order)
Can be used on part of an order
One-Piece Flow possible
Sortation during picking

Ship As Is possible
one pick run

ID Pick Method Detailed Description Why Use?
Why use Full Pallet Picking?

Full Pallet Pick applied to a single order line, no post pick When you have sufficiently large volumes of
Full Pallet Pick - No Post
PM01 activity (so taken direct to the ship dock). Able to utilize Y Y One Y N a SKU required for an order line that you
Pick Activity
with Ship As-Is functionality at the pallet level. would end up picking full pallets of a SKU
frequently. As such it makes more sense in
terms of operational efficiency to pick these
Full Pallet Pick applied to a single order line, then post pick directly from bulk storage rather than pick
Full Pallet Pick - With Post from a pick face and then have to also
PM02 activity (so taken to the stated activity zone - hence not N Y One Y N
Pick Activity replenish.
compatible with Ship As- Is).
Why use Pick-Pack?

Pick to one or many shipping containers applied to a single When the entirety of an order will be picked
Pick Pack in to Shipping
order, no post pick activity (so taken direct to the ship dock). in one pick run (not multiple) directly into
PM03 Container - No Post Pick Y Y One N N
Able to utilize with Ship As-Is functionality at the each level. the shipping container; the order size is also
Activity
sufficiently large that a trolley wouldn't be
used. Additionally multiple picking methods
Pick to one or many shipping container applied to a single are to be used for the site and / or there are
Pick Pack in to Shipping a number of extreme dimensions on
order and then post pick activity e.g. VAS (so taken to a
PM04 Container - With Post Pick N Y One N N products hence the volumetric version of
stated activity zone - hence not compatible with Ship As- Is).
Activity this method cannot be used.

CORE+
Applicable to one or many orders
pick method(s) for the rest of the

(used in conjunction with other

Ship As Is possible
in one pick run
order)
Why use Volumetric Pick-Pack?

Pick Pack in to Shipping Pick to one or many shipping containers applied to a single When the entirety of an order will be picked
Container with Volumetric order, no post pick activity (so taken direct to the ship dock). in one pick run (not multiple) directly into
PM05 Y N One N N
Assessment - No Post Pick Able to utilize with Ship As-Is functionality at the each level. the shipping container and you have a lots
Activity of different container sizes (with no real
extreme single dimension sizes on products)
Pick Pack in to Shipping Pick to one or many shipping container applied to a single and wish to tell the operator which container
Container with Volumetric order and then post pick activity e.g. VAS (so taken to a size to use. Getting the container size
PM06 N N One N N
Assessment - With Post stated activity zone - hence not compatible with Ship As- Is). correct is important during pick (so you can
Pick Activity avoid a packing process).
Why use Pick & Pack?
When the entirety of an order will not be
Pick to one or many containers applied to one or many picked in one pick run; the order once
order lines for an order, then post pick activity e.g. Packing picked will require further activity
Pick and then Pack in Post to shipping container (so taken to a stated activity zone - (consolidation of pick flows and/or post pick
PM07 N Y One Y N
Pick Activity Zone hence not compatible with ship as-is). Can be used activities). Additionally multiple picking
alongside other different allowed types of pick methods for methods are to be used for the site and / or
the Site. there are a number of extreme dimensions
on products hence the volumetric version of
this method cannot be used.
Why use Volumetric Pick & Pack?
When you will be picking one order at a
time, the order once picked will require
further activity (post pick activities) and you
Pick to one or many containers applied to one or many have a lots of different container sizes (with
Pick and then Pack in Post
order lines for single order pick runs, then post pick activity no real extreme single dimension sizes on
PM08 Pick Activity Zone with N N One Y N
e.g. Packing to shipping container (so taken to a stated products) so wish to tell the operator which
Volumetric Assessment
activity zone - hence not compatible with ship as-is). container size to use. Getting the container
size correct is more important during pick
(better pack efficiency), than picking lots of
broadly correct container sizes and then re
packing (better pick efficiency).

CORE+
Applicable to one or many orders in
(used in conjunction with other pick

method(s) for the rest of the order)

Ship As Is possible
one pick run

Why use Trolley Slot Picking?

Trolley Picking into Shipping Container (pick directed to the When you wish to pick a number of orders
Trolley Slot Picking - No correct container, each container in a trolley slot); no post separately but at the same time. Picking lots
PM09 N N Many N Y
Post Pick Activity pick activity. Not used with Ship As-Is functionality at the of orders into the broadly correct container
each level as have packed into a shipping container. sizes and then optionally re-packing (better
pick efficiency) is more important that
Trolley Picking into the trolley slot (pick directed to the getting the exact container size correct
correct slot); then post pick activity e.g. Packing to shipping during pick (better pack efficiency).
Trolley Slot Picking - With
PM10 container (so taken to a stated activity zone - hence not N N Many Y Y
Post Pick Activity
compatible with ship as-is).
Batch (Product line) Picking applied to order lines from one Why use Batch Picking?
or many orders, no post pick activity (so taken directly to the When you have sufficiently large volumes of
Batch Picking - No Post a SKU required for an order line that you
PM11 Ship dock). Able to utilize with Ship As-Is functionality at the Y Y Many N N
Pick activity would end up picking small quantities of a
each level.
SKU frequently. As such it makes more
sense in terms of operational efficiency to
Batch (Product line) Picking applied to order lines from one pick these as one single pick task (rather
Batch Picking - With Post or many orders then post pick activity [e.g. sortation, than pick separately) and then perform a
PM12 N Y Many Y N secondary sort into the quantities per order
Pick Activity packing, VAS] (so taken to a stated activity zone - hence not
compatible with Ship As- Is). required.
Batch (Product line) Picking applied to order lines from one

Batch Picking - Then Put to
PM13 or many orders then put to wall (so taken to a stated activity N N Many Y N
Wall
zone - hence not compatible with Ship As- Is).

CORE+
Cross Docking
Matrix WMS CORE+ offers a Cross Docking Option Pack which provides the ability to move inventory from the receiving area to a temporary holding
location, post pick activity area or direct to the loading lanes, without the need to put the items into storage.
CORE+ supports 3 distinct types of Cross Docking
1. Flow-Through Cross Docking: Receipt, putaway and storage of Cross Dock items in a dedicated Warehouse Zone in/between/next to the
Receipt and Ship Docks. Storage duration in this Zone is expected to be anywhere between a number of hours up to 5 days. All Pick Methods
can be used in conjunction with Flow Through Cross Docking. Supports all inbound order types.
2. Pre-Allocation Cross Docking: Receipt and Putaway directly to Post-Pick Activity Zone or Ship Dock, with no intermediate storage, using pre-
allocation to allocate orders to expected receipts. Allows for Pallet break-down and sortation to redistribute received inventory across multiple
orders and ship docks (aka Retail Cross Docking). Requires a Pre-Advice or ASN as receipt order and optionally the Post Pick Grid Sortation
Option Pack.
3. Full SSCC Pallet Cross Docking: Receipt and Putaway to the Ship-Dock of pallets, using their SSCC pallet barcode receipt, pick and vehicle
loading. Pallets can contain one or more inventory items. Requires an ASN as receipt order.
Key features of using CORE+ Cross Docking:
• Bypass conventional storage in warehouse

• Predefined Zone 15XDC01 for Flow-Through Cross Docking
• Distinct Receipt and Order Type XDC
• Allocation Attribute 2 with prefix XDC- must be used to identify, track and allocate all Cross Dock inventory. Removal of this indicator can be
• Directly pick from receipt dock to Post Pick Activity Zone or Ship Dock using streamlined picking process
• (Automatically) Pre-Allocate inventory to orders prior to actual receipt of inventory in warehouse
• Receive and Pick Pallets using SSCC pallet barcode (SSCC Pallet Cross Docking)
• Cross D
Unsupported within CORE+ Cross Docking:
• Receipt, picking and shipping of expired inventory

• Receipt, picking and shipping of rejected batches
• Use of Matrix WMS Portal for creation of Cross Dock inbound and outbound orders.

CORE+
Diagram
Outbound
Order Interface
1 2 3 5 6 7 8 9 10
Outbound Outbound Allocation Sort Load Outbound Vehicle Vehicle Outbound
Order Planning Preparation Vehicle Load Dispatch Vehicle
4
Despatch
Advice
Interface
ASN Inbound
Interface
Pick
7
1 2 3 4 5 6 8
Inbound Book In Inbound Unload Unloaded Receive Inbound
Order Vehicle Vehicle Vehicle Inventory Order
Creation Arrival Departure Completion
Receipt
Confirmation
Interface

CORE+
I2M SMART Solution Integration with Insequence & IFL

Matrix WMS CORE+ offers integration with Insequence and / or IFL as part of the CEVA I2M SMART Solution. Insequence is an Automotive tool that
drives the picking of parts to meet production line demand. IFL (In Factory Logistics) manages the final distribution of parts within a factory and the
subsequent return of assets.
Key features of using CORE+, Insequence and IFL as part of the I2M SMART solution:
• Inbound Receiving and Putaway as per any of the existing CORE+ processes,
• Predefined Zone to use for inventory handled by Insequence,
• Single pick face per SKU (within predefined zone) with minimum quantity triggering replenishment,
• attributes (e.g. serial number, etc),
• IFL set up as a Carrier/Service Level in CORE+,
•
• Insequence receives and sequences demand from the manufacturer,
• CORE+ Inventory Query API used by Insequence,
• CORE+ [Outbound] Order Create API used by Insequence to provide sequenced demand orders,
• Non sequenced outbound orders can also be processed via the existing CORE+ processes,
• Demand Orders include Carrier/Service Level for IFL, Consignment ID, Load Sequence,
• CORE+ pick notification API to Insequence to inform of allocated pick tasks,
• Insequence used for picking onto racks and production of paperwork,
• CORE+ Pick Confirmation API used by Insequence to confirm the picking activity and container,
• CORE+ Move Confirmation API used by Insequence to confirm the completion of picking activity for an order and its location,
• CORE+ used for the loading and dispatch of orders.
• IFL Despatch Advice API used to notify IFL of the orders to be delivered to the manufacturer.
• IFL used to manage the delivery to the final destination at the manufacturer.

CORE+
Diagram
Inbound Order
Interface / API
1 2 3 4 5 6 7 8
Receipt
Order Create Pick Confirm Confirmation
API for API for Interface / API
Sequenced Sequenced
Orders Orders
Move
Outbound Order
Complete API
Interface / API for
for Sequenced
Others
Orders
1 2 4 5 6 7 8 9 10
Pick
3 Notification API
for Sequenced
Orders
IFL Despatch
Advice API
Book In
Inventory
Query API for Despatch Advice
Sequenced Interface / API
Orders
2 3 4 6
SKU Inventory Inventory Information
Updates Adjustments Queries
Inventory Inventory
Update Adjustments
SKU Interface Interface Interface

CORE+
Co-Pack SMART Solution Integration with Pack Manager

Matrix WMS CORE+ offers integration with Pack Manager as part of the CEVA Co-Packing SMART Solution.
Key features of using CORE+, and Pack Manager as part of the Co-Pack SMART solution:
• Copacking activity is scheduled and managed by PackManager to build Finished Goods from Component parts, both of which are stored as
inventory within CORE+ (Build-to-Stock),
• Initial inbound receiving, putaway and Storage of inventory of component parts (as their own SKUs) occurs via CORE+ using existing processes,
• Final outbound instruction to dispatch, allocation, picking, packing loading and shipping of existing inventory of either component parts and/or
finished goods occurs via CORE+ using existing processes,
• CORE+ SKU interface to PackManager is used to inform the Copacking function of SKU and related Pack Configuration information. (If CORE+
kitting functionality was previously used then associated kit line information is also included),
• PackManager controls the Bill-of-Materials per Finished Good. Consumables are by default managed within the Copacking tool they can
however also be treated as inventory within the WMS (but strongly advised against),
• PackManager requests the component part inventor
interface,
• The Outbound Order type CPK is used to help visibility / reporting from CORE+,
• Order Lines contain predefined stage route ID (LINE01-LINE20) to guide the picking and movement to the appropriate location (matching a
production line) in the shipdock COPACK01,
• Unique Consignment IDs are advised to be populated on the orders provided so to remove the need for transport planning manually in the
WMS,
• CORE+ Dispatch Advice interface is used to inform PackManager of the handover of requested inventory,
• PackManager production line are used to perform copacking activity, producing the desired finished goods, including controlling a QA process
and GS1-128 compliant pallet labelling,
• CORE+ ASN inbound order interface is used by PackManager to inform CORE+ of the palletised Finished Good SKUs (and returning
component SKUs if appropriate),
• The Inbound Order types CPF (finished goods) and CPR (returns) are used to help visibility / reporting from CORE+,
• Trusted Receipt and Putaway is performed, with the CORE+ Receipt Confirmation interface used to notify PackManager of the transfer of
inventory.
• CORE+ Inventory Snapshot and adjustments are available if desired to keep PackManager aware of inventory levels.

CORE+
Diagram
Outbound Order
Interface
1 2 4 5 6 7 8 9 10
3 Despatch Advice
Interface / API
Book In
Inbound Order
Interface / API
1 2 3 4 5 6 7 8
Receipt
Confirmation
Interface / API
2 3 4 6
SKU Inventory Inventory Information
Updates Adjustments Queries
Inventory Inventory Inventory

Update Adjustments Snapshot
SKU Interface Interface Interface Interface

CORE+
Integration Overview
Available messages are listed per Business Process step and therefore will be duplicated if available at more than one stage.
Message # Type From or To WMS Abbreviation Description Extract Name Outbound Trigger Point
S-010 EDI To WMS PURORD Pre-Advice / Master Pre-Advice
S-012 EDI To WMS ASNINS ASN Instruction (Delivery / UPI Receiving)
S-013 EDI To WMS TAGREC ASN Instruction (Tag Receiving)
S-016 EDI To WMS RETINS Return Instruction
S-043 EDI From WMS APERAK-PAH Application Acknowledgment APKPRE_ADVICE_HEADER*.XML Add / update Pre-Advice Header
S-043 EDI From WMS APERAK-PAL Application Acknowledgment APKPRE_ADVICE_LINE*.XML Add / update Pre-Advice Line
Inbound Order Creation
S-014 EDI From WMS RECADV Receipt Advice - Cancelled PAHCANCELLED*.XML Pre-Advice Header status Update to Cancelled
S-043 EDI From WMS APERAK-UPI Application Acknowledgment APKUPI_RECEIPT_HEADER*.XML Add/update ASN
S-043 EDI From WMS APERAK-UPL Application Acknowledgment APKUPI_RECEIPT_LINE*.XML Add/update ASN
S-015 EDI From WMS RECADV-UPI Receipt Advice UPICANCELLED*.XML UPI cancelled
S-015 EDI From WMS RECADV-ASN Receipt Advice ASNCANCELLED*.XML ASN (Delivery) cancelled
S-018 EDI From WMS RECADV-RET Receipt Advice Returns PAHCANCELLED*.XML Pre-Advice Header status Update to Cancelled
S-210 API To WMS PURORD - POST Create Inbound Order - POST
S-216 API To WMS RETINS - POST Create Return Instruction - POST
S-210 API To WMS PURORD - PUT Update Inbound Order - PUT
S-210 API To WMS PURORD - DELETE Cancel Inbound Order - DELETE
S-210 API To & From WMS PURORD - GET Get Status Inbound Order - GET
S-244 API From WMS ORDSTA - POST Post Status Inbound Order - POST

CORE+
Pre-Advice Header status Update to Complete

S-014 EDI From WMS RECADV Receipt Advice PAHCOMPLETE*.XML
(fully received)
S-015 EDI From WMS RECADV-UPI Receipt Advice UPICOMPLETE*.XML UPI fully received
S-015 EDI From WMS RECADV-ASN Receipt Advice ASNCOMPLETE*.XML ASN (Delivery) fully received
S-018 EDI From WMS RECADV-RET Returns Receipt Advice PAHCOMPLETE*.XML
(fully received)
S-019 EDI From WMS TAGRCP Receipt Advice (Tag Receiving) PAHCANCELLED*.XML Pre-Advice Header status Update to Cancelled
Receive Inventory

S-019 EDI From WMS TAGRCP Tag Receipt PAHCOMPLETE*.XML
(fully received)
S-045 EDI From WMS ORDSTA-PAH Pre-Advice Header Status PSUIN_PROGRESS*.XML Pre-advice first receipt
S-045 EDI From WMS ORDSTA-UPI UPI (ASN) Header Status USUIN_PROGRESS*.XML Unique Pallet ID first receipt
S-045 EDI From WMS IFTMAN Dock Scheduler Booking Log BKLBOOKING*XML For each Dock Scheduler Booking Log created
At each change in Dock Scheduler Booking
S-045 EDI From WMS IFTMAN Dock Scheduler Booking Status BKUUPDATE_STATUS*XML
Status
S-214 API From WMS RECADV - POST Receipt Advice - POST
S-014 EDI From WMS RECADV Receipt Advice PALPUTAWAY*.XML Tag put away
S-014 EDI From WMS RECADV Receipt Advice PAHPUTAWAY*.XML
and all tags put away
S-015 EDI From WMS RECADV-UPI Receipt Advice UPLPUTAWAY*.XML Tag put away
S-015 EDI From WMS RECADV-UPI Receipt Advice UPIPUTAWAY*.XML UPI fully received and putaway
S-015 EDI From WMS RECADV-ASN Receipt Advice ASNPUTAWAY*.XML ASN (Delivery) fully received and putaway
S-018 EDI From WMS RECADV-RET Returns Receipt Advice PALPUTAWAY*.XML Tag put away
Putaway
S-019 EDI From WMS TAGRCP Receipt Advice (Tag Receiving) PAHCANCELLED*.XML Pre-Advice Header status Update to Cancelled
S-018 EDI From WMS RECADV-RET Receipt Advice Returns PAHPUTAWAY*.XML
S-019 EDI From WMS TAGRCP* Tag Receipt (still under development) PALPUTAWAY*.XML Tag put away
S-019 EDI From WMS TAGRCP* Tag Receipt (still under development) PAHPUTAWAY*.XML
S-214 API From WMS RECADV - POST Receipt Advice - POST

CORE+
S-020 EDI To WMS INSDES Instruction to Despatch
S-043 EDI From WMS APERAK-ORH Application Acknowledgment APKORDER_HEADER*.XML Add Outbound Order
Outbound Order Creation
S-043 EDI From WMS APERAK-ORL Application Acknowledgment APKORDER_LINE*.XML Add Outbound Order
S-026 EDI From WMS DESADV Despatch Advice - Cancelled ORDCANCELLED*.XML Order Header status Update to Cancelled
S-220 API To WMS INSDES - POST Create Outbound Order - POST Create Outbound Order
S-220 API To WMS INSDES - PUT Update Outbound Order - PUT Update Outbound Order
S-220 API To WMS INSDES - DELETE Cancel Outbound Order - DELETE Set Outbound Order to cancelled
S-220 API To & From WMS INSDES - GET Get Status Outbound Order - GET Get Outbound Order status
S-244 API From WMS ORDSTA - POST Post Status Outbound Order - POST
S-022 EDI From WMS TMSPLN Instruction to Despatch - To TMS TMSHOLD*.XML Send to planning tool
Outbound Planning
S-023 EDI To WMS TMSPLN Instruction to Despatch - From TMS Receive from planning tool
S-220 API To WMS INSDES - PUT Update Outbound Order - PUT Update Outbound Order
S-220 API To WMS INSDES - DELETE Cancel Outbound Order - DELETE Set Outbound Order to cancelled
S-044 EDI From WMS ORDSTA-ORD Order Status OSUIN_PROGRESS*.XML When the order has started to In Progress
S-026 EDI From WMS DESADV Despatch Advice - Ready To Load ORDREADY_TO_LOAD*.XML Order Header status Update to Ready to Load
Pick
S-226 API From WMS DESADV - POST Despatch Advice Ready To Load - POST
Order Header status Update to Packed
S-026 EDI From WMS DESADV Despatch Advice Packed ORDPACKED*.XML (only to be used for triggering the Commercial
Invoice)
S-044 EDI From WMS ORDSTA-ORD Order Status OSUREADY_TO_LOAD*.XML Order Header status Update to Ready To Load
Load Prep
S-026 EDI From WMS DESADV Despatch Advice - Ready To Load ORDREADY_TO_LOAD*.XML Order Header status Update to Ready To Load
S-226 API From WMS DESADV - POST Despatch Advice Ready To Load - POST

CORE+
Order Header status Update to Complete

S-026 EDI From WMS DESADV Despatch Advice - Loaded ORDCOMPLETE*.XML
(Vehicle Loaded)
V. Load
S-226 API From WMS DESADV - POST Despatch Advice Loaded - POST
Order Header status Update to Shipped
S-026 EDI From WMS DESADV Despatch Advice - Shipped ORDSHIPPED*.XML
(Vehicle Despatch)
S-048 EDI From WMS IFCSUM Forwarding and Consolidation Summary TRLTRAILER_SHIPPED*.XML Trailer Shipped (Vehicle Despatch)
Despatch
S-226 API From WMS DESADV - POST Despatch Advice Shipped - POST
S-000 EDI To WMS PRODAT Product Data

S-000 EDI From WMS PRODAT Product Data SKU*.XML Add/update SKU
Order Header status Update to Shipped (via Kit
S-026 EDI From WMS DESADV Kit Build Despatch Advice KITKITBUILD*.XML
Build)
S-031 EDI To WMS BATRSP-RSP Batch Status Update Stock Adjustment
S-031 EDI To WMS BATRSP-RSP Batch Status Update to Rejected Condition Update
S-033 EDI From WMS INVADJ-ADJ Inventory Adjustment ITLADJUSTMENT*.XML Stock Adjustment
S-033 EDI From WMS INVADJ-STS Inventory Lock Update ITLINV_LOCK*.XML Inventory Lock
S-033 EDI From WMS INVADJ-STS Inventory Unlock Update ITLINV_UNLOCK*.XML Inventory Unlock
Inventory Management
S-033 EDI From WMS INVADJ-STS Inventory Condition Status Update ITLCOND_UPDATE*.XML Condition Update
S-033 EDI From WMS INVADJ-OWN Inventory Owner Update ITLOWNER_UPDATE*.XML Owner Update
S-033 EDI From WMS INVADJ-BAT Inventory Batch Update ITLBATCH_UPDATE*.XML Batch Update
S-033 EDI From WMS INVADJ-ALL Inventory User Def Update ITLUSER_DEF_UPDATE*.XML User Defined Update
S-033 EDI From WMS INVADJ-ORG Inventory Origin Update ITLORIGIN_UPDATE*.XML Origin Update
S-033 EDI From WMS INVADJ-MFD Inventory Manufacturing Update ITLMANUF_DT_UPDATE*.XML Manufacturing Date Update
S-033 EDI From WMS INVADJ-QSU Inventory Quality Control Status Update ITLQCHOLD*.XML Update batch status to Hold
S-033 EDI From WMS INVADJ-QSU Inventory Quality Control Status Update ITLQCRELEASED*.XML Update batch status to Released
S-033 EDI From WMS INVADJ-QSU Inventory Quality Control Status Update ITLQCREJECT*.XML Update batch status to Rejected
KITSHIPPED-KIT*.XML Update partner on Kitted and/or Unkitted
S-036 EDI From WMS PRORES Production Response
inventory levels for kits and components
KITSHIPPED-UNKIT*.XML Update partner on Kitted and/or Unkitted
KITPUTAWAY-KIT*.XML Update partner on Kitted and/or Unkitted

CORE+
KITPUTAWAY-UNKIT*.XML Update partner on Kitted and/or Unkitted

KTLKIT_BUILD-KIT*.XML Update partner on Kitted and/or Unkitted
KTLUNKIT-UNKIT*.XML Update partner on Kitted and/or Unkitted
KTLPUTAWAY-KIT*.XML Update partner on Kitted and/or Unkitted
KTLPUTAWAY-UNKIT*.XML Update partner on Kitted and/or Unkitted
S-039 EDI From WMS INVRPT Inventory Report - Stock Reconciliation INVRPT*.XML Scheduled Nightly Report
S-043 EDI From WMS APERAK-SKU Application Acknowledgment APKSKU*.XML Add/update SKU
S-200 API To WMS PRODAT - POST Create SKU - POST Create SKU
S-200 API To WMS PRODAT - PUT Update SKU - PUT Update SKU
S-200 API To WMS PRODAT - DELETE Set SKU to Obsolete - DELETE Set SKU to obsolete
S-200 API To & From WMS PRODAT - GET Get SKU Data - GET Get SKU data
S-239 API To & From WMS INVRPT - GET Get Inventory per SKU - GET Get inventory data
S-233 API From WMS INVADJ - POST Inventory Adjustment - POST

CORE+
Reserved Characters Archiving Strategy Utilized

The following characters are reserved and should not be passed on any
interface: Stage Duration Held
• = [Special query mode character]
• > [Special query mode character] Live Tables 35 days
• _ [RDT communications character]
• \\ [RDT communications character] Archive Tables (still able to be accessed
36 days 545 days
• ] [RDT communications character] within the application)
• ^ [RDT communications character]
• | [RDT communications character] Full Purge / Backup via tape / disk Onwards
• [ [RDT communications character]
• < [Query mode & RDT communications character]
• % [Database or special query character]
• ( [Database or special query character]
• ) [Database or special query character]
• Â [Database or special query character]
• § [Database or special query character]
• ` [Database or special query character]
• ~ [Database or special query character]
• ; [Database or special query character]
• ' [Database or special query character]
• ? [Database or special query character]
• \ [Database or special query character]
Barcode Parsing
Barcode Parsing is the ability to scan a barcode which contains more
than one piece of data and for the different data elements to be
populated into a selected range of WMS fields.
Barcode Parsing is controlled through Super User access to barcode

mapping. Please liaise with your Regional Super User to make use of
this feature.

Bookmark
CORE+
Sign Off
Sign Off
We, the undersigned, accept this document as a statement of the functionality to be provided within Matrix WMS CORE+ and the associated
configuration that is required for data set up.
Decisions / Set Up Checklist
Party that completed the Decisions / set up information contained in this Inbound Order Creation
document
Receive Inventory
Putaway
HAZMAT Segregation
Signed : Outbound Order Creation

Planning
Name :
Allocation
Position :
Pick
Date : Load Preparation
Vehicle Load
IT Stream Lead for the Project Vehicle Despatch
Inventory Option Packs
Inventory Relocations
Stock Checks
Signed :
Inventory Updates
Name :
Inventory Adjustments
Position : Facility
Date : SKU
Operator

CORE+
Bookmark
Glossary of Terms
Term Description
Glossary of Terms FEFO First Expiry First Out the sequence for allocating,
Term Description picking and shipping goods from the warehouse
Activity Zone An area where post picking activities are able to based upon using the oldest expiry dated goods
be performed first.
AMHE Automated Material Handling Equipment. FIFO First In First Out the sequence for allocating,
AMR picking and shipping goods from the warehouse
type of AMHE, which can be used in a warehouse based upon using the goods oldest received
to autonomously transport goods goods first.
API Application Programming Interface which provide FMD Acronym for Falsified Medicines Directive.
the ability to make timely validated message GDPR The General Data Protection Regulation. EU law
exchanges between partners. on data protection and privacy in the European
AWB Acronym for the air freight term Air Waybill. Union and the European Economic Area.
Check-digit A string of characters used to confirm proof of Hazardous / A product that is deemed to be hazardous as
presence at a location that are often displayed in a HAZMAT classified by the United Nations.
non-readable format (i.e. barcode). HU Handling Unit. A package of goods which are
Client The generic name used for the party that CEVA treated as one, with no consideration for the
are performing warehousing on behalf of inventory contained.
Consignment A group of goods that will be shipped from the Inbound The notification in advance of goods due to arrive
warehouse together. This is typically all the goods Order at the warehouse. Within the WMS the Pre-advice
leaving the warehouse via the same dock door on functionality is used (which supports the preferred
the same Carrier / vehicle. process as well as the use of Purchase orders if
necessary)
Customer The generic name used for anyone that orders
goods from the CEVA Warehouse Inventory The Warehouse term for goods that have been
received into the warehouse
EAN European article number
ITL Inventory Transaction Log - every movement of
EDI Electronic Data Interchange which allows the inventory or status change in the WMS will create
exchange of information in a standard electronic an ITL
format between partners.
KPI Acronym for Key Performance Indicator

CORE+
Glossary of Terms
Term Description Term Description
Kit A collection of one or more items (either the same Picking The one or many picking methods that will be
and/or different) that grouped together are known Strategy used by a site / client at a given point in time.
as a different item. Also referred to as Bill of Over time the picking strategy may evolve to
Materials or BoM. further drive operational efficiency.
Master Pre- A Master Pre-Advice or Purchase Order serves Returns A location in the warehouse where returned goods
Advice as a notification of inbound inventory to the Location are stored (often for assessment and processing
- prior to putaway to a storage location).
the operation to match the notified expected
RF Acronym for Radio Frequency, which is a wireless
inbound inventory to be received.
connectivity method for updating the WMS with
Matrix WMS WMS) transactions that have been completed in the
CORE+ warehouse using Mobile Devices
Mobile Radio Data Terminal hand held or truck mounted Shipment A group of orders that will be delivered to the
Device device wirelessly connected to the WMS same delivery location (within a consignment).
Pack Warehouse term used to describe the number of SKU Stock Keeping Unit In SAP this is known as the
Configuration parts that can be added to a pallet. This helps Material Code
control putaway within the WMS
SLA Acronym for Service Level Agreement
Part or Alternative word for SKU (see SKU)
Storage A location in the warehouse where inventory is
Product
Location stored.
PC Personal Computer. Either a desktop or Laptop
Supplier A company or person that provides parts for use
device that can be used to access the web client
version of Matrix WMS CORE+. UDI Unique Device Identifier - a system used to mark
and identify medical devices within the healthcare
Pick Face A defined location in the warehouse for a SKU that
supply chain.
will be the primary place goods will be picked
from. UOM Unit of Measure A definite magnitude of a
quantity, defined and adopted by convention or
Picking A particular way of picking; a site would typically
by law that is used as a standard for measurement
Method employ one or many different picking methods to
of the same quantity [1]. Any other value of that
maximize picking efficiency.
quantity can be expressed as a simple multiple of
the unit of measurement.

CORE+
Glossary of Terms
Term Description
UPC Universal product code
VAS Value added service.
WMS Warehouse Management System

CORE+
Glossary of Terms

Matrix® WMS CORE+ Product Description

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Matrix® WMS CORE+ Product Description

Uploaded by

Copyright:

Available Formats

Matrix®

Release 7.1.0 CEVA Matrix® WMS CORE+ Product Description 2

Use the page progression arrows

Contents Set Up / Master Data

Type directly into these fields

Inbound Other Useful Information

Client Name Number of SKUs and anything Unique or

Client Primary Business Number of Inbound Orders

Types of Products Number of Outbound Orders

Facility Country Details on any Seasonality / Fluctuations

Facility Size Inbound Goods Receipt to Putaway

Number of Warehouse Staff and Shifts Outbound Order Creation to Shipping

Release 7.1.0 CEVA Matrix® WMS CORE+ Product Description 4

Inbound Inbound Order Creation  Receive Inventory  Putaway  HAZMAT Segregation

Inbound Product Description

Matrix WMS Operational

Release 7.1.0 CEVA Matrix® WMS CORE+ Product Description 5

1. Inbound Order Creation. An inbound order is provided to CEVA.

3. Inbound Vehicle Arrival. The vehicle containing the goods on the

5. Unloaded Vehicle Departure. Following any cursory checks, the

6. Receive Inventory. The goods on the receiving dock are positively

8. HAZMAT Segregation. If needed, hazardous goods / HUs are

Release 7.1.0 CEVA Matrix® WMS CORE+ Product Description 6

Inbound Option Packs Mobile Printing

Trolley Slot Receiving / Putaway DOT Management for Tires

Integration with Co-Pack SMART Solution

Release 7.1.0 CEVA Matrix® WMS CORE+ Product Description 7

Inbound Order Creation Guiding Principles

An APERAK message is able to be sent confirming successful

Release 7.1.0 CEVA Matrix® WMS CORE+ Product Description 11

Release 7.1.0 CEVA Matrix® WMS CORE+ Product Description 12

Exceptions Exception / Failure Activity Required

Interface conversion / movement: If Inbound Order is An inbound order may be amended if

Exception / Failure Activity Required

If what is held on the inventory record

Release 7.1.0 CEVA Matrix® WMS CORE+ Product Description 14

Inbound Order Creation Decisions (for configuration / Set up)

□ No □ Portal Form Pre-Advice (for use with the positive

• How will the inbound orders be provided to Matrix WMS

□ CEVA Standard Interface ASN

□ For Tag Receiving

□ CEVA Standard Interface Pre-Advice (for use with the

□ For Delivery / UPI Receiving □ Client Employees

□ For Tag Receiving □ Other 3rd Party

□ Client Specific Interface [Client format mapped to the

Release 7.1.0 CEVA Matrix® WMS CORE+ Product Description 15

• On successful creation of the inbound order, is the "APERAK

□ used? [select one]

□ In Progress Inbound Order Creation Section Complete

Release 7.1.0 CEVA Matrix® WMS CORE+ Product Description 16

Receive Inventory Guiding Principles

Release 7.1.0 CEVA Matrix® WMS CORE+ Product Description 18

SKU Labels Business Description Positive Confirmation Receiving

Release 7.1.0 CEVA Matrix® WMS CORE+ Product Description 19

Release 7.1.0 CEVA Matrix® WMS CORE+ Product Description 20

Information Comment / Description Information Comment / Description

Release 7.1.0 CEVA Matrix® WMS CORE+ Product Description 21

[6.2] Create C&E Invoice Information Comment / Description

Invoice Value Optional - but strongly recommended for

Invoice Currency Optional - but strongly recommended for

Line ID Optional. Normally left blank, this can be

Invoice Time Optional. [6.3] Link Consignment and Invoice

[6.4] Identify Inbound Order - Pre-Advice ID [mandatory]

Release 7.1.0 CEVA Matrix® WMS CORE+ Product Description 23