Connect with the business tools. Use https://mcp.ipaas.com/mcp/business?audience=business. The /business part gives you the four reports and the field map tools. The ?audience=business part makes results read in plain language. See Choosing Your Tools.

Give your key View permission for the data each report reads (see Getting Started):

The reports are read-only. None of the four can change your data. The field map tools are the only part of this guide that change anything, and they show a preview first.

Orders, revenue, average order value, units and discounts.

A split by the connected system the order came from.

A trend by day, week or month. The default is weekly.

Optionally, the mix of order statuses, top customers and top products. Ask for "details".

The period defaults to the last 30 days, using the date the order mapped on the to the iPaaS.com transaction. You can give a start and end date.

Details are capped. Top customers and top products read each order individually, for up to 100 orders (50 by default), starting with the most recent. The result tells you whether it is complete. The headline totals always cover the whole period.

Long periods can be incomplete. The platform can't filter transactions by date yet, so the report reads every page and filters here. Very old orders beyond the page limit aren't counted, and the result says so when that happens.

Currency. Transactions have no native currency field. Amounts are added up in whatever currency each order carries. If you sell in more than one currency, map a currency field (see "Field maps" below) before relying on the totals.

Out of stock and low stock. Low means sellable quantity at or below 5 by default. You can change that.

Negative quantities, which are a data fault.

Overstock, if you give it a level. It is skipped otherwise.

Sellable versus on-hand drift. It flags items where the sellable quantity differs from the on-hand quantity by more than 25% by default. This is the one that causes real incidents, because connected systems are usually sent the sellable quantity. When a store shows something greyed out that has stock on the shelf, look here.

Uneven spread: one location empty while another has plenty.

Stock value at cost (on-hand quantity times cost).

Which quantity a connected system receives depends on its inventory mapping. Ask the assistant to look at that system's mapping collections to confirm.

Discontinued products. If you've mapped a lifecycle field (see "Field maps"), discontinued products are left out of every alert list. They are still included in stock value, because the stock is still on your shelf.

Replenishment needs a field map. Only on-hand quantity, sellable quantity and cost exist natively. Committed stock, on-order stock, reorder points, lead times, vendors and last-counted dates aren't fields on the inventory record. If you keep them in custom fields, a field map switches on the matching checks.

The result says whether every product was read. A very large catalog can hit the page limit.

Orders that failed to reach where they were going, from the error queue and the transfer log, for order flows only.

Grouped by order, naming the system that rejected it and the likely cause: that system rejected it, the connector failed, or iPaaS.com failed to process it.

The number of attempts, when it was first seen, and when it will next be retried.

The queue retries on its own schedule, so an order listed here may fix itself if the cause was temporary. The report shows the next attempt.

An order that a mapping collection's filter excluded finishes "successfully" with nothing delivered. It only shows up in the destination-system check, never as an error.

For finance: outstanding balances on active cards, and expired cards that still hold a balance.

For marketing: dormant balances, meaning a card with a balance and no activity for 180 days by default, and cards expiring within 90 days by default. You can change both.

Totals issued, reloaded and redeemed, from each card's activity history.

Balances are what iPaaS.com holds now. If a sales channel redeems a card without syncing the redemption back, the liability here is overstated until it does (make sure to review any mappings involved to fully understand how this works).

Without a mapped currency field, all balances are added as one currency.

Where a card was spent lives on each activity, not on the card, so "where are cards redeemed" needs the activity records.

"How did we do over the last 30 days, split by week?"

"Show me last month's sales with top customers and top products."

"Is our stock healthy? Flag anything where sellable and on-hand disagree."

"Which orders are stuck, and which never reached NetSuite?"

"How much gift card liability do we have, and do the balances reconcile?"

"Suggest a field map from our custom fields."

The numbers don't match my accounting system. Expected. These are current-state views, and only live orders count as sales. Ask the assistant what the report included and left out.

The totals look too low. Check whether the result says some pages weren't read. Try a shorter period.

A value shows as unknown. A value you've mapped can be empty on a record, and the report says so instead of guessing. Check the field on the record in your system.

Revenue adds currencies together. You haven't mapped a currency field. Set up a field map.

You get a 401. Your key lacks a permission for the data the report reads. Ask the assistant to check your permissions.

The detailed version is slow. It reads each order separately. Lower the number of orders, or skip the details.