A Shopify wholesale application form should collect the company name, the buyer’s name, an email, a tax or VAT number, a website, and a typical order size. SK Form Builder can put those questions on a multi-step form. The catalog does not limit multi-step forms to a paid tier.
The form does not approve a wholesale account by itself. Someone on your team still checks the answers. Hiding retail prices, and sending a negotiated quote, is a different job. That job belongs on Request a Quote and Hide Price, not on the application form.
The questions below are a practical set for US, UK, Canadian, and English-language EU wholesale. They are not a template baked into the app. You add the fields yourself.
Fields worth asking
Ask for facts you will look up or type into a customer record. Skip anything you will never read.
- Company name: the legal name you will put on invoices, not a nickname.
- Buyer name and email: the person who will receive the decision. Email is validated on submit.
- Tax or VAT number: a text field. The form can store it. The catalog does not say the form checks the number with a tax authority.
- Website or shop URL: a URL field, so a broken address is caught before staff open it.
- Country and state: cascading country and state lists, which matter for tax and shipping later.
- Typical order volume: a number or a short select, such as units per month. Use it to sort applications, not as a contract.
- Resale or business type: a select for retailer, distributor, or internal use. This is the field that later drives show-and-hide rules.
If the buyer is logged in, smart prefill can fill name, email, and address from the Shopify customer. A first-time wholesale applicant usually is not logged in, so do not rely on prefill for the company name.
A submission can look up or create a Shopify customer, apply tags, and write customer metafields. That is useful after you approve the account. It is not the same as granting a wholesale catalog or a hidden price.
Fields that slow the application down
Long forms get abandoned. Leave these off the first version unless a person on your team uses the answer the same week.
- A full product wishlist. Ask for it after the account exists.
- Bank details or a card number. The form catalog has no card charge. Do not collect payment credentials in a text field.
- A file upload of a resale certificate, unless your region requires it before the first order. The upload field has an extension allowlist. The catalog does not publish a size cap, so test one real file.
- Marketing consent buried under wholesale terms. If you want a newsletter, make that a separate checkbox with your own wording.
A repeater field can let the buyer add another location or another contact. Use it only when you truly sell to multi-branch buyers. One extra contact is enough for most applications.
Split the form into steps
Multi-step forms are in the catalog. Each step has its own title and description, and the form shows progress navigation. The catalog does not assign this to Basic or Pro.
A clear split for wholesale is three steps: company, buyer, and order. Put the company name and tax number on the first step, the person and email on the second, and volume plus a message on the last. The last step should say what happens next, in your own words. The app will not invent an approval SLA for you.
The catalog records field-level drop-off on a multi-step form, so you can see which field people leave. That report does not explain why they left. If a tax field is empty, shorten the label before you add more questions.
Show extra questions only when they apply
Conditional logic can show or hide a field with AND or OR rules. Operators in the catalog are equals, contains, is empty, and greater or less than. If the buyer picks “distributor,” you can reveal a territory question. If they pick “retailer,” leave it hidden. Do not build a second form for each buyer type until that rule is not enough.
Hand the approved buyer to a quote workflow
An application answers “who is this company?” A quote answers “what will this order cost?” SK Form Builder can create a Shopify draft order from product fields on a form. Staff still set the price. The quote app is the one that hides prices, collects a quote request, and supports NET 7, 15, 30, 60, and 90 on its own draft orders.
Keep the two installs separate. Do not tell applicants that submitting the form hides retail prices. Link them to the quote path only after you have approved the account, or offer the quote form on its own page if you accept quote requests from the public.
Plan prices for the form app are Starter at no charge, Basic at $4.99 a month or $49.90 a year, and Pro at $12.99 a month or $129.90 a year. None of those prices is tied, in the catalog, to the wholesale fields above. The quote app is documented as fully free, which is a separate product.
What the form does not approve
A completed application is a message plus stored fields. It does not create a Shopify company location, a B2B catalog, or a payment term. Those are Shopify B2B features, and they are not what this form writes.
Staff should open the submission, check the website and tax number, and only then tag the customer or send terms. If you turn on the ticket behavior, a submission with an email becomes a ticket with an SLA due date. That tracks the conversation. It still does not approve the buyer.
Questions about wholesale application forms
Should wholesale buyers create a customer account first?
Not for the application itself. The form can create or match a Shopify customer from the submission. Requiring login first is a choice you make in the theme, not a requirement of the form catalog.
Can the form create a draft order?
Yes. A submission can create a Shopify draft order from product fields, or email a discount code. Use that for a priced request after approval. It is not a substitute for quote negotiation.
Does submitting the form hide retail prices?
No. Price hiding is configured in the quote app, with its own rules. The application form only collects the answers you add.
Build the application in SK Form Builder if these fields match the way you approve accounts. Install it from the Shopify App Store listing after you have decided which questions staff will actually read.