A supplier says yes, and then the real work starts. Who gets the invoices? Which days do they deliver? Who do we call when a pallet is late? I would rather ask once, in one form, than chase each answer.
Who it is for
Buyers, shop owners and operations teams who add suppliers more than once a year and want the same set-up details every time.
What each question is for
- Company, contact and phone: the name that must appear on orders, and a person to call.
- Invoice email, method and terms: so invoices reach the right inbox in the right shape.
- Delivery days, cut-off and late contact: what your receiving team plans around.
- System access and data contact: the answer your IT team needs before any login is issued.
- Code of conduct tick: confirms they read your rules.
I leave bank details off the form. Share those through your own secure process.
What a vendor's AI would ask
"Which email should invoices go to?" Then "Which days do you deliver?" Then "Will your staff need access to our systems?" It shows the answers and sends only after a yes. See agent-fillable forms.
Before you use it
Start from a supplier application to choose vendors. For goods that arrive, add a delivery receipt and an inventory template. More ideas are in forms for Ecommerce and Shopify stores and forms for IT and operations.
Questions
Is this the same as a supplier application?
No. A supplier application helps you choose. This form comes after you say yes and collects working details: contacts, invoicing, delivery days and access.
How do I use the answers?
Download the CSV and copy each row into your vendor list. Keep one row per vendor, and check the invoice email against what is on the first invoice you receive.
What is the access question for?
It tells your IT team which vendors need a login or a shared folder. Handle those vendors with your own access process, outside this form.