This is an analytics and follow-up center, not the Sell saved-cart picker. It does not contain a Resume, close, abandon, owner-change, or status-update action. Filters are in-memory against the loaded tenant data: sales dates use sale created_at, interactions use occurred_at, locations/registers/users use different source fields described below, and the Interaction Log renders only the first 80 matching rows even though its badge can be larger.
Step by step
- Go to Sales → Intelligence + Saved Sales and confirm the intended business. Wait for the sales data to finish loading. The page opens on Intelligence and also contains Saved Sales and Interaction Log tabs.
- Set Date range if needed. Quick choices include Today, Yesterday, This/Last week, This/Last month, This/Last quarter, This year, Last 30 days, and Last 90 days. Custom From/To dates are interpreted as full local calendar days. Sale filtering uses created_at, while interaction filtering uses occurred_at; a saved sale completed later can still fall under its original created date.
- Choose one or more Locations. Sales match either current location_id or origin_location_id. Interactions match their location_id. Changing locations clears any selected registers because the available register choices are rebuilt for the chosen locations.
- Choose one or more Registers. Sales match origin_register_id; interactions match metadata.register_id. A record missing those origin/metadata fields is excluded when a register filter is active.
- Choose one or more Users. Sales match cashier_id or origin_associate_id. Interactions match owner_id. This means a single user filter is not necessarily the same business role across the sales and interaction datasets.
- Use Interaction outcome only for interaction rows and interaction KPIs: Purchased, No purchase, Saved quote, Follow up, Lost, or Converted. The implementation compares the stored outcome, falling back to status, so labels that look related can remain distinct.
- Use Loss reason carefully. The choices combine saved-sale abandonment reasons with submitted interaction no-purchase reasons. On interactions it keeps only no-purchase rows with that exact normalized display reason. On saved opportunities it keeps only abandoned sales with that exact reason and excludes currently open saved sales. Clear all returns every filter to its initial state.
- In Intelligence, read Interactions, No-purchase Interactions, Saved/Future Interest, and Interaction Conversion. Conversion equals purchased interaction rows divided by all filtered interaction rows; it is not receipt conversion and does not include uncaptured store traffic.
- Review Source Intelligence and Associate Intelligence. Each lists up to eight buckets ranked by interaction count, then purchases. Bought/lost counts are derived from submitted interaction outcome/status. Uncaptured source and Unknown associate indicate incomplete attribution rather than a zero-performance channel or person.
- Review Loss Reasons. Selecting a reason applies it as the shared Loss reason filter. Then read Currently Saved, Revenue on Reserve, Saved Abandoned, and Opportunity Lost, which come from sale statuses and totals—not from submitted interaction cards.
- Open Saved Sales. Currently Saved is status parked; Abandoned is status parked_abandoned; Completed from Saved uses completed_from_parked; One-time Completes are completed sales without that flag. Save Rate is open + abandoned + completed-from-saved divided by all filtered sales. Saved conversion is completed-from-saved divided by those three saved-history groups.
- Treat revenue cards as opportunity analysis. Revenue on Reserve sums totals on currently parked sales, Opportunity Lost sums parked_abandoned totals, Recovered Revenue sums completed-from-saved totals, and One-time Revenue sums other completed totals. They are not cash, deposits, tender, tax, margin, or recognized-revenue reports.
- Review By Associate. Saved/open/abandoned/completed-from-saved credit prefers origin associate and falls back to cashier; one-time completed credit uses cashier. Unknown/unattributed sales are not added to an associate row.
- Review Abandonment Reasons. Reasons come from signature metadata saved_sale_abandonment.reason, then void_reason, otherwise Unspecified. Counts and totals represent abandoned saved sales only.
- In Open & Abandoned Saved Sales, read sale number/date, origin associate/location, abandonment reason, total, age, and Saved/Abandoned badge. Age is calculated from sale created_at, not necessarily parked_at. Choose Follow up only when a customer is attached; it opens the customer profile. The external-link button opens the sale in Sales → Receipts. Neither action resumes the cart from this report.
- To actually continue an open saved sale, use the approved Register → Sell saved-sales picker/workflow with the intended location/register and an open register session. Check cart conflicts and editing ownership there. Do not infer that opening the receipt here claims or restores the Sell workspace.
- Open Interaction Log to review submitted cards. The badge reports all filtered matching interaction rows, while the list displays only the first 80. Each row shows receipt/customer, interaction type, outcome/status, customer/source/loss context, associate, location, occurred date, and whether it is submitted/openable.
- Owners and Super Admins can choose Open card and edit the submitted interaction through the dialog; other roles see Submitted and the row is noninteractive. After an authorized save, the page refetches interaction activity. Editing the card can change intelligence results, so document corrections and verify the updated filters/KPIs.
- Use this page for coaching and opportunity follow-up, then confirm operational truth in the customer, receipt, saved Sell workspace, and appropriate financial reports before acting. If a count looks wrong, capture the active filters, tab, date/time zone, record identifiers, stored statuses/outcomes, and origin fields rather than repeatedly changing the sale.
Screen and contract reference
| Control or area | What it means |
|---|---|
| Intelligence tab | Combines submitted-interaction KPIs/buckets with saved-sale opportunity overlays. |
| Saved Sales tab | Sale-status conversion, revenue-opportunity, associate, abandonment, and open/abandoned opportunity analysis. |
| Interaction Log tab | Filtered submitted interaction rows; badge can exceed the 80 rows rendered. |
| Date range | Filters sales by created_at and interactions by occurred_at using full local days. |
| Locations | Sales use location_id/origin_location_id; interactions use location_id. |
| Registers | Sales use origin_register_id; interactions use metadata.register_id. |
| Users | Sales use cashier_id/origin_associate_id; interactions use owner_id. |
| Interaction outcome | Filters only interaction data using outcome with status fallback. |
| Loss reason | Shared exact-label filter; for saved sales it retains matching abandoned records and excludes open parked records. |
| Clear all | Clears date, location, register, user, interaction outcome, and loss-reason filters. |
| Interaction Conversion | Purchased submitted interactions divided by all filtered submitted interactions. |
| Source / Associate Intelligence | Top eight interaction buckets ranked by volume, showing bought and lost counts. |
| Currently Saved | Count of filtered sales with status parked. |
| Saved Abandoned | Count of filtered sales with status parked_abandoned. |
| Save Rate | Open + abandoned + completed-from-saved count divided by all filtered sales. |
| Saved conversion rate | Completed-from-saved divided by open + abandoned + completed-from-saved. |
| Revenue on Reserve / Opportunity Lost | Sum of sale totals for parked / parked_abandoned statuses; not collected or recognized revenue. |
| Abandoned → Completed | Completed-from-saved sales whose completed/created date is more than 30 days after parked_at. |
| Follow up | Opens attached customer profile; appears only when customer_id exists. |
| Receipt external link | Opens the saved/abandoned sale in Sales → Receipts; does not resume it. |
| Open card | Owner/Super Admin action to inspect/edit a submitted interaction. |
| 80-row display limit | Interaction query can load up to 5,000, but the visible Interaction Log slices matching rows to 80. |
| No exact screenshot | The real Amelia Grant Harbor & Hearth /sales/parked-report capture was rejected because the route redirected to the intelligence view and remained loading. No mismatched or fabricated screenshot is used. |
Expected result
The saved sale remains distinct from completed receipt history and shows the intended owner, reason, status, value, follow-up activity, and resume behavior.
Troubleshooting
- Keep the current receipt or order filters in place while opening details.
- Check the record status and activity before repeating a send, return, or fulfillment action.
- Use a safe receipt or order reference when contacting support.
CentriPOS API explorer · API Center administration