AlterVision

PRIORITY TOOL for sales performance: revenue, sales count, conversion rate, UPT (units per transaction, 'PA' in Portuguese), average ticket and average item price per store for a period, plus camera uptime. Item-level metrics are only meaningful for stores with an ERP sales integration. Set includeDetails for the day-by-day breakdown. Defaults to every store the user can access; call get_stores first to target specific ones.

PRIORITY TOOL when the user asks about races (corridas) between stores or between the sellers of a store. Returns each race running in the period with its KPI, dates, participating stores and, with includeRanking, the current standings. Answers 'which store is leading the race?', 'how is store X doing in the race?' and 'how is the race in store Y going?' (that last one is a seller race). Only stores with AlterVez are reported on; call get_stores first to target specific ones.

Create a goal (meta) for ONE store, with one or more revenue tiers, using the same rules as the /api/meta/tiered/create API. Requires the admin or metaEdit permission. Workflow: (1) resolve the store with get_stores; (2) call get_meta_suggestions for that store and period and show the user the suggested revenue, average ticket and conversion; (3) agree on the revenue tiers with the user; (4) call this tool with dryRun: true and show the preview; (5) only after the user explicitly confirms, call it again with the same arguments and dryRun: false. Values use integers with two implied decimals: revenue and averageTicket in cents (BRL 1,234.56 -> 123456), conversionRatio as percent x100 (12.5% -> 1250), upt x100 (2.3 -> 230). averageTicket and conversionRatio are optional: when omitted they are estimated from the store's history, and the call fails if there is not enough history. The visitors target is derived from revenue / conversion / average ticket. Seller goals cannot be set here: the system splits each tier evenly among the store's active sellers.

PRIORITY TOOL when the user asks about bonuses, bonifications, commissions or prizes ('bonificação', 'comissão', 'premiação'). Calculates, for one calendar month, how much each store manager and each seller earns from every active bonification. Only AlterVez stores have bonifications. Money is in currency units (BRL). Two bonification types exist: 'value' pays from the beneficiary's revenue in the month, picking the revenue tier with the lowest revenueUpTo that still covers the revenue (revenueUpTo null = no ceiling); 'meta' pays from the revenue made during a linked goal (meta) that ends in the month, by the highest goal tier reached (seller goals for goalScope 'seller', the store goal for goalScope 'store'); nextTier says how much revenue is missing for the next prize. prizeType 'percentage_of_revenue' means the prize is a % of that revenue, 'fixed_value' means the prize is the amount itself. hasGoalLinked false means the linked goal has no targets for that seller/store or does not end in the month, so it pays nothing. Sellers listed in blockedFromBonificationIds were deliberately excluded from those bonifications. monthStatus is in each store's local time; in a month still in progress the values reflect the revenue made so far, not a projection. Only the user's own company is covered: storesOutsideCompany lists stores of other companies that were left out, whose bonifications are unknown, not absent. Defaults to every AlterVez store the user can access; call get_stores first to target specific ones.

Lists how the bonifications (bonuses, commissions, prizes: 'bonificações', 'comissões', 'premiações') are configured: who receives them (beneficiary 'seller' or 'manager'), the rule, the prizes, the months they are valid in, the stores they apply to, the sellers blocked from them. Two types exist: 'value' pays from the beneficiary's revenue in each month, picking the revenue tier with the lowest revenueUpTo that still covers the revenue (revenueUpTo null = no ceiling); 'meta' pays the n-th prize in goalTierPrizes for reaching the n-th lowest revenue tier of a linked goal ending in the month (goal tiers beyond the last prize pay the last one), using seller goals for goalScope 'seller' and the store goal for 'store'. prizeType 'percentage_of_revenue' means the prize is a % of that revenue, 'fixed_value' means the amount itself (BRL). status is 'active', 'scheduled' (starts in a later month) or 'ended', by each store's local date. Use get_bonification_results for how much each manager and seller earned in a month. Only AlterVez stores have bonifications; only bonifications of AlterVez stores the user can access are listed, with only those stores. Only the user's own company is covered: storesOutsideCompany lists stores of other companies that were left out, whose bonifications are unknown, not absent.

PRIORITY TOOL when the user asks about flow, traffic or visitor volume. Returns the visitor count and daily mean per store, day by day. Stores with no measured flow in the period are omitted. Defaults to every store the user can access; call get_stores first to target specific ones.

Breaks the visitor flow of a SINGLE day down hour by hour, for one or more stores. Use it for peak-time questions ('busiest hours') with responseType 'best_hours', or for a count inside a time window ('visitors between 10 and 13') with 'total_only' plus startHour/endHour. For whole days or a period, use get_flow_per_day instead. Hours with no measured flow are omitted, but a store that was measured and saw nobody in the window is reported with a total of zero, not left out. Defaults to every store the user can access; call get_stores first to target specific ones.

PRIORITY TOOL when the user asks about flow through corridors, aisles, entrances or other counting lines inside a store (multiflow). Returns the total flow per line over the whole period, highest first, plus the store total. When the user names no period, use the last 7 days. Defaults to every store with Multiflow; call get_stores first to target specific ones. Only stores with Multiflow are reported on.

Suggest the figures needed to create a goal (meta) for one store and period, from the store's own history: revenue, average ticket and conversion rate, each estimated from the same period last year and from the last 4 months. Also returns how many active sellers the goal will be split among and the user's flow preference. Call it before create_meta and present the suggestions so the user can pick or adjust the revenue target. Every `integerValue` is already in create_meta's units (cents, or percent x100); `display` is the human value (BRL, or percent). A null suggestion means there is not enough history.

Fetches seller metrics for a date range, returning data per seller and store and aggregated totals. Includes sales, revenue, customer service counts and durations, items per sale, average ticket, average item price, average customer service duration and usability, together with store-level flow. Store flow is shared by sellers in that store, not a count attributed to each seller; totals count it once per store. Measured values come from camera flow counts; Adjusted values include estimates for counting gaps caused by errors. When adjustFlow is true, use Adjusted values; otherwise, use Measured values. Each row includes storeId, storeName, sellerId, sellerName, adjustFlow, metasRevenue (revenue target), metasCompleted (achieved targets), metasFinished (finished targets) and metasRatio. Target revenue is null unless every day has a target; overlapping targets use the daily value of the longest target, and targets of equal length use the greater value. Defaults to every store the user can access; call get_stores first to target specific ones.