Version 6.32

Services

Added support of a new printer model – IP AirPrint

Build 6.32.49.0: PRO-4787

In CHQ, we added the capability to configure connection to AirPrint printers using the IP address. Once configured in CHQ, the respective printer becomes available in POS.

Purpose

AirPrint is a technology that allows an Apple device and a printer to communicate via a wireless network. With AirPrint, a POS device can quickly connect to the required printer without any cables or printer-specific drivers.

However, the AirPrint technology doesn’t work across multiple subnetworks if the retailer employs network segmentation in their environment.

To communicate with a POS device in such an environment, AirPrint printers must be:

• set up within the same subnetwork as the device sending out the printing data, and
• connected to that device using the IP address

Thus, to allow mobile devices to communicate with AirPrint printers in conditions described above, we’ve made available the IP-based connection.

How to add the IP AirPrint printer

To make the IP AirPrint printer available for your POS device, in CHQ:

1. Go to services > device controller.

2. Find your device and click it.

3. In the edit device dialog that opens, go to the direct printers tab.

4. Click new to open the printer dialog:

5. In the dialog, populate the following fields:

   • printer: indicate your printer number
   • name: specify your printer name
   • type: make sure that network/IP is selected (set by default)
   • model: select IP AirPrint
   • IP/MAC address: specify your printer IP or MAC address

6. Click save twice.
   On clicking save, all the updates made in the direct printers tab are streamed to the respective POS device.

See also

V6.32 Mobile Release Guide in Teamwork Confluence

Sales

Viewing a full Gift Card number in sales history

Build 6.32.49.0: PRO-4808

We’ve introduced the capability to view the full Gift Card number in the following areas of CHQ:

• sales > customer > sales
• sales > sales receipts > items

Purpose

Checking the full Gift Card number may be useful, for example, when the customer loses the Gift Card and comes into a store for help. In that case, the store associate can sell a new Gift Card for the balance remaining and use the lost Gift Card number (retrieved from CHQ) to pay for the transaction.

New Security right

We’ve added a new security right that allows the user to view the full Gift Card number in the respective areas of CHQ:

How to view a full Gift Card number in the customer sales history

1. In CHQ, go to sales > customers.
2. Find the required customer record and click it.
3. In the customer details dialog that opens, go to the sales tab.
4. In the sales tab, add the gift card # column to the table if the column is not available. To do so, right-click the table header and select the gift card # checkbox.
   On adding, in the column, you will see the number of the Gift Card used during the respective sale:
5. Click the blue link in the gift card # column to open the gift card # dialog. In the dialog, the Gift Card number displays in full:
6. Click ok to close the dialog and then click cancel.

How to view a full Gift Card number in the sales history

1. in CHQ, go to sales > sales receipts.
2. Find the required Sales Receipt record and click it.
3. In the sales receipt details dialog that opens, go to the items tab.
4. In the items tab, add the gift card # column to the table if the column doesn’t display.
   To do so, right-click the table header and select the gift card # checkbox. On adding, in the column, you will see the number of the Gift Card used during the respective sale:
5. Click the blue link in the gift card # column to open the gift card # dialog. In the dialog, the Gift Card number displays in full:
6. Click ok to close the gift card # dialog and then click cancel.

See also

Cloud HQ User Manual: Sales & eCommerce in Teamwork Confluence

Settings

European fiscal compliance – Germany

Build 6.32.35.0: PRO-3623, PRO-3727

In CHQ, we’ve added the capabilities to:

• configure connection with a certified fiscal device
• define a custom fiscal name for a payment method
• define a fiscal code for a tax category
• configure Germany specific fiscal settings

Purpose

The updates ensure Teamwork Commerce Pro Suite is compliant with the following fiscal requirements of German authorities:

1. The POS Pro app must be connected with a certified TSE device (German: Technische Sicherheitseinheit, or “technical safety device”) at all times. This device receives all fiscal data during POS day-to-day operations and provides for the data’s security and inalterability. TSE also provides storage for fiscal-related data. Through POS Pro, this storage can be accessed to provide a fiscal report for tax auditing purposes.
2. The payment method used during the sale must be recorded on the fiscal device with a standard name. The same name is then used to refer to the respective payment method in a fiscal report generated in POS Pro V6.
3. In fiscal reports and on Sales Receipts, tax rates collected during the sale must be represented by fiscal codes. Additionally, the TSE device requires the fiscal code to be present on the issued Sales Receipt.

Configuring the connection to the TSE device

To configure the connection between the TSE device and the POS Pro app on an individual device, in CHQ:

1. Go to services > device controller.

2. Find your device and click it.

3. In the edit device dialog that opens, go to the app settings tab.

   The app settings tab is available for configuration in the edit device dialog only when:

   • your device is location-specific (the exact name of a location is indicated in the location field of the general tab) and
   • your device is Teamwork POS version 6.0 or higher

   Otherwise, the app settings tab is invisible.

4. Under fiscal device, in the device type field, choose the required TSE device (see the screenshot below). Selecting [your TSE device] enables the following fields for configuration:

   Setting	Description	Value
   network/IP	the IP address to connect to your fiscal device	Empty by default; required
   timeout (milliseconds)	the period of time in milliseconds for the TSE device to provide a response	Values can range from 5000 (5 seconds) to 120000 (2 minutes); 5000 is set by default; required
   PUK (personal unblocking key)	the Personal Unblocking Key to your TSE device. PUK is defined during the initial setup of the TSS device	A numeric 6-character value; empty by default; required
   admin PIN	the administrator’s PIN to log in to the TSE device. The Admin PIN is defined during the initial setup of the TSE device	An alphanumeric 5-character value; empty by default; required
   time admin PIN	the factory administrative PIN that can be changed during the initial TSE setup	An alphanumeric 5-character value; empty by default; required
   secret key	the code that allows POS to access the TSE device as well as pass and receive data from the latter. This value is defined during the initial TSE setup	An alphanumeric 8-character value; empty by default; required
   timeout for admin auto lockout (seconds)	the period of time in seconds after which the admin account is logged out of TSE if there is no activity on the admin login	Values can range from 900 (15 minutes) to 7200 (2 hours); 900 is set by default
   timeout for time admin auto lockout (seconds)	the period of time in seconds after which the time admin account is logged out of TSE if there is no activity on the time admin login	Values can range from 900 (15 minutes) to 86400 (24hours); 28800 (8 hours) is set by default
   export timeout period (seconds)	the time interval after which TSE data export is canceled if TSE is in the export mode but no export calls are made	Values can range from 100 to 330; 100 is set by default

5. When finished configuring the settings, click save for the changes to take place.

Defining fiscal labels for payment methods

To define fiscal labels, in CHQ:

1. Go to settings > sales > payment methods.
2. Click to select [your payment method record], then click edit.
3. In the dialog that opens, in the general section, populate the fiscal label field. To add a translation to your fiscal label, click the globe icon next to the required field.

   For a translation to be available in POS, first, it must be set up in CHQ. To do so:

   1. Click the globe icon next to the default label of the required field or value.
   2. On tapping the icon, the description: [default field name] dialog opens.
   3. Enter the required translation.
   4. Click save.

   Please be advised that if no translation is defined in CHQ for the language that is used for the user interface in POS Pro, default field labels and values display in POS.

4. Click save.

Defining fiscal code for the tax details dialog

To configure fiscal code for existing tax categories in CHQ:

1. Go to settings > company settings > taxes > tax areas.
2. In the area that opens, click to select [your Germany tax area record], then click set up tax details at the top.
3. In the dialog that opens, click to select [your tax category code record], then click edit.
4. In the tax details dialog that opens, populate the fiscal code field. The field is blank by default, values can range from 1 to 9999.
5. Click save twice.

Configuring the fiscal-related settings at the country level

For Germany, the fiscal tab is now available in the country details dialog.

To access the country details dialog, go to chq > settings > company settings > countries / regions, select Germany, and then click edit.

The fiscal tab includes the TSE section with the following fiscal settings:

• VAT #: the VAT number of the company that is printed on Sales Receipts. Blank by default.
• ID: the tax ID number that is printed on Sales Receipt. Blank by default.

See also

• Cloud HQ User Manual: Settings in Teamwork Confluence
• V6.32 Mobile Release Guide in Teamwork Confluence

European fiscal compliance – Italy

Build 6.32.35.0: PRO-3999

In CHQ, we’ve added the capabilities to:

• configure connection with a certified fiscal device
• define a custom fiscal name for a payment method
• restrict sales and returns in one transaction at the country level.

Purpose

The updates ensure Teamwork Commerce Pro Suite is compatible with the fiscal requirements of Italian authorities:

1. Every POS device must be connected to a special fiscal printer, the RT printer (from Italian “Registratore Telematico”). The printer has the capability to print fiscal receipts as well as automatically submit daily fiscal reports to the tax authorities.
2. Payment methods indicated in the fiscal reports that are submitted via the RT printer must have standard names.
3. In Italy, sales and returns on the same transaction are not allowed.

Configuring the connection to the RT printer

To configure the connection between POS Pro V6 and the RT fiscal printer:

1. Go to services > device controller.

2. Find your device and click it.

3. In the edit device dialog that opens, go to the app settings tab.

   The app settings tab is available for configuration in the edit device dialog only when:

   • your device is location-specific (the exact name of a location is indicated in the location field of the general tab) and
   • your device is Teamwork POS version 6.0 or higher

   Otherwise, the app settings tab is invisible.

4. Under the fiscal device section, in the device type field, choose the required RT device (see the screenshot below). Selecting [your RT device] enables the following fields for configuration:

   Setting	Description	Value
   network/IP	the IP address to connect to your fiscal device	Empty by default; required
   timeout (milliseconds)	the period of time in milliseconds for the RT printer to provide a response	Values can range from 5000 (5 seconds) to 120000 (2 minutes); 5000 is set by default; required
   cash drawer installed	if the checkbox is selected, a cash drawer is attached to the printer	The checkbox is clear by default

5. When finished configuring the settings, click save for the changes to take place.

   Please note that changes in the fiscal device section made at the CHQ side are automatically synchronized with the POS Pro device and vice versa.

Defining fiscal labels for payment methods

To define fiscal labels, in CHQ:

1. Go to settings > sales > payment methods.
2. Click to select [your payment method record], then click edit.
3. In the dialog that opens, in the general section, populate the fiscal label field. To add a translation to your fiscal label, click the globe icon next to the required field.

   For a translation to be available in POS, first, it must be set up in CHQ. To do so:

   1. Click the globe icon next to the default label of the required field or value.
   2. On tapping the icon, the description: [default field name] dialog opens.
   3. Enter the required translation.
   4. Click save.

   Please be advised that if no translation is defined in CHQ for the language that is used for the user interface in POS Pro, default field labels and values display in POS.

4. Click save.

Updated country details dialog

For Italy, in the POS tab of the country details dialog, the allow sales and returns on the same transaction checkbox is not available for selection.

See also

• Cloud HQ User Manual: Settings in Teamwork Confluence
• V6.32 Mobile Release Guide in Teamwork Confluence

Configuring Banorte integration

Build 6.32.35.0: PRO-4121

As of 6.32.35.0, we’ve added the capability to support integration with Banorte payment processor across CHQ, in particular:

• configuring the connection between POS Pro device and the Banorte payment terminal
• setting up Banorte payment processing for the entire company or for a selected location
• selecting Banorte as the payment processor at the payment method level.

Purpose

The update allows for using the Banorte payment processor when processing credit card payments in the POS Pro V6 app.

Configuring connection to Banorte payment terminal

To configure the connection between the POS device and the Banorte terminal, in CHQ:

1. Go to services > device controller.

2. Find your device and click it.

3. In the edit device dialog that opens, go to the app settings tab.

   The app settings tab is available for configuration in the edit device dialog only when:

   • your device is location-specific (the exact name of a location is indicated in the location field of the general tab) and
   • your device is Teamwork POS version 6.0 or higher

   Otherwise, the app settings tab is invisible.

4. In the payment terminal type field of the payment terminal section, choose Banorte (see the screenshot below): Selecting Banorte enables the following fields for configuration:

   Setting	Description	Value
   IP address	the IP address to connect to your Banorte payment terminal	Empty by default; required
   terminal ID	the Banorte payment terminal IP address	Terminal ID typically consists of several blocks: characters and digits, a hyphen, and then 9 digits. For example, P400-123456789. The max length of terminal ID is 24 symbols. Empty by default; required
   port	the port number of your Banorte payment terminal	Values can range from 1 to 65535; 1818 is set by default; required

5. When finished configuring the settings, click save for the changes to take place.

   Please note that changes in the payment terminal settings made at the CHQ side are automatically synchronized with the POS Pro device and vice versa.

Configuring company-level settings

In CHQ, to configure the Banorte settings at the company level:

1. Go to settings > sales > payment processing.
2. In the area that opens, scroll down to the new Banorte section at the bottom of the page.
3. In the Banorte section, populate the following settings:
   • user: your Banorte merchant’s username
   • password: your Banorte merchant’s password
4. Once finished, click save.

Configuring location-level settings

In CHQ, to configure the Banorte settings at the location level:

1. Go to settings > location settings > locations / location settings.
2. Click to select your location, then click edit.
3. In the [selected location] dialog that opens, go to the payments tab.
4. Scroll down to the Banorte section.
5. Populate the following settings:
   • user: your Banorte merchant’s username
   • password: your Banorte merchant’s password
6. Click save for the changes to take place.

Configuring Banorte payment method settings

To select Banorte as the payment processor for the Credit Card payment method:

1. Go to chq > settings > sales > payment methods.

   If a Banorte Credit Card payment method is not set up under settings > sales > payment methods, click new at the top-left to create one.
   In the new payment method dialog that opens, select credit card for the payment type field and then click ok. On clicking, the dialog displays where it’s required to set up parameters for the new credit card payment method and then click save.

2. In the payment methods area, click to select [your Banorte Credit Card record] from the code column, then click location settings.

3. Click to select your location and click edit to open the following dialog (see the screenshot below):

4. In the payment processing field, select Banorte to use the Banorte payment processor for this location.

   Please be advised that the payment processing field is available only when the disable integrated processing checkbox above is cleared.

5. Click save in both dialogs for the changes to take place.

See also

V6.32 Mobile Release Guide in Teamwork Confluence

Other Enhancements

JSON-based Secure Customers Import API: the KeyField setting supports “Email”

Build 6.32.35.0: PRO-4218

The KeyField setting of the JSON-based Secure Customers Import API now supports the Email value in addition to EID, MembershipCode and No. This enhancement allows for updating light customer records by the email address.

JSON-based Customer Export API: the “Search” operator added to filters

Build 6.32.39.0: DS-1635

As of version 6.32.39.0, the filtering functionality of the JSON-based Customer Export API has been extended with the Search operator.

The Search operator is available for the following fields:

• CustomerFirstName
• CustomerLastName
• CustomerMiddleName
• CustomerEmail1
• Phone

In addition, the Search operator allows for partial search among all the available customer records:

• in case of FirstName, LastName, MiddleName, and EMail1, the indicated value is used to filter out customer records that start with that respective value
• in case of Phone, on the contrary, the records that end with the respective value are included in the output.

JSON-based Sales Receipt Import API: Overriding restriction for Sales Receipts with sale and return items

Build 6.32.52.0: PRO-4913

Starting from version 6.32.52.0, we’ve changed the restrictions for importing a Sales Receipt that contains both sale and return items via JSON-based Sales Receipt Import API.

Now, if the SuppressIsAllowMixedApiReceipt setting is enabled at the database level, the respective Sales Receipt record is successfully created even if making sales and returns in one transaction is not allowed according to CHQ configurations.

Issue Resolutions

JSON-based TimeCard Export API: missing “EventType” values in API response

Build 6.32.39.0: DS-1912

Issue
Prior to 6.32.39.0, as a result of export via JSON-based Time Card Export API, only StartShift value displayed in the EventType field in the API response. Other possible values, in particular, StartBreak, EndBreak, and EndShift, though displayed in the respective time card record in CHQ under services > time card > [your time card record] > clock in-out, would not get into the API request output.

Resolution
The issue has been fixed. Now, all the available EventType values display in the API response as expected.

Customer Invoice not sent via Mandrill

Build 6.32.49.0: DS-1975

We have fixed the issue where the SendMail task would fail to send Customer Invoice to the customer’s email via Mandrill on finalizing the sale in POS Pro V6.

The Sync Customer Attributes job enhancement

Build 6.32.52.0: DS-1935

The Sync Customer Attributes job has been enhanced to process large amounts of data faster.

Big Query: Records missing in the PersonalInfo table

Build 6.32.52.0: DS-2006

Issue
After exporting sales data from Teamwork’s database to BigQuery, in BigQuery, some records could fail to appear in the PersonalInfo table.

Resolution
To help with this issue, we’ve added the StreamingDate field to the PersonalInfo table. Now, sales records are properly synchronized between Teamwork’s database and BigQuery.