HQ Calculator Order Search Now Shows Historical Metadata

Charles Evans

02 Oct 2025 — 1 min read

Previously, when you searched up an order by its order ID on the HQ calculator screen, it would get and show the current product metadata and excise tax calculation for that order. This was an issue because if someone was trying to solve an excise tax discrepancy that was caused by a products metadata changing over time, it would be hard to debug.

The new behavior is that when you search for an order, it will show you all of the products with their data that they had at the time of the order, as well as rerun the tax calculation on that historical metadata. There is a radio selector to switch between the historical product metadata with calculation and the current product metadata with calculation.

Historical metadata with historical calculation

Current product metadata with current tax recalculation (Notice top product changes)

Approach: Improve Bot Discoverability with Search and Team Scoping

1. Global Bot Search Bar What: * Add a persistent search input at the top of the bot directory. * Search should match: * Bot name * Short description * Tags / keywords * Owner or team (optional enhancement) 2. Role-Based Bot Filtering What: * Automatically filter bots based on the user’s authenticated role, team, or department.

Browse & Search Licenses

Overview This deliverable introduces a searchable License List page within OpsConfig. The page allows operators to browse and locate licenses using substring search across key identifiers, while ensuring all sensitive data remains masked according to the ClientConfig API response rules. The feature is read-only and intended to support operational visibility

License Details (View‑Only)

Overview The License Details (View‑Only, Masked) feature provides operations users with a secure, read‑only view of license‑specific client configuration data. Configuration is fetched via the ClientConfig API and rendered exactly as returned, with all sensitive fields masked. No unmasking or editing capabilities are provided. Scope & Goals

How do you setup identity or age verification so that only certain locations need to get verified?

Answer: Use Location-Based Identity Verification. This is enabled via the locationRestrictions.requiresVerification attribute in your application configuration to define which countries and regions require verification. Summary Token of Trust now supports location-based verification requirements through the locationRestrictions configuration. This feature allows you to specify which geographic locations (countries and regions)

Read more

Approach: Improve Bot Discoverability with Search and Team Scoping

Browse & Search Licenses

License Details (View‑Only)

How do you setup identity or age verification so that only certain locations need to get verified?