Multiple Carts arrives the week of September 8, 2026, on by default for every account.
Expect questions, and expect some excitement, so make sure your customers hear it from you first. We already drafted a landing page announcement to get you started. The rest of this article covers what is different, where it helps, and four ways to get the word out, starting with that page.
Already looking at the draft? Skip to Best practices for letting users know.
What's different
Until now | Starting the week of September 8 |
One cart per account | As many carts as the account needs, up to 50 |
Everyone ordering under the account built into the same cart | Each person can keep their own cart, private or public |
One delivery date and fulfillment setting at a time | Every cart carries its own name, fulfillment setting, and delivery date |
One order out the door at a time | Carts submit independently, in any order |
Note: Order minimums and promotion thresholds are evaluated per cart. Two carts for the same delivery date do not combine, so items that need to clear a spend threshold have to stay in one cart. Worth including in whatever you send, and worth telling your reps directly.
Where Multiple Carts helps your customers
Use these to spot the accounts worth targeting and to find your angle, with a ready-made line for each type of account that you can use as is.
Operations where more than one person orders. Hotels, clubs, and restaurants where the kitchen, the bar, and banquet each have their own buyer. Previously their items landed in one shared cart and someone sorted it out before cutoff. "The bar's order and the kitchen's order no longer have to be the same order."
Multi-department accounts. Campus dining, hospitals, and senior living, where separate departments buy against separate budgets under one account number. "Every department gets its own cart, under the account you already have."
Convenience store groups. A manager covering several stores, or several categories, who has been running all of it through one cart. "Keep a cart per store and submit each one on its own schedule."
Buyers running a prebook alongside a standing order. A cart per delivery date means next month's prebook stops competing with this week's order. "Start next month's prebook without touching this week's order."
A buyer who wants to build quietly. A private cart lets someone put an order together over a few days, then make it public or submit it when they are ready. "Build your order on your own time, then share it when it's ready."
Accounts that asked you for this. Multiple Carts has been a top request for a long time, and the customers who asked for it should hear it from you rather than from a notification.
Getting the word out
Pick what fits how you already talk to your accounts. The first one takes about five minutes.
Publishing the landing page draft we built for you
Start here. A landing page takes over the customer's screen when they open the app, before they start building an order, which makes it the only channel that reaches a buyer at the exact moment the change matters to them.
The draft is written and laid out already in Landing Pages, which sits under the More menu in Storefront, and in the Sales Rep Portal.
Open the draft titled New updates to app checkout in your Landing Pages list.
Read it through and put it in your own voice. Swap the headline for one of the lines above, trim anything that does not apply to your accounts, and change the button if you would rather send customers somewhere else.
Set the audience. Every account is a reasonable default, since every account is getting the feature.
Publish by hitting Schedule.
Publish before the week of September 8 so customers meet the new cart already knowing what it is. Nothing reaches your customers until you publish, and nothing happens to the draft if you leave it alone.
Tip: Consider publishing a second page aimed at the accounts from the list above. The narrower the audience, the sharper the message can be.
New to Landing Pages? The Landing Pages help article covers building one from scratch.
Sending a broadcast message
A landing page shows up once. A broadcast message sits in the notification feed, which makes it the better channel for something a buyer may want to reread later.
Two sentences and the link to the Help Center article is enough:
"Starting the week of September 8, you can keep more than one order open at a time. Each cart gets its own name and delivery date, so a standing order and a special event no longer have to share one cart. Here's how it works."
Send it a few days ahead rather than the morning of. A buyer who read it Tuesday and sees the tabs on Monday connects the two.
Not sure where broadcast messages live? Broadcasting and Marketing through In-App Messages covers sending one, and the Pepper Guide to Customer Marketing covers building the segment to send it to.
Having your reps bring it up
Get your reps up to speed before customers start asking. Here are a few key points worth covering:
What it looks like. Cart tabs at the top of the cart. Anyone can add one.
Who it helps. The accounts from the list above, and any account the rep already knows juggles orders for more than one person.
The minimums answer. Minimums and promotions apply per cart. A customer who used to clear a minimum in one cart and splits those items across two will fall short in both.
That nothing is required. A customer who wants one cart keeps using their default cart and barely notices.
Telling your own team first
Whoever answers your phone gets the first question, and inside sales, customer service, and AR usually find out about app changes from an annoyed customer.
Forward them the Multiple Carts help article and the minimums note a week ahead. Two sentences in an internal email prevents the call where nobody knows what the customer is describing.
Whatever channel you pick
Three things to get across:
More than one cart per account, starting the week of September 8.
Each cart carries its own name, delivery date, and fulfillment setting, and carts submit separately.
Nothing to do if they like things the way they are. Their default cart works exactly as it does today.
The Multiple Carts help article covers the rest, including private carts and how minimums apply, so link to it and let it carry the detail.
Frequently asked questions
Do I have to do any of this? No. The rollout happens either way, and customers who never add a second cart see almost no difference. The sections above reduce inbound questions and help the accounts who wanted this find out sooner.
Can I opt out, or delay it? Yes. You may opt-out here and contact your Pepper rep if you would like to enable Multiple Carts at a later time.
What happens to orders my customers have in progress? Nothing. Whatever is in a customer's cart becomes their default cart, and the order submits the way it always has.
Will this change how order minimums work? Minimums are checked per cart, which is a change in effect for any customer who splits an order across carts. A customer who used to reach a minimum in one cart and spreads those items across two will fall short in both.
Where do I find the landing page draft? In your admin portal under Landing Pages, with Draft status. If you do not see it, contact your Pepper representative.
Can my customers see each other's carts? Carts are scoped to the account. Public carts are visible to everyone ordering under that account, private carts only to the person who created them until they publish or submit. Nobody outside the account sees any of it.