Project Region, Currency, and Cost-Data Sharing

Currency and country

Every project has a currency (defaults to AUD) and an optional country. Both drive how BOM unit costs are entered and displayed, and both can be set two ways: when creating the project in the New Project dialog, or later from Project settings (open a project, then its actions menu). Currency always has a value; country stays unset until someone picks one; there's no way to guess it that wouldn't risk corrupting cross-org data keyed on it.

Sharing cost data for benchmarking

Share cost data for benchmarking is a per-project toggle, visible only to organization admins. Enabling it needs an explicit confirmation, since it's a decision that affects the whole org, not something any editor should flip in passing. It's also blocked until the project has a country set, since region is part of what gets shared.

When on, this project's BOM items contribute their unit cost, Uniclass Product/System codes, country, and currency to a nightly cross-org aggregate. Only aggregate statistics (median, min-max range, contributing org count) are ever shown to other organizations, and only once at least 5 organizations contribute to the same Uniclass code and region; raw per-org figures are never exposed. Turning sharing off stops future contribution but doesn't retroactively remove aggregates already published.

Where benchmarks show up

Once a BOM item's Uniclass Product/System code has enough cross-org data behind it, its detail panel shows a Cost benchmark line comparing that item's own unit cost against the median (and min-max range, and contributing org count) from other organizations. This only ever compares your item against other orgs' data, and only appears once the 5-org threshold for that code and region is met.