A food hall's vendor-directory site got out of its volunteers' way with a maintained WordPress setup

Representative examplesEvery case study in this library is an illustrative composite of the kind of engagement we deliver — written to show our method and standards, not to name clients.

Where they started

Two dozen independent food vendors — counters, stalls, and a bar — share a restored warehouse under one roof and one brand, operated by a property group that also runs the website. The site is the practical tool guests rely on: who's open today, what's on the menu, what event is happening this weekend. Changes come from vendors by email to the property group's marketing manager, who re-keys them into the site alongside her duties for the group's other properties. Event weekends stretch that arrangement past its limit.

What it was costing

The food hall's site listed every vendor's hours, menus, and events, but updates went through the property group's overworked marketing manager; vendors emailed changes that went live late or wrong, and event weekends exposed stale hours that guests complained about publicly.

What they could see

• Vendor hours went live late or wrong on event weekends, and guests complained about it publicly in reviews.
• The marketing manager spent hours each week re-keying emailed changes instead of the property work she was hired for.
• Vendors sometimes stopped sending changes at all, assuming the site would be wrong anyway.
• Menu prices and holiday hours drifted out of date quietly, with no record of who last touched a listing.
• Event-day corrections required the manager's personal attention — fixing the site from a phone during openings.

The constraints we worked inside

• Vendors vary from confident to tech-averse; editing access must be safe for the least technical user.
• The property group controls brand and legal pages; vendors must never edit outside their own listings.
• The site's design is the hall's brand; the workflow change cannot be a redesign.

What had been tried before

A shared inbox collected vendor changes, which the marketing manager keyed into the site herself.

The inbox worked until event season, when changes arrived faster than typing; hours went live late or wrong and the manager became the queue every vendor waited in.

One shared vendor login was created so stalls could update their own listings.

With one account there was no attribution and no revision history — a mistake was unattributable, and half the damage couldn't be undone without guessing who had edited what.

A weekend workshop taught the more confident vendors to edit their own pages directly.

It raised the confident vendors and left the least technical exactly where they were; one broken homepage section was enough for the property group to revoke open access.

What we proposed

We proposed getting the marketing manager out of the re-keying business: each vendor receives an account scoped to their own listing — hours, menu, photo, description — with the rest of the site invisible to them. A light review queue would apply to the first month of edits while trust calibrated, after which proven vendors publish directly; the design and legal pages stay locked to the property group. A weekly maintenance rhythm — updates, backups, a monthly report — keeps the platform boring, which is the entire point.

Just as important is what we ruled out, and why:

• A third-party vendor portal service — Another login vendors won't adopt, a monthly fee, and hours and menus living in two places; the listing pages are where guests already look.
• Open editing for all vendors, no queue — The least technical vendor is one broken homepage section away from a public complaint; the property group's brand pages can't be exposed to scope-less accounts.
• A structured intake form retained by the manager — The bottleneck was never the form — it was one person re-keying everything; a better intake would have optimized the queue instead of removing it.

How the work ran

Delivered by the systems pod — engineer over 4 weeks, with working increments reviewed with the client every week.

The stack, and the reasoning

WordPress

The hall's design is its brand and stays untouched; role-scoped editing changes the workflow without touching a single template or page.

Role-scoped vendor editing

Each vendor's account shows only their own listing, so the least technical user on the roster can't break what they can't see.

Review queue

A first-month review calibrated trust from real edit history, after which proven vendors published directly and the queue became a training-wheels state, not a gate.

Managed updates

Weekly maintenance keeps the platform deliberately uneventful — the property group bought reliability, not novelty, and the monthly report proves it.

Off-site backups

Handing every stall an editor is only safe because the restore has been tested — a mangled listing returns from the morning's copy before the lunch rush, and the vendor who made the mistake never has to explain a missing menu.

What went wrong

How we worked together

Cadence

A kickoff walkthrough with the marketing manager, weekly Tuesday notes, and after vendor onboarding a monthly 30-minute review of the report and any queue escalations.

Client side

The marketing manager owned the rollout order and the trust decisions; two confident vendors were recruited as the first testers of scoped editing.

Decisions

Which vendors earned direct publishing was decided from the first month's edit history at the monthly review — evidence, not favoritism, and the vendors could see the rule.

They provided

The vendor contact list with a named contact per stall, an afternoon per vendor for onboarding during quiet hours, and sign-off on the legal-page lockout.

What changed

The headline: vendors maintaining their own listings, with the marketing manager out of the day-to-day — Manager bottleneck → scoped vendor edits, read from Listing update timestamps. A second check: median hours-update turnaround at 9 days → same day.

The marketing manager's week changed shape: vendor updates went from a daily interruption to a monthly report to skim. Vendors update listings between services and see the result live, which changed how they talk about the hall in public. Guest complaints about stale hours all but disappeared, and event weekends lost their particular dread. The property group got something it hadn't had before: a website that runs itself well enough to be boring.

The result was read from Listing update timestamps against the pre-engagement baseline over the stated window, with a guardrail check on median hours-update turnaround. Where platform-reported numbers and business outcomes differ, this record says which layer it is quoting.

What they own now

• Per-vendor scoped accounts with a role map showing exactly what each can touch.
• The review-queue policy and the edit-history criteria used to graduate vendors.
• A vendor onboarding sheet for future stalls: thirty minutes, one listing, done.
• The monthly maintenance report format plus the backup and update schedule behind it.