If you're planning to build an online marketplace, don't judge a platform by how fast it can publish listings. The decision that actually protects you is what happens to your money, seller records, refunds, and account data after you subscribe.

A no-code builder can give you storefront pages and workflows while payment processing, seller checks, tax reporting, disputes, and data storage sit with other companies. For U.S. operators, map who is responsible for each part, and what remains if you cancel, before you pay. This is practical information, not legal or tax advice.

What a marketplace builder may and may not include

Get the service boundaries in writing. A demo can show listing pages and checkout while the operational work stays with you or another vendor.

Area Questions to ask before subscribing
Software and hosting What does the plan include? Are there usage limits, paid add-ons, overage charges, or automatic renewals?
Payments and payouts Which company processes payments? Who receives the money first? How are seller payouts, refunds, reserves, and payment disputes handled?
Seller verification Can the platform collect and verify seller identity, contact, banking, and tax information? Which steps remain your responsibility?
Buyer support Is there a built-in cancellation, refund, or dispute workflow? Are there deadlines or transaction-status rules?
Data and account access Can you export listings, orders, messages, invoices, and seller records? What happens to that data after cancellation?
Support Is support included, and how do you contact it for billing, payment, or account-access problems?

A feature in a product tour is not proof it's on your plan. Confirm whether it is included, needs custom development, or depends on a separate integration.

Calculate the real cost over 12 months

The advertised subscription is only one line in the budget. Make a 12-month worksheet that separates your costs from fees charged to buyers or sellers.

Include:

Find out how each transaction fee is calculated. Some fees use the full order value, some use the marketplace commission, and some use another amount. Then ask what a refund returns: the platform fee, the payment fee, both, or neither. Don't treat the word "refund" as the answer.

A hosted builder can reduce technical work, but it also creates a recurring relationship with the vendor. A custom build can offer more control, and it leaves you responsible for more integrations, maintenance, security, and support. Compare those costs on the same 12-month sheet, not on the monthly headline price.

Read cancellation and renewal terms carefully

Canceling is not the same as deleting the marketplace, stopping all charges, or getting your money back. Before you subscribe, pin down:

  1. Whether the plan renews automatically
  2. Whether cancellation takes effect immediately or at the end of the paid period
  3. Whether unused prepaid time is refundable
  4. What happens to your domain, listings, orders, messages, and seller records
  5. Whether buyers can still access past order information
  6. How long the provider retains account and transaction data
  7. Whether you can export your information before access ends

Procedures differ by vendor. Bubble's billing documentation describes cancellation through the current plan controls or through its support bot. Sharetribe's subscription guidance describes a customer portal for billing details and invoices, and notes that a longer commitment can change the monthly price. Sharetribe also warns that the subscription email may not match the email you use to log in to the Console.

Those pages explain how to manage an account. They do not promise that every prepaid charge will be refunded. Save the plan terms, confirmation emails, invoices, and cancellation screen. If a billing problem shows up later, those records beat a memory of the checkout page.

Separate a software refund from a marketplace refund

There are usually two different payments:

Canceling the software subscription does not cancel a buyer's order. Refunding a buyer does not refund your software plan.

Document, before launch, who can approve a refund, how money moves back to the buyer, what happens to the seller's payout, and how a dispute is recorded. Check whether the workflow supports full refunds and partial refunds; those are not always available in the same way.

Sharetribe's refund and dispute guidance is a useful example of product limits, not a U.S. legal deadline. In its documented purchase flow, after a provider marks a transaction as shipped, the customer or the marketplace operator can start a dispute within 14 days of the transaction date. Partial refunds are not supported out of the box. Calendar-booking transactions follow a different rule: they are marked complete two days after the booking period ends.

If a credit card was charged, the card issuer's dispute process is separate from marketplace support. Debit cards, bank transfers, and other payment rails can have different procedures. Contact the party named on the charge promptly and ask what evidence and deadline apply. A marketplace promise does not automatically cover every payment type.

Check seller verification and U.S. marketplace duties

Collecting an email address is not seller onboarding. Depending on the marketplace and the seller's activity, you may need workflows for identity, contact, banking, and tax information.

Federal FTC guidance on the INFORM Consumers Act says the law can cover smaller niche marketplaces as well as national platforms. Once a high-volume third-party seller provides banking-account, contact, and tax-ID information, the marketplace has 10 days to verify that information. Covered marketplaces also need a way for users to report suspicious conduct involving those sellers.

The FTC's guidance for third-party sellers adds a disclosure trigger: when a covered seller reaches at least $20,000 in annual gross revenue on a particular marketplace, the marketplace must disclose specified seller information on product listing pages or in order-confirmation messages. That can include the seller's name, physical address, and contact information that permits direct communication. If the seller does not provide required information within 10 days of notice, the marketplace must suspend future sales activity until the seller complies.

Before you choose a builder, ask:

A form that collects seller information is not a complete verification process. Write down who performs each step.

Plan for tax records and Form 1099-K questions

A marketplace payment system can create tax-reporting work for the business, the sellers, or the payment settlement entity. Don't assume the software builder handles all of it.

IRS guidance on Form 1099-K explains that the form may show gross payment amounts and that sellers should compare it with their own records. If you don't recognize the issuer, contact the payment settlement entity identified on the form rather than contacting the IRS first. Keep copies of corrected forms and related correspondence.

Before launch, confirm with the provider or payment processor:

A Form 1099-K reports gross payment information. Sellers still need their own records for refunds, expenses, fees, and other adjustments. Use the current IRS Form 1099-K FAQs for reporting rules and thresholds, not an old blog post.

Protect sensitive information and preserve your exit

Marketplace software may hold addresses, contact details, banking information, tax IDs, order histories, and private messages. Buyers and sellers reasonably expect that information to be protected.

Read the privacy and data-processing terms before you enter real data. Confirm what is collected and why, which vendors or payment services can access it, how staff and contractor access is controlled, how you export data, and what is deleted, retained, or returned after cancellation. Also confirm how you will be notified about a security incident, and whether the contract still lets you reach records needed for disputes or tax reporting.

Evaluate with test accounts and test payment details. Don't upload a real tax ID or bank account to an unverified demo just to see whether a form works.

Test the service before accepting real orders

A short pre-launch test will show limits a sales page won't.

  1. Create a test seller account and a test buyer account.
  2. Publish a listing and complete checkout.
  3. Check the payment processor's name and the amount on the receipt.
  4. Test a cancellation, a full refund, and any available dispute process.
  5. Test what happens when seller information is incomplete or can't be verified.
  6. Download an invoice and export order, payout, and seller records.
  7. Cancel or downgrade the test subscription and check what remains accessible.
  8. Send a support question about a billing or refund problem and save the reply.

Use dummy data or an approved sandbox. If a provider can't clearly explain a basic refund, export, or cancellation step before you subscribe, treat that uncertainty as a product risk.

What to do when something goes wrong

Start with the party that controls the specific problem:

Keep the paper trail in writing where you can. If the provider blocks access to records or applies a charge that conflicts with the terms you saved, review the contract and get advice on the appropriate U.S. complaint or dispute route.

Before you pay for a long-term plan, complete one test transaction, export the records, and save the provider's written answers on recurring charges, refunds, seller verification, tax forms, data retention, and cancellation.