Automate each purchase separately

Home > Ontraport for payments > Fulfilling digital orders > Automate each purchase separately

Home > Fulfilling digital orders > Automate each purchase separately

Use purchase fields, purchase messages and purchase automations to follow up on each purchase separately.

In this lesson you'll learn:

Store details on individual purchases
Update a purchase and use its fields in a message
Branch purchase automation by the product bought

Next lesson

Return to: Fulfilling digital orders

Comments

[Block//Author//First Name ##cap_first] [Block//Author//Last Name ##cap_first] on [Block//Date Added %F j, Y g:i a%+0d0h0m]

[Block//Comment]

Leave your comment

14-day free trial. No commitment.

Start your free trial to start growing your business with Ontraport.

Related resources

[Block//Resource Type]

[Block//Resource Name]

[Block//Resource Description ##ellipsis(166)]

Transcript

When one customer buys more than once, each order often has its own details. Two workshop dates. Two shirt sizes. Two projects. If you keep those details on the contact, the second order overwrites the first. Advanced Purchases fixes that. Each purchase becomes its own record, with its own fields and its own automations. Let's build one complete example. Here's the setup. You sell two products: a May workshop and a June workshop. A customer named Jordan buys both. Each one becomes its own purchase, and both belong to Jordan's contact record. Our goal: each purchase stores its own event date, and Jordan gets a confirmation for each workshop with the right date. First, click your profile icon, then Administration, then Advanced features, and turn on Advanced Purchases. It's available on some account levels, so check your plan. Sales, then Settings, now has a Purchases tab, with the Field editor, Purchase automations, Purchase messages, tags and broadcast history. Go to Sales, then Settings, then Purchases, then Field editor, and add a field called Event date. This field lives on each purchase, not on the contact, so Jordan's two purchases can hold two different dates. You fill purchase fields with the Update purchase element in an automation, or by editing the purchase record. System fields, like the product and price, are locked. Next, go to Purchase messages and write your confirmation email. Purchase messages can use merge fields from the purchase record, so drop in the Event date field. Each email shows the date from its own purchase. Now go to Purchase automations and click New automation. Start from a template or from scratch. This map runs from purchase records, not contacts, so it can start right after a purchase is made, using the same kinds of triggers, conditions and actions you already know. Add a condition that checks which product was bought. On the May path, use Update purchase to set Event date to May fourteenth. On the June path, set it to June eleventh. Then send your purchase message. Jordan's two purchases each run through the map, so Jordan gets two confirmations, each with the right date. One distinction keeps this straight. On an order form, the Manage Form Fills settings, like tags and rules, apply to the contact who bought. So tag Jordan as a customer there, and keep everything about each order on its purchase. You can also relate purchases to other records, like a ticket or a project, because Purchases appear in the Custom Object Editor when you create a relationship. Custom objects need a Dynamic CMS package, and the Custom Objects lessons cover relationships in depth. So: turn on Advanced Purchases, store order details in purchase fields, write a purchase message, and let a purchase automation fill in the details and send the right follow-up for every order. Next up: an overview of fulfilling physical products.