Overview
A Square catalog revenue gap auditor helps you find the items that look fine in the catalog but behave strangely in the business. This playbook compares Square catalog items with recent orders, payments, and refunds to spot weak sales, refund risk, stale setup, and merchandising gaps.
It is built for operators and marketers who need a product-level action list, not a vague sales recap. Juno turns the catalog into a practical tracker that shows which items to promote, clean up, investigate, or retire.
Why you should connect catalog setup to sales behavior
Catalog quality matters because item names, categories, variations, and prices shape how products are sold, reported, and merchandised. Square's Catalog API describes how catalog objects represent items, variations, categories, discounts, taxes, and related selling details in Square catalog data.
The hidden problem is that catalog issues rarely announce themselves. A stale category can muddy reporting, a duplicated item can split performance, and a refund-heavy product can keep looking popular until someone compares sales against returns.
This playbook gives Juno a focused way to connect item setup with transaction reality and produce a prioritized merchandising action tracker.
Step-by-step
- 1Confirm the Square catalog or location scope, the recent sales window, and whether the user wants all items or a focused product group reviewed.
- 2Compare catalog items with recent Square orders, payments, and refunds to build an item-level view of sales, order volume, refund signals, prices, and categories.
- 3Flag items with weak sales, revenue decline, refund risk, stale or missing metadata, duplicated setup, odd pricing, or unclear category placement.
- 4Separate real issues from acceptable low-volume cases, such as seasonal, specialty, bundled, or newly launched items.
- 5Rank the gaps by commercial impact, customer experience risk, ease of correction, and merchandising upside.
- 6Create a tracker with item-level evidence, recommended action, priority, and review notes so the user can work through fixes without losing context.
Frequently asked questions
Is this the same as a product performance report?
Not quite. A product performance report explains what sold. This audit focuses on the gap between Square catalog setup and sales behavior, then recommends item-level fixes.
What if catalog metadata is incomplete?
Juno should treat missing or unclear metadata as part of the audit. The report can still use item names, prices, categories, sales, and refunds where available.
Should every low-selling item be removed?
No. Low sales can be intentional for seasonal, specialty, new, or bundled items. The playbook prioritizes items where the evidence suggests a real revenue, refund, setup, or merchandising problem.
What does the final output look like?
You get an item-level tracker and a concise summary of the biggest risks, easiest fixes, and product opportunities to review next.
