Vendor onboarding takes a new seller, supplier or partner from signup to the point where they can trade and be paid — data collection, verification, contracting, then configuration in every system that will run the relationship. On a marketplace it is the gate standing in front of the first order.
From signup to the first payable order
Collection comes first: legal entity name, registration number, ownership, tax identifiers, bank details, and the named person authorized to change any of them. Verification follows: the entity exists, the people behind it are who they claim to be, the bank account belongs to that same entity. Then contracting, which fixes commission, payout timing and liability for disputes. Then configuration — vendor record, tax settings, catalogue permissions, payout instructions.
Skipping the fourth stage is the classic mistake. A vendor who is verified and contracted but not configured looks live from the outside and fails silently at the first order.
The bank-details step that decides whether payouts work
Most failed payouts are onboarding defects surfacing weeks later: an IBAN in the wrong format, an account name that does not match the verified entity, a currency unsupported on that corridor. Matching the account holder against the legal entity closes nearly all of it.
Currency, schedule and fee deduction belong in the same conversation. A vendor selling into more than one market needs the multi-currency payout question answered before go-live, not after the first cycle disappoints them.
Risk tiering beats one heavy form
Fifteen fields and a five-day review will lose small sellers to a competitor with a lighter gate. Instant approval with the checks deferred loses money instead, and always after funds have moved. The workable middle is tiering: light checks to start trading under a capped volume, deeper checks triggered by value, category or payout size.
How deep those checks must go is not a product choice. It is set by marketplace compliance obligations, and where sellers trade as sub-merchants the standard closely resembles merchant underwriting.
The fraud that targets an existing vendor record
A live vendor record is a standing payment instruction. The common attack is not a fake seller at signup but an email from a compromised mailbox asking to update bank details on an account that has traded happily for a year. Treat any payout-detail change as a re-verification event confirmed out of band with a contact captured at onboarding, never as a routine support ticket.
Vendor data stops being true quietly
Owners change, licences lapse, addresses go stale, and nothing in the system announces it. Periodic re-verification — annually for most sellers, more often for high-value or regulated categories — is what keeps the onboarding file worth anything when somebody asks to see it.