Let's suppose you have a number of items that can be sold as retail items or as tester items. The tester items are the same physical product but the packers will need to adhere a "tester" sticker or prepare the item in some way, so they need to distinguish the tester version from the regular version.

So we have two versions of the same item, each with their own SKU, but the barcode is the same and you need to distinguish them.

Here are two other cases where this approach would not be used:

Case 1

If instead, you have the same item sold under two different SKUs, same barcode, and you do not need to distinguish between them then you likely just need to Alias the items, which is to bring all the SKUs together into the same product record so the barcode can be shared. That is covered in this article on Aliases.

Note: If the SKU is different but the barcode is the same, it is possible to Alias the tester and regular versions of the SKU together into the same item allowing them to share a barcode but there would be no indication to the packer that a tester was ordered and GroovePacker could not distinguish between the items.

Case 2

If a separate SKU and barcode are to be used for the tester and the tester SKU appears as the line item in the order, then there is no need to take the steps below. You can simply set the tester up as a separate product.

In this instance it is assumed that barcode for the tester item is the same as the barcode for the regular item and the SKU is different. We are hoping to differentiate the regular SKU and tester SKU, even though they share the same barcode.

As it turns out there is a novel way to set this up.

Keep in mind this solution can only work if the SKU of the tester item that appears in the order is not the same as the SKU of the regular item. It is this difference that will allow GroovePacker to differentiate between the two items.


 1- The regular version of the item will not need to be modified. It will be set up as usual. 

2- The Tester version will need to be created and it's actual sku will be assigned. It's barcode will be a copy of the SKU. (This placeholder barcode will not actually be scanned) 

3- The tester version SKU is then converted to a Kit. Two items are added to the kit. The first is the regular version of the item. The second is a "generic tester item". This will be a regular product created separately. It can be named anything you like and any SKU and barcode can be assigned. In this example, we'll enter "TESTER" for both the SKU and the barcode.

This TESTER barcode can be printed out and posted near the packing station. You might choose to incorporate the barcode into the Tester label that goes on all tester products, or you might instruct packers to use the Click-Scan option rather than scanning.


When one of the tester items shows up in an order the packer will need to scan the barcode on the regular version of the item AND the TESTER barcode to confirm it is a tester product and the sticker is being added.