Within Vrio there is a hierarchy of data mapping. This allows flexibility for the end user to setup their program custom to them, without implementing custom dev or workarounds.

Data Layer	Description
Customer	Highest Level of the data hierarchy. Email, phone, address and card data are stored on the Customer Record. The email address will create a `Customer_ID`. The `Customer_ID` stores all `Order_IDs`.
Order	An Order is a record that ties the Customer to the goods/services (Items) that they purchased and the billing schedule (Offer) those Items are sold for. An Order contains Offers, or the line item of the purchase. One order can contain one Offer or multiple Offers. Each unique combination is defined as an `Order_Offer_ID`. These Offers determine the billing schedule: a one-time purchase, a subscription or a combination of both, within that Order.
Sale	A sale is a record tied to the Order. Each billing cycle will have a unique Sale. A sale can contain multiple transactions (attempts if it is declined and child transactions of Refunds, Voids, Alerts and Chargebacks). A sale will tell you whether you captured the unique payment or not.
Order Offer - Line Item	An Order Offer is the individual line item that details the specific [Item+ Offer] combination purchased. This line item (Item+Offer) determines what Item is shipped, price of that item and how often a charge and shipment are scheduled. It’s important to note that recurring offers DO NOT create a new `Order_ID` or `Order_Offer_ID` - each new billing cycle creates a new transaction within that `Order_ID` and `Order_Offer_ID`.
Transaction	A Transaction is the overall payment transaction of the Sale. This is what the consumer will see reflect on their credit card statement. A single Transaction can contain multiple offers.
Shipment	Item(s) being shipped to the customer. Note: Through configuration, multiple orders can be sent as one shipment.

FAQ

What does the customer purchase as configured in the UX?

A: The customer is purchasing an Item + Offer for a Specific Campaign.

How do I make a subscription?

A: A subscription differs from other types of Offers because it schedules future payment attempts and shipments. The Offer type is recurring.

How do I create a shipment for successful sales?

A: The item must be set to "is shippable." Anytime this Item is contained on a sale, it will create a shipment automatically when the payment is successful. The shipment can be sent directly to third party systems (i.e Shipstation) per our integration or can be managed manually within the UX.

How do I manage a payment attempt that failed?

A: Initial declines may be reattempted through the Payment Router settings. Ongoing decline reattempts for subscriptions is managed through Dunning Profiles. The dunning profile is a UX tool that lets you configure how often to retry a failed payment for a Sale. The process can retry the full amount or a discounted amount. Additionally, you can use a third party dunning connection.

What records are created for a customer?

A: The Customer, Order, Sale, Transaction, Shipment and Subscription (if applicable) are created at the same time on the first Sale of the Order. If the Order contains a Subscription, then each renewal will create a Sale, Transaction and Shipment.

Why does an Order have more than one Sale?

A: The Order contains a product that is on a subscription. Each subscription renewal will create a Sale, then attempt payment collection by creating a transaction.

Why does a Sale have more than one Transaction?

A: The Sale will have multiple transactions if the first payment attempt is unsuccessful. Each new payment attempt will create a new transaction. Additionally, a Sale will have more than one transaction if a refund, alert and/or dispute are applied against a payment.