Ops & Supply

How to vet and onboard vendors as Restaurant and Hospitality Founders

Ops & SupplyFor Restaurant and Hospitality Founders2 apps12 steps~24 min to set up

Every new vendor relationship — a new produce distributor, a linen service, a new liquor rep — starts with a paper certificate of insurance shoved in a drawer, a verbal price agreement you half-remember, and a net-30 terms email buried in your inbox. When your broadline distributor quietly bumps your case price 8% in January, you catch it in March when food cost jumps and you're staring at MarginEdge trying to figure out why. You have no central place to track who you're paying, what you agreed to, when their health permits expire, or when their contract auto-renews. Onboarding a new vendor means emailing back and forth for two weeks to get a W-9 and a signed terms sheet.

Build this on Starch → See the apps used

Ops & SupplyFor Restaurant and Hospitality Founders2 apps12 steps~24 min to set up

Outcome

What you'll set up

A vendor registry that tracks every supplier — produce, beverage, linen, pest control, equipment repair — with their agreed pricing, payment terms, insurance expiry dates, and contract renewal windows all in one searchable place

An onboarding checklist automation that fires when you add a new vendor: collects W-9, COI, food handler certifications, signed pricing agreement, and bank details without a single follow-up email from you

Price-change alerts that compare your current invoice amounts against the agreed rates in your vendor registry and flag any variance before it wrecks your food cost percentage

The Starch recipe

Apps, data, and prompts

The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.

Apps used

Project Management Contract Lifecycle Management

Data sources & config

Wire QuickBooks as a scheduled-sync provider so Starch pulls your bills, vendor records, and invoice line items on a schedule. Connect Slack from Starch's integration catalog so the agent queries it live to deliver weekly price-variance alerts. For vendors who send COIs or W-9s through a web portal with no API — like your insurance compliance portal or a distributor's supplier onboarding site — Starch automates the document retrieval through your browser, no API needed. Contract Lifecycle Management (coming soon) will handle e-signature collection and renewal tracking natively once it launches.

Prompts to copy

Build me a vendor registry app that tracks each supplier's name, category (produce, beverage, dry goods, linen, equipment, services), primary contact, payment terms, agreed pricing notes, insurance expiration date, and contract renewal date. Show me overdue renewals and expiring certificates in a red-flagged view.

Create an onboarding workflow: when I add a new vendor, generate a task list that includes collecting W-9, certificate of insurance, food handler certification if applicable, signed pricing agreement, and ACH banking details. Assign each task a due date 3 days out and alert me when the checklist is complete.

Every Monday, compare last week's invoices from my QuickBooks vendors against the agreed pricing in my vendor registry and send me a Slack message listing any line items that came in more than 5% over the agreed rate.

Run these in Starch → or paste them into your favorite agent

Walkthrough

Step-by-step

1 Connect QuickBooks as a scheduled-sync provider. Starch syncs your vendor list, bills, and invoice line items on a schedule so your vendor registry has real transaction history behind it from day one.

2 Describe your vendor registry to Starch in plain language — categories you care about (produce, protein, beverage, linen, pest control), the fields you need (agreed pricing, payment terms, COI expiry, renewal date), and the red-flag views you want. Starch builds the app.

3 Import your existing vendor list from QuickBooks into the registry. Starch maps vendor names and payment terms automatically; you fill in the fields QuickBooks doesn't track — agreed case prices, insurance dates, contract renewal windows.

4 Set up the onboarding checklist automation. When you add a new vendor record, Starch creates a task list in Project Management — W-9, COI, signed pricing agreement, banking details, any category-specific certs like food handler licenses — with due dates and owner assignments.

5 For vendors who use a web-based supplier portal to submit documents, Starch automates the retrieval through your browser so you're not logging into six different portals manually to chase paperwork.

6 Wire in Slack from Starch's integration catalog. The agent queries it live to push weekly price-variance digests and renewal deadline alerts directly to your ops channel.

7 Build the price-variance automation: Starch compares QuickBooks invoice line items against the agreed rates stored in your vendor registry. Any line item more than your threshold (say, 5%) triggers a flag before you pay the bill.

8 Set up a 60-day and 30-day renewal alert. Starch reads contract renewal dates and COI expiration dates from your registry and sends you a digest — which vendor needs a new certificate, which pricing agreement is up for renegotiation.

9 For vendor contracts currently living in email threads or Google Drive folders, describe to Starch what you want stored: 'create a contract record for my produce distributor with the signed PDF, agreed pricing schedule, and auto-renewal date of July 1.' Starch files it in your registry.

10 When Contract Lifecycle Management launches (coming soon), migrate your vendor agreements there for e-signature workflows, clause-level search, and amendment tracking — the registry you built today will connect directly to it.

11 Review your vendor registry monthly: flag any vendor where you have no signed pricing agreement on file and kick off the onboarding checklist retroactively to close the gap.

12 Run a quarterly vendor audit using Starch: 'show me every vendor we paid in the last 90 days where we have no COI on file or where the COI expires in the next 60 days.' Fix the gaps before your next health inspection or liability claim.

See this running on Starch

Connect your tools, describe what you want, and the agent builds it. Closed beta is free.

Try it on Starch →

Worked example

Onboarding a new protein distributor — April 2026

Sample numbers from a real run

Signed pricing agreement (chicken breast, ground beef, salmon)	0
W-9 collected	0
Certificate of Insurance (GL + product liability, expires Apr 2027)	0
Net 30 terms confirmed	0
First invoice — 14 line items, avg case price $47.20	661
Price variance flagged on invoice 3 (ground beef, +9% over agreed rate)	38

You added Coastal Protein Co. to your vendor registry on April 3. Starch immediately created a five-item onboarding checklist in Project Management: W-9, COI, signed pricing schedule, banking details for ACH, and a note to confirm their food-safety certification. All five items were closed by April 7 — Coastal uses a supplier portal, so Starch pulled the COI directly through browser automation without you logging in. Their agreed pricing schedule — chicken breast at $2.89/lb, ground beef at $4.10/lb, Atlantic salmon at $8.75/lb — went into the registry that day. Three weeks later, Starch's Monday morning price check caught invoice #3: ground beef came in at $4.47/lb, $0.37 over the agreed rate across 14 cases, a $38 overcharge that would have disappeared into your food cost variance without a flag. You replied to the invoice with the agreed rate; they issued a credit memo the next day. Before Starch, that $38 would have been absorbed silently, and the same distributor would have tested the same price bump the following month.

Measurement

How you'll know it's working

Vendor onboarding time: days from first contact to fully credentialed (W-9, COI, signed pricing agreement) — target under 7 days

Price variance rate: percentage of invoices with at least one line item above agreed price — track monthly, flag anything above 3%

COI coverage: percentage of active vendors with a current, unexpired certificate of insurance on file — target 100%

Contract renewal miss rate: number of auto-renewals that fired without a renegotiation window — target zero

Food cost variance explained by vendor price creep: dollar delta between agreed and invoiced pricing per period, broken out by vendor category

Comparison

What this replaces

The other ways teams handle this today, and how the Starch version compares.

Google Drive folder + email chain

Zero cost but zero structure — COIs expire without anyone noticing, pricing agreements can't be searched, and there's no audit trail if a vendor dispute goes legal.

MarginEdge

Strong for food cost tracking and invoice digitization, but it's not a vendor registry or contract tool — you still have no place to track COI expiry, payment terms, or onboarding status.

QuickBooks vendor records

Captures who you paid and how much, but has no fields for insurance certificates, agreed pricing schedules, or contract renewal dates — it's a ledger, not a vendor management layer.

Airtable

Flexible enough to build a vendor registry manually, but you'll spend a weekend configuring it, there's no native automation for onboarding checklists, and it doesn't connect to your QuickBooks invoices to catch price variances.

On Starch RECOMMENDED

One platform — project management, contract lifecycle management all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.

Try it on Starch →

FAQ

Frequently asked questions

Does Starch store actual vendor contracts, or just the metadata?

Right now, Starch stores the metadata you describe — renewal dates, pricing terms, contact info, expiry dates — and links to documents you've already stored elsewhere. The Contract Lifecycle Management app (coming soon) will add native contract storage, e-signature collection, and clause-level search. If you want to get ahead of that, build your vendor registry today and migrate contracts in when it launches.

My distributor invoices come in as PDFs via email. Can Starch read those?

Starch syncs your Gmail data on a schedule, so it can identify invoice emails. For line-item extraction from PDF attachments, describe to Starch what you want: 'when an email from [distributor] arrives with a PDF attachment, extract the line items and compare them against my agreed pricing in the vendor registry.' The agent handles the extraction. If your distributor also has a web portal where invoices live, Starch can automate retrieval there through your browser — no API needed.

We use Square, not QuickBooks. Does this still work?

Square is reachable from Starch's integration catalog, so the agent can query it live. The price-variance automation works best when QuickBooks is the scheduled-sync source (deepest integration, line-item data), but if Square is your system of record, tell Starch that when you describe the workflow and it will wire accordingly.

Is Starch SOC 2 certified? Our insurance requires it for tools that touch vendor contracts.

Not yet. Starch is not SOC 2 Type II certified today. If your insurance or a franchisor agreement requires SOC 2 for any tool that stores vendor contract data, that's a real constraint to weigh. The vendor registry and onboarding workflows work fine without storing sensitive financial data in Starch — you can keep contracts in Google Drive and use Starch as the metadata and alerting layer.

Can Starch automatically send onboarding emails to new vendors asking for their documents?

Yes. Wire Gmail as a scheduled-sync provider (Starch syncs your Gmail on a schedule and can also send). Then describe the automation: 'when I add a new vendor record, send them an email with our onboarding checklist and a link to upload their W-9 and COI.' The agent drafts and sends through your Gmail account. The Gmail OAuth consent screen currently shows the underlying connector name rather than 'Starch' — that's a known item on the roadmap.

How do I handle vendors who auto-renew if I don't cancel 60 days out?

Store the auto-renewal date and the cancellation notice window in your vendor registry when you onboard them. Then tell Starch: 'send me a Slack message 75 days before any vendor's auto-renewal date so I have two weeks to decide before the cancellation window closes.' The agent reads the registry and fires the alert on schedule. This is the most common way a restaurant owner loses $4,000 on a linen service contract they meant to renegotiate.