Monthly Archives: December 2013



I’ve run out of ideas on how to improve flowerSoft so please, unless you think flowerSoft is perfect as it is, send me a suggestion on how to implement something you feel flowerSoft lacks and I’ll try to incorporate.

Otherwise, I’ll spend my time updating the manual.



Unless otherwise notified, I will be upgrading all flowerSoft customers in good standing to the latest flowerSoft 2014 version during the next couple of days.

Please make sure you take all your computers to the desktop before leaving at night.
Do not leave them in a flowerSoft menu.

If you do not want to be upgraded, please notify me asap.


New Feature Revised

flowerSoft Silver 2014 has a new feature that lets you add item codes on the fly.  In other words, from the new orders entry screen.
Some of you did not like that new option or at least the additional question that it required.  I’ve modified the program to make this an option that you, as the manager, can turn on or off.

The new version used to work like this…


If you did not entered the item code exactly as it was in the database, flowerSoft would ask you if it was a new item code, with the default answer being “N” for no.

If you answered “Y”es, flowerSoft will let you continue addition the description and unit price for the item.


Then it would save the new item code so the next time you went into the item code field, the new ite just added would be available.


Since some of you did not like this new option, I’ve made it a choice in the control file…


If you have this option as “No”, do not allow adding of item codes on the fly, flowerSoft will behave as it used to on version 2013 and that is by selecting the item code that was highlighted just before you hit you hit Enter, which on the first screen-shot would have been the ARB item code.

If you select to have this option as “Yes”, flowerSoft will allow you to add new item codes on the fly as shown on the screen-shots above.


As some of you may or may not know, flowerSoft uses a database called filePro as a backend.  This database is what stores your data and makes it accessible to you via screens and reports that I am able to create using it.

The creator of this database, which was originally called the Electric File Clerk in 1978, was a Brooklyn-born young man named Howard Wolowitz.
In 1979, Howard founded the Small Computer Company
Bill Prady, the co-creator of the show called the Big Bang Theory, worked as a programmer in the 1980’s for Howie’s Small Computer Company.

I do not watch the show but I understand it is extremely successful so, for those of you who do watch it, here are a couple of pictures of the “real” Howard Wolowitz.


The TV Howard Wolowitz


The real Howard Wolowitz during a cameo on one of the shows.


The real and the TV Howard Wolowitz.

My wife, who is also from Brooklyn, was a good friend of Howie’s sister Ruth and her brother was also a friend of Howard.
Although we are not close friends by any means, I’ve had the pleasure of meeting Howie on several occasions.

Solution to Identical Credit Card Transactions Problem

I’ve come up with a solution to the problem.

The solution will allow you to charge your customer’s credit card again for the duplicate transactions you did not get paid for.

This solution requires you to get approval from your customer to charge the card for the transactions you did not get paid for, but does not involve Merchant Warehouse and trying to obtain the credit card numbers from them.

If you are interested in this solution, let me know and I’ll install it in your system and explain to you how to use it.

Identical Credit Card Transactions (Cont.)

Identical Credit Card Transactions (Cont.)

Here are a couple of report that you should run every day to make sure you are getting credit for all your credit card purchases.

As usual, these reports are found in the Manager’s menu.  Follow this path M > R > A > C > E





The total of this report is what should have been deposited to your account on 12/19/2013.

If it is not, some deduction for a duplicate transaction must have taken place.

This report can be run for any date period but I recommend running it for one day at a time to make it easier for you to check.

This report should be used in conjunction with the Identical Credit Card Transactions report posted previously.

You can get the report above by following this path: M > T > 2

Here it is again…


Hope this helps.

Identical Credit Card Transactions

Identical Credit Card Transactions

OK folks, the problem is real and it has definitely affected you.

The problem is not with Merchant Warehouse’s program but with First Data, the clearing house.  They are seeing those identical transactions as duplicates and not paying you for them.

How?  They are deducting the money from what they consider to be duplicate transactions from the next day’s money they deposit in your bank, so it might be hard to see if you do not check that deposit every day.

I don’t know when this problem will be fixed, but until it is you should check your batch deposit every day.

To get paid for the transactions they did not credit you for, you have to go the your Merchant Warehouse Portal and create “Forced Sales” for each of the transactions you did not get paid for.


The problem here is getting the credit card number from Merchant Warehouse if you cannot get it from the customer.  Merchant Warehouse will not give you the credit card number unless you have the approval number.  The problem is that approval numbers go away after 30 days, so if they do not have the approval number they cannot help you.  That is why it is imperative that you check these deposits every day.

You should print the report of identical credit card transactions and call Merchant Warehouse with the information provided in the report so that they can provide you with the credit card number used if at all possible.

Otherwise your only other recourse is to call the customer and try to get the information from them and then enter a new order for the same amount.