Skip to main content
All CollectionsManage
Manage transactions
Manage transactions

Learn how to manage, browse and transition transaction states using Console

Yifan Dong avatar
Written by Yifan Dong
Updated over a week ago

Any transaction initiated by users in your marketplace will be displayed in your Console, which has admin tools and views to help you understand and manage your marketplace transactions.

You can view your marketplace transaction data in Manage > Transactions.

Below, you can learn more about the admin capabilities available in Console.

Search and filter transactions

You can filter the list of all transactions in your marketplace by using a filter and some conditions.

In Manage > Transactions, you can search and filter to find the transactions you are looking for, from the entire list of your marketplace transactions.

Using the search bar, you can look for transactions using the transaction ID, the user name of a transaction party, or the transaction listing title.

With the "Filter" button, you can combine multiple conditions:

  • Last transition. A transition refer to a change in the stage of a transaction (when the transaction state moves from one to another). The condition dropdown displays a list of the 1000 most recent transitions that have occurred within the marketplace.

  • Transaction ID. The ID of the transaction you're looking for.

  • Participant ID. The ID of one of the two parties in the transaction you're looking for.

  • Listing ID. The ID of the listing of the transaction you're looking for.

Operator transitions

As a marketplace admin, you can change certain states of transactions through the use of operator transitions, depending on the type of transaction process utilized

Booking Calendar

After a booking request is made, the payment is confirmed, and before the transaction is accepted or declined, the following operator transitions can be triggered:

  • Operator Accept: This accepts the booking request and moves the transaction state forward.

  • Operator Decline: This declines the booking request, thus canceling the transaction and triggering a refund.

Screenshot of the operator transitions

Operator transitions for Calendar Booking

After a transaction is accepted and before and before the transaction is completed, the following operator transitions can be triggered:

  • Cancel: This cancels the transaction and triggers a refund.

  • Operator Complete: This completes the transaction and triggers the provider payout

Screenshot of the operator transitions

Operator transitions for Calendar Booking 2

Purchase

After a purchase is made, the payment is confirmed, and before the transaction is marked delivered, the following operator transitions can be triggered:

  • Cancel: This cancels the transaction and triggers a refund.

  • Operator mark delivered: this will mark the product as delivered (or shipped) on behalf of the provider.

Screenshot of the operator transitions

Operator transitions for Purchase 1

After a transaction is marked delivered but before it is marked received, the following operator transition can be triggered:

Screenshot of the operator transition

Operator transitions for Purchase 2

After a transaction is marked disputed, the following operator transitions can be triggered:

  • Cancel from disputed: This cancels the transaction and triggers a refund

  • Mark received from disputed: This completes the transaction and triggers the provider payout.

Screenshot of the operator transitions

Operator transitions for Purchase 3

Viewing data

Summary

The summary includes most of the information about the transaction.

  • Booking status: If your transaction uses the Booking Calendar transaction process, it will have a booking status. This status helps track where the booking currently stands within the transaction state.

  • Booking period: If your transaction uses the Booking Calendar transaction process, the booking period represents the specific timeframe of the transaction. This is the duration for which the service or rental is booked.

  • Seats: If your transaction uses the Booking Calendar transaction process, you can see the number of seats booked as part of the transaction. By default, the number of seats is always set to 1.

  • Stock reservation status: If your transaction uses the Purchase transaction process, it will include a stock reservation status.

  • Stock reservation quantity: If your transaction uses the Purchase transaction process, there will be a specified quantity of stock reserved for the transaction.

  • Transaction ID: This is a unique identifier for the transaction, automatically generated when the transaction is initiated.

  • Transaction process: This field specifies the specific transaction process used, whether it's a default or a customized process for your marketplace.

  • Customer paid: This field details the total amount paid by the customer. It includes a breakdown of any commission fees your marketplace collects from the customer.

  • Provider received: This field indicates the total amount of money the provider will receive from the transaction. It also breaks down any commission fees that your marketplace deducts, clarifying the net amount that the provider earns.

  • Marketplace receives: This field calculates your marketplace's total revenue from the transaction, which is the sum of both customer and provider fees. Note that Stripe’s fees are not included in this calculation and must be reviewed separately via your Stripe dashboard.

Activity

You can view a transaction's history in the activity section, which documents all the transitions that have occurred, much like a Timeline section. This section also interweaves the communication that has taken place within each transaction.

This communication encompasses all email notifications sent during the transaction process, written messages exchanged between users, and reviews provided at the conclusion of the transaction, if available.


Other data

Additionally, there are other data fields primarily used for code customization, building integrations, and automating processes using Zapier. These fields include:

  • Protected Data

  • Metadata

Events: This is an advanced tool designed for developers to query and retrieve historical data about a transaction. It utilizes the Sharetribe Command Line Interface (CLI) to access a comprehensive record of a transaction's states, actions and actors.

Exporting data

You can download your transaction data in a .csv file format. This can be useful if you need to perform operations or analysis that are not possible directly within the Console. For example, exporting your transaction data enables you to conduct detailed analyses, such as determining the number of transactions initiated within a specific month.

Shortcut links

When navigating a transaction's card in your Console, there are several links designed to streamline your management tasks and quickly access transaction-related data:

Shortcut links manage transactions


Customer: Clicking on the customer icon takes you to the manage users page, displaying the customer involved in the transaction. ​. ​

Provider: Clicking on the customer icon takes you to the manage users page, displaying the provider involved in the transaction. ​

Listing title: Clicking on the customer icon takes you to the manage listings page, displaying the listing involved in the transaction. ​ ​

Reviews: Clicking on this link takes you to the manage reviews page, where you can view the reviews associated with the transaction.

Did this answer your question?