Skip to main content
Seller requirements define the checklist a seller must work through before they can be approved and start selling on your marketplace. Each requirement is one thing you ask of them, such as accepting your terms, filling in the profile shoppers see, or uploading a document that you need to have on record. The checklist is the same for every seller. A seller sees it in their own panel as a list of tasks with progress tracker, and you see the same list on that seller’s page in the admin dashboard along with the state of each item. A requirement marked as required has to be done before the seller can be approved, and one left optional is shown to them as recommended. To manage the checklist, navigate to Settings → Seller Requirements in the admin dashboard.

Reviewing the Checklist

The Seller requirements list, showing the built-in requirements The list shows one row per requirement, in the order sellers work through them. Rows are dragged to reorder them, and the order they sit in is the order the seller sees.

Default Requirements

A new Spree marketplace has seven requirements on the list by default. They cover what any seller needs in place before they can trade, so most marketplaces add to this list rather than building one from nothing.
Before Spree 6.0.4, Complete profile also asked for the contact email by default. A marketplace set up on an earlier 6.0 release keeps asking for it. To stop, open Complete profile and turn off Require Contact Email.
A built-in requirement can be deleted like any other, and can be added again afterwards from the same type list. Switching it off is usually the better move where your marketplace simply does not need it, such as a shipping box or a returns address on a marketplace selling only digital goods, because switching off keeps anything sellers have already submitted.

How to Add a Requirement

  1. Click Add requirement.
  2. Choose a Type, which decides what the seller is asked to do.
  3. Enter the Name the seller sees on their checklist.
  4. Enter the Instructions telling them what you need and why.
  5. Fill in anything the type asks for, described below.
  6. Leave Required on if it must be done before approval, or switch it off to show it as recommended.
  7. Click Save.
A new requirement is added to the bottom of the list, and appears immediately on the checklist of every seller who has not yet been approved.

Additional Requirement Types

The seven default requirements cover what every seller needs in place before they can trade. Anything asked for beyond that is built from the types below, which are chosen when adding a requirement and decide what the seller is asked to do. Most types can only be used once on a checklist, because the thing they ask for is only worth asking for once. The four marked as repeatable below can be added as many times as needed, which is how a checklist ends up with two separate documents or several statements to confirm. A type that can only be used once is not offered when adding a requirement if it is already on the list, and becomes available again if that requirement is deleted. The default requirements all work this way. Seller confirmation, Manual check and Document all give the seller a note box alongside the answer itself, so a reference, an explanation or anything else worth knowing arrives with what they send. Document also tells the seller which file types are accepted, which are PDF, JPEG, PNG, HEIC, WebP and Word. Those three look much the same to the seller, and differ in what happens once they have answered. A seller confirmation is taken at the seller’s word and counts as met the moment they confirm it. A manual check and a document both wait for somebody on your team to accept them, which is why a manual check suits anything only your team can verify, such as a tax number against a public register. See Onboarding for making those decisions.
There is no plain text or tick box type. A written answer is collected with Required custom fields, and a statement the seller has to agree to is collected with Seller confirmation.

Custom Seller Fields

Required custom fields is how a seller is asked to type something in, such as a registration number or a license reference. It works differently from the other types, because the fields themselves are not created here. An existing custom field on seller records has to exist before a requirement can ask for it. Create the fields first under Custom Fields, choosing sellers as the type of record they apply to, and then add a requirement of this type and pick which of those fields the seller has to fill in. Pick only the fields the seller should answer themselves. A custom field on seller records is not necessarily a question for the seller, because your own team may be using some of them to record things of its own, such as the account manager looking after a seller or a note from a review. Every field picked here appears in the seller’s task for them to fill in, so adding one of those asks the seller for something that was never meant for them, and makes it something they have to answer before they can be approved. The fields become part of the seller’s record rather than living only on the checklist, so what a seller enters stays readable on their page afterwards. That makes custom requirements ideal for storing important information that you may need to reference later, such as a company number that you check against a register.

What to Ask Sellers For

The seven built-in requirements cover what any seller needs in order to trade. What you add on top depends on what you sell and what you are accountable for. Most marketplaces ask for some of the following, whatever they sell:
  • A company registration number and a tax registration number, as Required custom fields.
  • Proof of liability insurance, as a Document, where a seller’s goods could cause harm.
  • A confirmation that the seller owns the rights to everything they list, as a Seller confirmation, which is the usual protection against counterfeit goods.
  • A published returns policy, as a Seller policy, so a shopper can read the terms before buying.
Beyond that, what you ask follows your industry.
A requirement records what a seller told you. It does not verify any of it, so a license number collected as a custom field is a number in a box until somebody checks it against the register. Use a Manual check for anything that has to be verified by a person, which makes the verification itself a step on the checklist rather than something to remember.
Requirements are the same for every seller. A marketplace selling across several of the categories above asks every seller for all of it, so it is worth keeping the list to what genuinely applies to all of them and handling the rest when you review each seller.

How to Edit a Requirement

Choose Edit from the menu at the end of a row, which opens the same fields as creating one. Editing also offers an Active switch, which stops a requirement being asked for without deleting it or losing what sellers have already submitted. Editing a built-in requirement is where its own settings are changed, such as the terms sellers accept or the minimum number of products they have to list. Those settings are listed under Default Requirements.

How to Delete a Requirement

Choose Delete from the menu at the end of a row and confirm.
Deleting a requirement also deletes everything sellers have already submitted for it, including uploaded documents. Switching it to inactive instead stops it being asked for while keeping what has been submitted.

Further Reading