Administration¶

Reprinting Documents¶

This Action will reprint any documents previously created. It does NOT regenerate the document; rather it retrieves the previously created PDF and directs that specific file to the printer. This is useful if a hardware-based printing problem is encountered.

Reprinting Labels¶

This Action is the same as reprinting documents, except that it is specific to labels such as ship labels. This will retrieve any previously created ZPL-based labels and direct them to the printer. Like reprinting documents, this is useful if a hardware-based printing problem is encountered.

Regenerating Documents & Labels¶

If a document or label needs to be regenerated because a condition or data has been changed since the original document was printed, this is the Action that should be selected by the operator. This action will initiate the necessary ShipHawk WMS processes to regenerate the requested document or label. If a shipping label is to be regenerated, it will create a new tracking ID for the package.

Resetting Orders¶

This Action can only be performed if picking has not yet begun. Resetting an order will remove the order from any wave and batch. It will also deallocate any inventory and places the order in the initial state it was received in from the ERP.

Canceling Orders¶

Order cancellation is always a challenge in the warehouse, especially if picking has begun on the order. This Action, however, keeps the process very simple to manage, even after picking has begun. In fact, unless you have shipped the order, ShipHawk WMS will allow you to cancel a fulfillment order, and manage the re-slotting of any picked inventory without the need to perform any inventory adjustments or re-receipt of the inventory.

To begin, the authorized operator would access the Administration Menu and enter the order number or scan one of the containers on the order. The page is shown below. Based on the status of the order, ShipHawk WMS will list a variety of valid actions to take for this order. In this case, the order has begun picking, so an option to cancel is order is shown.

Of course, if picking has not yet begun, the operator can also cancel the order as shown on the page below.

Once the “Action to Take” is selected, the operator will be sequenced through a series of validation steps (to confirm the action requested). Once confirmed, the order will be canceled in ShipHawk WMS. The inventory and containers will be automatically moved to a specifically designated bin or staging area for “return to stock” (or RTS) inventory, as is shown below.

This “return to stock” bin may be defined as an allocatable bin, or not. If allocatable, then inventory in this bin is considered available for allocation and pickers could be directed to that bin if the allocation strategy dictates this. If not allocatable, then no picks will ever be allocated to that RTS bin, and you will need to move the inventory out of the bin to an allocatable bin.

To move inventory from the RTS bin, the operator will use the standard Move features to identify the Bin, Item, Quantity to Move. The operator may also simply scan the Container ID on the inventory to initiate a move. The operator can then select the standard “Suggest Bin” option and ShipHawk WMS will direct the operator to the proper bin based on the standard putaway rules setup for this item (see Putaway).

Editing Order Addresses/Attributes¶

At times, data received from the ERP on the order must be changed at the last minute in the warehouse. This Action permits that, allowing authorized operators to edit order attributes at any time, but before the order is shipped.

Rules¶

Usage:

Examples:

JSON for Decimal Inventory Management Rule:

{
    "active": true,
    "step": "0.25",
    "format": "#.##"
}

JSON for Print Labels at Receiving Rule:

{
    "print_label_default" : "YES",
    "print_label_default_qty" : 1
}

Roles¶

Usage:

Examples:

The LOV Table relates to the ROLE table in ShipHawk WMS which is defined as follows:

Examples:

Below is a sample Role Definition:

{
   "UnAuthorizedForms": [
       "Pack",
       "Count",
       "Search"
     ],
   "UnAuthorizedOptions": [
       "ReviewResults",
       "ResolveCounts",
       "SearchforPOASN"
   ]
 }

Location¶

Usage:

Examples:

Division¶

Usage:

Examples:

The Return Address element is represented with a JSON object and can represent multiple return addresses for different Locations (for the Division), and different Customers (for drop shipments). Return Addresses are listed on all Pack Lists, Shipping labels, BOLs, Commercial Invoices and other logistics-related documents.

{
    "returnAddress": {
            "company": "SWM Inc.",
            "addr1": "1234 Maple Street",
            "city": "Highland",
            "state": "MD",
            "zip": "20777",
            "countrycode": "US",
            "phone": "555-111-2222",
            "customssigner": "Customer Service"
    },
    "EAST-DC": {
            "returnAddress": {
                    "company": "SWM Inc.",
                    "addr1": "7654 Pine Street",
                    "city": "Highland",
                    "state": "MD",
                    "zip": "20777",
                    "countrycode": "US",
                    "phone": "000-000-0000",
                    "customssigner": "Customer Service"
            }
    },
    "WEST-DC": {
            "returnAddress": {
                    "company": "SWM Inc.",
                    "addr1": "4321 Oak Street",
                    "city": "Vista",
                    "state": "CA",
                    "zip": "92081",
                    "countrycode": "US",
                    "phone": "000-000-0000",
                    "customssigner": "Customer Service"
            }
    },
    "WALMART": {
            "returnAddress": {
                    "company": "Walmart.com",
                    "addr1": "1901 SE 10th St",
                    "city": "Bentonville",
                    "state": "AR",
                    "zip": "72712",
                    "countrycode": "US",
                    "phone": "000-000-0000",
                    "customssigner": "Customer Service"
            }
    }
}

The BOL Material Class element is represented with a JSON object and represents system-wide defaults for the National Motor freight Code (NMFC), Commodity Description, and Commodity Freight Classification to be listed on the BOL for shipments under this Division unless Item-specific data is set. An example is shown below:

{
"item_nmfc": "100240",
"item_classification": "100",
"item_commodity": "METAL/IRON/GLASS"
}

Classification¶

Usage:

Examples:

Ownership of Inventory¶

Usage:

Examples:

Workstation¶

Usage:

Examples:

Below is a sample Workstation Definition for LOV Attribute 2:

{
"printer_pdf": "49600",
"printer_raw": "49604",
"scale_id": "5637",
"scale_name": "toledo",
"start_bin_id":"DOCK.2",
"work_zone":"ZONE-A"
}

Status¶

Usage:

Examples:

Carrier Service¶

Usage:

Examples:

Container¶

Usage:

Examples:

Below is a sample Container Definition for LOV Attribute 2:

{
 "length": 16,
 "width": 12,
 "height": 1,
 "packfactor": 0.80,
 "tare": 0.65,
 "id": "52654"
}

Length, width, and height are the external dimensions of the container type. The pack factor defines the maximum cube utilization (0.0 - 1.0) for the container when considering all typical packing materials required for this container type. Tare is the empty weight of the container (used any time a weight check is used). The “ID” is optionally used to identify the container type’s internal id assigned in the ERP.

Adjustment Types¶

Usage:

Examples: