CTC Competitor Benchmark And Concrete Product Gap Matrix

• Status: P1-002 RESEARCH RESULT / USER REVIEW PENDING
• Observation date: 2026-07-30
• Research task: P1-002
• Owns: public competitor capability evidence, CTC current-versus-target comparison, concrete product gaps, adoption timing, and open research questions
• Does not own: current Runtime truth, product-scope approval, roadmap status, future Task or Phase IDs, commercial promises, certification claims, or automatic feature requirements
• Current-fact owner: .agents/rules/ARCHITECTURE.md
• Target owners: PRODUCT.md, .agents/rules/SYSTEM_DESIGN.md
• Background input: requirements/CTC_PRODUCT_PLATFORM_AND_DOCUMENTATION_RESET.md
• Update rule: material competitor change, target-customer discovery, approved roadmap review, package decision, or explicit benchmark task

1. Purpose And Guardrails

This benchmark answers one question:

Which market-proven product patterns should shape CTC now, which capabilities should remain post-stability candidates, and which patterns should be rejected?

It does not create future Tasks, assign future Phase IDs, change roadmap status, or turn advertised competitor features into CTC requirements.

Evidence classes:

Class	Meaning
OFFICIAL-PUBLIC	Capability advertised on an official vendor product page, official documentation, or a company-issued release. This is not independent proof of implementation quality, customer outcome, security, certification, or exact package availability.
CTC-CURRENT	Current repository or Runtime fact supported by the current architecture or source evidence.
CTC-TARGET	Approved product or design direction. It must not be described as already implemented.
UNKNOWN	Not established by reviewed public material or current CTC evidence. It requires product discovery, technical diligence, or field validation.

Decision classes:

Decision	Meaning
ADOPT_NOW	Preserve as a structural product-planning input: authority, tenant/profile, module, process, adapter, provenance, UI, onboarding, or repeatability. It does not authorize implementation by itself.
ADOPT_AFTER_STABILITY	Keep as a candidate only after an approved stability/repeatability gate, current customer evidence, and explicit user approval.
RESEARCH	Keep as an open question; do not promise or schedule implementation yet.
DEFER	Useful but lower priority than the approved product sequence.
REJECT	Conflicts with the CTC North Star or would create unjustified scope.

2. CTC Comparison Baseline

2.1 Verified current facts — CTC-CURRENT

• The current application is PHP/Apache/MySQL with server-rendered pages, shared JavaScript, API v2 routes, legacy Bootstrap, newer Tailwind surfaces, and OpenLayers yard-map UI.
• Active source surfaces exist across YMS, TMS, WMS, OMS, and BMS, including yard map/move, scale, appointment, dispatch, delivery, booking, inventory, commercial/inbound/outbound orders, allocation, rates, scale tickets, transactions, invoices, files, and reports.
• Current tenant scoping uses deployment-local numeric CLIENT_ID and getClientId(). The additive TenantExecutionContext foundation is not an active Runtime caller contract yet.
• CTC and MK behavior exists, but the two profiles are not yet proven as reusable product profiles.
• The process registry remains draft with partial traceability; MK role/menu and current browser evidence contain material unknowns.
• Current Runtime breadth is not proof of reusable product completeness, Shared SaaS readiness, field acceptance, stabilization, or repeatable onboarding.

2.2 Approved direction — CTC-TARGET

• One profile-based lightweight Operations ERP for small US recycling yards and logistics operators.
• One codebase and migration lineage for Shared SaaS and Dedicated deployment.
• Explicit tenant, profile, module, capability, entitlement, configuration, policy, role/menu, terminology, document-template, and adapter boundaries.
• Shared business authority for scale, inventory, orders, yard, transportation, documents, rates/billing, and reconciliation.
• Device-independent scale and unit provenance; validated import, retry, recovery, reconciliation, backup/restore, and audit.
• CTC as the execution-first reference, MK as the order-first reference, then a future no-fork third-yard proof.
• Reliable core and governed evidence before AI recommendation, human-approved action, or limited automation.

2.3 Not yet established — UNKNOWN

• Generic product completeness or a third-customer no-fork result.
• Current MK operational acceptance and stable Shared SaaS evidence.
• Repeatable package, entitlement, licensing, onboarding, upgrade, support, and SLA.
• Certified regional compliance or guaranteed hardware compatibility.
• Broad mobile/portal, multi-site enterprise visibility, advanced trading profitability, or autonomous AI operation.

3. Executive Findings

1. CTC's immediate gap is productization, not raw screen count. Competitors package authority, configuration, hardware, onboarding, support, and external workflows more coherently than the current CTC Runtime.
2. The current market has consolidated. GreenSpark and ReMatter combined into ReSpark in April 2026, so the benchmark treats ReSpark as the current platform and uses legacy product pages only as bounded evidence.
3. Direct competitors divide into four patterns:
4. enterprise breadth: AMCS;
5. trading/inventory depth: cieTrade;
6. scale/compliance/payment specialization: Scrap Dragon, ScrapRight, and Scaleit;
7. modern cloud operating experience: ReSpark.
8. Kaleris and Odoo are references, not direct substitutes. Kaleris is a yard-execution reference; Odoo is a multi-company, module, deployment, and upgrade reference.
9. The benchmark identifies planning areas, not future Task IDs. Structural themes can inform approved integration, platform, module, process, UI, and repeatability work. Competitive feature expansion remains conditional.
10. No vendor marketing claim proves CTC should copy its architecture. Public pages rarely establish exact tenant isolation, data model, failure recovery, deployment topology, security, or implementation quality.

4. Market Landscape

Product	Benchmark role	Primary signal	Directness to CTC	Current disposition
AMCS Metal / Brady	Enterprise suite	end-to-end recycling breadth, commercial depth, multi-operation productization	Direct, larger-enterprise segment	Structural patterns now; broad feature breadth later
cieTrade	Recycling/trading platform	configurable inventory, pricing, brokerage, logistics, and portal	Direct	Core inventory/commercial patterns now; advanced trading later
Scrap Dragon	Scale/compliance specialist	compliance, payment, inventory, trucking, multi-location, cloud/local delivery	Direct	Adapter/package seam now; vertical features later
ScrapRight	Scrap-yard operating package	compliance, ticketing, inventory, accounting, mobile, hardware, and tiered packages	Direct	Package/onboarding patterns now; compliance/payment later
ReSpark	Modern recycling platform	unified yard workflow, modern UX, inventory/logistics/finance, portals/mobile, and AI positioning	Direct	Product coherence now; advanced automation later
Scaleit	Scale-centric operating package	ticketing, scale, hardware, compliance, inventory, portal/API, and deployment options	Direct specialist	Device/package seam now; broad hardware/compliance later
Kaleris YMS	Yard-execution reference	gate, dock, asset, task, event, KPI, RTLS, and integration	Adjacent	Event/KPI patterns now; RTLS/gate automation later
Odoo	Product architecture reference	modular apps, multi-company semantics, configuration, deployment, and upgrade discipline	Adjacent architecture	Tenant/module lifecycle patterns now; general ERP clone rejected

5. Competitor Analysis

5.1 AMCS Metal Recycling / Brady

Verified public claims — OFFICIAL-PUBLIC

• End-to-end metal-recycling operations spanning purchasing, sales, scale transactions, inventory, trading, pricing, transport, production, brokerage, settlement, and finance.
• Truck/platform-scale and mobile operational workflows.
• Broader supplier/hauler portal, compliance, valuation, and multi-operation positioning.

Not established by reviewed public material

• Exact CTC-style one-codebase Shared SaaS/Dedicated contract.
• Exact tenant-isolation implementation, package/pricing model, implementation effort, recovery behavior, or customer-specific customization burden.

CTC comparison and decision

• CTC has meaningful execution surfaces, but not AMCS-level product breadth or commercial productization evidence.
• ADOPT_NOW: end-to-end authority map, profile/package discipline, and commercial-to-physical traceability.
• ADOPT_AFTER_STABILITY: broader compliance, portals, multi-site analytics, and advanced transport/pricing/finance.
• REJECT: full enterprise-suite replication.

Official sources:

• https://www.amcsgroup.com/solutions/enterprise-management/brady/
• https://www.amcsgroup.com/resources/press-releases/amcs-launches-amcs-platform-for-metal-recycling/

5.2 cieTrade

Verified public claims — OFFICIAL-PUBLIC

• Contracts, spot and formula pricing, dispatch, scale activity, inventory, shipping, documents, reporting, accounting integration, and self-service portal.
• Truck, floor, and forklift scale integration.
• Serial, bulk-perpetual, bulk non-perpetual, and do-not-track inventory models.
• Barcode/label support, warehouse workflows, landed-cost valuation, processing cost, gross-profit reporting, brokerage/export, and mobile/photo workflows.

Not established by reviewed public material

• Exact tenant execution context, isolation contract, dedicated deployment topology, offline behavior, or implementation/recovery quality.

CTC comparison and decision

• CTC has order, scale, inventory, logistics, document, rate, and billing surfaces, but lacks a proven reusable inventory-model and valuation catalog.
• ADOPT_NOW: inventory model contract, processing/provenance, adapter boundary, traceability, and configurable pricing/valuation seams.
• ADOPT_AFTER_STABILITY: portal/mobile package, advanced brokerage, multi-currency trading, and projected profitability.
• RESEARCH: how much advanced valuation is required for the initial metal/scrap segment.

Official sources:

• https://www.cietrade.com/recycling-plant-software/
• https://www.cietrade.com/mobile-apps/clickbale/

5.3 Scrap Dragon

Verified public claims — OFFICIAL-PUBLIC

• Compliance, payments, inventory, trucking, accounting, multi-location, web application, and scale-to-sale positioning.
• Public material supports cloud-hosted and locally installed product lines.
• Scale, photo/audit, customer, payment, inventory, and accounting-oriented operation.

Not established by reviewed public material

• Exact feature parity between cloud and local products, package boundaries, tenant model, upgrade path, or certification scope.

CTC comparison and decision

• Scrap Dragon shows that local/dedicated delivery and specialized scale/compliance operation can be commercially packaged.
• ADOPT_NOW: explicit provider/hardware adapter seam and optional vertical-package boundary.
• ADOPT_AFTER_STABILITY: compliance, payment/cash, hardware certification catalog, portal, and expanded accounting connectors.
• RESEARCH: actual jurisdiction coverage, device matrix, and cloud/local parity before any customer promise.

Official sources:

• https://scrapdragon.com/
• https://scrapdragon.com/about

5.4 ScrapRight

Verified public claims — OFFICIAL-PUBLIC

• Scrap purchasing/ticketing, advertised compliance coverage, inventory and margin visibility, customer management, accounting integrations, dispatching, mobile apps, and hardware integration.
• Public packages distinguish Basic, Standard, and Enterprise, with annual commitment, multi-location capability, onboarding, training, phone support, and installation assistance.
• Browser operation is advertised alongside iOS/Android mobile workflows.

Not established by reviewed public material

• Independent certification of legal coverage, exact hardware compatibility, exact pricing, tenant architecture, or support performance.

CTC comparison and decision

• ScrapRight is a packaging/onboarding reference: it converts specialist workflows, hardware, support, and location scale into understandable commercial tiers.
• CTC has not approved pricing or package tiers and must not copy those labels.
• ADOPT_NOW: package, entitlement, onboarding, and support structure as planning input.
• ADOPT_AFTER_STABILITY: compliance engine, payment devices, external/mobile workflows, and packaged hardware.
• RESEARCH: validated jurisdiction coverage, hardware matrix, and actual package economics.

Official sources:

• https://scrapright.com/
• https://scrapright.com/pricing

5.5 ReSpark — GreenSpark And ReMatter Combined

Current market fact

GreenSpark and ReMatter combined in April 2026 and now present the current platform as ReSpark. Legacy GreenSpark and ReMatter pages remain useful product evidence, but the benchmark does not count them as independent current vendors.

Verified public claims — OFFICIAL-PUBLIC

• A unified cloud platform for scale ticketing, pricing, inventory, logistics, contracts, sales, reporting, finance, portals, mobile workflows, integrations, and equipment/maintenance extensions.
• ReMatter material advertises real-time inventory, weighted-average cost, processing input/output rules, QR tags, physical inventory, multi-yard visibility, dispatch/bin tracking, driver communication, and photo verification.
• GreenSpark/ReSpark material advertises hardware/software integrations and AI/agent capabilities with human approval, guardrails, logging, and reversible-action positioning.

Not established by reviewed public material

• Independent proof of merger/product migration completeness, exact module parity, data migration experience, security, tenant isolation, recovery quality, or AI reliability.
• Whether every legacy capability is available in one generally available package today.

CTC comparison and decision

• ReSpark is the strongest current reference for a coherent modern user experience and unified scrap-yard product story.
• ADOPT_NOW: coherent workflow/product language, processing/inventory provenance, integration contracts, human approval, and audit patterns.
• ADOPT_AFTER_STABILITY: polished portal/mobile, equipment maintenance, and advanced AI agents.
• REJECT: autonomous agent as a parallel source of truth or authority bypass.
• RESEARCH: current post-merger module/package map and migration/support model.

Official sources:

• https://respark.com/
• https://respark.com/integrations
• https://www.rematter.com/inventory-management
• https://www.rematter.com/rematter-dispatch
• https://www.businesswire.com/news/home/20260413780377/en/GreenSpark-and-ReMatter-Combine-to-Form-ReSpark-the-First-AI-Native-Operating-System-for-the-Recycling-Industry

5.6 Scaleit

Verified public claims — OFFICIAL-PUBLIC

• Scale-centric software for scrap metal, recycling, waste, aggregate, and other weighing operations.
• Public material advertises custom tickets/reports, image and data backup, electronic tickets, accounting integration, inventory, scrap-compliance features, invoicing, container tracking, API access, customer portal, remote data operation, and multi-site views.
• Product options include unattended/mobile weighing, contactless ticketing, cloud backup, dedicated-server delivery, access levels, and hardware integration.

Not established by reviewed public material

• Independent compliance certification, exact device compatibility, security model, failure/recovery behavior, or parity across desktop/cloud/mobile products.

CTC comparison and decision

• Scaleit is a specialist reference for productized scale devices, ticketing, peripherals, and deployment options.
• ADOPT_NOW: scale/hardware adapter contract, capability declaration, provenance, diagnostics, and fallback requirements.
• ADOPT_AFTER_STABILITY: certified device catalog, unattended terminal, payment, and broad portal/mobile offering.
• RESEARCH: initial truck/floor/forklift scale and camera/label/ID device priorities.

Official sources:

• https://scaleitusa.com/
• https://scaleitusa.com/recycling-software-solutions/

5.7 Kaleris YMS

Verified public claims — OFFICIAL-PUBLIC

• Gate, dock, appointment, asset inventory/location, yard tasks, driver/kiosk check-in, exception management, dashboards, KPI, analytics, and multi-location visibility.
• Event-triggered automation, APIs/data streaming, WMS/TMS/ERP integration, RTLS/IoT, and asset-history positioning.
• Tiered approaches from lower-volume yards with minimal hardware to complex RTLS deployments.

Not established by reviewed public material

• Recycling-specific purchasing, scale, material inventory, billing, or commercial-document depth comparable to CTC's target.
• Exact implementation cost, tenant model, integration effort, or recovery semantics.

CTC comparison and decision

• Kaleris is a yard-execution reference, not a direct recycling ERP substitute.
• ADOPT_NOW: event/state model, exception/KPI contract, API/integration seam, and configurable workflow.
• ADOPT_AFTER_STABILITY: RTLS/RFID/GPS/vision, automated gate/kiosk, and enterprise multi-site visibility.
• REJECT: full enterprise-YMS clone.

Official source:

• https://kaleris.com/solutions/yard-management/

5.8 Odoo

Verified public pattern — OFFICIAL-PUBLIC

• Multi-company operation in one database, user company access, shared and company-specific records, company-aware defaults, and inter-company transactions.
• Modular application packaging, manifests, deployment choices, IoT integration, and documented upgrade/migration discipline.

Not established by reviewed public material

• Recycling-specific execution depth or direct suitability for CTC's target workflow without substantial configuration/customization.

CTC comparison and decision

• Odoo is an architecture/product-operation reference, not the product CTC should become.
• ADOPT_NOW: explicit tenant/company context, shared-versus-tenant data rules, module manifest/lifecycle, configuration-first variation, and upgrade discipline.
• REJECT: general-purpose ERP breadth, full accounting suite, or app-store scope as the initial CTC objective.

Official sources:

• https://www.odoo.com/documentation/19.0/applications/general/companies/multi_company.html
• https://www.odoo.com/documentation/19.0/developer/reference/backend/module.html
• https://www.odoo.com/documentation/19.0/administration.html

6. Concrete CTC Gap And Timing Matrix

Capability	Market evidence	CTC current evidence	Concrete gap	Decision	Planning area
Cross-profile core workflow	Direct competitors connect purchasing, scale, inventory, logistics, and commercial records	Broad module surfaces exist; reusable CTC/MK profile acceptance is unproven	shared authority, profile variation, MK regression/cutover evidence	ADOPT_NOW	CTC/MK integration planning
Explicit tenant/company context	Odoo and enterprise products expose company context/configuration	numeric CLIENT_ID; target context foundation inactive	active page/API/job/file/import context and isolation acceptance	ADOPT_NOW	multi-tenant platform planning
Module/package/entitlement	ScrapRight, Scaleit, and enterprise suites package capabilities	module guards exist; reusable manifest/package contract incomplete	manifest, public contract, resolver, package, and entitlement lifecycle	ADOPT_NOW	module and product-package planning
Process authority and recovery	Competitors market integrated workflows and exceptions	process registry is draft/partial	approved states, owner, exception, retry, recovery, and metrics	ADOPT_NOW	process and automation planning
Scale contract	All direct peers productize weighing	current scale routes/tickets exist	device-independent reading, unit/provenance, correction, diagnostics, and adapter tests	ADOPT_NOW	scale and adapter planning
Broad scale hardware catalog	Scrap specialists market peripheral/device support	no approved certified catalog	device matrix, certification/support policy, and field acceptance	ADOPT_AFTER_STABILITY	conditional competitive-feature review
Inventory models	cieTrade/ReSpark expose serial, bulk, processing, valuation, and physical count	current lot/location/inventory APIs and workflows exist	configurable identity/balance model, processing, WAC/COGS, and reconciliation	core ADOPT_NOW; advanced later	inventory core and later feature review
Yard event/KPI	Kaleris exposes event, exception, tasking, KPI, and RTLS	yard map/move/dispatch/current data exist	canonical event/state/KPI and baseline	ADOPT_NOW	process and performance planning
Gate/RTLS/vision	Kaleris markets kiosk, RTLS, IoT, and automation	no productized hardware package	adapter, privacy, failure/recovery, ROI, and field proof	ADOPT_AFTER_STABILITY	conditional competitive-feature review
Orders/pricing/billing	AMCS/cieTrade/ReSpark connect commercial and physical flow	OMS/BMS/rate/transaction/invoice surfaces exist	reusable pricing/rate/state/document/accounting adapter contract	ADOPT_NOW	CTC/MK integration and module planning
Advanced brokerage/profitability	cieTrade/AMCS expose brokerage, landed cost, and margin	partial reports/trade/billing surfaces	generalized valuation, multi-currency, accrual, and margin model	ADOPT_AFTER_STABILITY	conditional competitive-feature review
Modern operational UI	ReSpark emphasizes unified cloud UX and mobile operation	many current screens; mixed frontend stack	shared primitives, error/loading/empty/mobile/accessibility, and role workflow	ADOPT_NOW	UI standardization planning
Portal/mobile	Most direct peers expose customer/driver/buyer portals or apps	limited/fragmented external surfaces	product package, tenant/role/security/offline/effect/recovery model	ADOPT_AFTER_STABILITY	conditional competitive-feature review
Compliance	Scrap specialists advertise compliance	CTC is not a certified compliance product	jurisdiction research, rule/evidence/retention/update/support ownership	ADOPT_AFTER_STABILITY	conditional competitive-feature review
Payment/cash	Scrap specialists package payments/ATM/cash workflows	not an approved CTC baseline	device, cash authority, reconciliation, fraud, accounting, and support	ADOPT_AFTER_STABILITY	conditional competitive-feature review
Multi-site visibility	Several peers market multi-location operation	Dedicated reference exists; Shared SaaS and multi-site proof incomplete	company/site model, cross-site permissions, KPI, and consolidation	foundation now; feature later	platform/repeatability and later feature review
Onboarding/upgrade/support	ScrapRight, Scaleit, and ReSpark productize onboarding/support	Excel-first target; repeatability unproven	package, dry-run import, upgrade, backup/restore, diagnostics, and support policy	ADOPT_NOW	product repeatability planning
AI recommendation/action	ReSpark markets AI agents; Kaleris markets predictive/event automation	extraction surfaces and retrieval-ready evidence exist	governed inputs, citations, approval, mutation/effect audit, and ROI	bounded ADOPT_NOW; expansion later	process/AI governance planning
Autonomous AI operator	Vendor marketing increasingly promotes agents	product direction prohibits authority bypass	no safe business case before reliable core and field evidence	REJECT	none

7. Structural Inputs To Keep Now

These are not competitor-feature expansion. They are structural requirements for making existing CTC capability reusable and reliable:

• explicit tenant/profile/module/capability/entitlement resolution;
• shared-versus-tenant data classification;
• module manifest, public contract, owner, and dependency boundary;
• process state, authority, exception, retry, recovery, and metric contract;
• device/provider adapter interface with provenance, diagnostics, fallback, and reconciliation;
• scale, inventory, order, document, and billing lineage;
• reusable UI primitives and role-entered workflow acceptance;
• Excel-first import, onboarding, upgrade, backup/restore, and support package;
• one codebase and migration line for Shared SaaS and Dedicated;
• third-yard no-fork validation;
• governed AI evidence, human approval, and reversible-effect boundary.

8. Post-Stability Candidates Only

The following require an approved stability/repeatability gate, current market/customer evidence, and explicit user approval:

• state/local compliance package;
• customer, supplier, carrier, and buyer portal/mobile package;
• payment and cash-handling package;
• advanced trading, landed-cost, brokerage, and profitability;
• certified broad scale/peripheral hardware catalog;
• GPS/RFID/RTLS/vision and automated gate;
• enterprise multi-site analytics/consolidation;
• predictive or agentic AI expansion;
• expanded accounting/provider connector catalog;
• equipment-maintenance package.

9. Rejected Or Explicitly Deferred Patterns

• customer-specific source forks or Git branches;
• new numeric CLIENT_ID business/UI branches;
• copying every competitor feature into the roadmap;
• general-purpose ERP or full accounting-suite scope;
• broad compliance or hardware guarantees without jurisdiction/device evidence;
• enterprise YMS complexity before CTC process/KPI baseline;
• self-service onboarding, 24/7 SLA, SSO, multi-currency, or multilingual promises without a commercial decision;
• autonomous AI that owns business state, infers permission, or bypasses process/provider authority;
• pre-stability PostgreSQL or precommitted React rewrite as a benchmark response.

10. Open Research Questions

Question	Why it matters	Earliest legitimate decision point
What is ReSpark's current post-merger module and migration map?	Avoid benchmarking legacy capabilities as universally available	material market update or an explicitly approved benchmark review
Which truck, floor/forklift scale, camera, label, barcode, and ID devices are required by the first real profiles?	Determines adapter priority and support burden	approved adapter/hardware planning after customer evidence
Which inventory models are mandatory for CTC, MK, and a future third yard?	Prevents copying unnecessary trading complexity	current-profile discovery and approved integration planning
What compliance jurisdictions and evidence rules are demanded by real customers?	Compliance cannot be inferred from vendor marketing	explicitly approved compliance discovery
What package and support model fits the first paying customers?	Technical entitlement must follow commercial evidence	approved commercial and repeatability planning
Which portal/mobile roles produce measurable value?	Prevents a generic app backlog	approved role/customer discovery
What KPI baseline justifies RTLS, gate automation, or AI agents?	Hardware and automation require ROI evidence	measured process/performance baseline review
Which accounting adapters are required beyond current QBO-oriented flows?	Connector breadth has ongoing support cost	customer and integration discovery

11. Source Register

All competitor claims above are vendor-advertised unless explicitly marked otherwise. Observation date: 2026-07-30.

Vendor / product	Source type	URL	Use
AMCS Metal / Brady	official product page	https://www.amcsgroup.com/solutions/enterprise-management/brady/	enterprise metal-recycling breadth
AMCS Metal	official company release	https://www.amcsgroup.com/resources/press-releases/amcs-launches-amcs-platform-for-metal-recycling/	platform scope and launch positioning
cieTrade	official product page	https://www.cietrade.com/recycling-plant-software/	pricing, scale, inventory, dispatch, brokerage, and portal
cieTrade ClickBale	official product page	https://www.cietrade.com/mobile-apps/clickbale/	mobile/bale workflow
Scrap Dragon	official product page	https://scrapdragon.com/	compliance, payment, inventory, trucking, and multi-location
Scrap Dragon	official company/product page	https://scrapdragon.com/about	cloud/local product-line distinction
ScrapRight	official product page	https://scrapright.com/	purchasing, compliance, inventory, accounting, mobile, and support
ScrapRight	official pricing page	https://scrapright.com/pricing	package/tier reference
ReSpark	official current product site	https://respark.com/	current combined company/product positioning
ReSpark	official integrations page	https://respark.com/integrations	hardware/software integration positioning
ReMatter	official inventory page	https://www.rematter.com/inventory-management	inventory, processing, valuation, and tagging
ReMatter	official dispatch page	https://www.rematter.com/rematter-dispatch	dispatch, bin, driver, and photo workflow
ReSpark	company-issued release	https://www.businesswire.com/news/home/20260413780377/en/GreenSpark-and-ReMatter-Combine-to-Form-ReSpark-the-First-AI-Native-Operating-System-for-the-Recycling-Industry	April 2026 combination
Scaleit	official product site	https://scaleitusa.com/	scale, inventory, compliance, portal/API, and deployment options
Scaleit	official recycling page	https://scaleitusa.com/recycling-software-solutions/	specialist recycling/scale scope
Kaleris YMS	official product page	https://kaleris.com/solutions/yard-management/	gate, dock, asset, event, KPI, RTLS, and integration
Odoo	official documentation	https://www.odoo.com/documentation/19.0/applications/general/companies/multi_company.html	multi-company semantics
Odoo	official developer documentation	https://www.odoo.com/documentation/19.0/developer/reference/backend/module.html	module manifest/lifecycle
Odoo	official administration documentation	https://www.odoo.com/documentation/19.0/administration.html	deployment and upgrade discipline

12. Planning Handoff

P1-002 ends with research findings, not a future roadmap.

• No future Task ID, Phase ID, dependency, unlock, or status owner is assigned by this document.
• Structural findings may be consumed only by a later user-approved plan.
• Post-stability candidates remain inactive until a later explicit review and approval.
• The exact planning owner and sequence remain undecided here.

---

Source: docs/research/platform-foundation/2026-07-30/raw/benchmark/CTC-COMPETITOR-BENCHMARK.md — ctc repository · This page is an English translation of the source document. Identifiers, file paths and code symbols are unchanged.