Product Mappings
Products are named differently depending on the source — Microsoft names a license differently than ALSO sells it (“Microsoft 365 Business Standard” vs. “(NCE) Microsoft 365 Business Standard (monatlich)”). Product mappings bring both onto one row.
Where this matters
Microsoft 365 ↔ ALSO comparison
The comparison tab in the Microsoft 365 view compares side by side, per customer and product:
| Column | Source | Meaning |
|---|---|---|
| Sold (ALSO) | ALSO Marketplace | what we purchase and re-bill |
| Sold (Tenant) | Microsoft Graph | what is booked in the tenant according to Microsoft |
| Assigned | Microsoft Graph | what is actually assigned to users |
The comparison primarily runs on stable Microsoft IDs — the tenant ID for the customer and the license ID (skuId) for the product. This reliably puts identical products on one row even when the names differ (Clipchamp, “… EEA (no Teams)”, “… with Copilot”). For rows without IDs (older snapshots, Adobe, manual entries), name matching with the maintained product mappings serves as the fallback.
Maintaining product mappings
In the Product mappings tab of the Microsoft 365 view, differing product names are merged onto a canonical name with a click — the same mechanics as for customers: list, merge, can be split again. Bundled default mappings cover the usual catalog variants.
Metrics are products
In snapshots, every metric is a billable quantity per portal — sometimes a product name (ALSO subscriptions, Autodesk products, Meraki device models), sometimes a fixed figure (servers/workstations for NinjaOne, seats for Bitwarden, an amount in € for manual portals). The billing article mapping maps exactly these metrics to weclapp articles — the metric names per portal are listed on the respective integration page.
Special cases already built in
ALSO products are separated by billing type — “(monatlich)”, “(jährlich, monatliche Zahlung)” for annual commitments with monthly payment and “(jährlich)” for upfront payers — every Azure subscription remains its own row, and outliers such as “Extra File Storage” or Azure consumption do not flow into the dashboard totals.