POS Mapping Utility

The POS Mapping Utility screen defines the relationship between the data coming in from the POS system and the data on the Daily Sales Report. It does this through the POS Field drop-down menu that appears when you click any cell of the POS Field column. Here, you select from the list of descriptions you have previously associated with POS tracking numbers (see the General Procedure) for the one that will correspond to the DSR field in the same row. When all correspondences are made, click Update Mappings.

After POS mappings have been defined, data can be imported from the POS into the DSR. (POS information is automatically imported based on a schedule defined at the time you installed Compeat; for more information, contact Compeat Technical Support.)

Synchronizing Between the DSR Definitions and the POS Mappings

When you select the POS Mapping Utility from the Setup > POS Interfaces, you may get the following message:

Because there is a one-to-one correspondence between the fields defined for the DSR Definitions Time Periods tabs, and the fields being mapped from the POS, if you have added or removed fields from one of the Time Period tabs, you will first get the chance, in the above Confirm dialog box, to update your POS mappings.

Unless you want to manually update your POS mapping, you should select Yes whenever this message appears. If you select No, and later want to update your mappings based on DSR Definitions > Time Period tab changes, you can select the Update Mappings button at the top of the POS Mapping Utility screen. You should also use the Update Mappings button to synchronize the DSR Definitions and the POS mappings if you change the order of categories on the DSR Definitions time period tabs, or if you change the names of the time periods tabs. In these cases, Compeat does not automatically suggest the update because the changes are cosmetic and not required.

The POS Mapping Utility screen appears similar to the following:

Sample POS Mapping Utility screen for Micros 8700

Screen Column Descriptions

The POS mapping utility screen includes the following columns:

Compeat DSR Field

The items in this list are:

  • Fields defined in the Setup menu > DSR definition > Time Periods tabs (unique to your restaurant), and

  • 13 hard-coded fields at the bottom of the list, starting with Tax Food, Tax Liquor, and Cash, that are used by all restaurants.

    The hard-coded fields do not support either the Rev Center column or Time Period column information: data in these columns must be for all revenue centers and all time periods.

Depending on your business needs, you might not import POS data into all of the hard-coded fields; for example, your business may not use the Gift Redeem field, or perhaps your business may not accept Diner's Club cards.

If there is a field that you would like to import from your POS that does not appear in the DSR list, you will need to add it to your DSR definition, delete your current mapping, close the POS Mappings screen, and reopen it. When you reopen the mapping screen, it will reread the DSR Definitions and you will see all of the fields.

Note: If you want the sales figures for all of your time periods to be presented as one value on the DSR, make sure that you only activate one time period (by selecting the Active checkbox for the time period) on the DSR Definitions Time Periods tabs. When the POS mapping is created, the DSR field will be prefixed with the time period tab name, but it will include all data if you set the time period field to zero. For example, although you may see "Dinner - Food" in the POS Mapping screen, this could be for all time periods (just make sure you specify a zero in the Time Periods column). For more information, see Time Period information below.

Rev Center

The revenue center for the POS data. If you track information for your DSR by revenue center, specify the number from your POS associated with that revenue center. In order for this to work with the DSR, you must have set up your DSR Definitions to have a category for each item tracked for each revenue center.

For example, your restaurant may have two revenue centers, bar (1) and dining room (2), which you want to track separately. You should have defined your DSR definition to have categories broken out by revenue center, such as Food-Bar, Food-Dining Room, Liquor-Bar, Liquor-Dining Room, Beverage-Bar, and Beverage-Dining Room. For all of the Bar categories, you would enter revenue center 1; for all of the Dining Room categories, you would enter revenue center 2.

If you do not want to track your POS data by revenue center within Compeat, either enter zero, or leave this field blank. If the Compeat DSR field is one of the standard fields, you should also leave this field blank or enter zero.

Time Period

The time period of the POS data; can be any number up to five places, but is typically 0, 1, 2, 3, 4, 5, or 6. POS systems can typically be set up to track many time periods within a day for sales tracking purposes. The POS will track the data from each defined time period separately. With Compeat, you can import up to six of these time periods per day. Alternatively, you can specify zero to have all three time periods summed and presented as a single number.

The actual time periods do not matter to Compeat; you can set them according to your business needs. For example, you may only serve lunch and dinner, yet want to track your operating time in three periods. You could track 11 AM through 3 PM (in your Compeat DSR definition this is labeled Time Period 1), 3:01 PM through 7:00 PM as afternoon (in your Compeat DSR definition this is labeled Time Period 2 sales), and 7:01 PM through 12:00 AM as dinner (in your Compeat DSR definition this is labeled Time Period 3 sales).

Important: If any of your time periods overlap, your DSR data will be incorrect.

If the Compeat DSR field is a standard field or you want all six time periods summed and presented as a single number, leave the time period field blank or enter zero. (Zero is required for the standard fields such as TaxFood, TaxLiquor, Cash, and so on, because POS systems provide only one value for these fields for all time periods).

POS Field

The POS field description previously associated with a POS tracking number in your appropriate POS Tracking Definitions screen (see General Procedure). If you click in any cell of this column, you will see the drop-down list of all the descriptions that have been created so you can select one.

Count or Amount

The type of data to display in the DSR for the field; can be one of the following:

  • Amount: Display a dollar amount for this item.

  • Amount *-1: Display a negative dollar amount (or positive, if originally negative).

  • Count: Display a count for this item. Typically, you use counts for non-financial items such as the number of entrees sold (which you might use in a financial report to determine guest count trends).

  • Count *-1: Display a negative count (or positive, if originally negative).

POS mappings can be copied from one restaurant to another if they use the same type of POS and the POS systems are configured the same.