storeConnect® comes with a powerful transactional email system allowing you to define when various emails are sent from the platform.
Every email sent is sent via your Salesforce org using Classic Email Templates, meaning your Salesforce administrator can customise each and every template directly within your org themselves.
Carts, Orders & Payments Emails
Because storeConnect depends on the standard
Order object we let you define when each email is triggered to be sent, and this can be defined for each store you have. Every store can have different templates sent at different triggers.
There are 3 fields on the
Order object we read data from in order to determine if an email should be sent. The
Order.Checkout_Step__c text field and the
Order.Abandoned__c checkbox flag.
The storeConnect package creates a field called “Checkout Step” (Checkout_Step__c) which will always have one of the following values:
- open - User has added something to the cart
- customer - User is up to the customer information step
- shipping - User is up to the shipping step
- payment - User is up to the payment step (has chosen shipping)
- complete - User has completed payment.
- failed - User tried to pay but the payment failed
Additionally, the field might have
-syncing appended to it at certain times, such as
complete-syncing which indicates that the record has not fully been synchronised from the Connect eCommerce site. Just waiting a few minutes and the step will be updated and the
-syncing suffix will be removed.
Additionally the package includes an “Abandoned” (Abandoned__c) checkbox which is
FALSE by default on the standard Order object, indicating the cart has been abandoned after 10 hours of inactivity.
Thus, an Order that has the Checkout Step of
failed and Abandoned is
TRUE indicates that at least 10 hours ago, a customer attempted and failed to make a payment for a product.
Finally, storeConnect also integrates with the Standard “Status” field on Order as defined in your individual Salesforce environment. The default Salesforce setup has two statuses for order,
Activtated. We can integrate with these, or any other set of statuses you place on the Order object.
If you don’t have any special sequence of statuses defined for your Order object, we can help you set this up. Our customers generally use:
- Back Order
Our system then includes 11 different default transactional emails for the Order object as defined in this table:
|Transactional Email Name||Checkout Step||Abandoned?||Order Status|
|Order Abandoned Open||open||TRUE||Draft|
|Order Abandoned Customer||customer||TRUE||Draft|
|Order Abandoned Shipping||shipping||TRUE||Draft|
|Order Abandoned Pre Payment||payment||TRUE||Draft|
|Order Abandoned Failed||failed||TRUE||Draft|
|Order Payment Success||complete||FALSE||Draft|
|Order Backorder||complete||FALSE||Back Order|
The name of the Order step can be defined by your system and is completely flexible.
These are defined via the Transactional Emails releated list on your Store object within Salesforce under the storeConnect Config app. When we install your store for the first time, we create all 11 Transactional Email objects with the above default settings.
Each transactional email has a Classic Email template you can edit to fit your branding and store. We include the following templates in the storeConnect package:
|Transactional Email Name||Template Name|
|Order Abandoned Open||
|Order Abandoned Customer||
|Order Abandoned Shipping||
|Order Abandoned Pre Payment||
|Order Abandoned Failed||
|Order Payment Success||
We also allow you to create any number of additional transactional email objects as you want for any other order step / checkout step / abandoned combination you wish if the above is not enough.
Whenever an Order changes status, it will search the Transactional Emails related list of the store that the order belongs to for any Transactional Email object that matches the orders Checkout Step, Abandoned and Order Status fields and send all emails that match passing the Order and Contact record to the Classic Email template.
This should make your marketing team happy :)
Back to Documentation