Finding the Buyers Who Can Actually Stock You
For a brand trying to get on shelves, the hardest part of outreach isn't the pitch — it's the list. The person who decides whether your product gets stocked is a category buyer at a retail chain or a purchasing contact at a distributor, and those people don't fill out forms, don't appear on the retailer's website, and rarely show up in a generic lead list. Most brands stall at the front door: they know which retailers they want, but not who inside them to email.
That's the specific problem Apollo solves. Its B2B contact database lets you filter by the exact titles that control assortment — buyer, category manager, merchandising manager — scoped to retail and wholesale verticals, with verified emails and direct dials attached. ColdRelay is the layer underneath: the secondary domains, mailboxes, and dedicated IPs that Apollo's sequences actually send from, kept entirely separate from your store domain. This guide covers how ecommerce teams wire the two together and turn a target-retailer wishlist into a working buyer pipeline.
Why Run Apollo on ColdRelay Infrastructure
Apollo gives an ecommerce brand the two things wholesale outreach can't start without: the contact data to find buyers and distributor reps, and the sequencing engine to work them across email, phone, and LinkedIn. What Apollo doesn't do is provision the domains and mailboxes those sequences send from, or own the deliverability of the accounts you link under Settings → Mailboxes. That's the infrastructure layer's job — and buyer outreach punishes weak infrastructure harder than most motions, because retail buyers sit behind corporate mail gateways that filter aggressively and a bounced or spam-foldered pitch at a 400-store chain is an opportunity you don't get back.
ColdRelay fills that slot. You provision outreach mailboxes on isolated Azure tenants with dedicated IPs, with SPF, DKIM, and DMARC pre-configured, ready in about an hour — and there's no warmup waiting period before your first sequence, because warmup runs continuously as part of each mailbox's 4 sends/day budget (2 outbound + 2 warmup). ColdRelay supports 100-150 mailboxes per domain, so even a multi-vertical buyer motion rarely needs more than a couple of domains.
The pairing is additive, not competitive: ColdRelay is the infrastructure, Apollo is the data and sending layer on top. You keep Apollo's database, personas, and multi-channel sequences — you just point them at mailboxes built to land in a buyer's corporate inbox.
Visit Apollo →Connecting ColdRelay Mailboxes to Apollo
Provision an outreach mailbox pool on ColdRelay
Register secondary domains that read like the wholesale side of the business — brandtrade.com or brand-wholesale.com — never your storefront domain. Buyer lists are finite, so most brands start with 15-50 mailboxes on a single domain (ColdRelay fits 100-150 per domain). Everything provisions on isolated Azure tenants with dedicated IPs in about an hour, with SPF, DKIM, and DMARC already configured.
Link the mailboxes in Apollo under Settings → Mailboxes
In Apollo, go to Settings → Mailboxes and link each ColdRelay mailbox using the SMTP/IMAP credentials from your ColdRelay dashboard export. Each mailbox becomes a sending account Apollo can rotate sequence volume across, and replies sync back so they thread correctly in the contact record.
Set per-mailbox daily send limits to the ColdRelay budget
In each linked mailbox's settings, set Apollo's per-mailbox daily send limit to 2 outbound emails. That mirrors ColdRelay's per-mailbox budget — 4 sends/day total, split 2 outbound + 2 warmup. Warmup runs continuously on ColdRelay's side, so there's nothing extra to configure in Apollo and no waiting period before the first sequence goes live.
Build buyer personas and saved searches in Apollo
This is where the buyer-contact problem actually gets solved. Create saved personas for each role that controls stocking decisions — buyer, category buyer, category manager, merchandising manager, head of purchasing — and scope them by retail vertical (grocery, beauty, pet, sporting goods) and company type. Build a parallel persona set for distributors: purchasing managers and category leads at the wholesale companies that feed your target retailers. Save the searches so newly added contacts flow into your lists automatically as Apollo's database updates.
Create a multi-channel sequence and enroll contacts
Build an Apollo sequence that mixes email steps with call tasks and LinkedIn steps — buyers who ignore a second email often pick up a direct dial, and Apollo attaches phone numbers to many buyer records. A typical structure: email day 1, LinkedIn connection day 3, email day 6, call task day 8, breakup email day 14. Enroll contacts from your saved persona searches and let Apollo rotate sends across the ColdRelay mailbox pool.
The Ecommerce Apollo Playbook
Build the list from titles, not retailer websites
Brands waste weeks guessing at info@ addresses and LinkedIn-stalking individual chains. Invert it: define the title once in an Apollo persona — category buyer, merchandising manager — scoped to your retail vertical, and let the database return every matching contact across hundreds of retailers at once, verified email included. The wishlist of 20 dream retailers becomes a working list of 400 reachable buyers, and the saved search keeps refilling it as Apollo adds contacts.
Time outreach to buyer job changes and review windows
A buyer who just took over a category is the single best cold prospect in retail — they're expected to reshuffle the assortment in their first months and are actively looking for new lines. Use Apollo's job-change and signal filters to catch recently moved buyers, and reference the category review cycle in your copy: most chains reset assortments on fixed calendars, and a pitch that lands two months before a review reads as useful, not interruptive.
Work distributors as a second front, not a fallback
Many retailers won't buy direct from a small brand at all — they buy from the distributors they already cut POs to. Build a separate Apollo persona for distributor purchasing contacts and run them in their own sequence with different framing: distributors care about margin spread, MOQs, and fill rates, not your brand story. Getting picked up by one distributor can put you in front of dozens of retail accounts your direct buyer outreach would have ground through one by one.
Use the call step — buyer deals don't close in writing
Retail buyers drown in email but still answer phones, and Apollo's direct dials are most valuable exactly here. Treat email as the opener and the call task as the real conversion step: an emailed one-pager earns you recognition, and the follow-up call three days later turns it into a sample request or a line-review slot. Brands that run email-only sequences against buyer lists consistently leave the meetings to whoever picked up the phone.
Typical Retail Buyer Outreach Benchmarks (Apollo + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants matter most against corporate retail mail gateways |
| Reply rate — category buyers, email + call + LinkedIn | 3-6% | Multi-channel sequences outperform email-only against buyer titles; job-change timing pulls the high end |
| Reply rate — distributor purchasing contacts | 4-8% | Distributors actively hunt for new lines; clear margin and MOQ terms drive replies |
| Outbound capacity per mailbox | 2/day | 4 sends/day total per mailbox — 2 outbound + 2 warmup |
| Time to first sequence | Same day | ~60 minutes to provision, plus persona setup and sequence build in Apollo |
What It Costs: Apollo + ColdRelay
You pay per mailbox per month for the infrastructure, with volume tiers that drop as you scale (see the table below). DNS, dedicated IPs, and isolated Azure tenants are included — and because buyer lists are finite, most brands sit comfortably in the smaller mailbox counts.
Apollo is billed separately on its own subscription for the contact database, personas, sequences, and dialer — priced per its current plans, with database access and export credits being the parts an ecommerce brand actually pays for here.
Infrastructure cost scales with mailbox count; Apollo's cost scales with seats and credit usage. The two stack cleanly — one bill for sending capacity, one for the data and sequencing — and neither touches your Klaviyo or transactional email spend.
| Mailboxes | ColdRelay price / mailbox / month |
|---|---|
| 1–199 | $1.00 |
| 200–999 | $0.85 |
| 1,000–4,999 | $0.70 |
| 5,000+ | $0.55 |
Each mailbox sends 4 emails per day — 2 outbound to prospects + 2 warmup. ColdRelay provisions mailboxes on isolated Azure tenants with dedicated IPs; Apollo handles the sending, sequencing, and inbox rotation on top.
Frequently Asked Questions
Does ColdRelay replace Apollo?
No — they're complementary layers, used together. Apollo supplies the buyer and distributor contact data, personas, and multi-channel sequences. ColdRelay provides the underlying secondary domains, mailboxes, and dedicated IPs that Apollo's sequences send from. Apollo finds the buyer; ColdRelay makes sure the email reaches them.
Can't we just link our existing store-domain mailboxes in Apollo?
You can, and you shouldn't. Buyer prospecting generates bounces and the occasional complaint by nature, and any of that against your store domain puts order confirmations, shipping updates, and Klaviyo flows at risk. ColdRelay mailboxes run on separate secondary domains, dedicated IPs, and isolated Azure tenants, so wholesale outreach is physically walled off from customer email.
How accurate is Apollo's data for retail buyer titles?
Good enough to change the game, not perfect — buyer roles turn over often, and titles vary by chain (buyer, category manager, merchandising manager can all own the same decision). Use saved searches so your lists refresh as Apollo updates records, verify high-stakes contacts before a key sequence, and expect some bounce — which is exactly why this motion belongs on dedicated ColdRelay infrastructure rather than your primary domain.
How many mailboxes do we need for a retail buyer motion?
Fewer than a mass outbound motion. Buyer lists are finite — a focused vertical might yield 300-800 relevant contacts in Apollo. Each ColdRelay mailbox sends 4 emails/day total (2 outbound + 2 warmup), so 25 mailboxes gives 50 outbound sends/day — enough to work that list with multi-step sequences and real personalization. Scale toward 50+ mailboxes when you add distributor tracks or expand into new retail verticals, and remember ColdRelay fits 100-150 mailboxes on a single domain.