See the whole estate, down to one order.
Read merchant performance and institution wide commerce from the records already inside the deployment, with a visible path back to every contributing record.
Commerce in context
A payment total cannot describe a business.
Orders add the product, customer, location, channel, staff member, and fulfilment state behind the amount. That context is what turns reporting into something a merchant or institution can act on.
Product mixSee what created the movement.
Customer patternSeparate repeat trade from first visits.
Channel healthCompare counter, website, and payment links.
Fastest movementCollection ordersOpened from 146 contributing records
Reporting workflow
Start wide. Open the evidence.
Business view
Understand the merchant week.
Revenue, orders, customers, products, and channels appear together because the engine recorded those relationships when trade happened.
Location view
See where movement began.
Compare locations without separating counter and online activity into different reporting products.
Institution view
Read the network at each level.
Move from the institution total into region, category, merchant, location, and order while staying inside one deployment.
Record view
A total is never the end of the trail.
Open the products, customers, channels, and provider references that contributed to a result before choosing what to do next.
Useful questions
Reporting shaped around decisions.
What changed?
Compare periods, channels, products, customers, and locations without rebuilding the report.
What contributed?
Separate broad movement from a single large order, a location event, or missing provider data.
Who needs attention?
Produce an evidence backed list for merchant support or an institution review process.
Two altitudes
A merchant sees a business. An institution sees its network.
Both views read the same deployment records through different permissions. There is no pooled dataset and no cross institution benchmark behind either one.
Review the data boundaryEvidence before action
Signal, not decision.
No risk score
Box surfaces commerce history. It does not approve credit, set pricing, or make a regulated decision.
No invented settlement
Provider data that has not reached the engine remains missing rather than being filled with a forecast.
No shared training set
Merchant records stay inside the institution deployment and are not pooled across operators.
Insights questions.
Does Insights require a separate warehouse?
No. It reads the commerce records already held by the institution deployment.
Can an institution see every merchant?
Institution roles can receive an estate view. Merchant roles remain restricted to their own business.
Does Box benchmark institutions against each other?
No. There is no cross institution dataset or pooled merchant benchmark.
Can a finding start an action?
Yes. An operator can pass an appropriate result into a Connect flow or an institution review.