TOME — THE DIRECTORY ENGINE
Run a local directory that knows who owns what.
Listings, owners, reviews and paid placement, on the same foundation as everything else we build. The Directory engine is the part of Tome made for local directories: markets and listings, owners who claim and verify their business, reviews that get moderated, and promotions labelled as exactly what they are.
Capture pending — starter.wabbit.com/directory, the map-led browse (David's shot list)
Most directories start as a plugin, and the plugin runs out first.
A listing becomes a post with forty custom fields. Then every rule a directory actually needs shows up as another plugin: one for claims, one for reviews, one for paid tiers, each with its own idea of who a user is. It holds until the first owner disputes a claim, or a competitor floods a listing with one-star reviews, and you find out none of the pieces talk to each other.
A directory is a small business with rules of its own. Who can list. Who can claim a listing, and what proves it. What an owner may change and what stays locked. What a paid placement is allowed to say. The Directory engine keeps those rules in one place, on one identity model, with every change on the record.
The parts of a directory, already wired together.
Markets and listings
Each one has an address, hours and a menu, browsed on a map or in a grid, and each kind of listing gets its own fields, so a dispensary and a clinic don't share one form.
Owner claims
They start from a signed-in member, allow one pending claim per listing, and wait for approval before anything changes hands. An approved owner can edit their own listing, apart from the fields you lock.
Reviews and favorites
They're moderated, with a reply from the owner under each review.
Promotions
They carry a Sponsored label wherever they appear, because a paid spot should say it was paid for.
Paid tiers
They're billed through the Commerce engine. For industries Stripe won't serve, an Authorize.Net processor ships alongside it.
Blocks for all of it
It's the map-led browse, the listing grid and detail page, a claim call-to-action, the review form and an age gate.
Rules that belong to one industry live in your site's own policy file, not in the engine. That's how the same engine runs a cannabis directory with an age gate and a restaurant guide without one.
It's live.
A cannabis-dispensary directory in Kansas City runs its listings, maps and reviews on this engine today. It's our own build, so every rough edge we hit became a fix in the engine before it became your problem.
You can walk the whole engine on our demo store without an account: 24 seeded listings across a market, the map, listing pages, reviews, and the claim flow.
- A city or trade guide where the businesses themselves claim their listings and keep them current.
- A regulated industry that needs an age gate at the door and a payment processor that will take its money, which is how our own cannabis directory runs.
- A members' association that lists its members' businesses and sells them a featured spot, labelled as sponsored wherever it shows.
- A review site that can't afford a review war, because every review is moderated and every owner gets a reply under it.
A page listing twenty businesses doesn't need an engine.
A well-made table does that. The engine starts earning its keep when owners, reviews and money enter the picture.
Getting it
$400 a year, or included with Agency.
Add it to any plan, including the free one.
The directory blocks come with it, and Agency already includes every engine. It runs on the Tome foundation. Selling placements takes the Commerce engine too, since that's where payments live.
The quickstart walks through the wiring, and the docs cover every package in it.