Benchmarks and Best Practices for Orders and Transaction Export

Orders and Transactions

1. Orders - Any Sale, Return, Refund, or Exchange is an Order in POS.
2. Transactions - All events on POS Login, Logout, Void, Till Open, etc are referred as Transactions and logged in Electronic Journal.

Note Export files can be XML files in NRF POSLog 6.0 or JSON

Export Options

Orders

1. API with JSON payload - As Orders are placed on POS, an API is call out is made with the JSON payload of the current order. Point of Sale API spec can be found here. This would require a web server on the customer side that would accept incoming orders and provide an SLA of 99.99% uptime. Replay options are available on CMS.

   Out of the box, Point of Sale supports real-time order export into Salesforce Commerce, Salesforce OMS, and NetSuite.

2. Real-time Exports flat files- As orders as placed on POS, a TLog file in POSLog 6.0 format is created and published to an SFTP site.
3. Scheduled Batch Jobs with Compressed files - Scheduled jobs set to run at a set frequency, pick up the orders that were placed since the last export run, create individual TLog files for each order, and then create a compressed bundle to be exported to SFTP site.
4. Scheduled Batch Jobs with individual files - Scheduled jobs set to run at a set frequency picks up the orders that were placed since the last export run, create individual TLog files for each order, and send them to the SFTP site. Recommended frequency is hourly. Anything more aggressive than this can cause delays in publishing orders.

Note If API export is enabled Real Time export will only export orders via API. Flat files will not be transmitted in real-time. If flat files are needed then it needs to be as a scheduled Job.

As of July 2022, only one mode of order export is supported with API being the recommended and preferred option.

Transactions

1. Scheduled Batch Job with 1 file in CSV / TSV format on selected fields

Export Throughput numbers

Orders

1. API with JSON payload - 60,000 orders an hour on steady state. This is a horizontally scalable model and can scale up to 85,000 orders an hour
2. Real-time Exports with XML files in NRF POSLog 6.0 format - 8,000 orders an hour on steady state with Point of Sale SFTP provider Exavault. The bottleneck here is the number of connections Exavault can handle. Customers can use another FTP provider of their choice.
3. Scheduled Batch Jobs with Compressed XML files in NRF POSLog 6.0 format - 40,000 orders an hour on steady state. As the number of FTP connections are now reduced the throughput goes up.
4. Scheduled Batch Jobs with individual XML files in NRF POSLog 6.0 format - 3000 orders an hour as each file has to be generated and exported out. Known Limitation of this approach is with every run at max 1000 orders can be exported. So if a customer expects 20,000 orders in a day, then the job needs to be set to run at least every 20 minutes to be able to export all orders out.

Transactions

1. Scheduled Batch Job with 1 file in CSV / TSV format on selected fields

Recommended Setup 1

Orders

API with JSON payload - 60,000 orders an hour on steady state. This is a horizontally scalable model and can scale up to 85,000 orders an hour.

Recommended Setup 2

Orders

1. Real-time Exports with files - As orders are placed and files are shipped out in real-time
2. Scheduled Batch Jobs with Compressed files - This is a fallback that ships out the remaining orders that were not exported in real-time.