Claude Commerce Layer Metrics connectorWhat Claude can do in your Commerce Layer Metrics account.

Aggregates your orders by one field and computes a metric on another, using the operator you choose. Commerce Layer describes breakdowns as aggregations computed on field values, here on order records.

Spreads order data over a time interval and applies an operator per date, so Claude can show how a value evolves day by day or month by month.

Returns actual order records matching your filters, with the fields you ask for, sorted and paginated, rather than an aggregate.

Computes a single figure over one field of your orders, with the operator you pick. Commerce Layer calls stats numeric computations over values pulled from one field, here a field of your orders.

Groups carts by one attribute and measures another. It is the breakdown aggregation of the Metrics API, applied to cart records instead of orders.

Lays cart data out along dates and applies an operator to each day or period, so trends in basket creation become visible.

Lists real cart records that match your criteria, with chosen fields, ordering and pagination, so you look at individual baskets rather than totals.

Produces one number on a cart field, according to the operator selected. The result is a numeric computation over values extracted from that single cart field.

Summarises returns by one field and calculates a metric on another, a quick way to see which segment generates the most returned value. The answer comes back as metrics or statistics computed on the values of return records.

Places return data on a timeline and applies the chosen operator per date, so seasonal peaks in returns stand out. For each date, the operator runs over a selected field of the returns present on that date.

Pulls the individual return records that fit your filters, with the fields you need, sorted and split into pages.

Calculates a single statistic across a return field, using the operator you set. The computation runs over values extracted from one field of your return records.

Runs the Metrics API analysis that, across your entire order history, finds the items most often added to the same orders as a given SKU, bundle or set of items.

Gives the top N best-selling products for each market of your organisation in one pass, without you building the grouping. The ranking is computed separately for each market of the organisation.

Counts the customers who purchased a specific product or bundle, a fast measure of reach for one item.

Lists the products most frequently purchased alongside other ones, a ready view of natural pairings in your catalogue. The answer is a ranking of products drawn from what your customers actually bought together.

Fetches the most recently created carts that contain a given SKU, limited to one market of your choice. Both filters apply at once, the SKU and the market you name, newest carts first.

Brings back the orders most recently archived, handy to check what was set aside and when. The list starts from the order archived most recently.

Finds the last placed orders whose details contain specific email domains, which isolates purchases from given companies or partners. The match is made on the email domains found in the aggregated order details.

Provides mixed statistics on how many SKUs each order contains, grouped by country, so basket size can be compared across borders. The figures are mixed statistics on the number of SKUs per order, one set per country.

Counts the orders that triggered a specific promotion, a direct read of how far a discount actually went. You name the promotion, and the answer is a single total of orders.

Totals the orders that include a bundle, grouped by bundle name, so you see which packs customers really choose. Each bundle name gets its own line with its own order total.

Tallies your organisation's orders split by currency, a quick picture of where the money comes in. Each currency your organisation sells in gets its own order total.

Counts orders grouped by day, the simplest daily curve of activity for the whole organisation. Each day gets its own total of orders across the whole organisation.

Totals orders grouped by customers who bought from you more than once, a view of how much loyal buyers weigh. Only customers with more than one purchase enter this grouping.

Checks the errors attached to your orders, if any, grouped by error code and message, so recurring failures surface quickly. Commerce Layer's own description adds an "if any": the answer can come back empty.

Breaks orders down by shipment status and by shipping method name, so you see where parcels stand for each carrier option.

Sets order status against the related payment status and totals orders, which brings mismatches between the two into view. The grouping crosses two fields at once, order status and payment status.

Tells you how many orders were settled with a gift card, which measures how much that payment method is used. The answer is one total, the orders where a gift card served as payment.

Totals your refunds grouped by country and by currency, so refund pressure can be compared market by market. The totals cross two dimensions, the country and the currency of each refund.

Counts the returns requested on your orders, grouped by year and by destination city, a geographic view of returns over time.

Measures the average time your shipments remain in picking status before they are packed, a direct gauge of warehouse speed. The measure stops at the moment a shipment is packed.

Identifies your top-spending customers and shows how each one's total purchases divide across currencies. The list keeps only your top spenders, each total broken down by currency.