Vrio Customer Records and Statuses

Learn about the records in Vrio and how to interpret the statuses displayed.

Customers

**Customers - Generated based on a unique email address.

**If a customer returns and uses a new email, they will have a new customer record created in Vrio. The customer contains all Orders and the underlying Order records. When the customer is created, the date is known as Acquisition Date.

Learn about Customer Searching here.


Orders

Orders - Generated by the Customer.

When an API call is made to create an order or when the Customer uses the Vrio Checkout landing page, a new order is created. If the Order contains a Subscription, the Subscription creates new Sales against that Order (not a new Order per sale). The order contains all Sales, Transactions, Shipments, Responders and Events. When the order is created, the date is known as the Order Date.


Sales

Sales - Generated by the System.

The order will create the first Sale. If the Order contains a subscription, then each renewal cycle (not renewal cycle attempt) will create a new sale. The sale groups the payment and shipment into one location. When the Sale is created, the date is known as the Sale Date.

Sales Statuses

ValueDescription
AuthorizedThe sale has a payment transaction that was successfully authorized but as not yet captured the authorization.
CancelledThe sale has a payment transaction that was cancelled.
FailedThe sale does not have a successful payment transaction and will no longer attempt to collect payment.
In DunningThe sale is reattempting a declined payment transaction.
PaidThe sale has a payment transaction that was approved or an open authorization was successfully captured.
PendingThe sale is configured to use the delivered date to schedule the next payment transaction attempt and the shipment is not delivered.
ScheduledThe sale has a payment transaction that is scheduled but not yet attempted.
SkippedThe sale is rescheduled to the next billing period.

Transaction

Transaction - Generated by the System for each payment attempt, refund or dispute.

A sale can have one or many transactions. If the first payment attempt fails for the Sale, then another one will be scheduled (if using dunning profile or dunning connection). If the second attempt is successful, the Sale will be paid. When a transaction is attempted, the date is known as the Transaction Attempt Date. When a transaction is scheduled in the future, the date is known as the Transaction Scheduled Date. The Transaction Attempt Date and Scheduled Date will also show the Transaction Complete Date indicating the transaction was processed.

Transaction Statuses

ValueDescription
CancelledA transaction was cancelled to avoid a payment attempt.
DeclinedA transaction was declined by the payment network.
PendingA transaction does not have a scheduled date because the configuration is waiting on the delivered date of a shipment.
ScheduledA transaction is scheduled and will be submitted for payment attempt.
SuccessfulA transaction was approved by the payment network.

Learn about Transaction Searching here.


Shipment

Shipment - Generated by the System when a successful payment has occurred.

A sale can have one or more shipments. Additional shipments are created when an internal organization user manually selects a reship or a free shipment. When the Shipment is created, the date is known as the Shipment Created Date. The Shipment is tracked through the varies stages using different statuses and dates.

Shipment Statuses

ValueDescription
CancelledIf the payment transaction for the shipment is cancelled.
DeclinedDeprecated - A shipment is being created per transaction decline.
DeliveredFor integrated carriers, Vrio will indicate the order was delivered automatically. For unintegrated carriers, the shipment needs to be marked as delivered.
ErrorThe fulfillment connection did not accept the shipment. Learn about shipping errors here.
Pending PostThe shipment is configured with a delay before sending to the fulfillment connection.
Pending TrackingThe shipment was sent to the fulfillment connection but no tracking number has been created. For businesses who manually conduct fulfillment, a tracking number needs to be created and added.
Pending TransactionThe shipment is waiting for a successful payment before being sent to fulfillment.
ShippedA tracking number was added to the shipment manually or automatically via the fulfillment connection.
SkippedThe shipment is rescheduled to the next billing period.

Subscription

Subscription (Order Offer) - Generated by the Offer Configuration Type of Recurring.

The subscription manages upcoming Sales. When the current Sale is successful, it will schedule the next Sale. This process repeats until the Subscription is cancelled or paused. The subscription can be used to adjust the future Sale date.

Subscription Statuses

ValueDefinition
ActiveA subscription is actively billing, scheduled sales will continue to occur.
CancelledA subscription has been cancelled or ended, no additional scheduled sales will occur.
CompleteThis is not a subscription status, but a status when an order offer is a one-time sale and no subsequent sales will occur.
PartialThe subscription was created, or added to the cart and checkout captured some of the customer information. No attempt was made at the gateway to capture the payment.
DeclinedSale was attempted and declined and no further sales are scheduled, the subscription has been cancelled due to decline.
ArchivedCustomer is for all purposes, is removed from all reporting
RejectedThe customer was present an upsell offer and rejected to take the upsell
RemovedAn item was added into a cart, then it was removed before the checkout was completed.
PausedA subscription was paused, thus no longer has any scheduled sales
ExpiredBased on rules set within the Offer, the customer has expired and the order offer is inactive.