You are here:
TLog Export FAQs
Find answers to frequently-asked questions about the Point of Sale TLog export.
| Scenario | Solution | Help link |
|---|---|---|
| What is the XML schema of this export? | Refer to Retail Transaction Interface in the help link. | See the OMG ARTS XML Schemas documentation. |
| What will be the file name format of the export? | It can be configured, below is the standard format: RetailCloudOrders%1$tY%1$tm%1$tdT%1$tH%1$tM%1$tS_ Example: RetailCloudOrders20210301T122608__FR00000001.xml |
|
| How do I find the order number? | The order number can be found within the filename, specifically after the double underscores. For example, in this file, SHOPNOW_US_20220729T055610__OPS-022-1-072920220003_1659074169659.xml. The order number would be OPS-022-1-072920220003_1659074169659. | |
| What are different transaction statuses? |
|
|
| How are exchanges handled? | If you are exchanging an item and getting a new one of the same or different value then you will get two POS logs. One for the old order showing the item was returned/exchanged with IsExchange set as true and another POS log for the new order indicating the new item was purchased. Exchange at our end affects two transactions. One existing order and a new order are placed for the new items. | |
| Will return tenders always be listed as separate line items over sale tender? | Yes, returns tenders are listed explicitly even if the return was sent back to original sale tender. | |
| How will Order Export (i.e., what files will be created) work for an in-store transaction consisting of both sale and return? The return could be partial or full. |
|
|
| What is the purpose of the Sequence Number field under the transaction node? | <SequenceNumber xmlns:ns2="http://www.nrf-arts.org/IXRetail/namespace/" xmlns="">1</SequenceNumber> is not useful as such. It is just the sequence in which added elements to the xml. |
|
| The Receipt Datetime field, under transaction node, has type code "RefundExpiry". Does it mean the date indicates the end date of the return period of the order? | Yes | |
| Does the sequence number field in a node indicate that the node can appear multiple times? | No | |
How to differentiate between Transaction Level and Item Level Discounts? |
You should be able to differentiate based on below:
|
|
| Do you support Post Void? If yes, then will you be sending us those transactions in the Order Export feed? | No, we do not support Void - only Returns & Exchanges. | |
| How to uniquely identify a transaction? I will need to identify duplicate transactions. Order # will not work as Refunds won't have new order #s. I see a TransactionID attribute at CustomerOrderTransaction node. Can that be used for this purpose? | Yes, transaction ID can be used for the most part. For exchanges, same transaction ID is used/sent in TLog for order # from which item was returned and same transaction ID is used/sent in the new TLog for new order # that was placed for the items that were purchased in exchange. | |
| How to distinguish transactions/POS log of different countries? | We can have your order # prefixed with a country code (i.e., instead of order # string with PS, we can have them start with DE, FR, GB, etc.) For example, PS00000001 can be changed to FR00000001. | |
| Is there a detailed Field Spec/Explanation of data in various XML tags? | Please refer to the link as it containssample XML files. Start with basic sale file Checkout-RetailCloudOrders... file for explanation of all major fields and then navigate to more complex flows which start with file name Checkout-Promotion, PriceOverride, etc. | POSLog-SamplesWithComments.zip |
| Which transaction scenarios will require more than one export file? | The following transaction scenarios will require more than one export file (New Sale and Return of Old Transaction):
|
