What can you try before opening the marketplace?
Use Build to work on the test marketplace. Start with one listing, such as a fictional pottery lesson. Decide what a seller enters, what a buyer sees and what happens when a booking is requested.
Sharetribe now lists Build for testing and Live for running a marketplace. Its current plan guide says plans include one million usage credits per month, with extra usage billed separately. Actions such as searches, messages and bookings can consume credits. Lite, Pro and Extend are legacy plans.
Where should the operator start when a booking needs a refund?
Open the transaction in the marketplace controls and check its current state. Sharetribe documents operator cancellation and refund options for specific workflows and stages.
A refund entered directly in Stripe can leave Sharetribe’s transaction state out of sync. Decide who checks the booking and the payment outcome before updating the buyer. Avoid describing a booking as refunded based on one status alone.
Which records can you keep outside the service?
Sharetribe documents separate CSV exports for users, listings, transactions and reviews. A CSV is a spreadsheet-friendly record of selected fields.
Check which links between records are present, such as the listing ID on a transaction. Keep source images and a description of your booking and cancellation steps separately so you know what would need to be rebuilt.
How would you rehearse one marketplace booking?
Draw a listing for a fictional pottery lesson. Use paper with no account, payment or booking action.
- Trace the buyer and sellerMark what the buyer asks for and when the seller should see the request.
- Draw the cancellationGive the operator a place to see the booking state and a separate place to record the confirmed payment outcome.