Skip to content

Lost the original file when you sell to restaurants

Could you find the file your current list came from? Here is how people who sell to restaurants fix it.

Database in Riftjaw with active contacts, segment, lead file and source

Could you find the file your current list came from?

After a few rounds of editing, nobody knows what the original list looked like or where it came from. When something looks wrong, there is nothing to check it against.

It hits harder when you sell to restaurants. Restaurants run on thin margins and long hours, and the owner or general manager decides on suppliers, software and marketing. Groups have a head office buyer, but independents choose on price, reliability and how little extra work a change brings.

Errors cannot be traced back to their source. You also lose proof of where your data came from.

The original file stays with every import.

Riftjaw keeps the original import file attached to each import. You can get the original file back whenever you need it. Every record also keeps its source and date.

  • Fields that fit restaurants, such as cuisine
  • Email prefixes that fit, like info@, bookings@, reservations@ and manager@
  • Status, tags and a segment on every record
See the feature
List of imports and scrapes in Riftjaw
Every import stays on record with its lead file, date and status.

Fixing it in Riftjaw

  • Import as usual. The uploaded file is stored with the import automatically.
  • Open the import. Find the import in your history when you need to check something.
  • Get the file back. Retrieve the original file exactly as it was uploaded.
Import in Riftjaw: every column matched to a profile field, with all rows previewed
Columns from a maps export matched to profile fields such as company, phone, website and city.

Other walls when prospecting restaurants

Restaurant lists change fast as places open, close and change owners.

Each record keeps its source and date, and you can archive closed places so your active list stays current.

The bookings@ address reaches a host, not the owner.

Tick several prefixes in email from domain, such as info@ and manager@, and note on the contact who replied.

You cannot tell which restaurants you already visited in person.

Set the status to Contacted and add a note after each visit, so the whole team sees it.

Fields worth recording for restaurants

Record these and you can split the list later, write sharper mails and see who fits your offer.

FieldWhy it helps
Company nameThe key field. Duplicates are checked on it or on the website.
WebsiteNeeded to derive an email when the export has none.
CuisineThe type of food shapes which products and suppliers are relevant.
CoversSeating capacity hints at volume and budget.
Independent or groupGroups buy centrally, so you need a different contact and approach.
DeliveryRestaurants that deliver need packaging and ordering tools.
Opening hoursKnowing when they open helps you pick a time to call or visit.

Questions people ask

Collect restaurants from public listings such as Google Maps or review sites with a scraper, then import the CSV or Excel file. Riftjaw flags duplicates and lets you add a field for cuisine or area.

Many teams do both. Riftjaw keeps phone numbers as fields and email history per contact, so you can tag who to call and send a short campaign to the rest.

If your file has an email column, that wins. If it only has websites, tick the prefixes you want, such as info@, bookings@, reservations@ and manager@, and Riftjaw derives addresses from each domain. Derived addresses are good guesses, not verified, so start with small batches.

Yes. The Free plan runs the whole pipeline on one list with small campaigns, and you do not need a credit card. Move to Pro when you want more lists, segments and bigger campaigns.

Build a database you own

Create your account, import your first list and see it turn into records you can work.

No credit card · cancel any time · your data stays yours