Product configuration is where you tell Metriks how each product synced from your source should be treated in your analytics. It's a one-time setup that decides which revenue counts as recurring (and feeds MRR, ARR, churn and retention), how long the typical subscription runs, and — if you use Automated Invoicing — the default price, currency and yearly increase used when invoices are generated.
Get this right once and the rest of Metriks reports the numbers you'd expect; get it wrong and MRR will look too high (one-offs counted as recurring) or too low (recurring products marked one-off). This guide walks through every setting on Settings → Products and what it changes downstream.
Products only show up here once they've synced from a source. If the list is empty, connect an E-conomic source or custom source first, then come back. You'll also need Admin permissions to edit — Observers can view the configuration but the inputs are disabled.
Go to Settings → Products. The page lists every product Metriks has synced, one row per product, with its name and source ID on the left and the configuration columns on the right. Use the search box to jump to a specific product, and the All products / Only included filter to hide the ones you've parked in the "Other" bucket.
The list paginates at 25 rows by default; switch to 50 or 100 from the pager at the bottom if you want to scroll through everything in one go.
The most important toggle on the page. For each product, decide:
- Recurring — turn the toggle on for subscriptions and recurring services. The product's invoice lines feed into MRR, ARR, churn, retention, LTV and revenue retention. This is the right choice for monthly seats, annual licences, recurring support contracts, and so on.
- One-off — leave the toggle off for single-purchase items: hardware, setup fees, one-time consulting, training days. The revenue still appears in total revenue and on the customer's invoice history, but it doesn't count in any recurring metric.
A one-off product accidentally marked recurring will inflate MRR every cycle the customer was invoiced. A recurring product marked one-off will silently drop the customer out of MRR entirely. If a number looks off, this is the first place to check.
When you turn on Recurring, a Length (months) input appears. It tells Metriks how many months the typical subscription period covers — 1 for monthly billing, 3 for quarterly, 12 for annual, and any value in between. Use the plus and minus buttons or type the number directly; the field accepts values from 1 to 60.
Length is used to spread the revenue evenly across the subscription period, so a 12-month invoice for 12,000 DKK shows up as 1,000 DKK / month in MRR rather than a 12,000 DKK spike followed by eleven empty months. Set it to the contract length you actually sign with customers on this product, not the invoicing cadence.
Set Length to whatever is most common for this product. Per-customer overrides are handled on the customer's agreement in Customers → {customer} → Agreements, not on the product. Product Length is the default that new agreements inherit.
The Group as 'Other' checkbox is a tidying tool, not a metrics switch. When ticked, the product is bundled with everything else flagged "Other" in product breakdowns — useful for shipping fees, manual line items, currency adjustments and the long tail of products that aren't worth their own slice of the pie chart.
The revenue still counts (and is still recurring if you've marked the product recurring), it just gets aggregated. You can filter the "Other" bucket in or out on the stats pages whenever you want to see the detail again.
If you have Automated Invoicing enabled on your account, each row has an extra Invoicing button that expands four more fields:
- Default Monthly Price — what one month of this product costs. Used when Automated Invoicing generates a new line and the agreement doesn't override the price.
- Currency — the currency that price is denominated in (DKK, EUR, USD, …). Picked from the standard ISO-4217 list.
- Yearly Increase % — automatic annual uplift, between 0 and 99.99%. Leave blank for no automatic increase.
- Next Increase Date — when the next yearly uplift kicks in. Must be a future date.
These four fields are defaults. Anything written on an individual customer's agreement overrides them — so use the product-level defaults to set the price for new agreements and update the agreement fields for one-off customer-specific deals.
The Invoicing column only appears when Automated Invoicing is enabled on your workspace. If you're not on that add-on, you can still set Recurring, Length and Group as 'Other' — the analytics side of product configuration works without it. See Automated Invoicing for what you'd unlock.
Edits are staged in the page until you press Apply Changes in the sticky bar at the bottom. Until you do, the bar stays visible and Metriks warns you with an "unsaved changes" prompt if you try to navigate away — so it's safe to edit several products in one pass and apply them together.
When you press Apply, every edited product is updated in one go and the sticky bar disappears. New invoices generated after this point use the new configuration; historical analytics recompute on the next sync so MRR, churn and retention all reflect the change going back through your history.
The Download Config button in the top-right of the page exports the current product configuration as a file, named with the current month and timestamp. Useful for:
- Backup before a bulk change — keep a snapshot in case you need to revert.
- Audit and review — share the configuration with a colleague or accountant outside Metriks.
- Comparing across companies — download from one company, compare with another's setup.
The download is read-only; there's no "upload to restore" option today — corrections go back through the page.
No. New products land with sensible defaults — typically not recurring, no length set, not grouped as Other. You only need to touch the ones that should behave differently, most importantly the ones that represent your actual subscription products. Most teams configure their core SKUs on day one and revisit the page when they launch new products.
Changing Recurring or Length retroactively rebuilds the analytics for that product, so MRR and churn for previous months will update to reflect the new classification. Changing Invoicing Defaults only affects invoices generated after the change — historic invoices keep the price and currency they were booked with.
Yes. Observers see the same list with the same data, but every input is disabled and the Apply Changes bar never appears. Only Admins and Super Admins can edit. The page header shows a notice when you're viewing as a non-Admin so it's obvious why nothing is editable.
No. Product names come from your source (e-conomic, custom upload) and Metriks doesn't override them. Rename the product in e-conomic and the change will flow through on the next sync. The product ID never changes, so configuration you've set in Metriks stays tied to the product even if the name changes.
- Automated Invoicing — once products are configured with prices and currencies, this is the add-on that uses them.
- Connecting an E-conomic source — if your product list is empty, start here.
- Working with the stats page — verify that MRR and churn look right after a configuration change.
Was this guide helpful?