CStoreOffice® Support & Learning

Tobacco Scan Data Supporting Altria

With this report, you can set up the transaction-level scan data export to the Altria Group Distribution Company (AGDC) (previously named Philip Morris Companies Inc.) on a weekly basis.

This report is only available for the cash registers with the PJR files enabled. For details, see Enabling PJR Files.

To start working with the report, use the following navigation tips:

Before You Begin

Before you start configuring the Scan Data reports for your locations, make sure they have an active Scan Data subscription.

If a location does not have an active Scan Data subscription, such location is disabled in the report and cannot be configured.

If the location's Scan Data subscription has been expired, the report's data is not sent for this location.

For collecting and sending your data files, the Altria Group Distribution Company cooperates with the third-party client - IRI. Before starting to set up the scan data export settings, make sure the following conditions are met:

  • Your cash register is compatible with the scan data program.
  • Your CStoreOffice® account settings are configured properly and data files can be collected and sent from CStoreOffice® to IRI.

If you have not already filled out a Scan Data Discovery form, please choose the form that best fits your company structure:

  • Altria One account number for entire company, follow this link or scan QR code below:

  • Altria One account number for each location or a combination of locations, follow this link or scan QR code below:

Opening the Report

You can find the report at Reports > Accounting > Export Data > Tobacco Scan Data supporting Altria.

The Tobacco Scan Data supporting Altria report can be opened at all levels:

  • Account
  • Company
  • Division
  • Location (Station)

For more information, see Viewing Reports.

Setting Up the Report's Export

You can set up the data export with the Tobacco Scan Data supporting Altria report in the following two ways:

Data Export Control

To control whether the report is exported successfully, you can perform the following actions:

Try sending the report ahead of time

To make sure that the export settings are set up correctly, you may export the report data ahead of the schedule. Do the following:

  1. Go to the top of the report form and set the sending date range. The recommended date range is from Sunday to Saturday. For example, you can take the most recent data range available.

  2. Make sure that its data is correct. Click the Download button, extract the report file from archive and check its data.
  3. Export the report data ahead of the schedule. Click the Send button and wait until the report data are exported. When successful 'Done' notification is displayed, it means your report data are exported successfully.

File Sending Control

CStoreOffice® allows you to control if the required reports are generated and sent successfully to the destination by schedule. To do this, CStoreOffice® introduces a special service—File Sending Control—that is responsible for the following activities:

Submission Cap Guidelines

Altria tracks the cumulative number of report submissions for each store during a promotional period, known as the Submission Cap. The Submission Cap amounts to the number of weeks in the promotion period multiplied by 2. If a retailer's submissions exceed the Submission Cap, the retailer will not earn a Scan Data Promotional Fund payment for the promotion period from Altria.

In this report, the scheduled Scan Data report exports are considered as the report submissions already used. In the Submission Cap column, you can see how many times you can manually submit the Scan Data report for the stations you purchased the Scan Data subscription for.

Location events

Messages about relevant events in the location appear in the Location events column.

The messages about these events may appear in this column:

  • Successful report submission: shows submission date and time and which week the report was submitted for.
  • Failed report submission: shows date and time when the issue occurred and which week the report was not submitted for. The following issues may occur:
  • Connection issue: the system stopped report submissions because of connection issues.
  • No data: appears in case if the data is absent for the station.
  • User-initiated credential update: appears when the user updated the credentials for the location.
  • Report delivery subscription expiration: a notification when the report delivery subscription expired.

Exported File Structure

The report exports the data in the TXT file with the pipe "|" separator. The data in the file is grouped into the following sections:

File Header

The file header represents the row which contains the following data:

The first row in the file contains the following data:

  • The number of transactions in the file.
  • The number of items in the file.
  • The total cost of all items in the file.

For example, the file presented in the image below contains the information about 3459 transactions, 4086 items. The total cost of all items in the file equals to 23446.17.

Transaction Details Section

The Transaction Details section contains the following data:

  • [1] Management Account Number: A five-digit Management Account Number (Chains), or a six-digit Retail Control Number (Independents). This number is unique to AGDC systems and will be provided to you by your AGDC representative. In the report form, this value is taken from the Altria Acc Number field.
  • [2] Week Ending Date: The last calendar day of the time period associated with data submitted in each file. The format is YYYYMMDD. In the report form, this value is taken from the Period To: field located at the top of the report form.
  • [3] Transaction Date: The actual date of the transaction's record. The format is YYYYMMDD.
  • [4] Transaction Time: The actual transaction's time. 24-hour format is used. The format is HH:MM:SS.
  • [5] Transaction ID Code: A unique identifier that separates purchase transactions from each other. The format is Station ID + Transaction ID.
  • Please note that the transaction ID code which contains the data on the sales of multiple different items will be repeated for each item as a separate record in the file.

For example, the file presented in the image below contains the following data in the first row of the Transaction Details section:

  • Management Account Number (Altria Acc Number): 518129
  • Week Ending Date: 20210717
  • Transaction Date: 20210717
  • Transaction Time: 23:47:15
  • Transaction ID Code: 11151016729 = 1115 (Station ID) + 1016729 (Transaction ID).

Store Section

The Store section contains the following data:

  • [6] Store Number: A unique store identifier. Once assigned to the store, it must remain unchanged. In CStoreOffice®, this value is taken from the Station ID field.
  • [7] Store Name: The retail store name. The store name may include the store number. In CStoreOffice®, this value is taken from the Station Name field.
  • [8] Store Address: The physical street address of the retail store. In CStoreOffice®, this value is taken from the Station Street field.
  • [9] Store City: The name of the city where the retail store is located. In CStoreOffice®, this value is taken from the Station City field.
  • [10] Store State: The name of the state where the retail store is located. The format is SS (two characters). In CStoreOffice®, this value is taken from the Station State Abbreviation field.
  • [11] Store ZIP + 4 Code: The valid nine-digit ZIP code in which the retail store is located. This value is separated from 4 Code value by hyphen.
  • For more information about where to find the station data in CStoreOffice® and how to configure them, see General Station Options.

For example, the file presented in the image below contains the following data in the first row of the Store section:

  • Store Number: 1115
  • Store Name: Aramingo
  • Store Address: 2750 Aramingo Avenue
  • Store City: Philadelphia
  • Store State: PA
  • Store ZIP + 4 Code: 19134-0000

Item Section

The Item section contains the following data:

  • [12] Category: A unique identifier of the type of the products sold. In CStoreOffice®, this value is taken from the items Category field.
  • [13] Manufacturer Name: The name of the manufacturer of the UPC sold as it is reported in your system. For each manufacturer, the corresponding loyalty code is assigned in accordance with the format from the table below:
  • Manufacturer Loyalty Code
    USSTC 073100070013
    PM USA 028200197214
    Helix 840095781008

    The loyalty codes, if any, can be found in the MFG Deal Name fields. For more information about these fields, see Manufacturer-Funded Discounts Section.

  • [14] SKU Code: A unique code or number that identifies SKU in your chain or retail store. This value may coincide with the UPC Code value.
  • [15] UPC Code: The 12-digit UPC code assigned by the manufacturer. No spaces, hyphens or other special characters are allowed.
  • [16] UPC Description: The description of the UPC code.
  • [17] Unit of Measure: The description of the form in which the product was sold. The default value is equal to Each. Other possible values are: 2 Pack, 3 Pack, Roll, Carton and so on. The maximum length of the field is 15 symbols.
  • [18] Quantity Sold: The number of units sold in the defined units of measure.
  • [19] Consumer Units: The number of individual consumer units for the defined unit of measure. Depending on the defined unit of measure, the consumer units value may take the following values:
  • Unit of Measure Consumer Units
    Each 1
    2 Pack 2
    3 Pack 3
    Roll 5
    Carton 10

    The list of possible values presented in the table above is not exhaustive. Additional values may be provided for both Unit of Measure and Consumer Units.

For example, the file presented in the image below contains the following data in the first row of the Item section:

  • Category: Cigarettes
  • Manufacturer Name: RJ Reynolds
  • SKU Code: 00012300000932
  • UPC Code: 1230000093
  • SKU/UPC Description: CAMEL CRUSH MENT
  • Unit of Measure: Each
  • Quantity Sold: 1
  • Consumer Units: 1

Multi-Pack Discounts Section

The Multi-Pack Discounts section contains the following data:

  • [20] Multi-Pack Indicator: Indicates a transaction with the account funded discount offered for purchasing multiple units. May have the following values:
  • Y: This value indicates that the item was sold with the discount within the promotion of the Multi-Pack Discounts type.
  • N: This value is used in all other cases.
  • [21] Multi-Pack Required Quantity: The number of the Consumer Units (packs) required to be purchased for referring this transaction to the Multi-Pack transaction.
  • [22] Multi-Pack Discount Amount: The total discount provided for the quantity from the Multi-Pack Quantity field.

For example, the file presented in the image below contains the following data in the first row of the Multi-Pack Discounts section:

  • Multi-Pack Indicator: Y
  • Multi-Pack Required Quantity: 2
  • Multi-Pack Discount Amount: 1.00

Retailer-Funded Discount Section

The Retailer-Funded Discount section contains the following data:

  • [23] Retailer-Funded Discount Name: The name of the Retailer-Funded discount. In the report, this value is equal to the Promotion Name in case the promotion type is equal to Retailer-Funded Discount.
  • [24] Retailer-Funded Discount Amount: The amount of the Retailer-Funded discount.

In case there is no Retailer-Funded discount applied to the items, these values will be empty.

Manufacturer-Funded Discounts Section

The Manufacturer-Funded Discounts section contains the following data:

  • [25] Coupon Discount Name: This field is used to identify a discount provided in support of the Manufacturer-Funded promotion. The maximum length of this field is 50 symbols.
  • [26] Coupon Discount Amount: The dollar amount of the Manufacturer-Funded discount applied to the Quantity Sold amount.
  • [27] Other Manufacturer Discount Name: This field is used to identify a discount provided in support of the Manufacturer-Funded promotion.
  • [28] Other Manufacturer Discount Name: The dollar amount of the Manufacturer-Funded discount applied to the Quantity Sold amount.
  • [29] Loyalty Discount Name: The loyalty codes for three Altria companies which are populated in accordance with the following format:
  • Manufacturer Loyalty Code
    USSTC 731000*
    PM USA 28200*
    Helix 855022*
  • [30] Loyalty Discount Amount: The dollar amount of the loyalty discount applied to the Quantity Sold amount.
  • [31] Final Sales Price

In case there is no Manufacturer-Funded discount applied to the items, these values will be empty.

Optional Information Section

The Optional Information section contains the following data:

  • [32] Store Telephone: The retail store telephone number if available. No spaces, pluses, hyphens, or special characters are allowed.
  • [33] Store Contact Name: Retail store contact (manager) name.
  • [34] Store Contact Email: Retail store contact (manager) e-mail.
  • [35] Product Grouping Code: A Retailer defined code or number assigned to a product.
  • [36] Product Grouping Name: The description of the Product Grouping code or number.
  • [37] Loyalty ID / Rewards Number: An unique loyalty or "rewards" number of the customer making a purchase.
  • [38] Truncated (6-digit) Adult Tobacco Consumer Mobile Phone Number: Last 6 digits of adult tobacco consumer mobile phone number.
  • [39] Age Validation Method: The field indicates which method was used to age verify the consumer. It should be one of three following values:
  • manual = Manual Entry
  • scanned = Scanned ID
  • skipped = Other
  • [40] Manufacturer Offer Name
  • [41] Manufacturer Offer Amount
  • [42] Purchase Type
  • [43] This field is reserved for future use.
  • [44] This field is reserved for future use.
  • [45] This field is reserved for future use.

Additional Actions

To view the export history, click View Log or click Tobacco Scan Data Supporting Altria Log at the bottom of the page. For more information, see Tobacco Scan Data supporting Altria Log.

To leave the report interface and go to the home page, click Home.

To view the log of the last export, click Show/Hide Last Transmission log.

For more information on additional report features, see Reports.