SCIS 2.0 Reliability, Performance, and Refactored Processing
Over several releases, SuiteCommerce InStore (SCIS) has undergone internal changes that focus on increased reliability and performance.
SCIS 2.0 continues this work by providing enhanced reliability, recovery, and record-handling for payment processing. These enhancements benefit both your sales associates and your customers by reducing the time needed to process transactions at the point-of-sale (POS).
Reliability
Improvements that promote reliability include:
-
Transaction recovery if SCIS fails while checking out a customer
-
Feedback on errors reported by the payment authorization process
-
Application recovery for errors that occur on the payment device
Performance Improvements
We built in performance improvements in these areas:
-
Adding lines to the cart during a Sale or Return/Refund/Exchange
-
Performing an unvalidated return on a line in the cart
-
Performing validated returns of items from an original transaction
-
Reducing the waiting time from payment authorization to showing the authorization in the application
-
Tendering using any payment method, including payments through an EMV-enabled payment device.
-
Time required after completing a transaction until the application is ready for the next transaction
Audit Log Availability Improvements
You can use the SCIS Audit Log to track restricted operations that were performed during SCIS transactions. Restricted operations are events that require approval from authorized personnel, such as applying a discount over the designated limit. Audit logs are generated automatically whenever a restricted operation occurs.
SCIS 2.0 includes the option to view audit logs from the associated transaction records. Previously, access to audit logs was limited to viewing audit log records, with links to the transactions.
Refactored Payment Processing
SCIS 2.0 provides enhanced payment processing at the POS and in NetSuite. These enhancements reduce the wait from tendering payment to having the receipt display. The shorter wait times are gained by pre-staging the required records and having most behind-the-scenes processing occur after the customer interaction is complete.
Another performance factor is that we use an on-demand transaction number instead of waiting to receive that number from NetSuite. This on-demand number is generated locally and is later referenced to the NetSuite transaction number. We include the on-demand number in the bar code to assist with processing for exchanges and refunds.
See SCIS 2.0 Payment Processing Comparison With SCIS 1.0 for more information about the SCIS 2.0 “payment first” method.
Records Removed From Transaction Processing
The following two records are no longer used to process transactions. Support for these records will continue for activities dependent on historical data, such as exchanges and refunds from past purchases.
-
Cash Sale — If you have standard scripts that use the Cash Sale record, the SCIS team will modify them to use Invoice and Sales Order records. If you have custom scripts that depend on the Cash Sale record, you will need to have those scrips updated.
-
Customer Payment — Replaced with the Customer Deposit record.
Also see SCIS 2.0 Payment Processing Comparison With SCIS 1.0.