Tip #145 – Adding Recipes


Tip #145
Adding Recipes in flowerSoft

One of the things you may want to do if you are going to be using flowerSoft’s wedding module is enter the recipes for your favorite bouquets.

Here is how.

From the Manager’s menu, got Utilities and from there to User definable Codes & Settings.
From there you can access the Recipes menu.

recipe01

recipes02

When you select the “Add Recipes” option, the following screen opens up:

recipes04

Let’s analyze the different elements of the recipes screen.

#1 – Every recipe must be associated with an item description code.  This would be the recipe ID or code.
So if you are entering a recipe for a floral bouquet, you might want to give it a code like WB001 or something similar.
If the item code does not exist in the item description codes database, flowerSoft will inform you that it does not exist and ask you if you want to add it to the database.

recipe05

If you have made a mistake while entering the code, you can then correct it or if not, you can go ahead an add a new item description code.
The point is that every recipe must be associated with an item description code via their mutual ID.  So, if you have a recipe ID of WB001 you must also have an item code WB001.
The opposite is not true since you do not have to have a recipe for every item code you have in your database.

#2 – The quantity field must always be filled.  If you just want to use a line to enter a comment, enter a zero in the quantity field.

#3 – The item code field can be left blank but if you fill it, it will be checked against the item description codes database and if found, the description field will be automatically filled with the description of the item description code.

#4 – The description field must always be filled.  You can have a zero in the quantity field and no item code in the item code field but you must have a description in this field.

#5 and #6 – The size and color fields are optional fields and they do not have to be filled.

#7 – The notes area consists of 4 separate lines.  You can use this are for designer instructions or for other any purpose.  These lines do not have to be filled.

#8 – The image path field is also optional and does not have to be filled.  However, if you want to associate an image with the recipe you have to adhere to certain rules.
The image must be a .jpg file and it must reside in a folder inside the \FSROOT\IMAGES\RECIPES folder.  flowerSoft will only et you enter the name of the file (without the .jpg extension) in this field.
If an image name is entered for a recipe and the recipe is used in a wedding consultation section, the image will be available for viewing from the wedding consultation screen.

Note: If you go into a wedding consultation section that does not have a recipe associated with it, once finished entering the items for that section, flowerSoft will ask you if you want to save the items entered as a recipe.  If you answer “Yes”, flowerSoft will ask you to give the new recipe a code and save the items you’ve entered for that section.  This recipe will then be available for future use in other wedding consultations.  We will go into this in more detail when we talk about wedding consultations in a future post.

So this is how you enter recipes in flowerSoft.  Recipes can be used to describe in detail any produced item you offer, not just in wedding consultations.
Some flowerSoft customers use recipes extensively and use them to control inventory and costs.

recipes05

When used in conjunction with the “Bill of Materials” used program, it can be a useful tool to also make sure orders are filled to value.
More on the “Bill of Materials” program in a future post.

If you have any questions or comments, please let me know.

1 thought on “Tip #145 – Adding Recipes

  1. I received a comment on this post which read:

    “George, thank you for this useful post. Is there a limit on the overall number of item codes that can be created? That is, in your example, you used the hypothetical code W0001. Since for most weddings we do the arrangements are custom-made and completely unique and would, therefore, not follow an already created recipe. Could we create a unique item code for each wedding bouquet we are creating? For example, instead of W0001, could we create a code based on the bride’s name (e.g. MICHLIG01, MICHLIG02, JOHNSON15 etc.)? Or would that create too many item codes?”

    Here is my response:

    “The problem is not creating too many item codes as much as staying within the 5 characters limitation of a recipe ID, which is also the limit for an item code.
    There is just not enough space to do what you propose.

    5 characters allow you to have 658,008 different combinations, so in theory you could have that many item codes and recipes.

    You could try using the bride’s initials instead, so for example, if the bride’s name is Mary Smith you could use MS001. This would give the ability to have you 999 different codes for each set of initials (1000 if you use MS000).

    There is always the remote possibility of running out of numbers for brides with the initials of MS. Even if you had 3 weddings each week for brides with those initials, it would take you over 6 years to run out of numbers.

    In your case however, since each one of your bouquets is unique, there is no need to keep those recipes around for future reference, so you can delete them after a while and then re-use them as needed.

    In other words, what I’m saying is that if and when you enter a recipe for item code MS999, you could go to the recipe database and delete, let’s say recipes MS001 through MS500 and then be able to have 499 more recipes available for brides with the MS initials.

    I hope I’ve explained myself clearly, if not let me know and I’ll try again.”

    Like

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s