Profit and POAS All plans

Revenue and ROAS tell you how much an order or a campaign sold. Profit tracking tells you how much it earned. AxiTrace calculates the profit of every order from your product costs and cost rules, and POAS (Profit on Ad Spend), the profit counterpart of ROAS.

What profit and POAS mean

  • Profit is the contribution margin of an order: revenue without VAT, minus the cost of goods, the shipping cost, the payment fee and a handling cost per order. Company fixed costs such as rent or salaries are not part of it.
  • POAS is profit divided by ad spend. A POAS of 1.0 means the orders paid back exactly what the ads cost: that is the break-even point. Above 1.0 you earn money after ad costs, below it you lose money.
  • POAS needs ad spend, so it exists only where AxiTrace knows the spend: Meta, Google Ads and TikTok. For other sources (organic search, email, referrals, other ad platforms) AxiTrace reports profit but no POAS.
  • ROAS is not affected by any of this. It keeps dividing revenue by ad spend, exactly as before.

Turn on profit tracking

Profit tracking is off by default for every workspace. A workspace that never switches it on sees no change anywhere. To switch it on:

  1. Open Workspace settings → Profit & POAS and find the Profit tracking card.
  2. Enter the Default VAT rate (%). It is used when an order arrives without its tax amount. 0 is allowed, for example for a store that does not charge VAT.
  3. Click Turn on profit tracking. Your orders of the last 90 days are calculated in the background (see the 90-day backfill).
  4. Fill in the Cost defaults: the default margin, the default shipping cost, the handling cost per order and the payment fee, then add your product costs (see the cost catalog or the setup for your platform).

Anyone who can edit the workspace can switch profit tracking on or off and change its settings. Turning it off removes Profit and POAS from your reports, but keeps your costs, rules and settings for when you switch it back on.

How profit is calculated

For every order:

  1. Revenue is the order revenue AxiTrace already stores: after discounts, including tax and the shipping the buyer paid.
  2. Tax is the tax amount sent with the order. Without it, when prices include tax, AxiTrace takes it out with your default VAT rate: revenue minus revenue divided by (1 + VAT rate). When the order says prices do not include tax and no tax was sent, tax is 0.
  3. Revenue without tax = revenue minus tax.
  4. Cost of goods is the sum over the order lines of quantity times unit cost. How the unit cost is found is described in cost sources.
  5. Profit = revenue without tax - cost of goods - shipping cost - payment fee - handling cost.

The shipping the buyer paid is revenue; what you pay the carrier is the shipping cost, subtracted separately. An order-level discount is spread over the lines in proportion to their price, so every line carries its share of it.

Worked example

An order of 123.00 EUR, prices including 23% VAT and no tax amount sent. The buyer paid 12.30 EUR for shipping. Two units of one product whose cost in your catalog is 25.00 EUR. A shipping rule sets 6.00 EUR, the payment fee is 2% plus 0.54 EUR, and the handling cost is 2.00 EUR per order.

Step Calculation EUR
RevenueAs sent with the order123.00
Tax123.00 - 123.00 / 1.23-23.00
Revenue without tax123.00 - 23.00100.00
Cost of goods2 x 25.00-50.00
Shipping costShipping rule-6.00
Payment fee2% of 123.00 + 0.54-3.00
Handling costPer order-2.00
Profit100.00 - 50.00 - 6.00 - 3.00 - 2.0039.00

If this order were the only one from a Meta campaign that spent 15.00 EUR, its ROAS would be 123.00 / 15.00 = 8.2 and its POAS 39.00 / 15.00 = 2.6.

Cost components and switches

Under What is subtracted from revenue on the Profit tracking card you choose which costs count. Revenue without VAT is always the starting point; a component you untick counts as 0.

Component Where the amount comes from, first match wins
Cost of goods Per line: see cost sources.
Shipping cost 1. A shipping cost sent with the order. 2. The first shipping rule that matches. 3. The Default shipping cost.
Payment fees 1. A payment fee sent with the order. 2. The payment fee rule of the order's payment method. 3. Payment fee (%) of the revenue plus Payment fee, fixed amount. An order with no revenue gets no rule or default fee.
Handling cost per order 1. A handling cost sent with the order. 2. The Handling cost per order.

A cost sent with the order always beats a rule or a default. The default shipping cost, the handling cost and the fixed payment fee share one Cost currency. Every amount in another currency than the order is converted at the exchange rate of the order date, using the rates AxiTrace has stored.

Cost sources and resolution order

The unit cost of each order line is the first of these that exists:

  1. Sent with the order: a unitCost sent server-side with your secret key (see per-platform setup).
  2. Catalog: the product in your cost catalog with the same external id (for example shopify:44012345678), using the cost that was valid when the order was placed.
  3. Catalog (SKU): the catalog product with the same SKU, using the cost valid at order time.
  4. Estimated: later cost: when the product is in the catalog but its first cost was entered after the order, that first cost is used and the line is estimated.
  5. Estimated: default margin: the line's revenue without tax times (100% minus the Default margin (%)). With a 40% default margin, a line with 90.00 of revenue without tax costs 54.00.
  6. Missing: no cost and no default margin. The order gets no profit at all (see below).

A line with neither an external id nor a SKU goes straight to the default margin. When two catalog products share a SKU, the one added last is used. A catalog cost in another currency is converted at the rate of the order date; if AxiTrace has no stored rate for that currency pair and date, the line counts as missing.

Estimated orders and cost coverage

Every order's profit carries a quality:

  • Actual: every line's cost was sent with the order or found in the catalog at order time.
  • Partial: some lines are actual, others estimated.
  • Estimated: no line is actual, or the order was calculated by the 90-day backfill.
  • Missing: at least one line has no cost and there is no default margin. The order has no profit and is left out of profit and POAS. The Profit page shows how many orders and how much revenue were left out. Set a default margin, or add the missing costs, to include them.

Cost coverage is the share of revenue without tax whose cost of goods is actual (sent with the order or found in the catalog at order time). The rest is estimated. A POAS with a low coverage is only as good as your default margin, so check coverage before you act on it. The Products without a cost list on the Profit page shows which products to add first.

Shipping and payment fee rules

Open the Profit page and choose Shipping and fee rules, or click the link on the Profit tracking card.

  • Shipping cost rules set the shipping cost by destination country and order value. The first rule from the top whose country (or "Any") and order value range match the order is used. The minimum order value is included, the maximum is not, and an empty bound has no limit. Use Move up and Move down to change the order of the rules. Without a matching rule, the default shipping cost applies.
  • Payment fee rules replace the default fee (percent of revenue plus a fixed amount) for orders paid with one payment method. Method names are matched without regard to case and spacing, so "PayPal" and "paypal" are one rule.
  • Each rule has its own currency; it is converted to the order currency at the order date.

Model your carrier costs with shipping rules and your payment provider's price list with payment fee rules. AxiTrace does not read carrier invoices or the actual fees of a payment provider.

The 90-day backfill

When you switch profit tracking on, AxiTrace calculates the profit of your orders of the last 90 days in the background, with your current costs and settings. Those orders are marked estimated, because the costs you enter today may not be the ones that applied back then. Until it finishes, the Profit page may say that no order has been calculated yet. The card shows its progress. New orders are calculated as they arrive.

The same restatement runs again after your first CSV import into an empty cost catalog and after the first Shopify product cost sync, so the orders that fell back to the default margin pick up your product costs. Orders older than 90 days are only calculated if you use Apply from date.

Changing settings and "Apply from date"

A change to your cost defaults, components or rules applies to new orders only. Orders already calculated keep their figures, so changing a rule today never silently rewrites last month.

To restate past orders, use Apply from date on the Profit tracking card: choose a date (not in the future) and every order from that date until today is recalculated with the current costs, rules and settings. AxiTrace first tells you how many orders will be restated and asks you to confirm. Only one recalculation runs per workspace at a time; a new request takes over the part of the previous one that had not been processed yet.

Product costs work slightly differently, because each cost has a date from which it is valid (see below): a cost that becomes valid in the past recalculates the cost of goods of the orders since that date, never earlier than 90 days before profit tracking was switched on. Tax, shipping cost, payment fee and handling of those orders stay as they were.

The cost catalog

Open the Profit page and choose Product costs. Each product has an external id, a SKU or both, an optional title, a unit cost, a currency and the date it is valid from. A cost change never rewrites history: each order keeps the cost that was valid when it was placed.

Import a CSV file

Click Import CSV and upload a file with a header row. Columns can be in any order:

Column Required Notes
external_id One of the two The platform id, for example shopify:44012345678, woocommerce:123, shopware:<product id>, magento:<product id>, prestashop:<product id>. Matched before the SKU.
sku One of the two Your SKU.
title Optional The product name, for your own overview.
unit_cost Required What one unit cost you, without VAT. A comma is accepted as the decimal mark (12,40).
currency Required Three-letter currency code, for example EUR.
valid_from Optional A date (2026-09-01) or a date and time, in the workspace timezone. Empty means now. A date in the past recalculates the orders placed since then.
external_id,sku,title,unit_cost,currency,valid_from
woocommerce:123,CHAIR-01,Office chair,25.00,EUR,2026-09-01
,DESK-MAT,Desk mat,6.20,EUR,
  • Comma or semicolon separated, UTF-8. Up to 50,000 rows and 10 MB per file.
  • An unknown column rejects the whole file. A bad row is rejected with its line, column and reason, and the valid rows are still imported.
  • A row with the same cost as the one already in force is skipped, so importing the same file twice changes nothing.
  • Cell contents are read as text and never evaluated.

Add or edit one product

Add product and Edit change one product. A cost entered here applies to orders placed from now on. To change the cost of past orders, import a CSV file with a valid_from date. The external id of a product cannot be changed later.

Export

Export CSV downloads the catalog in the import format, so an exported file can be edited in a spreadsheet and imported back.

Profit by platform

The By platform view assigns every order to one paid platform using the workspace attribution model, so each order counts for at most one platform. The platform cards on the Overview, Campaigns and Traffic Sources use the same attribution, so their totals match this view. POAS is profit divided by spend. Profit after ad spend subtracts spend from profit. Cost coverage shows how much net revenue has actual or estimated cost data, while spend coverage shows how many days in the selected range have synced spend.

Meta expands from campaigns to ad sets and ads. Google Ads expands to ad groups, except Performance Max, which remains at campaign level. TikTok remains at campaign level. Unassigned within campaign means the campaign is known but a lower-level id is missing. Unmatched campaign means a paid campaign name could not be matched to the spend catalogue. Other ads groups low-spend rows, and Not paid / unattributed contains orders assigned outside paid advertising.

Campaign spend refreshes hourly and lower levels refresh every six hours. The report is rebuilt in the background and can be about an hour old. Opening the report never calls an advertising platform directly.

Per-platform setup

Every platform can use the cost catalog, the cost defaults and the rules. On top of that, each integration can deliver product costs with the order. Cost data is accepted only from your server: see privacy of your cost data.

The secret key for the WooCommerce, Shopware, Magento and PrestaShop plugins

  • Where to find it: open your workspace, go to Workspace settings → Tracking & domains and, in the Container Information card, click Reveal next to Secret Key (sk_live_...). Only the account owner and members with edit rights can reveal it. Use the secret key of the same workspace whose Public Key the plugin already uses.
  • No key: purchases are tracked as before, without product costs and without refunds.
  • A mistyped or malformed key: purchases are still tracked, but their cost fields are dropped, as if no key had been set. If the Profit & POAS module shows only estimated orders from a plugin that should send costs, check the key first.
  • The secret key of another workspace: the request is refused with 401 Unauthorized. A key only works for its own workspace.

Shopify

  1. With profit tracking on, the Profit tracking card shows Product costs from Shopify for your connected store. Click Connect product costs.
  2. Shopify asks you to approve one extra, read-only permission: read_products. The app install never asks for it, and stores that never connect product costs keep exactly the permissions they installed with.
  3. Back in AxiTrace the first sync starts on its own. If the card has not noticed the approval yet, click Check access.
  • AxiTrace reads the Cost per item of every product variant and stores it in your cost catalog under shopify:<variant id>. A variant without a cost per item is skipped, so it uses your default margin rather than a cost of 0.
  • Costs are synced four times a day. A changed cost becomes a new catalog version valid from the sync, so earlier orders keep the cost they had.
  • The first sync restates the orders of the last 90 days with the synced costs, marked estimated (see the 90-day backfill).
  • Tax, the shipping the buyer paid, whether prices include tax, the destination country and the payment gateway come with every order automatically.
  • Shopify Payments fees are not read. Set the payment fee in the cost defaults, or add a payment fee rule for the gateway name (for example shopify_payments).
  • Carrier costs are not read. Use the default shipping cost and shipping rules.
  • Refunds and cancellations are received from Shopify automatically (see refunds).
  • If you remove the permission in Shopify, the sync stops and the card offers Reconnect product costs. Costs already in the catalog stay.

WooCommerce

  • Plugin 1.5.0 or later. In WooCommerce → Settings → Integrations → AxiTrace paste your secret key (sk_live_...) into AxiTrace secret key (optional). Without it the plugin sends no product costs and no refunds. Where to find the key and what a wrong key does: the secret key.
  • Product costs come from WooCommerce's own Cost of Goods Sold feature (WooCommerce 9.5 or later, with the feature switched on): the cost recorded on the order line, else the product's current cost. A product without a cost is sent without one, never as 0.
  • Orders in a currency other than the store's base currency (multi-currency plugins) carry no costs, because WooCommerce keeps costs in the base currency. Those orders use your catalog or default margin.
  • Products are identified as woocommerce:<variation id or product id>.
  • Refunds and cancellations are reported automatically once the secret key is set.

Shopware

  • Plugin 0.5.0 or later. In the plugin configuration, per Sales Channel, set AxiTrace secret key (optional, sk_live_...). Without it the plugin sends no product costs and no refunds. Where to find the key and what a wrong key does: the secret key.
  • Product costs come from each product's purchase prices, as a net amount in the order currency. A variant without its own purchase price uses its parent's. A line gets no cost when the purchase price is missing, zero, or kept in another currency than the order; AxiTrace then applies your catalog or default margin.
  • Products are identified as shopware:<product id>.
  • Tax, the shipping the buyer paid, whether prices include tax and the billing country come with every order. Plugin 0.5.3 or later also sends the payment method by its technical name, as shown in Shopware under Settings → Payment methods (for example payment_paypal): add a payment fee rule for that name. Older plugin versions send no payment method, so their orders always use the default payment fee.
  • Refunds and cancellations are reported automatically once the secret key is set. The plugin's Conversion value setting does not affect profit.

Magento

  • Module 0.3.0 or later. In Stores → Configuration → AxiTrace → General set AxiTrace secret key (optional). Without it the module sends no product costs and no refunds. Where to find the key and what a wrong key does: the secret key.
  • Product costs come from the order item's cost (copied from the product's Cost attribute when the order was placed), else the product's current Cost attribute. A zero or missing cost is left out. Costs are sent only when the store's base currency equals the order currency.
  • Products are identified as magento:<product id>; for a configurable product, the simple product that was bought.
  • Credit memos and order cancellations are reported automatically once the secret key is set.

PrestaShop

  • Module 1.0.0 or later (see the PrestaShop guide). In Modules → Module Manager → AxiTrace → Configure, per shop on a multistore, set Secret key. Without it the module sends no product costs and no refunds. Where to find the key and what a wrong key does: the secret key.
  • Product costs come from the purchase price recorded on the order line when the order was placed: the supplier price when the product has one, otherwise the cost price (wholesale price, without tax); if the line has neither, the product's or combination's current cost price. PrestaShop keeps it in the shop's default currency; the module converts it into the order currency with the order's exchange rate. A zero or missing cost is left out, and AxiTrace then applies your catalog or default margin.
  • Products are identified as prestashop:<product id>, with the combination id as the variant and the product reference as SKU.
  • Tax, the shipping the buyer paid and whether prices include tax come with every order. The payment method is sent by the payment module's technical name (for example ps_wirepayment or ps_cashondelivery): add a payment fee rule for that name.
  • Refunds are reported automatically once the secret key is set: every credit slip with its products and shipping, including tax, in the order currency; products cancelled on an order that was already sent; and an order set to Refunded or Canceled without a credit slip, as one refund of the rest. The module's Conversion value setting does not affect profit.

PHP SDK

PHP SDK 1.9.0 or later. TransactionEvent gains setTax(), setShipping(), setTaxesIncluded() and setCosts($shipping, $paymentFee, $handling), and each product accepts unitCost and externalId. The SDK always authenticates with your secret key. Refunds are sent with $axiTrace->refund(). See the "Profit tracking: cost fields and refunds" section of the SDK README for complete examples.

Custom store: /v1/transaction

Add these fields to the transaction you already send from your server. Every field is optional. Cost fields are kept only on a request authenticated with your secret key; a request with the public key is accepted, but its cost fields are removed. tax, shipping and taxesIncluded are kept on every request.

Field Type Meaning
tax number Total tax of the order. When sent, the default VAT rate is not used.
shipping number Shipping the buyer paid, tax included. This is revenue, not your shipping cost.
taxesIncluded boolean Whether revenue and prices include tax. Absent means true.
costs.shipping Money What you pay the carrier for this order. Secret key only.
costs.paymentFee Money What your payment provider charges for this order. Secret key only.
costs.handling Money Packing, picking and other per-order costs. Secret key only.
products[].unitCost Money What one unit of the line cost you, without VAT. Secret key only.
products[].externalId string Your product id, matched against the external_id of your cost catalog before the SKU.

Money fields take {amount, currency}; a plain number is read in the revenue currency. A negative amount or a currency other than revenue.currency is answered 400. The payment method (paymentInfo.method) selects the payment fee rule and the buyer's country (client.country, two letters) selects the shipping rule. The example below adds the fields of the worked example; the rest of the transaction body is unchanged:

"tax": 23.00,
"shipping": 12.30,
"taxesIncluded": true,
"costs": {
  "shipping": { "amount": 6.00, "currency": "EUR" },
  "paymentFee": { "amount": 3.00, "currency": "EUR" },
  "handling": { "amount": 2.00, "currency": "EUR" }
},
"products": [{ "sku": "CHAIR-01", "externalId": "custom:1001", "name": "Office chair", "quantity": 2,
  "finalUnitPrice": { "amount": 55.35, "currency": "EUR" }, "unitCost": { "amount": 25.00, "currency": "EUR" } }]

Refunds and cancellations

A refund or a cancellation lowers the profit of the order it belongs to, on the date the order was placed:

  • A refunded product line takes back its revenue without tax and its cost of goods.
  • A refund of an amount without products (a goodwill or shipping refund) takes back revenue without tax only.
  • A cancellation takes back every line of the order.
  • Shipping cost, payment fee and handling are not taken back: you usually paid them anyway.
  • A refund repeated with the same refund id counts once.
  • Refunds are recorded only while profit tracking is on. A refund received while it is off is discarded, so refunds from before you turn profit tracking on are not included.
  • Revenue and ROAS do not change, and nothing already sent to an ad platform is changed afterwards. The Profit page shows refunded revenue and refunded cost of goods as separate lines.

Refunds arrive from the Shopify app automatically, from the WooCommerce, Shopware, Magento and PrestaShop plugins and the PHP SDK once the secret key is set, and from your own server through POST /v1/refund. See the Refund event reference and the HTTP API reference for the request format.

Where profit shows up

Once profit tracking is on, profit appears wherever revenue does, for everyone who may see profit. All amounts are in your reporting currency, and an order whose profit is not known yet (not calculated yet, or a product cost missing without a default margin) is left out of every profit figure rather than counted as 0.

Overview and Profit by platform

  • Overview shows revenue and ROAS only. The Overview module (Summary, Traffic and the Google Ads, Meta and TikTok tabs) shows revenue, ad spend and ROAS and never shows a profit or POAS figure, whoever is looking.
  • Profit by platform. Profit figures live in the Profit & POAS module. Its By platform tab lists your campaigns with Spend, Orders, Revenue, Profit, After ad spend, POAS and Coverage. POAS is profit divided by the same ad spend ROAS divides, so 1.00x is break-even: below it, the ads cost more than the profit they brought.
  • "-" instead of a number means there is nothing to divide or nothing to show: a source or campaign without ad spend (direct traffic, organic search), a row built before profit tracking was on, a Facebook ad set or ad (profit is attributed per campaign), or the first week of tracking, when POAS stays hidden like ROAS.
  • Coverage badge. Under each POAS figure a badge such as 82% actual costs says how much of the revenue behind it has actual product costs; the rest uses your default margin and is estimated. Its tooltip also says how many orders without a product cost are left out of Profit and POAS, because a coverage of 100% over 1 order of 10 is still only 1 order.

Orders & journeys

  • The Orders list has a Profit column: the profit of the order, less its refunds, with a badge for where its costs came from: Actual, Partial, Estimated or Not included (hover the badge for the reason).
  • Breakdown under the amount opens From revenue to profit for that order: every step from revenue to profit with where each figure came from (sent with the order, catalog, rule, workspace default, default margin or default VAT rate), and the line items with their unit cost and its source.

Profit & POAS module

  • By platform: profit by platform and per campaign.
  • Profit breakdown: profit, profit margin, orders with profit and cost coverage for the date range; a breakdown From revenue to profit (revenue, tax, revenue without tax, refunds, cost of goods, shipping cost, payment fees, handling cost); profit per day; profit per product with where its cost came from; and the products sold without a cost.
  • Product costs: your cost catalog.
  • Shipping & fees: your shipping and fee rules.

Costs marked "Not included" in a breakdown are switched off under cost components.

REST API and MCP

With the profit:read scope (see who sees profit), the REST API and the MCP tools add profit next to revenue:

  • Overview (get_overview), traffic sources (get_traffic_sources) and campaigns (list_campaigns): profit, poas, profit_coverage (0 to 1, the share of revenue with actual product costs) and profit_orders_left_out (orders with no known profit, outside both profit and coverage) on the KPIs, on every row and in the totals. The overview series also carries profit per day or week, and campaigns can be sorted by profit or poas.
  • Transactions (list_transactions): profit per order and cost_quality (actual, partial, estimated or not_included).
  • Without the scope, or when profit is hidden from the token's user, these fields are absent from the response, not null. Product costs and cost components are never returned.

Who sees profit

  • Account owners always see profit once profit tracking is on.
  • Team members and agency partners see it too, unless an account owner switches on Hide profit from team members and agency partners on the Profit tracking card. They then see no profit figure, no cost and no POAS, and they cannot change profit bidding. Only account owners can change this switch.
  • Through the REST API and MCP, profit fields need a token with the profit:read scope and are left out without it. A token with the scope follows the same rule as the user who created it, so a hidden team member's token gets no profit either.

Privacy of your cost data

Your costs are your margin

Cost data is never accepted from the browser. The tracking script, the Shopify web pixel and every request made with your public key lose their cost fields before the event is stored, because anything a storefront visitor can send could be forged. Costs reach AxiTrace only with your secret key, from the Shopify app, or through the cost catalog in the admin panel.

Cost data is never forwarded to ad platforms or analytics tools, and it is removed from every copy of an event that leaves the profit calculation (data feeds, error logs, integration payloads).

Profit bidding Business and Custom plans

Once your profit figures are reliable, you can send the profit of each order to Google Ads, Meta and TikTok, so their own value bidding optimises for profit instead of revenue. It needs a default margin and is switched on per connection. See Profit Bidding for the setup, the risks and how to switch it off.