The focus of this manual so far has been on the "Standard Retail" module, which is the most commonly implemented module of MicroBiz. MicroBiz also offers several different types of business setups to choose from, called modules. This chapter will cover the various MicroBiz modules and give information on how they differ from the Standard Retail module.

List of Available Modules

  1. Standard Retail Business
  2. Standard Service Business
  3. Another Service Model
  4. Marina/Boat Yard
  5. Shoe Store
  6. Pet Business
  7. Bike Business
  8. Liquor Business
  9. RV Controller

Figure 16-1

Some modules can be loaded at any time, and some require a special Keyblock or other authentication. For information on obtaining a specific module that you don't currently have access to, please contact Sales at (702) 749-5353 Option 2.
In addition to each business type, there are "Easy" and "Plus" versions available for most modules. For the extra options available using a "Plus" version of MicroBiz, see Chapter 10 - Accounts Receivable.
The next section will give a brief description of each module and cover the differences between each and the Standard Retail module, as well as describe how the module is loaded. 

Standard Retail Business

This is the most commonly used module, and the primary focus of this manual. With the correct Keyblock, it is selected first at installation, but can be loaded later by choosing the first option under Management | Custom System Settings | Business Type Settings

*All other modules (found below) will be described in comparison to the Standard Retail module. 

Standard Service Business

The Service modules are used primarily by businesses with a need to track the services performed on specific "units" (such as a car or computer). This is done with the use of additional database files that track units per customer. See the section on "Customize Transaction Settings" under the "Service" tab in Chapter 3 - Customizing Your Software for more information.
With the correct Keyblock, this module is selected first at installation, but can be loaded later by choosing the option for "Standard Service Business," or "Another Service Module," under Management | Custom System Settings | Business Type Settings.

If you have multiple workstations, it is important to only use one module at a time. If you switch to the Standard Service module on one workstation, make sure to do the same on all of your other workstations too!

Using Units
There is a section on the Front Register, just to the right of the item grid. "Customer / Product" panel, that displays unit information.

Figure 16-2

Once a customer is loaded, the first unit record will be displayed here (see Figure 16-2 above the total, on the right side). You can maintain as many unit records per customer as you would like, and you can switch records by clicking on the Edit/Add button. This will open a window where you can browse and edit or add records.

Most of the fields used to track units are customizable. This means that you can rename them and use them in a way that will suit your needs! The following section will describe each field available as follows:

  • Customizable or non-customizable field.
  • Appears on the Front Register or not.
  • Prints on service invoices or not.
    • Will mention all, none or some invoices. See section on service invoices below to verify if "some" is listed.
  • Updated by "Due Dates" window (see Figure 16-4 below).
  • Cust No. – Non-customizable field, displays the customer number currently selected.
  • Unique Tag – Customizable, displayed on both the Front Register and invoices.
  • ID # – Customizable, displayed on invoices only.
  • Vendor # – Customizable, not displayed.
  • Year – Customizable, displayed on both the Front Register and invoices.
  • Brand – Customizable, displayed on both the Front Register and invoices. 
    • This field is tracked by its own database so that you can manage
      your "brands" used and associate them with "models."

Figure 16-3

  • Model – Customizable, displayed on both the Front Register and invoices. 
    • This field is also tracked by its own database and is associated with your "brands."
  • Misc – Customizable, not displayed.
  • Start – Customizable, displayed on both the Front Register and invoices. 
    • This can be used with the "End" field to track time spent servicing a unit.
    • This field is updated using the "Due Dates" feature.
  • End – Customizable, displayed on both the Front Register and invoices. 
    • This can be used with the "Start" field to track time spent servicing a unit.
    • This field is updated using the "Due Dates" feature.
  • Cross – Customizable, not displayed.
  • Mfg Date – Customizable data field, not displayed.
  • Service note – Customizable, displayed on some service invoices. 
    • When printed, the line "Needs Service:" is displayed before the service notes.
    • This field is updated using the "Due Dates" feature.
  • Service note (2) – Another field, just like above, for entering notes.
  • Special – Customizable, displayed on some service invoices.
  • NOTE – Not customizable, displayed on some service invoices. 
    • This field is updated using the "Due Dates" feature.
  • Service Dates – These date fields are all customizable and will display on some service invoices. 
    • You can use the Service Due reports (found under Reports on the Main Menu) to track units with service due.
    • You can associate a SKU with each of these dates so that the Service Date is updated whenever that SKU is sold. For more information on this, please see the section on "Customize Transaction Settings" under the "Service" tab in Chapter 3 - Customizing Your Software.
  • Number of Units – Not customizable, not displayed. This displays the total number of unit records entered for this customer. 
    • Click on the browse button to see all saved unit records.
  • Remarks – Not customizable, not displayed.

 

There is a row of buttons at the bottom of the window. Here's what they do:

  • OK – This button is used when browsing (as opposed to editing) a record to load it.
  • Cancel – Used when browsing to close the Unit window without loading.
  • Save – Used when editing a record to save your changes.
  • Undo – Used when editing a record to cancel editing without saving your changes.
  • Next – Used when browsing to view the next unit record for this customer.
  • Prev(ious) – Used when browsing to view the previous unit record for this customer.
  • Delete – Used when browsing to delete the currently selected unit record.

Due Dates/Miscellaneous Info 
This screen appears when you choose F-9 Print from the Front Register. It allows you to enter some unit notes, which will update the currently selected unit record and possible print on your invoice.

All of the fields here have been covered in the Units section above. Note that the "other notes" field is the same as the "NOTES" field listed in the unit record.

Service Invoices 
There are a few invoices that are designed specifically for use with the service modules.

Figure 16-4

Invoice #19 – Standard Blank Service Invoice (80-col dot matrix) 
This is the basic full-page invoice for service module users. For a sample of this invoice, please refer to Chapter 3 - Customizing Your Software. The service data included on this invoice is:

  • Unit record fields:
    • Unique Tag
    • ID Number
    • Unit Year
    • Unit Brand
    • Unit Model
    • Start
    • End
    • Service Notes (both 1&2)
    • Special
  • Waiver
    • This is optional and can be enabled by choosing "Invoice Type" from the Tender screen (after choosing F9 and entering misc. notes) and checking "Print Waivers..."
    • The Waiver can be configured by choosing the Waiver button from the Tender screen.
  • Shop Fee
  • Separated Service/Product sections.
    • Also Separate "Labor"/"Items" subtotals.
  • Next Service date.

Invoice #20 – Yet Another Standard Blank Service Invoice (80-col laser) 
This is the recommended full-page service invoice. For a sample of this invoice, please refer to Chapter 3 - Customizing Your Software. The service data included on this invoice is:

  • Unit record fields:
    • Unique Tag
    • ID Number
    • Year
    • Brand
    • Model
    • Start
    • End
  • Waiver
    • This is optional and can be enabled by choosing "Invoice Type" from the Tender screen (after choosing F9 and entering misc. notes) and checking "Print Waivers..."
    • The Waiver can be configured by choosing the Waiver button from the Tender screen.
  • Shop Fee

Invoice #21 - Standard 40-column Service Invoice 
This is the recommended invoice type for service module users with 40-column printers. For a sample of this invoice, please refer to Chapter 3 - Customizing Your Software. The service data included on this invoice is:

  • Unit record fields:
    • Unique Tag
    • ID Number
    • Year
    • Brand
    • Model
    • Start
    • End
    • Service Notes (both 1&2)
    • Service Dates (1-4)
  • Shop Fee
  • Separated Service/Product sections.
    • Also Separate "Labor"/"Items" subtotals.

Tracking Hours
MicroBiz has the ability to track the hours spent on a job (see section on Technicians' Hours Report Below). To enable this feature:

  1. From the Main Menu, click on Management | Custom System Settings | Transaction Settings | Service tab.
  2. Check the option for "Track Actual Hours Spent on Job."
  3. When loading a service SKU to the Front Register, make sure to enter the Hours along with the Quantity.
    • The Hours field is used for tracking hours spent on the job, but does not affect the price of the service.
    • The Quantity field is used for calculating the price of the service. For example, if a service is priced at $10.00 and a quantity of 3 is entered, the extended price will be $30.00.

Service Reports
The service modules also include a couple of extra reports, which can be found under Reports from the Main Menu.
Service Due Report
Allows you to set a date range and get results on any customers that have units with service due. This report works best when associating services with SKUs from Management | Custom System Settings | Transaction Settings, under the Service tab.

Figure 16-5

Fields included:


    • Name
    • Address
    • Home Phone
    • Work Phone
    • Unique
    • Special
    • Service Needed
    • Service Notes

Technicians' Hours Report
See the section above on tracking hours with MicroBiz. This report will allow you to set a date range and load details on any hours recorded, grouped by technician.

Figure 16-6

This report will give subtotals per invoice per technician, and the grand total and average for all jobs within the date range specified. Fields included:

  • Date
  • Invoice Number
  • Description
  • Revenue
  • Hours
  • Revenue Per Hour
  • Technician
  • Job Code (SKU)

Another Service Business, Marina/Boat Yard, Shoe Store, Pet Business

These Service modules are essentially the same as the "Standard Service Business."
With the correct Keyblock, this module is selected first at installation, but can be loaded later by choosing the desired option under Management | Custom System Settings | Business Type Settings.

If you have multiple workstations, it is important to only use one module at a time. If you switch to one of the service modules on one workstation, make sure to do the same on all of your other workstations too!

Selecting one of these instead of "Standard" will change the unit record tags as shown in Figure 16-7.
Clockwise from the upper-left:

  • Another Service (for auto industry)
  • Marina/Boat Yard
  • Shoe Store
  • Pet Business

Figure 16-7

Bike Business

The Bike Shop Controller incorporates many of the features of the service modules, plus a few extra ones. For information on Unit Records, please see the section "Using Units" under the Standard Service Module above.
With the correct Keyblock, this module is selected at installation. A Bike installation is required as a special "BikeWin" Local Files path is created and used for this module.

If you have multiple workstations, it is important to only use one module at a time. If you select the Bike module on one workstation, make sure to do the same on all of your other workstations too!

 Figure 16-8

Assembly Status
Inventory items can be stored in this module as "assembled" or "unassembled" for the purpose of more accurate tracking. MicroBiz will track the total on hand quantity, and the assembled quantity is stored as a part of this total.

To set an item as "May Require Assembly":

  1. From the Main Menu, choose Inventory | Add/Edit Inventory.
  2. Select the desired inventory item and choose Edit.
  3. From the Stock tab, check the option for "May Require Assembly."
    • The field "Available Assembled" is now available.
  4. Enter the assembled quantity in the Available Assembled Field.
    • This quantity is not to exceed the total quantity listed under "Qty In Stock." The difference between these two figures is the unassembled quantity.
  5. Click on the Update button at the bottom of the screen to save your changes.

Once an item is set to "May Require Assembly," you will be prompted to choose Assembled or Unassembled when loading the item to the Front Register (Figure 16-9). If the item is sold as unassembled, only the "Qty In Stock" will be affected. If the item is sold as assembled, both the "Qty In Stock" and the "Available Assembled" quantity will be affected and you will have the additional option of entering a "Bike Tag."

Figure 16-9

The Bike Tag will be shown on the invoice and in Customer History. The assembly status is noted on the Front Register under the "As" column as "A" for Assembled or "U" for Unassembled. Items saved to a Work In Progress (WIP) retain their assembly status, and there is a report available to show WIPs along with the assembly status of each item. To view this report:

  1. From the Main Menu, choose Reports | Product Reports | Assembled/Unassembled.
  2. Choose the desired option from the Select Destination screen and your report will be loaded.

Bike Controller Front Register
There are a few extra features available on the Front Register for the Bike module.

Figure 16-10

  • The "As" column, as noted above, displays the assembly status of each item loaded to the Front Register.
  • The bike icon shown above will load the Bike-alog (see section below), if available.
  • The WIP and Layaway features can be accessed by their respective buttons at the bottom of the Front Register.

Bike Controller Invoices
The Bike module has simplified the invoice list to four options, two each for 80-column and 40-column printers.

Invoice #1 – Standard Dot-Matrix (80-column)

Figure 16-11
Invoice #2 – Laser (80-column)

 Figure 16-12

Invoice #3 – Standard (40-column)
This invoice is identical to Invoice #9 as seen in Chapter 15 - Invoices.
Invoice #4 – Standard (40-column)
This invoice is identical to Invoice #5 as seen in Chapter 15 - Invoices.
Bike-alog Import
The "Bike-alog" is a third-party bike industry database. This database can be loaded from the Bike module and its contents can be imported directly into your system. For more specific information about Bike-alog, see their website at www.bikealog.com.
You can launch the Bike-alog from the Front Register by clicking on the bike logo from the top of screen as seen in Figure 16-10.
To import data from Bike-alog into MicroBiz:

  1. From the Main Menu, choose Management, Import/Export Data, Bike-alog Import, Import Data.
    • Your inventory items should now include data from your Bike-alog.

Liquor Business

The Liquor Controller incorporates many of the features of the retail modules, plus a few extra ones.
With the correct Keyblock, this module is selected at installation by choosing option 5 for the MicroBiz Server and option 6 for an additional workstation. A Liquor installation is required as a special "LiqWin" Local Files path is created and used for this module.

If you have multiple workstations, it is important to only use one module at a time. If you select the Liquor module on one workstation, make sure to do the same on all of your other workstations too!

Importing Liquor Data
The Liquor module includes a liquor database (liqdata.dbf, with over 7500 items) that can be be imported into your inventory. The prices and quantity will not be imported, but can be entered after importing. The system will prompt you for a price the first time each item is loaded to the Front Register, and the price entered will be stored in your system for future use.
To import the Liquor Database into MicroBiz:

  1. From the Main Menu, choose Management, Import/Export Data, Import Liquor Data.

Using Aggregate SKUs
The Liquor Controller has a unique feature in MicroBiz that helps you manage items that can be sold in various packages. Consider a 6-pack of beer: you can sell the 6-pack, an individual beer from the pack, or an entire case of 6-packs. This feature enables you to link these items together for better control and tracking abilities.
The idea here is to create one "main" or "aggregate" SKU for an item that is sold as a "pack," and then have associated SKUs when selling either a unit out of the pack or an entire case of packs. Here are a couple of examples:
Example #1: A 6-pack of beer

  • The item is entered into inventory with the SKU for the 6-pack.
  • A "singles" SKU is created so that one beer out of the 6-pack can be sold (thus breaking up the 6-pack into 6 individual beers).
  • A "case" SKU is created so that an entire case of these 6-packs can be sold.

Example #2: A pack of cigarettes

  • The item is entered into inventory with the SKU for the pack of cigarettes.
  • A "singles" SKU is created so that one cigarette out of the pack can be sold (this breaking up the pack into 20 or so individual cigarettes).
  • A "case" SKU is created so that a carton of these packs can be sold.

Fast Add Data Fields
The easiest way to setup a new inventory item with this feature is to use the "Fast Add" method. A sample walkthrough is provided below, but first let's take a look at all of the data fields available:

Create a new item from the Main Menu by choosing Inventory, Add/Edit Inventory, Fast Add.

  • SKU – Enter the "aggregate" SKU here. In Example #1 above, this would be for a 6-pack of beer.
  • Brand – Enter the brand here. This is used for grouping items in certain reports by their Brand.
  • Description – Enter the description here
  • Size – Enter the size, if applicable.
  • Qty per Case – Enter the number of aggregates (packs) per case. If the main SKU is for a pack of cigarettes (Example #2 above), then it might be 10 packs per carton.
    • Leave this field empty or enter 0 to disable the use of cases for this item.

Don't enter the number of single items per case, but the number of "packs" or whatever unit you're using for the main SKU per case.

 Figure 16-13

  • Qty per Pack – The number of single items per "pack" (main SKU). In Example #1 this would be 6, as there were 6 beers to a 6-pack. In Example #2 this would probably be 20, as there are normally 20 cigarettes to a pack.
  • Order by Case – Check this box if this inventory item will be ordered by the case. This works just like previous versions of LiquorBiz. If left unchecked, it is assumed that you order by the main SKU (like by a 6-pack or single pack of cigarettes).
  • Cost per Case – Enter the cost per case of this item.
  • Department – Enter the department for this item, if applicable.
  • Unit Cost – Enter the cost for the aggregate (main) SKU here. For Example #1, this would be the cost per 6-pack, as you can have a separate cost per Case of 6-packs.
  • Taxable – For Tax1, enter Y for Yes or N for No.
  • Qty On Hand – Enter the number of aggregates (main SKU) you will start with. In Example #2 this would be packs of cigarettes.
  • Loose Qty –This is the number of single items that have broken off of the aggregate SKU. In Example #2 this would be how many individual cigarettes you have outside of a pack.
    • This number should always be less than the Qty per Pack.
  • Reorder – Enter the reorder level here as usual.
  • Taxable2 – For Tax2, enter Y for Yes or N for No.
  • Normal Stock – Enter the normal stock level for the item.
  • Vendor SKU – Enter the SKU used by the vendor, if applicable.
  • Price – Enter the price for the aggregate (main) SKU.
  • Vendor Code – Enter or Browse to the vendor for this item.
  • Price B – Enter the Price Level B figure here.
  • Charge Deposit – Check this option if you want LiquorBiz to charge a bottle deposit for this item.
  • Case Price – Enter the price to charge when a Case is being sold at the Front Register. This could be the aggregate Price multiplied by the Qty per Case, or a different price if desired.
  • Deposit Amt – Enter the deposit fee per aggregate (main SKU) here. In Example #1, this could be .30 if the bottle deposit is 5 cents per bottle with 6 bottles per pack.

LiquorBiz will automatically calculate the deposit for Singles or Cases based on this figure.

  • Case Barcode –Enter a different SKU for this item when sold as a case.
    • If you don't have a separate barcode for a case of this item then it is recommended to add a case SKU by entering "C" here (without the quotes) and then the main SKU. In Example #2, if your pack of cigarettes uses SKU "123456," then a carton could be sold by entering "C123456" at the Front Register.
  • Singles Barcode –Enter a different SKU for this item when a single item from the aggregate is sold.
    • If you don't have a separate barcode for singles of this item then it is recommended to add a singles SKU by entering "S" here (without the quotes) and then the main SKU. In Example #2, if your pack of cigarettes uses SKU "123456," then a single cigarette could be sold by entering "S123456" at the Front Register.

Edit Product Data Fields
The next page outlines what the data looks like when editing the item and where these new options are stored.

The "SKU" field shown below is for the aggregate entered using Fast Add.

Price Levels tab

  • The Deposit Amount for the aggregate is shown here.
  • The Case Price is located at the bottom of this tab.

Figure 16-14

Stock tab

  • Quantity In Stock refers to the number of complete aggregates on hand. When a "single" is sold, it breaks an aggregate up into Loose Quantity until the loose quantity reaches 0 (at which point it breaks up another aggregate).
  • Quantity per Case can be edited here. 
    • The (2+2 In Stock) displayed to the right notes the number of cases on hand.
Figure 16-15

    • The first digit is the number of cases, the second is the number of loose aggregates (2 cases + 2 packs would equal 10 aggregates, because 2 cases [at 4 packs per case] is a total of 8 packs).
  • Quantity per Pack can be edited here.
  • Loose Quantity shows the number of "singles" that are currently available. If this number is 0, then the next time a Singles SKU is loaded, an aggregate will be broken up by the Qty per Pack figure. The remainder of "loose" items will be displayed here.
  • Brand can be edited here. Note that this field is also displayed under the Misc. tab.

 

 

Misc Fields, Barcodes tab

  • Brand is displayed here also.
  • Case Barcode can be edited here.
  • Singles Barcode can be edited here.
Figure 16-16

Walkthrough For Creating a New Item
Follow this example to create a 6-pack of beer:

  1. From the Main Menu choose Inventory, Add/Edit Inventory, Fast Add.
  2. Fill out the data fields as shown in the image to the right.
  3. Click on the Save button when finished.
  4. Choose Yes to save, then No to skip adding another record.

Figure 16-17
Walkthrough For Selling Items
After creating your aggregate item from the example above, this example will show you what to expect when selling these items:
Figure 16-18

  1. From the Front Register, enter your 6-pack SKU: BEER001.
    • Nothing special here, the item should load as any other item would.
  2. Now enter your Singles SKU for this item: SBEER001.
    • Notice the extra description of (Each).
    • The Price here is the aggregate Price divided by the Qty per Pack.
    • The Deposit here is the aggregate Deposit Amt divided by the Qty per Pack.
  3. Now enter your Case SKU for this item: CBEER001.
    • Notice the extra description of (Case).
    • The Price here is set by the Case Price field when creating the item.
    • The Deposit here is the aggregate Deposit Amt multiplied by the Qty per Case.

Assuming the Qty On Hand before this sale was 10, lets look at the Stock tab after the sale:
Figure 16-19

  • In the previous example, 1 6-pack, 1 beer and 1 case were sold.
    • That's a total of 5 6-packs plus 1 beer.
  • The Qty In Stock (of aggregates, or in this example 6-packs) is now 4.00.
    • There were 10 6-packs to begin with.
    • 5 6-packs were sold.
    • 1 6-pack was broken up into individual beers so that the single could be sold.
  • The Loose Qty is now 5.
    • Since 1 aggregate was broken up into single beers, there are 5 beers left out of 6-pack because 1 was sold.

Reports
Different reports in MicroBiz shown here vary in their methods for representing this data. The following examples cover the important variations.

In the examples below, one sale was recorded (the same as shown in the example above). One 6-pack, one single beer from the same SKU, and one case of 6-packs were sold on the same invoice. A Close Out was performed immediately afterwards.

Exception Report

  • This is an 80-column Close Out report.
  • An entry appears here any time a Singles or Case SKU is used.


     Figure 16-20

Products Used

  • This is an 80-column Close Out report.
  • Each aggregate/singles/case SKU used is listed here separately.


     Figure 16-21

Product List by Margin & Markup

  • This is an Inventory Report.
  • The Cost listed here is the current Weighted Unit Cost.
  • The Price is $10.00, which is the price for one aggregate.


     Figure 16-22

Product List/Qty On Hand by SKU

  • This is an Inventory Report (by SKU with "New Format" checked).
  • The Price is that of the aggregate SKU.
  • The "Qty C+U, L" displays the quantity for the cases, aggregates and loose quantity respectively. 
    • There is a total of 4 6-packs and 5 loose beers, so... 
      • "C" = 1 (4 6-packs per case)
      • "U" = 0 (no extra 6-packs outside of the 1 case)
      • "L" = 5
  • The Cost is displaying the current Weighted Unit Cost.
  • The QTYxCOST is showing $24.17, which is the Weighted Unit Cost of $5 times all quantity on hand (including Loose quantity).
  • The Total Retail Value is $48.33... this represents the 4 6-packs but leaves out the 5 loose beers.
  • The Total Cost of Goods is the same as the QTYxCOST.

     Figure 16-23


Product List by SKU

  • This is an Inventory Report (by SKU with "New Format" unchecked).
  • The Quantity is displayed with the C+U,L scheme as outlined above.
  • The Cost is $5.00, which is the current Weighted Unit Cost.
  • The Price is that of one aggregate.
  • The Total Cost of Goods is showing $24.17, which is the Weighted Unit Cost multiplied by all quantity on hand (including Loose Quantity).
  • The Total Retail Value is showing $48.33, which is the current aggregate Price multiplied by all quantity on hand (including Loose Quantity).
  • These Inventory Reports are essentially the same (with extra groupings): 
    • Product List by Brand
    • Product List by Department
    • Product List by Description
    • Product List by Style
    • Product List by Vendor

       Figure 16-24

Employee Report

  • This is a Sales Report (by Employee).
  • Each use of an aggregate/singles/case SKU is listed here separately.

     Figure 16-25

Brand Sales Report

  • This is a Sales Report (by Brand).
  • Each use of an aggregate/singles/case SKU is listed here separately.
  • These Sales Reports are essentially the same: 
    • Department Sales Report
    • Style Sales Report
    • Vendor Sales Report

       Figure 16-26

Vintage
The Standard Retail module several categories used for organizing inventory: Department, Style, Size, Color. The Liquor controller replaces the Color category with "Vintage."
Bottle Deposits
The Liquor module can help you manage deposits for bottles and cans. You can can set a deposit amount for every or each inventory item, and process deposit returns.
To enable bottle deposits:

  1. From the Main Menu, choose Management | Custom System Settings | Transaction Settings.
  2. Choose the Liquor tab from the top of the window.
  3. Make sure that "Charge Deposit for each Sale" is enabled.
  4. Set the "Default Deposit Amount" as desired, then click on the Save button to save your settings and exit this window.
    • This will be the default deposit amount for all items and used when returning deposits from the Front Register.  Leave this set to 0.00 if some items will not be charged a deposit.
  5. Choose Inventory | Add/Edit Inventory.
  6. Select the item desired and choose Edit.
  7. From the Price Levels tab, check the option for "Charge Deposit."
    • The "Deposit Amount" should display the Default Deposit Amount.
    • This amount can be changed for this item using this field.
  8. Click on Update when done to save your changes and exit this window.
  9. Enable the "Charge Deposit" option for any other items desired (this can also be done when first entering the item into inventory).

Once deposits are enabled for the items of your choosing, the deposit will automatically be calculated as a tax-free charge on the Front Register.
To return bottle deposits:

  1. From the Front Register, enter "REF" (without quotes) into the SKU box and press enter.
  2. Enter the number of bottles to return and press enter.
  3. Enter the deposit amount per bottle.
  4. You can edit the deposit rate and/or quantity if needed by choosing F6-Edit and selecting the line number to change.
  5. When finished, choose F9-Print to complete the deposit return.

To generate reports on bottle deposits:

  1. From the Main Menu, choose Reports | Bottle Deposits.
  2. Enter the date range desired.
  3. Choose the output type desired on the Select Destination window.
    • The report will display bottle deposits collected and returned, grouped by month.

Liquor Controller Front Register
The Front Register here is customized for the Liquor Module. The current date is displayed at the top of the screen, along with the latest birthdate fitting the legal drinking age of 21.
Figure 16-27
The bottle deposits will be displayed, if applicable, in their own column on the Front Register. Deposits are also totaled at the bottom of the screen after taxes.

Liquor Controller Invoices
The Liquor module has simplified the invoice list to four options: one for 80-column and three 40-column printers.


Invoice #1 – Standard 40-column (recommended)
Figure 16-28
Invoice #2 – Standard 40-column (without header)
 Figure 16-29

Invoice #3 – Standard 80-column
This invoice is identical to Invoice #9 as seen in Chapter 15 - Invoices. Note that it does not include deposit data individually, although the totals will be displayed correctly.
Invoice #4 – Standard 40-column with Signature
This invoice is identical to Invoice #6 as seen in Chapter 15 - Invoices. It includes deposit data. 

RV Controller

The Recreational Vehicle (RV) Controller is another service module, with a few differences. It shares the same features as "Another Service Business Model," but has a different list of invoices and a different Front Register.
With the correct Keyblock, it is selected first at installation (option 1 for MicroBiz Server and option 2 for additional workstation). It can then be loaded AFTER installation by inserting the "RV Trigger File" into your BizWin folder. To do this:

  1. Make sure MicroBiz is closed.
  2. Open your BizWin folder in a Windows Explorer (i.e. "My Computer")
  3. Create a new file and name it "rv.mbz" (without the quotes).
  4. Open MicroBiz back up.

If you have multiple workstations, it is important to only use one module at a time. If you select the RV Controller on one workstation, make sure to do the same on all of your other workstations too!

RV Front Register
The Front Register for the RV Controller is split into two parts: labor (services) and parts (products). When first entering the Front Register, you will be looking at the Labor screen. From here, choosing F3-Services will display only Service Items.
Figure 16-30
To change to the Parts Screen, choose F12-Parts Screen. This screen is where you load non-service items (accessible via F3-Parts).
Invoices
The list of invoices for the RV Controller is shorter than that of other service modules:

  1. Standard Blank (80-column)
  2. Laser Service Invoice (uses form LASER36711)
  3. Standard Service Invoice with Waiver (80-column)
  4. NEBS Service Invoice (uses forms NEBS12341/AUTO12223)
  5. Laser Service Invoice (uses form LASER36711-1)
  6. Yet Another Standard Blank (80-column)
  7. YASB with Separate Labor/Parts (80-column)
  8. New 40-column with Signature & Barcoded Invoice (40-column)
  9. Standard (40-column)
  10. Standard Blank (80-column, laser printer)

All of these invoices are covered in other sections except for #7. This invoice is just like the Standard Service invoice, except services are grouped together at the top of the receipt before other items.