Stand up a new location's vendors in your books
When a new location opens, WebRun reads your onboarding vendor list in Google Sheets, drafts each supplier as a vendor record in Restaurant365 with payment terms, GL defaults, and the location mapped, leaves every record unsaved for review, and posts you a Slack checklist of any vendor still missing a tax ID or account number.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I set up a new restaurant location's vendors in Restaurant365 automatically?
When a new location opens, WebRun reads the vendor list from Google Sheets and drafts each supplier as a vendor record in Restaurant365 with payment terms, GL defaults, and the location mapped. It leaves every record unconfirmed for review and posts a Slack checklist of vendors still missing a tax ID or W-9, so onboarding a unit takes minutes.
- A new unit's vendors are drafted in the books the day the list arrives
- Missing tax IDs and W-9s surface on one checklist, not at first payment
- Every vendor record stays unconfirmed until a human signs off
Built for restaurant controllers · multi-unit operators · franchise accountants · restaurant bookkeepers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
docs.google.com/spreadsheetsin a real browser with your saved login - no setup, no API keys. -
1
Google Sheets - read the vendor list
WebRun reads the new location's vendor list from Google Sheets. - Open the onboarding vendor Sheet for the new location
- Read each vendor's name, contact, terms, category, and tax ID where present
- Note which rows are missing an account number, terms, or a W-9
Done when Every vendor row for the new location has been read and gaps noted.
-
2
Restaurant365 - draft each vendor record
WebRun drafts each supplier as a vendor record in Restaurant365 for review. - Open Restaurant365 vendors and draft a record for each supplier on the list
- Prefill payment terms, the default GL account, category, and the new location
- Leave every vendor record unsaved and flagged for a person to confirm, never activate a vendor on its own
Done when Each vendor on the list exists as a drafted, unconfirmed record in Restaurant365.
-
3
Slack - post the setup checklist
WebRun posts the vendor setup checklist to Slack. - Post a checklist of vendors drafted for the new location
- List any vendor still missing a tax ID, account number, or W-9
- Note that every record is drafted and waiting for a person to confirm
Done when The team has the new location's vendor setup checklist in Slack.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it activate vendors without me checking?
No. WebRun drafts each vendor record in Restaurant365 and leaves it unconfirmed. A person reviews the terms, GL default, and tax ID before activating, so no supplier goes live in your books unchecked.
What if a vendor row is missing a tax ID or account number?
It still drafts the record but flags the gap on the Slack checklist. WebRun never invents a tax ID or account number, so you know exactly which vendors need a follow up.
Can it map everything to the right location?
Yes. WebRun sets the new location on every drafted vendor and applies the GL and category defaults you specify, so the records are ready for that unit as soon as you confirm them.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.