ResourceWise Launches Compass Platform, Consolidates Chemicals Intel

The decision facing any Head of Analytics who currently pays for both OrbiChem360 and ChemEdge360 just got made for them. On September 7, ResourceWise folded two established chemical market intelligence products into a single new platform called Compass, with an AI query layer bolted on top. For teams with a renewal coming up in the next two quarters, this is a procurement event dressed up as a product launch.

What Happened

As ANTARA News reported, the Charlotte-based data provider ResourceWise announced Compass alongside a companion tool called ResourceWise IQ, which lets users query the underlying datasets through natural language. The launch went out at 14:31 GMT+700 on September 7, 2026, and it consolidates the intelligence assets of two acquired brands, Tecnon OrbiChem and Chemical Intelligence, that were until now delivered through separate products branded OrbiChem360 and ChemEdge360.

Compass launches with chemicals coverage first. According to the announcement, the platform bundles pricing intelligence, historical trends and forecasts, plant-level production data, global capacity, producer trends, announced projects, import and export flows, trading partner analysis, geographic flow visualization, supply-demand balances, utilization rates, and analyst commentary from ResourceWise's in-house experts. The IQ layer sits on top of all of that as the natural-language interface.

Pete Stewart, President and CEO of ResourceWise, framed the launch around decision speed: "Our customers need immediate access to high-quality data to make critical business decisions," adding that Compass "gives customers a clearer view of what is shaping market direction and business risk." Peter Coutu, the company's COO, was more direct about the strategic intent, calling Compass "a modern foundation for delivering that market intelligence and insight in a way that is easier to handle, analyze, and apply."

Chemicals is the first vertical. ResourceWise says forest products, pulp and paper, and low-carbon fuels will migrate onto the same platform as development progresses. That sequencing matters more than the launch itself, because it tells you Compass is not a chemicals product. It's a platform play across every commodity vertical ResourceWise touches.

Technical Anatomy

Strip the marketing off and Compass looks like a fairly standard 2026 data-product architecture: a consolidated warehouse of proprietary datasets, a unified access layer, and an LLM-based retrieval interface on top. The interesting engineering questions are the ones ResourceWise didn't answer publicly, and they're the ones that determine whether the platform is a genuine consolidation or a UI wrapper over two still-separate backends.

The first question is the data model. OrbiChem360 and ChemEdge360 were built by different teams, with different taxonomies for chemicals, different plant identifiers, different pricing series conventions, and different geographic hierarchies. Merging those into a single queryable model is the hard part. Anyone who has run a warehouse consolidation on Snowflake or a lakehouse migration on Databricks knows the ETL work to reconcile two product taxonomies into one canonical entity model is measured in engineer-quarters, not sprints. If Compass ships with true entity resolution across the two source datasets, that's real work. If it ships with a router that sends chemical A queries to one backend and chemical B queries to another, that's a demo.

The second question is IQ. Natural-language interfaces over structured market data are the current fashion, and they fail in predictable ways: hallucinated joins, wrong unit conversions on pricing series, and confident answers about time ranges the underlying data doesn't cover. A well-built system uses a semantic layer to constrain what the LLM can ask, something similar in spirit to what dbt exposes through its metrics layer. Without that constraint, IQ becomes a support ticket generator.

The third question is export and API access. Chemical procurement teams don't live inside vendor dashboards. They pull pricing into their own models, feed forecasts into S&OP tools, and increasingly want raw feeds into internal analytics stacks. Whether Compass exposes clean APIs, or forces users through a web UI with export buttons, determines whether it lives at the center of a customer's data workflow or on the periphery.

Who Gets Burned

Existing OrbiChem360 and ChemEdge360 customers are the immediate audience, and they fall into three groups. Group one paid for both products and now presumably gets consolidated billing, which is either a discount or a stealth price increase depending on how ResourceWise handles renewal math. Group two paid for one and will be upsold to the combined platform. Group three built internal pipelines against the legacy product APIs and now has a migration project they didn't plan for. Every platform consolidation creates that third group, and their pain is invisible in the press release.

The competitive question is sharper. Chemical market intelligence has a small vendor set: ICIS, S&P Global Commodity Insights, Argus, and a handful of specialists. A consolidated Compass platform with an AI query layer changes the RFP conversation because buyers will now ask every other vendor whether they have equivalent natural-language capability. Vendors that don't will spend the next four quarters retrofitting one, which is expensive and rarely produces a good result on the first try.

The GC at any chemical trading firm or procurement organization should be asking their Head of Analytics this week whether the current market intelligence contract has an assignment or platform-migration clause, and what data-portability rights exist if ResourceWise sunsets the legacy product interfaces on a timeline the customer didn't approve. That question determines whether the buyer has use in the renewal cycle or whether they're captive.

Downstream, the forest products, pulp and paper, and low-carbon fuels verticals now have a roadmap dependency on chemicals-first execution. If Compass ships well in chemicals, those verticals get a modernized platform. If it ships badly, they wait longer and get a more cautious rollout. Buyers in those categories should treat the chemicals launch as a public beta they're paying to observe.

Playbook for Data Teams

For platform leads in commodity-adjacent businesses, three actions this quarter. First, audit your current market intelligence spend across all providers and map which internal systems consume which feeds. Consolidation announcements are the trigger to renegotiate, not the moment to accept new terms silently. If you're paying for OrbiChem360 and ChemEdge360 separately today, the combined price should be lower per seat, not higher.

Second, stress-test the IQ interface before letting analysts rely on it. Natural-language query tools produce answers that look authoritative regardless of accuracy. Run a benchmark set of questions you already know the answers to, across pricing, capacity, and trade flows, and measure how often IQ gets them right, wrong, or partially wrong. Publish that internally before it becomes a source of quiet decisions no one audits.

Third, plan for API continuity. If your S&OP models, pricing dashboards, or risk systems pull from OrbiChem360 or ChemEdge360 endpoints today, get written commitment on how long those endpoints remain available and what the migration path looks like. Platform consolidations always sunset legacy interfaces eventually. The customers who negotiate the timeline up front pay less to migrate than the ones who react after the deprecation notice.

Teams evaluating Compass on the buy side should now be asking themselves whether they're procuring a data product or a decision platform, because the answer changes both the price they should accept and the integration budget they need to reserve.

Key Takeaways

• ResourceWise consolidated OrbiChem360 and ChemEdge360 into Compass on September 7, 2026, with chemicals as the first vertical and forest products, pulp and paper, and low-carbon fuels planned to follow.
• ResourceWise IQ adds a natural-language query layer over the combined datasets, following the 2026 pattern of LLM interfaces on top of proprietary structured data.
• Existing customers of either legacy product face a renewal-cycle procurement event and should audit assignment clauses and data-portability rights before the next contract signature.
• Competing chemical market intelligence vendors will be pressured to ship equivalent natural-language capability, which is a multi-quarter engineering investment that rarely lands cleanly on the first attempt.
• Data teams consuming legacy APIs should get written commitments on endpoint lifecycles now, before deprecation timelines become someone else's decision.