Oracle Point of Service: Oracle's Point-of-Sale Solution

Table 1. Oracle Modules Through Which a POS Solution Is Offered

Module

Features

Oracle Retail Point-of-Service (ORPOS)
Developed on the Java platform
Current version of full base release — 13.1.1

ORPOS can deliver the usual expected day-to-day front-end POS functionality (for example, scanning items, applying price adjustments, sales and tender processing) expected of POS applications for Tier 1 retailers. Back-office-type of store operations (for example, opening and closing the store and managing the registers) set up in the back-office application ORBO can be handled through ORPOS.
Key capabilities the solution can support include:

Complex promotions, including cross-channel promotions and redemption — for example, best deal and preferred customer.
Multiple types of item and transaction discounts and promotional pricing.
Advanced price execution to ensure the right discounts and promotions are applied without intervention.
Centralized customer database and customer-specific pricing to execute the central management of customer profiles and customer-specific pricing.
Capability to centrally retrieve cross-channel transaction data to facilitate returns.
Capability to increase sales through layaway, nonmerchandise sales, pickup and delivery reservations, and suggested sales, which provide added services.
Cross-store inventory search capability.
Set up and maintain customer profiles and purchase history to drive customer loyalty.
Line-buster retrieval for rapid transaction completion.
Item messages to communicate item-related information to the employee within the transaction.
Item pictures displayed in item look-up and related item screens for more-accurate item identification.
Configurable receipts to allow the retailer to address localization issues and/or to differentiate themselves from the competition — for example, add marketing or customer messages to the customer's receipt based on the items in a transaction.
Electronic receipts for convenience and to support "green" initiatives in the store — cashiers can offer customers the option of having receipts e-mailed to them for convenience, rather than printed at the till. The electronic receipt is an e-mail generated with a PDF version of the receipt attached to the e-mail.
Reporting for visibility and accountability — the structure and content of receipts and reports are defined in XML files known as blueprint files. These files are modifiable, and new blueprint files can be created using the Receipt Builder tool, which is an editor available as an Eclipse plug-in.

Version 12 of ORPOS incorporated several enhancements for internationalization. For example, ORPOS has a tax engine that ships with it with significant enhancements made in Version 12 to calculate the price inclusive of tax. The engine is configurable, so users can choose to use the North American configuration or the configuration for the value-added tax (VAT), with the VAT-detailed receipt dependent on the setting.
The base solution also supports localization foundations that are configurable to address country-specific localizations, such as translation, time format, currency, exchange rate table, date format/calendar, address, telephone number format and government-assigned numbers. (See Table 2 for more details on the multinational capability.)
A browser embedded directly in the POS can give sales associates access to the corporate portal, intranet or even the online store — for example, for in-store out-of-stock situations, the customer associate can view stock in other channels and assist the customer to order the item with a convenient delivery option.
Business logic in ORPOS exists as a library of Retail Domain objects based on a common object model for the consistent expression of business rules. It uses an application-independent design to support reusability and enable retailers to implement unique business rules through easy-to-modify parameters and, thus, can be extended to fit retailer-specific business needs. For example, the same business objects delivering ORPOS functionality at the traditional check-out in the store can be used at other points of service — for example, self-check-out. Support for the ARTS data model and using JDBC-compliant relational databases is included with the Retail Domain.
ORPOS relies on a data store based on the data model ARTS. The data store can be hosted by any variety of databases that conform to the JDBC standard. Persistence is encapsulated and abstracted from application logic using data-specific Retail Domain objects and a sophisticated data integration architecture that can be customized to support databases, flat files and nonstandard data stores.
Sales and control transactions are exported by ORPOS as platform-independent XML documents. Parameters are also received by ORPOS using XML documents.
For example, ORPOS has the ability to generate the Retail Sales Audit (ReSA) transaction log, referred to as RTLog. This format supports the integration between ORPOS and the Oracle ReSA application. In essence, this is a text-based format to support the normal POS transaction log (TLog) for the sales audit application to consume. The RTLog, which can be tailored by the number of stores and network bandwidth, can be produced "on the fly" or at the end of day. Feeds to the sales audit application are then used to update the ORSIM application in terms of sales history — for example, items sold and items returned. (Note: Oracle continues to support POSlog [IXRetail XML format] for other sales audit applications, as well as to create additional transaction log formats to support the retailer's legacy sales audit/financial systems.)
Message-oriented middleware allows asynchronous, guaranteed delivery of all data to and from the ORPOS application. To accommodate offline situations, the business data created at the POS is queued to prevent data loss.

Oracle Retail Back Office (ORBA)
Developed on the Java platform
Current version — 13.1.1

The ORBO application enables operational efficiency of POS back-office-type functions, such as in-store cash management.
Key capabilities for operational efficiency include:

Local in-store parameter maintenance and system configuration management. For example, authorized users can edit parameters to match store-specific or local policies, such as security settings or exchange rates.
In-store promotional event management. For example, the store manager can set up, view and maintain item, price and promotion files for store-specific assortments and events. It also has advanced features for customer-specific pricing and promotions.
Start and end-of-day operations.
Store-level time and attendance maintenance.
Store-level role and security maintenance.
Real-time and remote access anywhere in the store and enterprise.
Comprehensive and integrated reporting package.

ORBO is a browser-based application written entirely in Java and based on industry standards. For example, it relies on a data store based on the ARTS data model standard, which can be hosted on a variety of databases that conform to the JDBC standard. It can run on many different operating systems, databases and application servers, and it is optimized for products from Oracle and IBM.
The basis of ORBO is a set of "commerce services" developed using SOA design principles. These services are accessible from a variety of technology platforms, enabling the same business logic to be reused, extended or replaced across the enterprise.
As with ORPOS, sales and control transactions are exported by ORBO as platform-independent XML documents. Parameters are also received and distributed by ORBO using XML documents. Message-oriented middleware allows asynchronous, guaranteed delivery of all data to and from the ORBO application. It is worth noting that, when ORBO is deployed with ORCO, a Java-based transaction data exchange option is also available.

Oracle Retail Central Office (ORCO)
Developed on the Java platform
Current version — 13.1.1

The ORCO all-in-one application can be scaled to enable retailers to centrally oversee operations in all the stores in their estate, as well as to facilitate data movement and to access real-time information across all the channels in the enterprise. It provides a corporate repository of sales and customer information.
Key capabilities include:

Provision of enterprisewide aggregation of transaction, e-journal and signature information — for example, for loss prevention management. This is done through the Transaction Tracker component of ORCO.
Centralized management of customer information, including real-time access to customer information from any channel through the Centralized Customer component of ORCO. This enables customer data to be entered, stored and managed, and this information can be retrieved from any store through ORPOS.
Ability to manage the consistency of store policies via parameter management. For example, the Parameter Maintenance component allows an authorized operator to easily change the values of existing parameters for store applications, as well as to manage the distribution of parameters to applications running in all the stores.
Ability to query information based on business needs.

Like ORBO, ORCO relies on a data store based on the ARTS data model standard, which can be hosted on a variety of databases that conform to the JDBC standard.
As with ORBO, the SOA-based Web services, called Commerce Services, form the basis for ORCO, so they can be extended, replaced and reused as necessary.
For example, retailers may choose to build an in-store kiosk that uses the transaction and e-journal look-up capabilities found in the Transaction Tracker component of ORCO — this can be accomplished in a straightforward way by building an application that uses the Transaction Tracker Commerce Service hosted by ORCO.
ORCO uses a bidirectional data exchange facility, which provides the ability to distribute transactions and other information from points of origin to their systems of record, and provides the ability for retailers to manage data flow from the enterprise to their stores. Data — including transaction logs, e-journal files, signature data and parameters — is transferred as platform-independent XML documents that can be imported/exported on an automatic, scheduled or manual basis.
Customers also have the ability to extend their solutions to transfer other types of data, such as price files, tax information or exchange rates. Data can be exchanged asynchronously using message-oriented middleware that assures delivery or, when appropriate, synchronously using message-oriented middleware or Web services. Data travels bidirectionally and, when using assured delivery, is queued in offline situations, so nothing is lost.

Oracle Retail Returns Management (ORRM)
Developed on the Java platform
Current version — 13.1.1

The ORRM application can be used to efficiently automate the management of policies for returns at an enterprise level and, when implemented in conjunction with ORPOS, has the potential to reduce fraudulent returns.
During a return transaction, ORPOS sends a return request message to ORRM containing customer, cashier and transaction facts. In turn, ORRM sends ORPOS a response message indicating what action must be taken to complete the return. This integration speeds return handling through intelligent automation and can even provide preferential return policies for loyal customers.
Key components of ORRM are:

Returns Authorization Engine: This engine evaluates each return request and provides the cashier with a guided response on how to handle the return according to preset policies. For example, the guidelines can include whether to accept/reject returns based on the appropriate store policies, which tenders to use for refunds, whether a manager is needed for approval or whether to request positive identification documentation from the customer.
Return Policy Manager: This enables authorized operators to use built-in, retailer-specified business rules to create and modify return policies, and is accessed via a Web-based workbench. These rules are used to evaluate the return and incorporate all available criteria to determine how the return should be handled. This can include information such as whether a receipt is available, identification of the merchandise group/item, the customer's return history, which store the return is taking place in and the condition of the item.
Customer Service Console: This Web-based interface provides authorized users immediate access to return/refund information to handle customer inquiries or to research particular trends. Receipts can be accessed by customer information, a cashier ID or a store. Other features of the console include:
- Customer service overrides to grant returns to customers who had previously been denied, or to tighten controls for chronic return abusers (customers or employees) or shoplifters
- Receipt search to allow searching the receipt by the unique identifier or other information, such as cashier, customer or item information
- Audit trail to simulate a rule-by-rule flow of the item through the policy to see which rules triggered the final decision that was applied to the return

Table 2. Multinational Capabilities of ORPOS

Function

Capabilities

Multilanguage

ORPOS has been implemented in many countries, and existing translations of ORPOS include the following languages:

English
French
German
Italian
Japanese
Korean
Portuguese
Russian
Simplified Chinese
Traditional Chinese
Spanish

An implementation is currently progressing in Japanese.
ORPOS uses external files to display text and characters on the screen, which makes it easier to modify and add new translations as needed.
The ORPOS approach to language support allows the definition of a store's default language, as well as allowing employees to select their preferred language. This feature simplifies training and presents the application in the language that is most comfortable to the employee.
Furthermore, it's also possible to define a customer's preferred language to be used for customer displays and receipts. However, although the receipt for the creation of the order is printed in the preferred language of the customer, the receipt for a completed order is not printed in the preferred language of the customer.

Multicurrency

The current release, 13.1.1 supports the following currencies:

U.S. dollar
British pound
Japanese yen
Euro
Mexican peso
Canadian dollar

A localized foundation is provided that can be used to support any currency. However, Oracle does not test all the currencies available in the countries where there is language support.
Although the till reconcile and daily register operations are not affected, if currencies additional to those called out as supported in the current release are added to ORPOS, they are not displayed in the financial reports.
The POS solution has also been implemented in an environment that supports Dynamic Currency Conversion (DCC). DCC is understood to govern the conversion rate that is used when a customer pays for an item with a credit card that uses a non-native currency. This special rate is determined by the cardholder, and the POS system must access it and use it to create the correct amounts in the transaction.

Taxation and Fiscalization

The application has been implemented in an environment that calls for adherence to local fiscalization regulations — for example, in Italy for the nota fiscal VAT invoicing requirement and in Mexico for the Factura VAT invoicing requirement.

Support for Europay, MasterCard and Visa (EMV)

The application has been implemented in "chip and PIN" EMV environments — for example, in the U.K.

Table 3. Examples of Integration With Payment-Processing and ERP Applications

Payment-Processing Application/Payment Switch and Vendor

ERP Applications

ISD Payment Switch — ISD

Oracle

Solve SE — The Logic Group

Oracle Retail

StorePay — IBM

SAP

iPay — Oracle

JDA

eSockets — Mosaic

Intrepid

Also integrated with offerings from AJB, Setefi, 3C and Plutus Software

Retail Interact

Table 4. Examples of Integration With Front-End Hardware Peripherals

Device

Vendor

Bar code scanner

Symbol, HP

Weighing scales

Magnetic stripe reader

IBM, HP

Swipe reader — smart card

Swipe and park reader — smart card

PIN entry device

Ingenico, VeriFone

Contactless reader

Biometric reader

DigitalPersona

Radio frequency identification (RFID) reader

Mobile/cell phone

iTouch, Motorola

Self-check-outs

NCR

Kiosks

Mobile POS

DT Research

Other