Using Coil
Reports, Mileage, and Audits
Use Coil's calculations, record trips, and inspect the effects of agent changes.
Location Payout Report
Revenue excludes sales tax before commissions are calculated. Net-share payouts use revenue minus COGS and card fees, plus the recorded platform-fee deduction when opted in. Gross shares ignore platform fees. Other location expenses do not reduce the commission basis.
Sales waiting for inventory appear in detail with Cost pending. Missing costs can change payouts when stock is matched. Negative payouts remain informational only. Reports create no payments or receipts.
API/MCP clients use get_location_payout_report with reports:read, inclusive local dateFrom/dateTo, and optional locationId, page, and limit. Responses echo the resolved period and time zone.
- Open Reports and choose Location Payout. Overview, Sales, and Purchase Tax are separate report tabs; the shared date control applies to the selected report.
- Review Location, Sold, Revenue, COGS, Card Fees, Net Profit, and Payout Owed in the topline CSV. Net Profit is revenue less COGS and card fees. Select a location or click its name to see one item-summary row per product, followed by every sale in that period, paged by date.
- Choose Download payout CSV, then select topline summary, item summary, or full sales detail. Sales exports require a selected location and include the whole period, not just the visible page. The payout view and CSV omit net profit and sales-tax liabilities.
Review Calculated Results
Dashboard and Reports calculate revenue, COGS, fees, net profit, taxes, and location payouts from workspace data. Check dates, inventory events, and settings before relying on the result or exporting it. Reading a report does not settle a payment or remit taxes.
Sales Tax to Remit includes tax charged separately and tax backed out of tax-included prices; the summary CSV lists both. Sales still waiting for stock count toward revenue, tax, fees, and payouts with no cost until matched, and the dashboard shows how many units are waiting.
Personal-use removals contribute their additional tax to Use Tax Owed for the consumption period and use_tax_owed in period exports. Tax-paid removals record zero additional tax and do not count as sales. Removal events snapshot the cost, purchase-tax evidence, rate, basis, and amount; later cost edits do not silently recalculate an already recorded liability.
Agent Reporting
get_inventory_summary returns aggregated stock/valuation. get_dashboard, get_history, and export_period_summary use inclusive calendar dateFrom/dateTo values in the workspace time zone, spanning at most 366 days. Each response echoes resolved UTC period boundaries (end exclusive) and the time zone; CSV includes period_start, period_end, and period_time_zone. DST is respected. Sales, receipts, mileage, and location expenses use the same boundary rules. CSV responses are capped at 256 KB; narrow an oversized request. Agents should use these calculations rather than recreate accounting logic from partial unit lists.
Net-profit-share payouts preserve losses across the selected period. A losing period shows a negative payout with a Losing period label. This is informational only: nothing is charged to the location, no negative payout receipt is created, and no loss is carried forward.
Record Mileage
Record the actual ordered start, stops, end, date, miles, and applicable mileage rate. The rate is snapshotted on each trip. Supply the correct rate explicitly for historical dates rather than assuming today's default. Agent route calculation uses Coil's configured Google Maps service and may incur provider charges.
Inspect Agent Changes
Settings shows recent request activity. list_automation_audit and get_automation_audit expose redacted before/after changes to keys with audit:read; larger unit snapshots are paged.
New management mutations commit their audit changes in the same MongoDB transaction. Existing receipt/Blob workflows append snapshots after successful actions and are not a transaction across services. A failed or pending request may need reconciliation; do not generate a new request ID to force it through.