Email Website
Contents
Search:

Home > All About Me > My Transactions

My Transactions

Overview

My Transactions is one of the first features to come to eRatex for All About Me initiative. It's a new Order and Billing History view that shoppers can access from their account page.

Features

When a shopper clicks the View Your Order/Billing History link on the Account Information page the My Transactions page appears as illustrated below:

 From the My Transactions page, account holders may enter any combination of filter criteria to find orders of interest. The list filters automatically as the user types. 

The transaction list displays when, where, and amount paid for each order transaction. eRatex web orders,  Point of Sale (POS), and Pending transactions are included.

The transaction list also enables account holders to easily reorder and request receipts of their previous transactions where possible. The Reorder and Re-send receipt options appear when those actions are possible. Note that POS orders cannot be 're-ordered' from the website, so therefore the Reorder link appears only on transactions where reordering is possible.

  

Reorder immediately attempts to insert into the shoppers cart each product from the original order. Products no longer available within eRatex are not added to the cart.  Once products are added to the cart, the shopper is immediately redirected to the Checkout page.

While Reorder is available for Web orders and POS orders alike, know that it is quite possible that reordering a POS order may result in no available products because the original POS order may include products that were never available online in eRatex.

Resend Receipt generates and emails a receipt to the account-holder's email address.

To view order details, click the Order ID, which opens the Order Detail page. Orders are grouped by shipment.

Users can choose to reorder individual products from this page, or click a product link to display the product's detail page.

 When a transaction has a Shipment ID available in VR a barcode will show for that transaction representing the Shipment ID number:

These barcodes may then be scanned to quickly read the Shipment ID number for that shipment.

Configuration

Settings

The following settings must be correctly configured for My Transactions to function. If left blank, eRatex will list only orders completed on the eRatex website and provide no reorder or re-send receipt functionality.  

AllAboutMe.Transactions.Enabled

When true, All About Me: My Transactions will be available from the Account page. Please note: this requires that the RatexNet API is correctly configured for your website.

Ratex.API.Environment

The Subdomain of the RatexNet API environment. An example would be omni  if the full domain was https://omni.azure-api.net. If this value is missing, only eRatex Web orders are listed. Please contact PrismRBS support to learn the proper value for this setting.

Ratex.API.Key

The random, unique key generated for the Environment and Context. It allows connection to the RatexNet API Environment. If this value is missing, only eRatex Web orders are listed. Please contact PrismRBS support to learn the proper value for this setting.

Ratex.API.Context

The User Name tied to your site as it exists in the RatexNet API Environment. Must be configured alongside RATEX.API.Context and RATEX.API.Environment. If this value is missing, only eRatex Web orders are listed. Please contact PrismRBS support to learn the proper value for this setting.

Ratex.Email.UseTopicsForEmail

When emailing an order confirmation for orders not generated on the eRatex website, it's possible to use either an HTML template or topic Ratex.Email.Template.Receipt. If this setting is true, the topic will be used. If false, it will search for an HTML template in the EmailTemplates directory of your site. Please see the section below, POS Order Receipt Emails, for more information on this configuration. Ratex.Email.Template.Receipt is set true by default.

Topics

RATEX.Email.Template.Receipt

This Topic contains a receipt template which will be used when the shopper clicks Resend receipt from the Order History page. This topic will only be used for POS order receipts (not eRatex web orders). Orders generated from the eRatex website use the default receipt email.

Prompts

Ratex.Email.Subject.Receipt

This prompt specifies the subject line for POS order receipts. The default value is "Your receipt".

RATEX.Transactions.Button.Receipt.Resend

This prompt specifies the text on the button which resends the receipt. The default value is "Resend receipt".

RATEX.Transactions.Button.Reorder

This prompt specifies the text on the reorder button. The default value is "Reorder".

RATEX.Transactions.LineItem.Isbn

This prompt specifies the shipment header's ISBN label. The default value is "ISBN".

RATEX.Transactions.LineItem.Quantity

This prompt specifies the shipment header's quantity label. The default value is "Quantity".

RATEX.Transactions.LineItem.Sku

This prompt specifies the shipment header's SKU label. The default value is "SKU".

RATEX.Transactions.LineItem.UnitPrice

This prompt specifies the shipment header's unit price label. The default value is "Unit Price".

RATEX.Transactions.ReorderError

This prompt specifies the error that occurs when a line item cannot be reordered. The default value is "Oops! We were unable to reorder. We may not have any of your products in stock at the moment."

RATEX.Transactions.SectionHeaders.Canceled

This prompt specifies the label for canceled line items within a shipment. The default value is "Canceled Products".

RATEX.Transactions.SectionHeaders.InProcess

This prompt specifies the label for in-process line items within a shipment. The default value is "In-Process Products".

RATEX.Transactions.Summary.Merchandise

This prompt specifies the summary label for merchandise (items). The default value is "Merchandise".

RATEX.Transactions.Summary.Shipping

This prompt specifies the summary label for shipping. The default value is "Shipping".

RATEX.Transactions.Summary.Taxes

This prompt specifies the summary label for taxes. The default value is "Taxes".

RATEX.Transactions.Summary.Total

This prompt specifies the summary label for the order total. The default value is "Order Total".

POS Order Receipt Emails

Overview

Email receipts for POS orders have additional configurations available which are currently not in place for eRatexorder email generation. By default, the RATEX.Email.Template.Receipt topic is used for POS order emails. It's recommended that this setting is left alone unless your site has more detailed email requirements which would be better met using an HTML email template versus a Topic.

EmailTemplates Directory

When the Setting Ratex.Email.UseTopicsForEmail is false, a POS order email searches for a file named RATEX.Email.Template.Receipt.html  in the [your site folder]\EmailTemplates directory on the server. This file must exist in that directory for emails to be successfully created for POS order receipts.

Frequently Asked Questions

My shopper clicked "Reorder" but one of the items wasn't added to their cart.

If an item is no longer available for purchase from your store, it will still show up in the transaction history of the shopper but will no longer be able to be added to the cart.

I've just created my new site and placed some test orders but I don't see transactions.

At least one order in eRatex needs to exist in Visual Ratex for My Transactions to begin displaying transactions. Please make sure you have configured the API correctly (see above, in the Configurations section). If your test orders were only on the eRatex side, My Transactions may not display as you expect.

I would like to take advantage of an HTML POS email template, but I don't have an EmailTemplates directory.

By default, new eRatex sites will not have an EmailTemplates directory. Please create the directory and make sure that the template you place there matches the filename RATEX.Email.Template.Receipt.html.

 

 



Actions
Print This Article
Bookmark
Email This Article
Previous Article
Next Article