Docs / Pages
Application form
One page where a supplier builds its credit application, writes its marketplace listing, shares the apply link and QR codes, and emails customers an invitation.
/application-form is the one place for the job "get customers to apply". It has four tabs, each offered only to a role that holds its permission; the first tab you may open is the default. The old pages /application-builder, /my-qr, /my-qr/<kind> and /invite-customer redirect here (to the Form, Share and Invite tabs), so bookmarks and old emails still work. The address of a tab is /application-form?tab=form|listing|share|invite, and kind=personal|company shows one QR code in the Share tab.
| Tab | Needs | What it is |
|---|---|---|
| Form | builder.manage | the builder: questions on one side, a live preview of what the applicant sees on the other |
| Listing | builder.manage | the optional tagline and rich text customers see in Find vendors, with a live preview |
| Share | qr.view | the apply link and the personal and company QR codes, with how many applications each started and submitted |
| Invite | invitations.customer | the readiness checklist, the apply link, and the email invitation |
A role without any of the keys is sent to /applications. Opening a tab you may not use shows an access panel that names the missing permission; the services endpoints behind each tab stay the authority.
Form tab#
Split view on wide screens; below 1120px an Edit | Preview switch shows one pane at a time. Publishing is its own step: Publish opens a dialog that states what will change before anything goes live, and on a phone Save draft and Publish stay pinned above the bottom navigation. Deleting a variation asks for confirmation. The tab loads GET /v1/supplier/builder and creates an empty configuration for the organization the first time; without builder.manage that endpoint answers a redirect to /applications.
What you set:
- The "Preferred terms" question offers the platform list of payment terms in days (Net 30, Net 60, Net 90); a form published before 2026-10-25 may still show Net 15, which is stored as not specified.
- Brand (name, abbreviation, logo), questions and documents, the supplier's terms and consent wording, minimum references, and the Owners and personal guaranty panel above the builder: Ask for owners and officers (the apply form then requires at least one owner or officer with name, title, ownership %, last 4 of SSN and email) and Require a personal guaranty acknowledgement with its wording. The guaranty is a checkbox covered by the applicant's own signature on the application; it needs principals, so ticking it turns principals on (publishing the other way round is refused with 400). Both are part of the published version, so changing them needs a new publish; existing forms published earlier do not ask for principals.
- A supplier can keep several variations, for example per type of customer.
Saving and publishing:
- Save draft and Publish both call
PATCH /v1/admin/credit-app-configwith anintent, the version you started from and the draft revision. - Publishing a personal guaranty requirement without its wording is refused (400: add the wording first).
- If another editor saved or published meanwhile, the call fails with 409 "Reload before publishing".
- The header shows "Draft - not published", "Live version N", or "Prepared version N - intake unavailable" when the organization is not yet approved to receive applications.
- Drafting terms with AI is rate limited and returns an error you can retry.
Listing tab#
The supplier's page in the Find vendors marketplace. Everything here is optional; with nothing written the supplier is still listed with its name, category and computed facts (terms granted, decision time, references).
- Tagline: one line, at most 140 characters, shown on the supplier's card and as the subtitle of its page.
- About your company: up to 6000 characters of Markdown, shown on the supplier's page. The toolbar inserts Heading, Bold, Italic, List, Quote and Link around the selected text; the preview beside the box shows what customers will see.
- Images and raw HTML are not shown, and links must be
http,httpsormailto. Clearing a field and saving removes it from the listing. - Save listing is enabled only when something changed. It calls
PUT /v1/listing(needsbuilder.manage, audited aslisting.updated); errors from the API show above the button. Rules and errors: Supplier listing API. - Saving the listing does not publish or change the application form.
Share tab#
Both kinds of code open the supplier's public application at /apply; the personal code adds the rep token so submissions are attributed to that rep. The list shows each code with the credit application version it opens, applications started and submitted, and the date of the last one; the company code also includes email invitations. The detail of the personal code lists the applications that rep sourced (code, applicant, status, requested limit). The company code also has a Website button card: a preview, a text and a color, and the code to copy. The code is one link to your public application with its styling inline (no script), to paste into any page of your own website that accepts custom HTML. A customer who clicks it opens your application on VendorLogic, in the same tab, signed in or not; those applications are counted with the company code because the address is the same. A readiness checklist explains what is missing: a code only works once the application is published and the organization can receive applications. Vendor users without qr.view see an access panel; a kind other than personal or company shows the list.
Invite tab#
Reads first: the readiness checklist, the attached application, and the apply link with Copy link and Show QR code. Sending an email is a separate step behind the "Send an invitation" button, which opens a dialog (a full-height sheet on a phone). Until the business is approved and an application is published, the tab explains what is missing and the button is disabled; POST /v1/invite-customer refuses too. If the onboarding gate for invitations is open, a note names the step to finish first.
- Inputs: customer email (required), name and a personal note (optional).
- Send queues the email. The dialog then confirms the address and offers "Invite another" or "Done". Cancel and Esc close it without sending; it cannot be closed while the request is running.
- Errors from the API (for example an address that is already invited) show inside the dialog.
For tests#
Stable test ids: form-tabs, form-tab-form, form-tab-listing, form-tab-share, form-tab-invite, listing-tab, listing-tagline, listing-body, listing-preview, share-tab, qr-card, website-button, website-button-label, website-button-color, website-button-code, website-button-copy, invite-tab.
Related#
An empty listing offers a Start from an outline button that inserts three headings (who you supply, how credit works with you, delivery area and hours) to fill in.