Application intake
Collect vendor details, program context, documents, and application status before the market week gets noisy.
Vendor management workflow markers summarize the intake, approval, and payment areas covered by this public page.
Vendor application intake feeds the manager review workflow instead of a disconnected form stack.
Vendor applications
Approval follow-through moves accepted vendors into operating records for recurring market work.
Vendor approvals
Payment posture stays connected to vendor readiness and market-day follow-up.
Vendor payments
Vendor management software for recurring markets.
Manage vendor applications, approvals, payments, booth assignments, and market-day operations in one connected system.
Open public pricing for vendor management plans and limits.
Jump to the public starter trial path on the home page.
Vendor management workflow summary
Visual summary of vendor intake, approval follow-through, and market-day context for recurring markets.
Vendor management workflow stages explain how intake, approval follow-through, and market-day context stay connected.
Use this stage to collect vendor details before manager review begins.
Approved vendors can move into operational rosters without rebuilding the data manually.
Approval follow-through
Move approved vendors into operating records instead of recreating rosters in a separate spreadsheet.
Market-day details stay connected to the vendor record after intake and approval.
Market-day context
Keep assignments, reminders, payment posture, and follow-up tied to the same vendor workflow.
Vendor Management
Keep vendor operations in one place instead of juggling spreadsheets and disconnected tools.
The Market Manager helps recurring market teams handle intake, approvals, payments, booth assignments, reminders, and market-day follow-through from one workflow.
Vendor management operating benefits summarize how connected records reduce spreadsheet cleanup for recurring markets.
This workflow keeps vendor intake, approval, payment, and market-day records connected.
Vendor management operating point 1
Vendor applications, approvals, payments, booth assignments, reminders, and market-day follow-through stay in one workflow.
Readiness context helps managers spot vendor follow-up before the next market day.
Vendor management operating point 2
Recurring market teams can see vendor readiness before the next session instead of reconciling scattered notes.
Public application access still preserves manager review before vendors move into operations.
Vendor management operating point 3
Public application paths connect to vendor operations without removing the manager review and approval steps.
Public intake does not make private vendor records public.
This public page explains the vendor workflow, but applications, notes, payment records, files, and review decisions stay inside authorized workspaces.
Vendor management public boundary notes distinguish public application access from protected manager review records.
Public intake pages can collect applications without exposing manager-only review records.
Public application path
Applicants can start from public-facing pages when intake is open.
Vendor review details stay behind authorized manager access.
Manager review
Approvals, notes, payment posture, and follow-up remain protected workflow context.