5. Bulk Wine and Aging Profiles
Easily navigate and configure your work-in-process and aged items with Claret. Make the most of our simple hierarchy for WIP items and follow our comprehensive steps to get set up quickly.
So now we know what you sell and who you sell it to. If you use the Make or Farm Modules, you will need to perform some additional setup steps to ensure all your bulk wine, vintage and aging details are connected correctly.
The first part of this is the Work-In-Process, or Bulk Wine, items.
The hierarchy for these items is already set up so that's a great start. The hierarchy can be seen on the 'Work in Process - aged' tab on the Item Hierarchy page.
We have the Parent Work In Process items and then their Child Work In Process items (generally used for the vintage level).
Routings and Item Properties
Work in Process items have a bit more information attached to them than Finished Good items.
For Parent WIPs, we need to know which vintage is the Current Vintage, and how long you age the WIP for,
For Child WIPs, we need to know the Vintage and when you plan to start agingw.
Within Claret, we also use Routings to manage aging periods. How you use these depends on how you manage aging.
First, we must set up the steps that may occur within your aging process. You may wish to break your aging process down into steps like ‘Time in Barrel’ and ‘Time in Bottle’, or just have one step for ‘Aging’.
To set up these steps, go to the 'Routing Steps' tab within the Routings page. Then add your required standard step(s) by going to the options (ellipses) button in the top right and selecting 'Add Routing Step'. The example below shows a 'Barrel age' and 'Bottle age' set of steps, but you can set up whatever works for you.
If you set up more than one 'Aging' step, not all steps have to be used in the aging profile (routing) of every wine. You can pick and choose.
Now that we have the steps set up, we can use these to build out the routings. There are a couple of ways to do this, depending on how you manage your aging profiles.
If you manage your aging profiles based on the type of wine, we can set up the routings now and then connect these to your bulk wine items later. If you want your routings to be automatically set up when we create your items, then jump down to Setting up WIP Aged Items.
To set up routings now, go to the Routings tab on the Routings page.
The above screenshot shows an example 'High-grade Cabernet Sauv' routing with 2 steps - 3 months in 'Barrel age' and 3 months in 'Bottle age' for a total routing/aging of 6 months.
To add your routings here, go to the 'Add Routing' option in the Options (ellipses) menu in the top right.
Here you can add a name and description for your Routing. For example, 'Standard Pinot Noir'.
Hit 'Save', and you will see the routing added.
You can now add steps to the routing by first expanding out the row and then selecting the + button.
You will need to indicate a sequence number - this is the order in which the steps will occur, and indicate how long this particular aging step will take. Continue to add steps as required by your routing profiles.
Subsequent routings can be added by repeating the steps above.
Setting up WIP Aged Items
Now that we understand the WIP Hierarchy and have set up Routing Steps and possibly Routings, you can set up the WIP Items themselves.
Let's start with an example. Let's look at the FNE St Lucia Pinot Noir. We have Bulk Wine which we will identify as FNESLPNO (this is our Parent WIP), and then a Child WIP for each vintage.
For each Child WIP, we need to know:
which Routing to use (in our example, we'll use the aging steps and Pinot Noir routing we set up earlier)
the 'Age Start' date
the Vintage (you can see these up on the 'Vintages' page, or we can create them for you on Item import.)
And for the Parent, we need to know the Current Vintage.
So the data, in tabular form, would look like this (scroll to the right for all columns):
| Parent WIP | Parent WIP Description | Current Vintage | Child WIP | Child WIP Description | Routing | Vintage | Age-Start |
|---|---|---|---|---|---|---|---|
FNESLPNO | FNE St Lucia Pinot Noir | 2022 | FNESLPNO21 | FNE St Lucia Pinot Noir 2021 | Standard Pinot Noir | 2021 | 2022-01-01 |
FNESLPNO | FNE St Lucia Pinot Noir | 2022 | FNESLPNO22 | FNE St Lucia Pinot Noir 2022 | Standard Pinot Noir | 2022 | 2023-01-01 |
FNESLPNO | FNE St Lucia Pinot Noir | 2022 | FNESLPNO23 | FNE St Lucia Pinot Noir 2023 | Standard Pinot Noir | 2023 | 2024-01-01 |
FNESLPNO | FNE St Lucia Pinot Noir | 2022 | FNESLPNO24 | FNE St Lucia Pinot Noir 2024 | Standard Pinot Noir | 2024 | 2025-01-01 |
Or, if you did not set up your routings earlier, replace the 'Routing' column with a column for each of the Routing Steps you created earlier, and a value, in months, for how long the wine will be aged at that step.
| Parent WIP | Parent WIP Description | Current Vintage | Child WIP | Child WIP Description | Barrel Age | Bottle Age | Vintage | Age-Start |
|---|---|---|---|---|---|---|---|---|
FNESLPNO | FNE St Lucia Pinot Noir | 2022 | FNESLPNO21 | FNE St Lucia Pinot Noir 2021 | 3 | 4 | 2021 | 2022-01-01 |
FNESLPNO | FNE St Lucia Pinot Noir | 2022 | FNESLPNO22 | FNE St Lucia Pinot Noir 2022 | 3 | 4 | 2022 | 2023-01-01 |
FNESLPNO | FNE St Lucia Pinot Noir | 2022 | FNESLPNO23 | FNE St Lucia Pinot Noir 2023 | 3 | 4 | 2023 | 2024-01-01 |
FNESLPNO | FNE St Lucia Pinot Noir | 2022 | FNESLPNO24 | FNE St Lucia Pinot Noir 2024 | 3 | 4 | 2024 | 2025-01-01 |
You can set up each of your bulk wine items one by one using the process described in the Items section, but selecting the 'Default WIP Aged Hierarchy' to build your tree. You will notice you are asked to add the Vintage and aging data as you drag WIP items across from being 'Unassigned' and into the tree.
However, you can also provide us with a file to load your WIP items. The sheet will be structured in the same way as the tables above. Here is an example for you to use as a starting point, however, you can replace the 'Routing' column with your Routing Steps columns if you have not yet created any Routings (as we did in the second table above).
Last updated
