Branch: issue/6355-devrock-order-endpoint-for-devops JTBD Commitment: APIs available for Integrations Release Note: Adds a DevOps-only order lookup endpoint so ops dev teams can pull PMD, order metadata, and product context by order ID without exposing PII. 1. Prerequisite — Enable Internal APIs for the App Domain 1. Open the API Keys editor:
Business Summary What happened? Starting around Feb 9, 2026, two issues in the excise tax engine could cause $0 tax on some orders that should have been taxed: products with incomplete catalog metadata were being silently exempted, and minor differences in how location names are formatted — capitalization, extra spaces, or
When products are synced into the excise tax system, some may arrive with incomplete information and get flagged with missingData=true in their details JSON. There may be some cases where we may need to remove these manually (as was the case when BigDVapor.net re-SKU'd all of
Historically we had a situation where excise tax products were synced into Cassandra and case-insensitive duplicates accumulated — for example, "Widget-A" and "widget-a" as separate rows. The find-duplicate-skus maintenance script detects these duplicates, reports on them, and optionally removes them with a safety backup. How it works
Your CI pipeline just went red. There are 23 test suites, a wall of logs, and somewhere in there a handful of tests are timing out or throwing cryptic errors. You could spend the next hour scrolling through terminal output — or you could hand the structured logs to an AI
This article shows how to turn a Sentry issue URL into a high-quality Trello card using Warp and the tot20 playbooks. It also explains what MCP is and how to set up the required MCP servers (Sentry + Trello). This flow will immediately save developers in my estimation at LEAST 5-10
This article explains how to run regression tests for the tot port to Node 20, how the test architecture is structured, how we use Docker to match CI, and how to manage quarantined tests (including the new enable/disable mechanism). This article applies to epic/5103-node20core-main and derived branches. Since
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)
When a consumer starts Token of Trust verification but does not finish, Token of Trust can send reminder emails to prompt them to complete verification. By default, reminders follow a fixed schedule and are not otherwise configurable at this time. FAQ How many reminder emails are sent, and when? Two
1) Goal Convert public DOR guidance into machine-readable tax rules for the Excise Tax Service so wholesale/retail transactions get correct excise tax lines. 2) Core Rule Shape Rules are JSON objects keyed by jurisdiction, optionally nested by county/locality, with optional arrays for multiple bands. "WA": { "
Keywords: pack quantity, volumeInMl, volume per unit, total volume, pack pricing, product sync, Shopify integration, API product updates Summary Pack products in Token of Trust HQ are specified using full pack-scaled amounts, not per-unit values. This applies to both volume (volumeInMl) and pricing fields (wholesalePrice, wholesaleCost, msrp, retailPrice). The Rule
How do I know what to set a rule's transactionType to? * a retail rule → applies only if the transaction/order's transactionType is retail. * a wholesale rule → applies only if the transaction/order's transactionType is wholesale. * both or unspecified → applies to all transaction types. A