Mobile Sales. Version 4.2

Transcription

1 Mobile Sales Version 4.2 Siriusware, Inc. 302 Camino de la Placita Taos, NM google.siriusware.com 1

2 Copyright Copyright 2013 Siriusware, Incorporated. All rights reserved. NOTICE: All information contained herein is the property of Siriusware, Incorporated. No part of this publication (whether in hardcopy or electronic form) may be reproduced or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written consent of Siriusware, Incorporated. The software, which includes information contained in any databases, described in this document is furnished under a license agreement and may be used or copied only in accordance with the terms of that agreement. This publication and the information herein is furnished AS IS, is subject to change without notice, and should not be construed as a commitment by Siriusware, Incorporated. Siriusware, Incorporated assumes no responsibility or liability for any errors or inaccuracies, makes no warranty of any kind (express, implied, or statutory) with respect to this publication, and expressly disclaims any and all warranties of merchantability, fitness for particular purposes, and non-infringement of third party rights. 2

3 Mobile Sales MOBILE SALES... 1 COPYRIGHT... 2 MOBILE SALES... 3 OVERVIEW... 4 BRIEF TECHNICAL DESCRIPTION... 4 Functionality... 4 Mobile Sales capability... 5 Performance... 5 Important features and notes:... 6 Mobile Sales Host... 7 Mobile Sales module installation and basic operation... 7 Salesware Service installation... 7 Mobile Sales Host utility... 9 Mobile Sales module... 9 Mobile Sales deployment...10 Mobile Sales module use...11 Basic operation...13 Mobile Sales module signature capture...19 Credit card signature capture setup...20 Signature ID Tag...20 Mobile Sales printing...20 Functionality...20 Salesware Service printing setup...21 Printing options ing options

4 Overview Mobile Sales module is a simplified version of the Sales application and has been developed for the ipod Touch/- iphone - Linea-Pro integrated barcode scanner/magnetic stripe reader, Mobile Sales module is available for iphone as well. Mobile Sales module allows a business to generate quick and easy transactions without being anchored to a stationary salespoint. Items can be added to a sale by navigating an item tree, performing an Item search on Nickname or UDF or scanning a barcode encoded with the Item s Nickname or UDF. Member/Passholder discounts can be applied and payments can be made using credit cards, In-House Cards items, Cash or any other form of payment configured and allowed for Mobile Sales module. Brief technical description Functionality Development of an application for ios (the operating system used on iphone and ipod Touch). Development of a centralized Sales engine that the ios apps connects to in order to perform basic sale operations through Siriusware Inc. 4

5 Mobile Sales capability Operator Log-ins including the scan/swipe of operator log-in codes Adding an item to a sale by selecting it from the Item Menu, scanning a barcode encoded with the Item s Nickname or UDF or doing a manual lookup of the barcode contents Changing quantity and deleting items from the sale Paying with Cash Paying with Credit Cards Paying with In-House Cards items, including scanning a modified barcode (%B plus a partial sixteen digit number) Application of %E pass discounts Performance Salesware Service application: Coordinates calls from the Mobile Sales devices and the SiriusSQL database via ww.dll. It is really the brains behind the operation. Prerequisites for Salesware Service include the following: IIS 7.Net 4.0 ww.dll (must be installed on the same computer as the Salesware Service application) Mobile Sales iphone/ipod App: Connects to the Salesware Service application and submits sales Mobile Sales Host utility: Similar to Sales Host utility for E-Commerce module. Its job is to process the sales submitted by the Mobile Sales App. 5

6 Important features and notes: 1. The devices must have Wi-Fi connectivity to Salesware Service application in order to function. This architecture allows for centralized use of Sales logic while taking advantage of the device specific functions for the app development. It also allows for easier expansion to other devices in the future, such as the Android. 2. The first iteration of the handheld salespoint only support basic Sales, such as selecting a midway game item to add to the sale (or scanning a barcode to add the item to a sale) and taking payment. 3. The handheld salespoint supports the multikey lookup functionality that allows an operator to type the item nickname or User Defined Field (UDF) in order to add it to the sale. This multikey lookup function can also be achieved by scanning a barcode that contains the item nickname or UDF. Support of this feature allows for quick sales of games and redemptions of prizes. 4. Although the intent is to primarily pay with a credit card swipe or IHC barcode scan, it is possible to pull up a list of other payment types so that customers can still pay with, for instance, Cash. In order to facilitate easy payment to cash, a barcode scan or single button press can be used to finalize the sale to cash. 6

7 Note: In this barcode scan or single button press Pay to cash process, change due would need to be calculated by the operator, not the system. If a Change due calculation by the system is required, then the one-touch Pay-to-cash option is not used. 5. The handheld salespoint is able to detect modified IHC barcodes printed on wristbands (barcodes with %B + the IHC number that have either the BIN or BIN+Program ID omitted) and append the static portion of the card numbers prior to getting authorizations for IHC charges. 6. Operator log-ins are supported, including the barcode scan/ card swipe log-in feature. 7. %E pass swipes for automated discounts are supported. 8. Wireless network and Bluetooth printers can be used for printing sales receipts or even tickets, if they are required for customers. Mobile Sales Host Sales has two different Sales Host modes, web and mobile (Sales Host and Mobile Sales Host utilities). These are licensed differently and slightly different operations. The main difference right now are that Mobile Sales Host (MSH) only gets ww_sales records that are marked with the MSH salespoints name in the host_sp column. This prevents another Sales Host instance from grabbing transactions that are meant for a MSH instance. In the sales32c.ini file: [Salespoint] Interface=Mobile This is the way to identify the proper type (although this is set if the license is correct automatically). The title bar on Sales Host utility reads Sales Host or Mobile Sales Host accordingly. Mobile Sales Host utility has its own license type, although it is allowed to make a web salespoint start up as mobile. Mobile Sales Host utility uses the correct license now and allows for running in classic mode for troubleshooting. Mobile Sales module installation and basic operation Salesware Service installation Installation requirements:.net 4.0 Siriusware Common Files application Siriusware ww.dll Local Firewall on the PC needs to allow communication over TCP port 80 A static IP address is required on the Salesware Service PC/Server IIS 7.0 or higher An operating System of Windows 7 or Windows Server 2008 or newer is required 7

8 1. Run the Salesware Service installer, Install_Siriusware_SaleswareService_4200.msi. 2. Edit the web.config file, located in the c:\inetpub\wwroot\saleswareservice directory. Configure the IHCSettings section if you plan to accept In-House Cards items Configure the Printers section by entering the IP of the wireless network printer, if you plan to use this type of printer. Configure the Hostsettings section to reflect the salespoint name of your Mobile Sales Host, MOBSH by default. Check the Logsettings section, make sure it is not set to 5 after you are up and running. 3. Test the Salesware Service application by browsing to: Note: This returns an xml page displaying the version info on the Salesware Service, ww.dll and database. 4. Create a folder named Print in the c:\programdata\siriusware\saleswareservice directory. This directory is where the print/ templates live. They can be obtained from Siriusware Technical Support. Note: When you first launch Mobile Sales module, you must enter the salespoint name and the host path. The host path is: but you need to replace localhost with the static IP address of the Salesware Service computer. SQL options Salesware Service application was modified to be able to use SQL CE 4.0, SQLite 3 or SQL Server/Express to store local data. This is all selectable via web.config file setting. Example: SqLite <LocalDB dboption="sqlite" dbinitstring="version=3"/> SqlCE <LocalDB dboption="sqlce" dbinitstring=""/> SqlServer The SqlServer method is not recommended. It is not used unless the sqllite or sqlce solution can't be used. 8

9 Functions A new function was added to Salesware Service application to get the list of most recent sales. The function is GetListOfRecentSales and specifies the salespoint and the number of previous hours of sales to get. Mobile Sales Host utility 1. In SysManager creating a new salespoint, Activities > System List > Sales > New has two additional selections of Mobile Sales, mode 10 and Mobile Sales Host, mode 11. In the Licensing grid, Preferences > Salespoint Licenses, the new mode of Mobile Sales is designated in the mode column dropdown as "B" and the Mobile Sales Host is designated by "H" in the dropdown. Support was added for new Mobile Sales and Mobile Sales Host salespoint modes as well. 2. Run the install for Sales (4.2) making sure to select the web mode when prompted. Note: Mobile Sales Host ([Salespoint] Interface=Mobile) and Sales Host ([Salespoint] Interface=Web) are similar to each other, but Mobile Sales Host (MSH) only processes records from salespoints licensed for Mobile Sales and Sales Host ignores those records. This allows for separate processing of web transactions and mobile device transactions. Additionally, Mobile Sales Host processes transactions using the operator and salespoint named passed in from Mobile Sales module rather than its own operator and salespoint name. Mobile Sales module 1. Create a salespoint in SysManager for each Mobile Sales modules that are installed and license each of them for Mobile Sales module. 2. Select an Item Tree for each Mobile salespoint. Keep in mind that the item tree selected for the salespoints are basic; no fancy multi-layered groups or always top types of features. 3. Load the Mobile Sales App on the ipod device. 9

10 Note: When clients downloads the app, they get to run it up to the launch page. They are not able to install/use the actual application until they enter all the required information that needs to be obtained from Siriusware Inc. through a license purchase Mobile Sales deployment To deploy using itunes, start by providing the device name and UDID to a Siriusware Technical Support staff member. This information can be obtained by connecting the device to itunes and clicking on the device name under the Devices menu. The Serial Number is displayed initially, but the UDID can be obtained by clicking on the Serial Number. 1. Connect the ipod to itunes. 2. From the Devices/ <name> iphone/apps screen remove, by unchecking, Prior Version (if any) and hit Apply. 3. From the Library/Apps screen delete the older version (if any). 4. Drag the new version into the Library/Apps screen. 5. Back on the Devices/<name> iphone/apps screen be sure the New App is checked, and then hit Apply. 6. Wait for the sync to finish and you re done. 10

11 Note: In Mobile Sales module, if the Linea Pro Hardware is not present the message, Linea Pro Hardware required displays on a red splash screen. If a connection to Salesware Service application is not possible the message, Waiting for Connection to Salesware Service is displayed again on a red splash screen. When the two messages occur, only a limited User Interface (UI) with Main, Contact and Settings tabs appear. Note: A horizontal swipe of the ipod Touch/iPhone screen changes the tab that Mobile Sales module displays. Mobile Sales module use Mobile Sales module supports the following basic functionality. 1. Operator Log-ins including the scan/swipe of operator log-in codes 2. Adding an item to a sale by selecting it from the Item Menu, scanning a barcode encoded with the Item s Nickname or UDF or doing a manual lookup of the barcode contents 3. Changing quantity and deleting items from the sale 4. Paying with Cash 5. Paying with Credit Cards 6. Paying with In-House Cards items, including scanning a modified barcode (%B plus a partial sixteen digit number) 7. Application of %E pass discounts Log-in/Sales invoice screens Operator Log-in Screen is viewed after starting the Mobile Sales App, followed by the Sales Invoice screen where items added to the current sale are listed. Note: The middle SCAN button can be pressed to activate the barcode scanner. An additional button on the upper right hand side of the device can also be used to activate the barcode scanner. 11

12 Utility tab The Info section displays the version of Mobile Sales and Host Version is the version of Salesware Service application running. Operator tools contains Debitware card Balance Check, Recall Sales and Printer Scan for detecting Bluetooth printers. Utilities contains Item tree Reload, Network Connection Test, Operator Logout and Bluetooth printer test. Settings is read only and contains the Salespoint name and Host Address for the Salesware Service application. To be able to edit Salespoint and Host Address consult with Siriusware Technical Support. 12

13 Basic operation Scanning items To add items to the sale, a barcode can be scanned. The barcode must be encoded with either the Item s Nickname or the contents of the Item s UDF (configured on the General tab in SysManager.) Screen captures below show the Sales Invoice after a barcode on a Hershey s Bar is scanned. To set the quantity > 1 or to delete the item or refund, select the blue arrow pointing to the right on the line item. 13

14 Item lookup The Item Lookup button can be used to select items from the item tree or to perform a Search. When adding an item to the Sales Invoice in this manner, the user is prompted to confirm the selection. 14

15 Item search 15

16 Making payments To pay for the sale, press the Payments button. The payment option defaults to Cash so that the user only has to press Payment, and then Finalize (same button) to pay the entire sale to Cash. The user also has the option of entering the amount of cash in order to have the system calculate change due. When paying with a Credit Card or In-House Cards item, the user can swipe the card or scan the IHC barcode (using the device s top-right-side button to activate the barcode scanner). As soon as the payments entered are greater than or equal to the sale total, the Payment button becomes the Finalize button. As soon as the Finalize button is pressed, the sale is submitted to Mobile Sales Host utility for processing. 16

17 Up to four payments can be entered for each sale. Each payment made is displayed at the top of the screen. To delete a payment, select the Payment Number button (first, second, third or fourth). 17

18 Additionally, credit card numbers can be entered manually if the swipe on the card doesn t work. 18

19 In House Cards items and Mobile Sales In-House Cards item charges made using Mobile Sales module link to the sale that is generated when processed by Mobile Sales Host utility by MasterSale. This process uses a new local table (modrec) and forward mechanism. There is now an In-House Cards item balance lookup in the Utility tab. If AddCardPayment or AddNonCCSwipePayment is attempted with an IHC item payment over the available amount, the payment is still added but the amount is automatically decreased to the maximum approval amount. The call still returns OK although the Message field in a verbosity 5 Salesware Service log is populated indicating that this occurred. If the amount available is 0, then the payment is not added and error is returned. Mobile Sales module signature capture This functionality provides electronic signature capture capability for Mobile Sales module. Encrypted signature information is retrieved from Mobile Sales module and sent to ww.dll when submitting a sale. Salesware Service application decrypts the credit card number and expiration data that Mobile Sales module sends to it. 19

20 Credit card signature capture setup Credit card data including the signature is sent to Salesware Service application encrypted. Mobile salespoint configuration values have been moved from the "Utility" view into config files stored in the Salesware Service application ProgramData/Data directory in the Default-config.xml file or alternatively XYZconfig.xml where XYZ is the name of the Mobile salespoint. Currently all settings are Boolean (True/False). Future settings may include strings or other values. The settings names are self-descriptive. Example: A typical config file: <SalesPointConfig xmlns=" xmlns:i=" <AllowCCSaleWithoutSignature>false</AllowCCSaleWithoutSignature> <AutoFinalize>false</AutoFinalize> <AutoShowSummary>true</AutoShowSummary> <PromptForSignature>true</PromptForSignature> </SalesPointConfig> If a salespoint config file is not found and the Default-config.xml file is missing, the Defaultconfig.xml automatically is created. Signature ID Tag This functionality allows for the ability to process the Signature ID Tag that is inserted into the sigid tag in the saletext by ww.dll. Mobile Sales Host inserts the Signature ID into the sigid field of the cc_trans table after processing the credit card transaction. Mobile Sales printing Mobile Sales module is able to , print to Wi-Fi or print to Bluetooth, receipts and tickets. Functionality Receipt/Ticket generation In order to generate tickets or receipts Salesware Service application processes layouts using XSL (a templating engine). XML is fed through the XSL templating engine and is converted to plain text, HTML or PDF, etc. 20

21 Wi-Fi printer configuration Salesware Service application specifies multiple Print Location settings. Each location includes settings to pair an XSL template with its Wi-Fi printer for each type of printing: Receipt, CC Receipt and Ticket. Receipt/Ticket delivery options: At the end of a sale, Mobile Sales module submits a request to Salesware Service application to , print to Wi- Fi, or print to Bluetooth. Salesware Service processes the layouts (templates), and then prints or s accordingly. Mobile Sales module sends a request to Salesware Service application which then s the receipt through the Messenger Service application. Wi-Fi/Blue-Tooth printing: When a Printing Location is selected, Tickets/Vouchers or Receipt layouts that are configured with an XSL template is processed by Salesware Service application and prints to the specified printer for that location. If Local Bluetooth is selected, then Salesware Service application processes the layouts and return them to Mobile Sales module where the application sends the Tickets/Receipts to the local Bluetooth printer. Salesware Service printing setup Salesware Service application supports the printing of receipts and tickets in Mobile Sales module. SPML (Sirius Print Markup Language), for Receipt and Ticket layouts is support for SwS network printers and Mobile Sales Bluetooth printers. Direct printing to a network/wi-fi printer is supported via the Salesware Service.config file. The format TCP:address:port for the WindowsPrinterName attribute connects directly to the network. Example: <Printers> <Printer name="receipt" windowsprintername="tcp: :9100" mode="spml" transform="btreceipt.xsl"/> <Printer name="ticket" windowsprintername="tcp: :9100" mode="spml" transform="btticket2.xsl"/> </Printers> Printing options Credit card receipts Credit card receipts can be printed in Mobile Sales module. The current web.config settings to do so are: 21

22 <Printers> <!--<Printer name="receipt" windowsprintername="starwire" mode="rawwithff" transform="textreceipt.xsl"/>--> <!--<Printer name="ticket" windowsprintername="starwire" mode="html" transform="ticket.xsl"/>--> <Printer name="receipt" windowsprintername="tcp: :9100" mode="spml" transform="btreceipt.xsl"/> <Printer name="ticket" windowsprintername="tcp: :9100" mode="spml" transform="btticket2.xsl"/> <Printer name="ccreceipt" windowsprintername="tcp: :9100" mode="spml" transform="ccreceipt.xsl"/> </Printers> <Transformations> <Transform name="simple Receipt" transform="btreceipt.xsl"/> <Transform name="simple Ticket" transform="btticket2.xsl"/> <Transform name="cc Receipt" transform="ccreceipt.xsl"/> </Transformations> < s> < name="simple " subject="quitung" transform=" .xsl" /> </ s> </PrintingSettings> Note: the ref# on cc receipt is the wwsale_id. Wireless printer Receipts and Access Tickets can be printed to a wireless printer and receipts can be ed. Salesware Service application orchestrates the printing and in conjunction with MessengerService, s a receipt. The wireless printer is configured through Salesware Service application. The Sale Summary screen now has a Print button, with which a receipt or ticket may be printed or a receipt ed immediately. A sale may be recalled from the Utility tab and the Sales Receipt / Ticket(s) can be printed or receipts can be ed. A sale may be recalled up to sixty minutes after the sale has taken place. Bluetooth printer Receipts and Access Tickets can be printed to a Bluetooth printer and receipts can be ed. Salesware Service application orchestrates the printing in conjunction with MessengerService, s a receipt. On the Mobile Sales Utility tab > Printers Scan button detects and attaches a Bluetooth printer. The Sale Summary screen now has a Print button with which a receipt or ticket may be printed or receipt ed immediately. A sale may be recalled from the Utility tab and the Sales Receipt or Ticket(s) can be printed or receipts can be ed. A sale may be recalled up to sixty minutes after the sale has taken place. 22

23 Prefix and encrypted barcodes Prefix and "encrypted" barcode printing was added through SPML configured in btticket2.xsl. New attributes to <barcode> SPML tag: encrypt38="true" forces the barcode data to base38. Prefix="XYZ" prefixes the barcode data (to put a % in the prefix use: i.e., <barcode encrypt38="true" prefix="%aaxx"> where "%" is the special character designation for "%" required to express "%" in SPML. The complete expression for the encrypted access.pass_no barcode follows: <barcode encrypt38="true" prefix="%aaxx"> <xsl:value-of select="$ticketnumber"/> </barcode> In order to not encrypt the number encrypt38="true" must be removed from the expression. Example: <barcode prefix="%aaxx"> <xsl:value-of select="$ticketnumber"/> ing options ing of a Sales Receipt is now possible through Mobile Sales module. An additional User Interface was added to access those features and support for printing interfaces provided by Salesware Service application. After completing a sale or recalling a sale choosing Print allows access to the Printing dialog. To the receipt, the operator chooses Simple and Send. The is handled through MessengerService. A valid layout must be present in C:\ProgramData\Siriusware\SaleswareService\Print\ for an to be sent. With the following web.config settings, the presence of .xsl in C:\ProgramData\Siriusware\SaleswareService\Print and Messenger Service application running, a receipt can be ed to an address entered in Mobile Sales module. Note: "subject="your Receipt" sets the subject line for the . <Printers> < s> < name="simple " subject="your Receipt" transform=" .xsl" /> </ s> </PrintingSettings> 23