These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Meal Prep / Subscription Box
- Features
- Carts and traffic
Carts and traffic
Trace storefront visits and active carts through checkout and abandoned-cart follow-up.
OverviewAbandoned cart follow-up×
Meal Prep / Subscription Box · Carts and traffic
New
Abandoned cart follow-up
Abandoned carts
| Abandoned at | Recovery stage | Recovery emails sent | Subtotal | ||
|---|---|---|---|---|---|
| rt@example.com | 15 Oct | Stage1_1hr | 250 | 250 | |
| sb@example.com | 12 Oct | Stage2_24hr | 210 | 680 | |
| xx@example.com | 13 Oct | Stage3_72hr | 50 | 280 | |
| yu@example.com | 14 Oct | Stage1_1hr | 610 | 820 | |
| xd@example.com | 03 Oct | Stage2_24hr | 840 | 580 |
6 of 6 records
rt@example.comAbandoned carts · AC-78166
Stage1_1hrAbandoned at15 Oct
Recovery emails sent250
Subtotal250
What you can do
Follow the path to checkout
A storefront visit is useful only when the team can connect it to customer activity. Store Sessions records the visit source, campaign, device and whether it converted. A cart links its catalog and, when known, the subscriber and session. Cart Items hold the chosen variants, quantities and unit prices. Customer Service Rep can inspect a cart when a buyer asks why an item or total changed before checkout.
For a meal merchant promoting a new lunch choice by email, Marketing Manager can compare sessions from that campaign with carts and eventual orders. The session record offers a source and conversion flag. The cart shows whether checkout started, while the order record confirms whether a purchase exists. This is a practical way to distinguish browsing interest from placed orders without treating every visit as a sale.
How the work is organized
- Arrival. store sessions gives Marketing Manager a source and campaign context for each visit.
- Basket. Carts and cart items preserve the market, variant choices, quantities and activity time.
- Follow-up. abandoned carts records a cart left behind and its recovery stage; emails sent holds related communication evidence.
What to agree during setup
The team chooses its campaign naming and how the storefront passes session identities into the app. A consistent session ID lets staff join later cart activity to the correct visit. Catalog Manager checks that cart variants still belong to the intended catalog. Customer Service Rep sets a practice for examining cart state before answering a buyer: a cart in checkout is different from one already converted to an order.
Marketing Manager and Merchant Owner agree which abandoned-cart messages are appropriate for their customer relationship and which communication provider will deliver them. The recovery record and email evidence help staff trace follow-up. They should also decide when a recovered cart is considered complete: the recovered meal order link provides a concrete result, while a changed recovery stage alone does not show what was purchased.
Check the handoff on an actual case
A visitor arrives from a paid campaign, chooses two meal variants and starts checkout. Store Sessions identifies the source and the cart records both lines. If the buyer leaves, Marketing Manager examines the abandoned cart, its subtotal and recovery stage. If the buyer returns and places an order, Customer Service Rep checks the new order and the cart’s converted state. The linked records should tell one story: original visit, selected variants, last cart activity and final order.
Now try a customer who opens a second cart under the same email. Staff should use the cart token and linked order rather than guessing from the address. This keeps separate attempts distinct when answering a support request or measuring campaign outcomes.
What your team sees
- Active carts — Baskets still active or at checkout, with last activity and subscriber context.
- Abandoned cart follow-up — Carts at a recovery stage that may need staff attention.
Follow the work through
See order intake for the move from cart to order, and customer resolution for questions after purchase.
What it keeps track of
Data model- Store sessions
- Captures one visit to the storefront, tracking where it came from, used to analyze traffic and conversions.
- Carts
- Represents an in-progress shopping cart, used to hold items a customer hasn't checked out yet.
- Cart items
- Represents one product added to a shopping cart, used to see what a customer intends to buy.
- Abandoned carts
- Tracks a cart left without checkout, used to follow up and recover the lost sale.
- Emails sent
- Logs one email sent to a subscriber, used to track opens, clicks, and marketing performance.
- Subscribers
- Represents a customer who shops or subscribes, holding their contact info and order history.
- Meal orders
- Represents one customer order for meal boxes, used to track payment, fulfillment, and status.
Who uses it
Permissions- Marketing Manager
- Reviews acquisition and follow-up.
- Customer Service Rep
- Checks cart and order links during customer conversations.
- Catalog Manager
- Resolves incorrect variant listings.
- Merchant Owner
- Sets the operating rules for customer contact.
Set up Meal Prep / Subscription Box your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.