Some transactions require additional details to ensure the service or product is delivered correctly. Transaction fields allow collecting this information on during checkout, offer or inquiry page.
Whereas user fields collect information about users, listing fields collect information to describe the service or product offered, transaction fields capture specific details that apply to a single purchase, booking, or an offer submission (in a reverse marketplace).
In regular marketplaces, you can use transaction fields when the provider needs extra instructions that will influence how a product or service they offer is delivered to the customer. For example:
In a food catering marketplace, customers can enter dietary restrictions, allergies, and preferred food pickup time.
In a marketplace for buying custom bikes, customers can specify bike components, sizing, color preferences, or other requirements for the build.
In a petting sitting marketplace, customers can provide feeding instructions, behavioral information, and a phone number so the sitter can care for the pet safely.
In a reverse marketplace, transaction fields can help customers collect structured information from providers when they submit offers, so they can compare offers and select the right provider for their needs.
For example, in a reverse marketplace for hiring web developers, transaction fields can be used for customers to request details such as the estimated timeline, relevant past projects, communication approach, and post launch support.
How transaction fields work
Transaction fields can be added in Console’s Build section, Listings > Listing types by opening the Listing type settings and clicking on + Add a transaction field.
By default, transaction fields are optional, but they can be made mandatory for users to fill in by enabling the “Make this field mandatory” option.
Transaction fields allows collecting additional details when a transaction is initiated. This information is specific to each individual transaction.
You can add up to 100 transaction fields. However, add them thoughtfully. Requiring too many fields can make initiating a transaction slower and may discourage users from completing it.
In Calendar booking, Purchase and Free messaging transactions, transaction fields appear on the checkout and inquiry (for free messaging) page and are shown to the customer. The customer completes these fields before finalizing the checkout process.
In Regular Price Negotiation transactions, you can select the placement of the transaction field to either appear when the customer requests a quote or when the provider submits an offer.
In Reverse Price Negotiation transactions, transaction fields appear on the offer page and update offer page and are shown to the provider. The provider completes the fields when submitting or updating an offer.
Transaction fields in a regular price negotiation transaction
On the marketplace, transaction fields information can be viewed by users in their inbox page, by opening the specific transaction page.
The marketplace operator can view transaction field data in the Manage → Transactions page in the Protected Data field.
Transaction fields content and information cannot be changed or edited once they are filled in and submitted. This applies in both the Console and the marketplace interface.
The only exception is with reverse price negotiation transactions. If the Listing type with the reverse price negotiation process allows providers to update their negotiation offer, the provider can also update the transaction fields content and information associated with the offer. These updates can only be made through the marketplace interface, not in the Console.
Transaction field types
Just like user fields and listing fields, you can add five types of transaction fields: Free text, Number, Select one, Select multiple, and Video.
Free text
This field type allows users to enter text or numbers. It will appear as a text box on the checkout page. This field can be used for the user to provide additional details about what they need or expect from the transaction.
Number
This field type allows users to enter a whole number (an integer). It can be positive or negative. You can set low and high limits. The max and min values are really large, respectively -9007199254740991 and 9007199254740991.
Select one
This field allows users to select one attribute from a list of options on the checkout page. When you create this field, you have to define the options that will be available for listing authors to select. This field's options will be displayed as a dropdown in the listing creation form.
Select multiple
This field type allows users to select multiple attributes (as many as are available) from a list of options. To create this field, you have to define the list of options available to select. These will be displayed as checkboxes on the checkout page.
Video
This field type allows users to add the URL of a video on YouTube to the transaction.