Put your newest items, your best pricing, and your most important notices directly in front of the customers who need to see them. Landing Pages give you the first screen a customer sees when they open the app, before they start building an order.
Before You Begin
You will need:
Admin or DSM access to the Sales Rep Portal
Landing Pages enabled for your organization. If you don't see a Landing Pages tab, contact your Pepper rep to have the feature turned on.
How Landing Pages Work
A landing page displays as a full takeover when a targeted customer opens the app or website. The customer reads it, optionally taps your call to action, and dismisses it to continue into the app.
Three behaviors shape how you plan a landing page:
Each customer sees a landing page once. After a customer views or dismisses it, the page never appears for that customer again, even while the date range is still active.
Overlapping pages stack into a carousel. If more than one landing page is live for the same customer, they see all of them in sequence.
Dismissing removes it permanently. A customer cannot reopen a landing page to check a detail later.
How often it appears Each customer sees a landing page once. After they view or dismiss it, that page never appears for them again, even while the date range is still open.
That last point drives the most important planning decision. Landing pages guarantee a read, and they leave no record behind. For a message a customer may need to reference again, such as a cutoff date or a new ordering deadline, send a broadcast message alongside the landing page so the details stay available in their chat.
Landing Pages vs Broadcast Messages
Both tools reach your customers inside the app, and each one suits a different job.
| Landing Page | Broadcast Message |
Where it appears | Full takeover on app open | Customer's in-app chat |
How often | Once per person | Stays in chat |
Can they refer back? | No | Yes |
Best for | Recalls, price changes, holiday cutoffs | Routine updates, seasonal notes, campaigns |
Reserve landing pages for messages where a missed read costs somebody money or creates a safety issue. Frequent takeovers train customers to dismiss on sight, which spends the attention you want available when a recall goes out.
Creating a Landing Page
Open the Landing Pages tab and click Create new.
In the Recipients section, choose your Supplier first. The rest of the form stays locked until you do, because targeting depends on it.
Choose who receives the page. Select All restaurant groups to reach everyone, or pick specific restaurant groups. You can select up to 100 groups.
Write your content: Headline — the first thing your customer reads. Up to 100 characters. Body — the message itself. Up to 1,000 characters. Image (optional) — PNG, JPG, or WebP, up to 5 MB. 1200 x 750 works best.
Add a call to action (optional). See the section below.
Set your Display dates in the Display window section.
Click Save draft to keep working on it, or Schedule to make it live.
Adding a Call to Action
The call to action is two fields, and the button appears only when you fill both:
CTA label — the button text, up to 36 characters.
CTA URL — where the button goes. Must begin with http:// or https://.
Entering a URL without a label returns a validation error rather than an unlabeled button.
Tapping the button opens your link in a web view inside the app, so your customer stays in Pepper and returns to their order guide when they close it.
Items and promotions do not have their own URLs, so a call to action points to a destination such as a page on your website, an order form, or a PDF price sheet.
Who Sees the Landing Page
Landing pages display to everyone in the customer groups you target, across all user roles — distributor admins and reps included. That means you can check your own work: open the Restaurant App on a targeted account and the page will take over on launch. Note that each user sees a landing page only once per account, so preview it on an account you're not planning to demo.
Managing Your Landing Pages
The main view lists every landing page with its current status:
Draft — saved but not scheduled, invisible to customers
Scheduled — set to begin on a future date
Live — currently displaying
Ended — past its display window
Each row offers four actions:
Edit — change the content or dates
Duplicate — copy an existing page as a starting point, useful for recurring notices like holiday schedules
Stop — end a live page early
Delete — remove it entirely
Best Practices
Write for one read. Your customer sees this once. Put the essential fact in the title.
Keep the body short. Customers open the app standing in a walk-in with one hand on a phone.
Pair critical details with a broadcast. Dates, deadlines, and part numbers need somewhere to live after the page is dismissed.
Target deliberately. A regional delivery change that reaches every account reads as noise.
Watch for overlap. Two live landing pages for the same group become a carousel, so schedule around each other unless you intend the sequence.
Set a realistic date range. The window controls who becomes eligible, since customers who don't open the app during it never see the page at all.