Arts

IXRetail POSLog Charter Revision Date:

June 12, 2003 Page 1 of 1

IXRetail POS Log Charter

June 12, 2003

Release 2.0

Version 2 of POSLog is a significant expansion of Version 1 released in July of 2002. Version 2 includes tendering, taxation and some non-point of services transactions. For the complete list of the enhancements, please see section 2, Revision History.



Abstract: This document serves as the IXRetail POSLog Work Team Charter and Executive Overview for the ARTS XML POSLog schema. POSLog V2 was developed following beta implementations of V1 to incorporate the recommendations of these early implementers 360Commerce, Triversity and IBM and the functional requirements of The Limited. Target, Blockbuster, Radio Shack and other retailers.

Status of this Document This document is an IXRetail Proposed Recommendation, for review by IXRetail Technical Committee members and use by retailers and vendors.

Open Issues: None Copyright © National Retail Federation 2003. All rights reserved. This document may be copied or used by and for ARTS Members for purposes consistent with adoption of the ARTS Standards. However, any changes or inconsistent uses must be pre-approved in writing by the National Retail Federation. As such, this document may not be furnished to others, and derivative works (the term “derivative works” does not include functional additions that do not modify or change the base standard as written) that comment on or otherwise explain it or assist in its implementation may not cite or refer to the standard, in whole or in part, without such permission. Moreover, this document may not be modified in any way, such as by removing the copyright notice or references to the NRF, ARTS, or its committees, except as needed for the purpose of developing ARTS standards using procedures approved by NRF, or as required to translate it into languages other than English.



1. INTRODUCTION................................................................................................................. 7

2. VERSION CHANGE DOCUMENTATION...................................................................... 7

2.1 REVISION HISTORY ..................................................................................................... 7

3. TEAM NAME ....................................................................................................................... 8

4. TEAM MISSION .................................................................................................................. 8

4. MEMBERSHIP ROSTER ................................................................................................... 9

5. BUSINESS JUSTIFICATION........................................................................................... 10 INTRODUCTION .......................................................................................................................... 10 WHAT IS A POSLOG?................................................................................................................. 11

6. MISSION SCOPE............................................................................................................... 11

6.1 OUT OF SCOPE FOR VERSION 2 ............................................................................. 12

7. USE CASE SURVEY.......................................................................................................... 14

7.1 VOLUME 1: SALES AND RETURN........................................................................... 14

7.1.1 USE CASE: ITEM PURCHASE ............................................................................... 14 SCENARIO: ITEM PURCHASE AT POS ......................................................................................... 14 SCENARIO: ITEM PURCHASE VIA WWW OR TELE-SALES............................................................. 14 SCENARIO: ITEM PURCHASE FOR DELIVERY FROM STORE........................................................... 14 SCENARIO: ITEM PURCHASE FOR DELIVERY FROM WAREHOUSE................................................. 15 SCENARIO: ITEM PURCHASE FOR ALTERATION & SUBSEQUENT PICKUP ..................................... 15 SCENARIO: ITEM PURCHASE BY RANDOM WEIGHT ..................................................................... 15 SCENARIO: ITEM PURCHASE OF SERIALIZED ITEM ...................................................................... 15 SCENARIO: ITEM PURCHASE WITH PART EXCHANGE................................................................... 15 SCENARIO: ITEM PURCHASE WITH QUANTITY PRICING ............................................................... 15 SCENARIO: ITEM PURCHASE OF MULTI-PACKAGE ITEMS............................................................. 15 SCENARIO: ITEM PURCHASE VIA OPEN DEPARTMENT ................................................................. 15 SCENARIO: ITEM PURCHASE BY SELLING LOCATION................................................................... 15 SCENARIO: ITEM PURCHASE WITH SPECIAL ORDER..................................................................... 16

7.1.2 USE CASE: ITEM PURCHASE OF KIT/COMBO/COLLECTION ITEMS ..... 16

SCENARIO KIT/COMBO/COLLECTION PURCHASE WITHOUT SUBSTITUTION............................... 16 SCENARIO: KIT/COMBO/COLLECTION PURCHASE WITH SUBSTITUTION.................................... 16 SCENARIO: FOODSERVICE COMBO............................................................................................. 16

7.1.3 USE CASE: ITEM PURCHASE & RETURN WITH DEPOSIT.......................... 16 SCENARIO: PURCHASE CRATE OF BEER WITH EMPTIES............................................................. 16 SCENARIO: PURCHASE CRATE OF BEER WITHOUT EMPTIES ...................................................... 16



SCENARIO: RETURN EMPTIES .................................................................................................... 16

7.1.4 USE CASE: ITEM PURCHASE WITH REFILLABLE CONTAINERS ............ 17 SCENARIO: ITEM PURCHASE WITH REFILLABLE CONTAINER .................................................... 17 SCENARIO: ITEM PURCHASE WITHOUT REFILLABLE CONTAINER.............................................. 17

7.1.5 USE CASE: ATTEMPTED ITEM PURCHASE WITH RAIN CHECK ............. 17

7.1.6 USE CASE: ITEM PURCHASE ON LAYAWAY/LAYBYE ................................ 17 SCENARIO: CUSTOMER COMMENCES LAYAWAY ....................................................................... 17 SCENARIO: PROGRESS PAYMENT ............................................................................................... 17 SCENARIO: CUSTOMER COMPLETES A LAYAWAY...................................................................... 17 SCENARIO: CANCELLATION ....................................................................................................... 18

7.1.7 USE CASE: ITEM PURCHASE WITH MANUAL PRICE OVERRIDE............ 18 SCENARIO: OPEN PLU (UNPRICED ITEM) .................................................................................. 18 SCENARIO: RAIN CHECK............................................................................................................ 18 SCENARIO: CUSTOMER COMPLAINT ABOUT PRICE .................................................................... 18 SCENARIO: DIFFERENT TAG PRICE ............................................................................................ 18 SCENARIO: MANAGER COMPLIMENTARY .................................................................................. 18 SCENARIO: CHARITABLE CONTRIBUTION................................................................................... 18

7.1.8 USE CASE: ITEM PURCHASE WITH EMPLOYEE TRAINING ..................... 18

7.1.9 USE CASE: ITEM RETURN .................................................................................... 19 SCENARIO: RETURN TO STORE................................................................................................... 19 SCENARIO: RETURN FOR DELIVERY BY CUSTOMER................................................................... 19 SCENARIO: RETURN FOR PICKUP FROM CUSTOMER ................................................................... 19

7.1.10 USE CASE: GIFT CERTIFICATE PURCHASE ................................................... 19

7.1.11 USE CASE: ITEM PURCHASE ON BACKORDER ............................................. 19 SCENARIO: BACK-ORDER FOR PICKUP....................................................................................... 19 SCENARIO: BACK-ORDER FOR DELIVERY ................................................................................. 20 SCENARIO: PREVIOUS BACK-ORDER CANCELLATION................................................................ 20

7.1.12 USE CASE: BATCH END OF DAY TRANSFER .................................................. 20

7.2 VOLUME 2: TENDER USE CASES............................................................................ 20

7.2.1 USE CASE: SALE TENDER..................................................................................... 20

SCENARIO: CUSTOMER TENDER’S PURCHASE WITH CASH TENDER WITHOUT CASH BACK ... 20 SCENARIO: CUSTOMER TENDER’S PURCHASE WITH CASH TENDER WITH CASH BACK .......... 20 SCENARIO: CUSTOMER TENDER’S PURCHASE WITH DEBIT OR CREDIT TENDER WITHOUT CASH BACK ............................................................................................................................... 20 SCENARIO: CUSTOMER TENDER’S PURCHASE WITH DEBIT OR CREDIT TENDER WITH CASH BACK ......................................................................................................................................... 20 SCENARIO: CUSTOMER TENDER’S PURCHASE WITH CHECK TENDER WITHOUT CASH BACK . 20



SCENARIO: CUSTOMER TENDER’S PURCHASE WITH CHECK TENDER WITH CASH BACK........ 21 SCENARIO: CUSTOMER TENDER’S PURCHASE WITH TRAVELERS CHECK IN A FOREIGN CURRENCY ................................................................................................................................ 21 SCENARIO: CUSTOMER TENDER’S PURCHASE WITH PURCHASE ORDER ................................ 21 SCENARIO: CUSTOMER TENDER’S PURCHASE TO STORE CHARGE ACCOUNT ....................... 21 SCENARIO: CUSTOMER TENDER’S PURCHASE WITH IN-STORE COUPON AND CASH.............. 21 SCENARIO: CUSTOMER TENDER’S PURCHASE WITH MANUFACTURER’S COUPON AND CASH 21 SCENARIO: CUSTOMER TENDER’S PURCHASE WITH VOUCHER, GIFT CERTIFICATE OR OTHER STORED VALUE MEDIA WITH CHANGE AS VOUCHER AND CASH .............................................. 21 SCENARIO: CUSTOMER TENDER’S PURCHASE WITH VOUCHER, GIFT CERTIFICATE OR OTHER STORED VALUE MEDIA WITH CHANGE AS VOUCHER ONLY ...................................................... 21 SCENARIO: CUSTOMER TENDER’S PURCHASE WITH VOUCHER, GIFT CERTIFICATE OR OTHER STORED VALUE MEDIA WITH CHANGE AS CASH ONLY. ............................................................ 21 SCENARIO: CUSTOMER TENDER’S PURCHASE WITH VOUCHER, GIFT CERTIFICATE OR OTHER STORED VALUE MEDIA WITH NO CHANGE ................................................................................. 22 SCENARIO: CUSTOMER TENDER’S PURCHASE WITH FOOD STAMPS ....................................... 22 SCENARIO: CUSTOMER TENDER’S CO-PAY PURCHASE, I.E. DRUG PURCHASE ..................... 22 SCENARIO: CUSTOMER TENDER’S PURCHASE WITH “MALL BONUS BUCKS” .......................... 22

7.2.2 USE CASE: REFUND TENDER .............................................................................. 22

SCENARIO: CUSTOMER GETS REFUND IN CASH ...................................................................... 22 SCENARIO: CUSTOMER GETS REFUND ON THEIR CREDIT CARD ............................................ 22 SCENARIO: CUSTOMER GETS REFUND ON THEIR STORE ACCOUNT....................................... 22 SCENARIO: CUSTOMER GETS REFUND IN MERCHANDISE VOUCHER ...................................... 22 SCENARIO: CUSTOMER GETS REFUND IN A CHECK SENT TO AN ADDRESS............................ 22

7.2.3 USE CASE: POST PURCHASE PRICE ADJUSTMENT ..................................... 22

SCENARIO: CUSTOMER GETS REFUND IN CASH AFTER RETURNING TO THE STORE ............. 23

7.2.4 USE CASE: MERCHANDISE FOR STORE USE ................................................. 23

SCENARIO: EMPLOYEE TAKES AN ITEM OFF THE SHELF FOR USE IN THE STORE .................. 23

7.3 VOLUME 3: TAXATION USE CASES....................................................................... 23

7.3.1 USE CASE: TAX ........................................................................................................ 23

SCENARIO: US SALES TAX AT THE TRANSACTION LEVEL........................................................ 23 SCENARIO: MULTIPLE TAX AUTHORITIES.................................................................................. 23 SCENARIO: EAT IN TAXES V TAKE OUT TAXES......................................................................... 23

Alternate Flow 1: Taxes Not Charged on Food Eaten in the Store...................................... 23 Alternate Flow 2: Taxes Charged on Food Taken from the Store........................................ 23

SCENARIO: TAX ON MANUFACTURER’S COUPON ..................................................................... 23 SCENARIO: PURCHASE TAXED AT THE POINT OF ORIGIN WITH DESTINATION IN ANOTHER STATE........................................................................................................................................ 24

7.3.2 USE CASE: VAT TAXES.......................................................................................... 24

SCENARIO: NORMAL VAT TAX.................................................................................................. 24 SCENARIO: VAT TAX ON TRANSACTION ................................................................................... 24



SCENARIO: VAT TAX EXCEPTION ............................................................................................. 24 SCENARIO: MULTIPLE VAT TAX ON KIT.................................................................................... 24 SCENARIO: ZERO PERCENT VAT TAX AND NORMAL VAT TAX ON THE SAME TRANSACTION 24 SCENARIO: VAT LUXURY TAX .................................................................................................. 24

7.3.3 USE CASE: TAX FORGIVEN.................................................................................. 24

SCENARIO: ILLINOIS FOOD STAMPS .......................................................................................... 24 SCENARIO: SOME OF THE ITEMS ARE TAXED AND OTHERS ARE NOT IN THE SAME TRANSACTION ........................................................................................................................... 25

7.3.4 USE CASE: TAX EXEMPT ...................................................................................... 25

SCENARIO: DUTY FREE TAX EXEMPTION ................................................................................. 25 SCENARIO: TAX EXEMPTION BY AGE ........................................................................................ 25 SCENARIO: TAX EXEMPTION FOR NON-PROFIT GROUP........................................................... 25

8. PLANNED DELIVERABLES........................................................................................... 25

9. DOMAIN GLOSSARY ...................................................................................................... 25



1. Introduction

This document serves as the IXRetail POSLog Work Team Charter and executive overview document. It has been developed following the, IXRetail Development Process, and includes:

• Version Change Documentation • Team Name • Team Mission • Membership Roster • Business Justification • Mission Scope • Use Case Survey • Planned Deliverables • Revision History • Domain Glossary

2. Version Change Documentation POSLog version two was developed following the beta implementations of version 1 to expand the functionality and incorporate corrections and enhancements suggested by early implementers.

2.1 Revision History Event Changes Date

Version 1.0 01-Jul-2002 Version 2.0 - Added customer identified corrections to the Version 1

standard - Added additional sales and return use cases (41 Total) - Added tendering validation thru use cases (25 Total) - Added taxation validation thru use cases (18 Total) - Extended domain model and schema to include (to be

validated in a future version): Tender control transactions Control transactions Foodservice transactions Forecourt transactions Inventory control transactions

-

12-June-2003



POSLog 2 is a Proposed Recommendation that is ready for implementation by vendors and retailers. ARTS requests that those implementing POSLog V2 will send comments and questions to [email protected] to enable development and release of V3. V3 is targeted for release before the end of 2003. Please see the IXRetail Technical Report: Best Practices -- Schema Extensibility available on www.nrf-arts.org for the approved method to extend this and all IXRetail schema. It is required that this method be followed to pass conformance testing.

3. Team Name The name of this IXRetail Work Team is POS Transaction Log (POSLog).

4. Team Mission The mission of the IXRetail POS Transaction (POSLog) work-team is to develop a standard comprehensive schema of all data captured at multiple points of sale that can be used to integrate POS systems with most related applications such as ERP’s, Fraud Analysis, Customer Purchase History, Big Ticket, etc. any system that can use POS data in a publish and subscribe manner. Future releases of the standard POSLog may include request respond messages.

The IXRetail POS Log Schema has been developed using the ARTS Data Model and other works provided by a cross section of retail segments including convenience, fast food, general merchandise, specialty, food and drug to ensure broad based adoption.



4. Membership Roster Chairman: Version 1: Tony Montgomery-Smith PCMS-Datafit Version 2: Richard Halter ARTS-MIC Authors: Version 1: Richard Halter Apigent Solutions Stuart McGrigor, ARTS Tony Montgomery-Smith PCMS-Datafit Version 2: Richard Halter ARTS-MIC Contributors: Version 1: Alice Cain-Nelson Nordstrom Doug Jones Target John Carrier Shell International & IFSF John Hervey NACS Jon Ransdell McDonald’s Tryggvi Thordarson HBI Jim Galloway AfterBOT Version 2: Jeannine Ralston The Limited, Inc. Perry Kramer Ames Department Stores, Inc Ann McCool Radio Shack Corporation Tim Reagan Radio Shack Corporation John Rohland Blockbuster, Inc. Nancy Hudak Target Corporation Timothy Hood Triversity Jim Galloway AfterBOT John Fluke IBM Ellen McCubbin IBM Michael Maximilian IBM Barry Henderson ISS Retail Paul Olson Blue Martini Yoko Nakagawa Drummond Group Mike Dillon Drummond Group


June 12, 2003 Page 10 of 10

John Hervey NACS Brian Blauvelt CRS Retail Systems Jerry Rightmer 360 Commerce Steve Gannon 360 Commerce Aaron Link SIVA Corp Ed Shirey ELSWare Technologies, Inc. Richard Mader ARTS Stuart McGrigor ARTS Tony Montgomery-Smith PCMS-Datafit

5. Business Justification

Introduction Point of Sale Data is the most frequently and perhaps the most valuable data in retailing. This data is used by a myriad of associated systems, from sales reporting to complete back office merchandise processing and reporting systems. Many of the business systems that use POS data are shown on page 7. POS is the most critical system in retail, the only place customers are served and money exchanged. Accordingly, POS systems must operate 100% of scheduled hours which requires that POS system changes be very controlled and infrequently. Integrating POS with new or replacement systems is therefore time consuming and costly, yet often required due to the number of systems that utilize POS data. ARTS IXRetail has developed the standard POSLog to allow frequent and low cost integration with POS data without jeopardizing the accuracy and reliability of the POS systems. Various solutions have been tried. One solution is to obtain all systems from the same vendor. Most retailers reject this solution, as a single vendor normally does not provide the “best of breed” solution for all the systems.

A second solution is to build all the systems in-house. Retailers normally reject this approach because of the initial development cost and the impossible commitment to maintenance and future upgrades.

IXRetail provides the third solution, by creating a standard POSLog (TLOG) which vendors of POS software and related systems can adopt, thereby providing an effective and less cost costly solution for POS integration. So of these potential solutions IXRetail is clearly the best, if you are buying Retex, SAP or simply a Layaway or Big Ticket system.

IXRetail POSLog requires no special integration software, reduces implementation costs, and allows retailers to easily enhance or extend purchased systems.

POSLog has been designed to provide sufficient processing speed. One feature eliminates the need for a runtime XSLT translation conversion. Partial departure from the IXRetail POSLog does not destroy all the benefits. In practice, systems are likely to have some extension messages and elements; the effect of which is that some XSLT mapping may be required, but the costs can be contained proportionately.

The benefits of specifying IXRetail POSLog are clear for the retailer & vendor alike:


June 12, 2003 Page 11 of 11

• Allows mix and match of differing POS related systems within the same enterprise. • The barriers of entry into new technology are lowered, allowing pilot and proof of

concept projects test systems without great impact on existing legacy systems. • The need for costly converter software & mapping services for each kind of POS is

reduced if not removed entirely.

Only one format transaction log need be supported by a particular software system, which reduces software costs.

What is a POSLog? POSLog is all the data captured at point of sale, sales, returns, exchanges, delivery, customer and others. POSLog data can be created at the POS terminal or the store or central server thereby allowing POSLog schemas to be formatted from the following selling channels:

• In-store POS • Web • Tele-sales • Mail-order • Kiosk

Many retailers have reached out beyond in store point of sale into one or more of the new selling channels, creating multiple sources for POSLog data. Ensuring that multi-sourced POS data can be merged into one consistent all-inclusive stream of data for use by multiple systems within the enterprise is a pre-eminent integration issue in the retail industry. The POSLog provides a standard basis for this integration.

Web BasedSelling

Tele-Sales Mail Order

Kiosk

POS

POS-Log

Other Apps

6. Mission Scope The IXRetail POSLog includes many different kinds of transactions and events. POSLog was designed to permit integration with all the business systems shown on the next page. The initial


June 12, 2003 Page 12 of 12

version of POSLog is best used in a publish-and-subscribe manner limiting some of the integration required by some of the business systems shown. Future releases will enable request-response real time integration. Beyond business system integration, POSLog can transport control transactions often used in sales audit and fraud detection.

The IXRetail POSLog Schema consists of a single XML Schema that defines the set of all possible transactions & events that can be sent by a POS to another system in the retail enterprise:

• Retail Transactions: Transactions where one or more items are sold or returned to or by customers.

• Tender Control Transactions: Transactions that record the movement of cash (and other tenders) into and out of various tender repositories (Cash-drawer, Till, Safes etc.) in the retail enterprise.

• Control Transactions: Transactions that record miscellaneous activities performed at POS. (E.g.: logon & logoff, lock & unlock, No sale, Accounting period close, etc.)

6.1 Out Of Scope for Version 2 The following have been included in the Version 2 of the POSLog Domain Model and Version 2 of the POSLog Schemas but have not had use case verification and will be validated in a future version.

• Tender Control Transactions • Control Transactions • Food Service Transactions • Forecourt Transactions • Inventory Control Transactions

This allows the POSLog users the knowledge of how these extensions will be handled and allows them to provide feedback on missing elements or wrong implementations.


June 12, 2003 Page 13 of 13

Alterations

POS

Payments and Refunds

Approve Credit/Debit/Check Transaction

Record logging on and off

Sales and Returns

Drawer PullsDrawer Loans

Tip OutsTender Adjustment

Paid Out, Paid In, No Sale

Customers

Create Order and P

ay

New AccountsN

ame,

Add

ress

and

Item

Info

rmat

ion

Update Software - App/Equip Status

Real-t

ime

mon

itorin

g

of a

ctivit

y

Correct Price and

Associated data for each item

Customer setup data and points

Setup ListsRetrieve Lists

Debits & Credits

credit authorization

Time andAttendance

Online CreditAuthorization

Loyalty

Gift Registry

Cash Office/sales audit

Fulfilment/Customer Order Management

Make/Ship Instructions

Replenishment Requisition for Back Order

Purchasing

Requisition for Special Order

PLU

Check

out G

oods

and P

ay

Catalogue

Comprehensive Product Informaiton

Correct Price and

Associated D

ata

Web BasedSelling

Layaway

Voucher/GiftCertificate Management

Customer

InformationServices

Accounting

Customer AccountManagement

Loss PreventionSales History

Customer Delivery,Will Call

VisualMerchandising

Image of the Item

CommissionManagement

SalesPulling

Items in another store

Stock Locator

Loca

te Ite

m

Currency Rates

Rentals

Loaners Consignment

Activation Cards

CouponAuthorization

POS-Log

Special Orders,

Laways, Sales &R

eturns

Stock Inquiry

Chec

k Av

aila

bility

Price Server

CatalogManagement

Store

Sale/StockRecording

Stock Reservation

Reserve stock

Tele-Sales

Alteration Instructions


June 12, 2003 Page 14 of 14

7. Use Case Survey • The set of use-cases to produced by the POSLog work-team include use-cases for

all interactions shown on the application unit diagram above: • Recording Sales, Returns, Layaways and Special Orders, including Pickup &

Delivery of merchandise. • Recording of relevant sales and consumption taxes that were charged. • Recording of sale and return transaction tendering. • Recording of miscellaneous cash movements, performed at POS. • Recording of administrative tasks performed at POS.

The Use Case documentation is divided into 3 volumes. Volume 1 deals with physically selling and returning items. Volume 2 deals with the various tendering situations. Volume 3 deals with taxation.

7.1 Volume 1: Sales and Return Volume 1 contains all the use cases dealing with selling and returning items.

7.1.1 Use Case: Item purchase One or more items are purchased via any one of a number of sales channels. The transaction is entered in via an appropriate application, and is sent using the POSLog schema to the POSLog application, which may forward to the transaction to other applications in the enterprise.

Scenario: Item Purchase at POS Customer selects one or more items and purchases them. The number of those items available in inventory is decremented.

Scenario: Item purchase via www or Tele-Sales Customer selects one or more items for purchase via a website, or from a printed catalogue. Purchase order is accepted via one of www, fax or telephone along with payment details. The items purchased, are shipped to the customer, and inventory count for the items is decremented.

Scenario: Item purchase for delivery from store Customer purchases some item of furniture that’s made from re-cycled timber. They want the exact chosen item, because they like the patina of age on that item. They specifically do not want ‘one just like it’ from the warehouse.


June 12, 2003 Page 15 of 15

Scenario: Item purchase for delivery from warehouse Customer purchases some item of furniture for delivery. The Cashier arranges delivery of ‘one just like it’ from the warehouse.

Scenario: Item purchase for alteration & subsequent pickup Customer selects some kitchen cabinets from unpainted models on shop floor, and selects color for them to be painted. The paint-shop takes the cabinets from inventory, paints them and makes them available for the customer to pickup.

Scenario: Item purchase by random weight Customer purchases an item from the delicatessen, which is sold by weight.

Scenario: Item purchase of serialized item Customer buys one or more items some of which require that the serial number of the unit sold be recorded.

Scenario: Item purchase with part exchange Customer purchases an item, such as a car battery, where an accompanying dead battery will reduce the price of the new battery. There is no refundable amount on a dead battery without a corresponding purchase.

Scenario: Item purchase with quantity pricing Candy bars are priced at $0.59 each or 2 for $.99. This is not a promotion; this is the normal pricing for the collection of items.

Scenario: Item purchase of multi-package items Customer purchases a can of a popular soft drink. The can is scanned into the POS. The UPC code on the can is for both a can and a 6 pack. Some distinction between the single can and the 6-pack must be made.

Scenario: Item purchase via open department An item is manually entered into the POS without scanning because the item doesn’t scan or it isn’t setup in the POS. Item information is not entered, but some generic item classification of Merchandise Hierarchy is entered with a dollar amount instead.

Scenario: Item purchase by selling location Customer purchases an item that is sold in multiple locations within the store. The store wants to track where the item is selling or not selling, and may assign inventory holdings to each selling location. This helps them arrange the items in the store to maximize sales.


June 12, 2003 Page 16 of 16

Scenario: Item purchase with special order Customer wants to buy a particular model of computer but wants a different monitor and more RAM.

7.1.2 use case: Item purchase of kit/combo/Collection items For some retailers an item may actually be a Kit, Combination or Collection of other items, e.g. A garden furniture set, may comprise a table, four chairs and a sun umbrella. Some retailers may allow some items in some kit items to be substituted; others may not.

Scenario Kit/Combo/Collection Purchase Without Substitution Customer buys a kit of garden furniture comprising a table, four chairs and a sun umbrella. The POS sells this kit as if it was a single item, and no substitutions are permitted.

Scenario: Kit/Combo/Collection Purchase With Substitution Customer buys a kit of garden furniture set but wants to replace the sun umbrella with another brand of equal value. The system removes one brand of sun umbrella from the kit and adds the desired brand of sun umbrella to the kit.

Scenario: Foodservice Combo Customer buys a combination meal and has the onions removed from the hamburger.

7.1.3 use case: Item purchase & REturn with deposit Many items are sold in a container that has a deposit. This deposit is included in the retail price of the item, and is refunded to the customer when the empty container is returned. Examples include, soft drink bottles & crates, bread crates, milk bottles & crates, etc. The examples in this use case use a wooden crate holding 12 bottles of beer, to show how an item with multiple deposits would be handled.

Scenario: Purchase Crate of Beer With Empties Customer brings a wooden crate containing 12 empty beer bottles, and purchases another wooden crate containing 12 full bottles of beer. Customer does not have to pay any deposit on the crate & bottles, because he is return a complete set.

Scenario: Purchase Crate of Beer Without Empties Customer purchases a wooden crate containing 12 bottles of beer without bringing in a matching set of empties.

Scenario: Return Empties Customer returns a crate of bottles to retrieve the deposit.


June 12, 2003 Page 17 of 17

7.1.4 use case: Item purchase with refillable containers Propane gas is sold in large refillable containers. Usually the customer brings in an empty container for refill, although when they don’t the retailer can always sell them a refillable container. The main point to note is that the containers are sold, and there is no deposit on empty containers.

Scenario: Item Purchase With Refillable Container The customer has bought in one or more approved empty containers, each of which hold 15 Kg of propane, for refill.

Scenario: Item Purchase Without Refillable Container The customer purchases one or more approved empty containers, each of which hold 15 Kg of propane, and has them filled.

7.1.5 use case: Attempted Item purchase with rain check Customer wants to purchase an item that is temporarily out-of-stock. Customer gives contact details & receives a “rain-check” receipt guaranteeing the price of the item when it is next available.

7.1.6 use case: Item purchase on layaway/laybye Customer wants to purchase an item but can’t afford to pay for it right now. The customer pays a portion of the purchase price as a deposit, and the store keeps the item in a separate inventory location. The customer makes subsequent payments for the item, and when the purchase price has been paid the customer receives the item. The customer may change their mind at any time, and receive some or all of the money paid as a refund or gift certificate.

All scenarios in this use-case have the same set of Actors.

Scenario: Customer Commences Layaway Customer wishes to purchase an item over a (short) period of time, the retailer provides allows the customer to commence a layway account.

Scenario: Progress Payment The customer makes a progress payment on a layaway that does not complete the layaway.

Scenario: Customer Completes a Layaway Customer makes a final payment on a layaway account and receives the items being sold.


June 12, 2003 Page 18 of 18

Scenario: Cancellation Customer wishes to cancel the Layaway and receives a (partial) refund, layaway items are returned to stock.

7.1.7 use case: Item purchase with manual price override Items can have their prices overridden for a variety of reasons. The scenarios in this use-case show a number of examples, and attempt to show that the form of the resultant XML does not vary very much. All the scenarios in this use-case make use of the same set of actors and system interaction diagram.

Scenario: Open PLU (Unpriced Item) Customer purchases an item that is recognized by the POS but does not have a price in the system. Although the cashier will perform a manual price override, it may not require any special approval because the item doesn’t have a price in the system.

Scenario: Rain Check Customer purchases an item, and has a rain-check receipt, guaranteeing the item at a lower price than the POS looks up.

Scenario: Customer Complaint About Price Customer complains about the cost of an item, compared to the price at some competitor. The manager gives the customer a discount on the price of the item, to match the competitor price.

Scenario: Different Tag Price An item is scanned at $12.99, but the item price tag says the item is sold for $10.99. The POS is overridden and the price is entered for $10.99

Scenario: Manager Complimentary The customer has a problem with their order. The manager gives them a complimentary scarf to make things better.

Scenario: Charitable contribution The manager gives a TV to a charitable cause for a raffle, and it is entered into the POS as a 100% discount.

7.1.8 use case: Item purchase with employee training The store is training a new employee and doesn’t want the transactions performed during the training session to have any affect on inventory, financials…etc.


June 12, 2003 Page 19 of 19

7.1.9 use case: Item return Items are returned to a retailer for various reasons, and the return process may be conducted over the www or via a Tele-Sales center. The scenarios in this use-case illustrate the fact that the resultant XML follows the pattern established by the sale of items via the various channels. All scenarios in this use-case us the same set of actors.

Scenario: Return to Store Customer returns an item to a store, and the number of those items available in inventory may or may not be incremented, depending on whether the returned item is put back into stock.

Scenario: Return for Delivery by Customer Customer wishes to return an item purchased over the www, (or via tele-sales). Tele-sales enters the return into the system, and gives the customer the delivery address of a central returns facility. The number of those items available in inventory may not be incremented, until the actual item is delivered at the returns facility.

Scenario: Return for Pickup from Customer Customer wishes to return a large item. The store cashier enters the return into the system including the pickup address. The number of items available in inventory may not be incremented, until the actual item has been received by the returns facility.

7.1.10 use case: Gift Certificate Purchase For most retailers Gift Certificates, Money Order, Stored Value Card or Voucher are not items, so the sale of a Gift Certificate must explicitly state that the transaction is selling a Gift Certificate rather than an Item.

7.1.11 use case: Item Purchase on Backorder When a Customer wishes to purchase an item that is temporarily out of stock a Back-Order is entered at the POS, the customer may pay some of or the entire purchase price of the item as a deposit. When the item is back in stock the arrangements will be made for the customer to complete the purchase. All scenarios in this use-case use the same set of actors.

Scenario: Back-Order for Pickup Customer wishes to purchase an item that is temporarily out of stock. A Back-Order is entered in at the POS, the customer may pay some or all of the purchase price of the item as a deposit. When the item is back in stock the customer will pickup the item from the original store.


June 12, 2003 Page 20 of 20

Scenario: Back-Order For Delivery Customer wishes to purchase an item that is temporarily out of stock. A Back-Order is entered in at the POS; the customer may pay some or the entire purchase price of the item as a deposit. When the item is back in stock, fulfillment will arrange for the item to be delivered to the customer.

Scenario: Previous Back-Order Cancellation When the store is unable to source an item on Back-Order, the Back-Order must be cancelled, and the customer receives their deposit back.

7.1.12 use case: Batch End Of Day transfer At the end of day, all the individual transactions are send above store in one file.

7.2 Volume 2: Tender Use Cases Volume 2 contains all the various tendering situations.

7.2.1 USE Case: Sale Tender Customer selects one or more items and purchases them with various tenders.

Scenario: Customer Tender’s Purchase with Cash Tender without Cash Back Customer selects one or more items and purchases them with exact cash.

Scenario: Customer Tender’s Purchase with Cash Tender with Cash Back Customer selects one or more items and purchases them with cash getting cash back.

Scenario: Customer Tender’s Purchase with Debit or Credit Tender without Cash Back Customer selects one or more items and purchases them with a debit or credit card.

Scenario: Customer Tender’s Purchase with Debit or Credit Tender with Cash Back Customer selects one or more items and purchases them with debit or credit card getting cash back.

Scenario: Customer Tender’s Purchase with Check Tender without Cash Back Customer selects one or more items and purchases them with a check.


June 12, 2003 Page 21 of 21

Scenario: Customer Tender’s Purchase with Check Tender with Cash Back Customer selects one or more items and purchases them with a check getting cash back.

Scenario: Customer Tender’s Purchase with Travelers Check in a Foreign Currency Customer, on vacation in a foreign country, selects one or more items and purchases them with a traveler’s check in a foreign currency.

Scenario: Customer Tender’s Purchase with Purchase Order Customer selects one or more items and purchases them with purchase order.

Scenario: Customer Tender’s Purchase to Store Charge Account Customer selects one or more items and charges them to their store account.

Scenario: Customer Tender’s Purchase with In-Store Coupon and Cash Customer selects one or more items and purchases them with in part with an in-store coupon and the remaining with cash.

Scenario: Customer Tender’s Purchase with Manufacturer’s Coupon and Cash Customer selects one or more items and purchases them with a manufacturer’s coupon and cash.

Scenario: Customer Tender’s Purchase with Voucher, Gift Certificate or Other Stored Value media with change as Voucher and Cash Customer selects one or more items and purchases them with a gift certificate with the difference refunded as cash.

Scenario: Customer Tender’s Purchase with Voucher, Gift Certificate or Other Stored Value media with change as Voucher Only Customer selects one or more items and purchases them with a gift certificate and getting a voucher for the remainder of the value of the gift certificate.

Scenario: Customer Tender’s Purchase with Voucher, Gift Certificate or Other Stored Value media with change as Cash Only. Customer selects one or more items and purchases them with a voucher, receiving the change in cash.


June 12, 2003 Page 22 of 22

Scenario: Customer Tender’s Purchase with Voucher, Gift Certificate or Other Stored Value media with no change Customer selects one or more items and purchases them with voucher but tracking the unspent amount.

Scenario: Customer Tender’s Purchase with Food Stamps Customer selects one or more items and purchases them with food stamps in a location where the taxes are forgiven.

Scenario: Customer Tender’s Co-Pay Purchase, i.e. Drug Purchase Customer selects one or more items and pays co-pay, instead of the total price, typically insurance picks up the remainder of the cost of the item(s).

Scenario: Customer Tender’s Purchase with “Mall Bonus Bucks” A customer goes into a store in a mall and purchases an item with “Mall Bonus Bucks” she received at another store in the mall. She receives the change from the “Mall Bonus Bucks” as cash.

7.2.2 USE Case: refund tender Customer returns an item to a store, and the number of those items available in inventory may or may not be incremented, depending on whether the returned item is put back into stock.

Scenario: Customer Gets Refund in Cash Customer returns an item to a store, and gets the refund in cash.

Scenario: Customer Gets Refund on Their Credit Card Customer returns an item to a store, and gets the refund on their credit card.

Scenario: Customer Gets Refund on Their Store Account Customer returns an item to a store, and gets the refund on their store account

Scenario: Customer Gets Refund in Merchandise Voucher Customer returns an item to a store, and gets a store voucher.

Scenario: Customer Gets Refund in a Check Sent to an Address Customer returns an item to a store, and a check is sent to the customer’s home address.

7.2.3 USE Case: Post Purchase Price Adjustment


June 12, 2003 Page 23 of 23

Scenario: Customer Gets Refund in Cash After Returning to the Store Customer purchases an item. On the way to the car, the customer realizes she was overcharged for the item. She returns to the store and gets cash for the difference.

7.2.4 USE Case: Merchandise for Store Use

Scenario: Employee Takes an Item Off the Shelf For Use in the Store An employee takes an item off the shelf to use in the store. The store charges the purchase against the store account.

7.3 Volume 3: Taxation Use Cases Volume 3 discusses the various taxation situations. It deals with US style sales tax, European style VAT taxes, tax exempt and tax forgiven use cases.

7.3.1 USE Case: Tax Customer selects one or more items and purchases them with various tenders.

Scenario: US Sales Tax at the Transaction Level A customer buys several items for $10.00 USD and has a 10% sales tax added. The total cost of the items is $11.00 USD. The amount of tax is calculated using a tax table.

Scenario: Multiple Tax Authorities A customer buys a $10.00 item with a 5% municipal tax. The price of the item is now $10.50. The state tax authority uses this value ($10.50) to compute their sales tax. If the state tax is 10%, then the total cost of the item is $11.55.

Scenario: Eat In Taxes v Take Out Taxes

Alternate Flow 1: Taxes Not Charged on Food Eaten in the Store

Alternate Flow 2: Taxes Charged on Food Taken from the Store A customer purchases 3 hamburgers to take home.

Scenario: Tax on Manufacturer’s Coupon A customer buys and item and pays with a combination of manufacturer’s coupon and cash. The coupon is treated as tender and the taxes are on the entire purchase.


June 12, 2003 Page 24 of 24

Scenario: Purchase Taxed at the Point of Origin with Destination in Another State Customer selects one or more items for purchase via a website, or from a printed catalogue. Purchase order is accepted via one of www, fax or telephone along with payment details. The items purchased, are shipped to the customer, and inventory count for the items is decremented.

7.3.2 Use Case: VAT Taxes

Scenario: Normal VAT Tax A customer purchases an item. The VAT taxes are reported at the item level.

Scenario: VAT Tax on Transaction A customer buys an item at an airport. In addition to the VAT on the individual items, there is a fixed VAT amount on the transaction.

Scenario: VAT Tax Exception A customer purchases an item. A different tax rate was applied. Both the normal and exception rate and amounts are recorded.

Scenario: Multiple VAT Tax on Kit A customer purchases a child’s toy that contained 100 parts and as a part of the “kit” they get a bottle of aspirin. The 2 parts of the “kit” are taxed at a different rate.

Scenario: Zero Percent VAT Tax and Normal VAT Tax on the Same Transaction A customer buys two items. One has a VAT Tax but the other doesn’t.

Scenario: VAT Luxury Tax A customer purchases an expensive item. The item has a normal VAT tax and a luxury VAT tax.

7.3.3 USE Case: tax forgiven

Scenario: Illinois Food Stamps Customer selects one or more items and purchases them with food stamps in a location where the taxes are forgiven. The tax rate is 10%.


June 12, 2003 Page 25 of 25

Scenario: Some of the Items are Taxed and Others Are Not in the Same Transaction A customer purchases some of their items with food stamps and others in the same transaction with cash.

7.3.4 USE Case: Tax Exempt Diplomats get no tax charged while his aide has a tax reduction of 5%.

There can be tax exempt - people who have a tax exempt status a. Old age b. Foreigner c. Non-profit organization d. Duty Free – import or export

Scenario: Duty Free Tax Exemption A customer purchases an item at the airport en route to a foreign country in the Duty Free Shop.

Scenario: Tax Exemption by Age An elderly customer purchases an item and gets a tax exemption.

Scenario: Tax Exemption for Non-Profit Group Non-profit organizations are exempted from paying tax.

8. Planned Deliverables

Deliverable Estimated Date Actual Date

9. Domain GLOSSARY Term Definition POS An acronym for Point of Service that includes traditional

Point of Sale devices in addition to Kiosks, Websites and Telephone call centers and any other device or system that is used to record the exchange of Merchandise for Tender.

POSLog An abbreviation for the POS Transaction Log, an application that stores transactions received from other applications for future reference, and makes them available to other applications in the system.


June 12, 2003 Page 26 of 26

Arts

Documents

poslog v2

arts xml poslog schema

arts members

revision history

documentthis document

ixretail pos log charterjune

version change documentation

team mission