GroovePacker lists orders which are imported but not scanned in a clear and obvious way so that it's easy to verify that everything which gets imported, gets scanned. Occasionally there are some orders which may not require scanning for some reason, so they must be handled in another way so they do not build up in the "Awaiting" list.
There are 3 options for these orders:
Their status can be changed to "Scanned" manually, which removes them from the awaiting list and prevents them from getting re-imported in the future. This is done by selecting the order in the orders list, then choosing "Scanned" from the Status drop down. This change and the user who made it is logged in the order activity log.
They can be marked cancelled in GP. This also gets them out of the awaiting list and prevents them from getting re-imported. This option does not remove their items from inventory.
Lastly, if orders that do not need scanning are a regular occurrence, it is best to avoid importing these orders into GroovePacker. This may be possible with a workflow change or by using the GP Ready tag to select only those orders that should be imported and scanned.
One final thought. In general, you want to ensure that every shipment is correct. Depending on the situation it may be possible to scan these "exception" orders like the rest, even if it requires adding barcodes for cases or using some type of workaround. One interesting option for orders that can not be scanned item by item is to use the SCANNED action barcode. To start the order would be cued as usual. The user could then review the order and mark it scanned by scanning the SCANNED action barcode. This would be logged differently so it would be clear if the order was scanned normally or if this function was used. This would move the order to the scanned status and give the user a chance to review the order items and receive notes related to the order even though the items are not scanned.