Skip to main content

Aliases for brands and packages

Teaching Tagify how to read incoming item descriptions let's you:

Alias diagram

What's an alias?

In our case, an alias would be another name for a brand or package. Let's take this item description as an example:

LAGUNITAS IPA 4/6/12NR

LAGUNITAS IPA would be an alias for our (assuming we've got it set up) Lagunitas IPA brand. 4/6/12NR would probably be an alias for our 6pk Bottles package.

We would then edit our brand to add our Brand aliases. We would do the same for our Package aliases.

Now, anytime Tagify encounters that item description, it's going to know exactly what to do with it.

Example #1: Importing via Excel

Let's say we're importing this sheet (check out Import/Export via Excel for more info):

#Item DescriptionPrice
1LR RANCH RITA CLASSIC 4/6/12CN
3LAGUNITAS IPA 4/6/12NR12.99

Tagify is going to read that Item Description column to try and figure out what brand and package to use for our tag. It reads the first one LR RANCH RITA CLASSIC 4/6/12CN and we might not have LR RANCH RITA set as an alias for our Lone River Ranch Rita brand. Tagify will skip that row.

But the next row is LAGUNITAS IPA 4/6/12NR and Tagify knows exactly how to read that one so it's going to make three Lagunitas IPA 6pk Bottles tags for $12.99.

You can see how useful this is when dealing with importing imperfect data.

Example #2: Syncing data from your RAS

Let's say you're Syncing pricing from your RAS and you've got something like this coming in:

Item KeyItem DescriptionUPCRetail
33444LAGUNITAS IPA 4/6/12NR72383000009412.99

Assuming we don't already have item #33444 setup, Tagify is going to automatically create new brand data with that item # and UPC to create that tag. So there's no need to have to manually setup item #'s anymore as long as we keep our brand/package aliases up to date.

The goal is for you not to have to touch Tagify every single time there's a new item; just when you've got a completely new brand or package.