Competitor Benchmark And Product Gap Refresh¶
- Classification:
RESEARCH-INPUT / P1-003 USER-APPROVED DECISION INPUT - Authority: vendor findings remain research; the approved C1~C7 decisions are integrated into canonical Product/Design/Roadmap owners
- Task:
P1-003 - Artifact owner: retained P1-003 research and decision provenance
- Audience: user, Product/Architecture reviewers, commercial planning and AI agents
- Reviewed CTC source snapshot:
origin/qa@6614c9fd9a79ac4a976c1a86f77fb2eb4fe1b7dc, Reset Revision 25 - Observation date:
2026-07-30 - Sources: official vendor/company documentation only
- Environment: Cloud public-source review plus current repository source review; no vendor tenant or CTC Runtime access
- Downstream consumers: canonical Product/Design owners, P1-002, P2, P4 through P10 and Roadmap review
- Runtime/DB/provider/service/Production mutation: none
- Retention/removal: retain official-source citations and C1~C7 decision provenance until canonical Product/Design/Roadmap owners absorb all useful detail; remove only after downstream consumers no longer cite this record
1. Evidence boundary¶
| Class | Meaning |
|---|---|
OFFICIAL-PUBLIC |
official vendor claim; not independent quality, security, certification or outcome proof |
CTC-CURRENT |
verified current source/architecture fact |
CTC-TARGET |
approved Product/System target; not implementation proof |
UNKNOWN |
not established by reviewed evidence |
Decision labels are planning classifications, not implementation authorization.
ADOPT_NOW means structural Product/System/contract input only.
AFTER_STABILITY means every common Stability Gate criterion is met and the
user then activates the applicable P10 work. The other labels are RESEARCH,
DEFER and REJECT.
The English Odoo 19 multi-company application page was not directly retrievable during this review. Its claim was cross-checked against current official Odoo 19 localized application documentation and the official multi-company developer guide; no vendor tenant was inspected.
2. CTC comparison baseline¶
CTC-CURRENT¶
- PHP/Apache/MySQL with server-rendered pages, shared JavaScript and API v2.
- active YMS/TMS/WMS/OMS/BMS surfaces and legacy
CLIENT_ID/getClientId()compatibility; - dedicated environments exist, but Shared SaaS isolation, reusable Product completeness, process acceptance and repeatable onboarding remain unproven.
CTC-TARGET¶
- profile-based lightweight Operations ERP for small US recycling yards and logistics operators;
- CTC execution-first, MK order-first, then no-fork third-yard validation;
- one codebase/migration line, explicit tenant/profile/module/capability/config, governed adapters, unit/scale provenance, evidence/recovery and SaaS/Dedicated parity.
UNKNOWN¶
- actual Shared SaaS isolation and MK/third-yard acceptance;
- repeatable onboarding, upgrade, support and SLA;
- certified jurisdiction/device coverage;
- broad portal/mobile/multi-site/trading and autonomous-AI reliability.
3. Official-source findings¶
| Vendor | Official public claim summary | Planning classification | Unknown/rejected boundary |
|---|---|---|---|
| AMCS Metal / Brady | end-to-end metal-recycling purchase/sales/yard/freight/settlement/scale/inventory/trading/finance and multi-company/depot positioning | ADOPT_NOW: authoritative end-to-end state and commercial/physical traceability; AFTER_STABILITY: enterprise finance/compliance/portal/multi-site |
tenant/deployment/security/recovery/pricing unknown; full-suite clone REJECT |
| cieTrade | contract/spot/formula pricing, scale, multiple inventory models, landed cost/COGS, dispatch/export/brokerage, portal/accounting sync | ADOPT_NOW: inventory identity/valuation/provenance and pricing/scale seams; AFTER_STABILITY: portal/mobile/brokerage/multi-currency |
first CTC/MK valuation model requires research; tenant/offline/recovery unknown |
| Scrap Dragon | cloud/on-prem, scale/photo/audit, compliance/payment/inventory/trucking/accounting/multi-location | ADOPT_NOW: generic provider/hardware adapter, accounting-handoff and deployment boundary; AFTER_STABILITY: payment/device/provider implementation, expanded accounting connectors and compliance catalogue |
certification, cloud/local parity, tenant/upgrade unknown |
| ScrapRight | ticketing/compliance, inventory/margin, multi-site/mobile/accounting/dispatch plus current Basic/Essentials/Ultimate packages and onboarding/support | ADOPT_NOW: entitlement/onboarding/support package structure; AFTER_STABILITY: compliance/payment/mobile/hardware |
package names/pricing are not copied; legal coverage/device/support/security unknown |
| ReSpark | combined GreenSpark/ReMatter company positioning across yard/logistics/finance/maintenance/AI and integrations | ADOPT_NOW: shared dataset/provenance/integration/profile/onboarding and human-reviewed AI boundary; AFTER_STABILITY: portal/mobile/equipment/AI assist |
official FAQ says existing products remain while combined platform rolls out; native connected GL is roadmap; autonomous authority bypass REJECT |
| Scaleit | Scaleit One plus iW8 cloud/API, mW8 unattended/mobile/contactless and cW8 multi-site dedicated-server product families | ADOPT_NOW: scale adapter/capability/package/deployment/provenance/diagnostics; AFTER_STABILITY: unattended/payment/portal/device catalogue |
certification/security/recovery/device parity unknown |
| Kaleris YMS | kiosk/check-in, gate/dock/asset/appointment, RTLS, KPI/event/API, tasks and WMS/TMS/ERP integration | ADOPT_NOW: event/state/exception/KPI/integration patterns; AFTER_STABILITY: RTLS/IoT/predictive/gate/multi-site |
cost/tenant/recovery/recycling-commercial depth unknown; enterprise-YMS clone REJECT |
| Odoo 19 | one-database multi-company context, shared/company-specific records, module manifests, security, testing and upgrade discipline | ADOPT_NOW: explicit company context, shared-vs-tenant records and module lifecycle; RESEARCH: commercial package economics |
recycling fit unknown; general ERP/full-accounting/app-store clone REJECT |
| 21CP ROM | recycling-specific purchase-to-processing/inventory/sales, barcode/lot/QC, cloud/local, multi-facility/mobile/customer access and support | ADOPT_NOW: lot/provenance and QC extension boundary plus deployment/onboarding/training structure; AFTER_STABILITY / RESEARCH: QC feature, mobile/portal/accounting/compliance |
cloud/local parity, tenant/security/recovery/pricing unknown; customer-specific source model REJECT |
| ScrapWare | purchases/contracts/sales/inventory/dispatch/container/ledger interface, anti-theft, customization, cloud and training | ADOPT_NOW: module/ledger-adapter/onboarding boundaries; AFTER_STABILITY: anti-theft/payment/mobile/dispatch |
whether customization is upgrade-safe config is unknown; tenant-specific bespoke source REJECT |
Additional official context:
- AMCS waste and recycling
- Scrap Dragon about
- ReSpark integrations
- Odoo module manifests
- Odoo administration
- ScrapWare training
4. Cross-vendor decision matrix¶
| Theme | Classification | CTC meaning |
|---|---|---|
| explicit tenant/profile/module/capability/entitlement | ADOPT_NOW |
Product/System contract input; not implementation completion |
| authoritative process state, exception, retry, recovery and provenance | ADOPT_NOW |
shared business authority before automation |
| inventory identity/valuation/unit and scale/hardware adapter | ADOPT_NOW |
explicit model and adapter boundary; exact first model/device requires discovery |
| package/onboarding/support/upgrade discipline | ADOPT_NOW |
define repeatable product boundary without copying competitor tiers |
| jurisdiction compliance and payments | AFTER_STABILITY / RESEARCH |
validate legal/device/customer need before promise |
| portal/mobile/multi-site/RTLS/IoT | AFTER_STABILITY |
conditional package after core/MK proof |
| advanced finance/trading/multi-currency | DEFER |
adapter-first accounting before full GL |
| assistive AI | AFTER_STABILITY / RESEARCH |
governed evidence, human approval and reversible effects |
| customer source fork/numeric client branch | REJECT |
violates one-product-line direction |
| full competitor/general-ERP clone | REJECT |
unjustified scope and maintenance burden |
| autonomous AI business authority | REJECT |
bypasses tenant/process/mutation/provider controls |
5. Commercial decision package¶
| ID / decision | Options and impact | Recommendation |
|---|---|---|
C1 — first commercial vertical |
A: US metal/scrap recycling + logistics first; B: support every recycling vertical equally from the start | A; B expands scope before repeatability; general ERP remains REJECT |
C2 — accounting scope |
A: operational billing + accounting adapters; B: full native accounting/GL now | A; multi-currency remains a separate deferred feature |
C3 — compliance timing |
A: post-stability optional package after jurisdiction proof; B: early generalized compliance promise | A; B creates legal/product risk |
C4 — SaaS data topology |
A: preserve one-codebase/shared-vs-dedicated invariant and leave exact topology OPEN until P4-001~005 evidence; B: precommit shared-DB row isolation now; C: precommit tenant schema/DB isolation now |
A; no topology is inferred from vendors |
C5 — hardware priority |
A: scale/device adapter contract, then evidence-selected devices; B: broad certified catalogue now | A |
C6 — Reset #6a package/entitlement |
A: define capability/package semantics without names/prices; B: copy competitor tiers | A |
C7 — Reset #6b support/SLA |
A: retain managed-service baseline and leave pricing/SLA open; B: promise tiers before evidence | A |
User approval recorded on 2026-07-30:
P1-003 C1 through C7 all approved as A — the exact SaaS data topology and the pricing/SLA remain OPEN
6. Phase linkage¶
| Finding | Downstream owner |
|---|---|
| Product scope and commercial model | docs/PRODUCT.md, P1-003 review and P9-004 |
| Scale/unit/inventory/order/billing/reconciliation | P2-002, P2-004~006 and required P4 foundation |
| MK profile/module/capability/config | P2-003 and P4-002/P4-003 |
| tenant/data classification, identity/context, resolver and query/write boundary | docs/DESIGN.md and P4-001~004 |
| SaaS/Dedicated topology and parity | P4-005/P4-006 |
| package/entitlement structural seam | P4-003 and P5-002 |
| release/backup/restore parity | P9-006 and common Stability Gate evidence |
| module/repository and hardware-adapter contract boundaries | P1-002, P5 and P5-004 |
| process/state/recovery and governed AI boundary | P6 and P6-006 |
| performance/KPI | P6-003 and P9-001~003 |
| UI/portal/mobile/React-ready separation | P7, conditional P10/P12 |
| manuals/onboarding/support knowledge | P8/P9 |
| compliance/payment/advanced trading features | conditional P10 |
| assistive/agentic feature | P10-005 after Stability Gate and user activation |
| certified device catalogue/RTLS/device package | P10-004 after Stability Gate and user activation |
7. Verification and limitations¶
| Check | Result |
|---|---|
reviewed origin/qa@6614c9fd9 snapshot, Reset, P1-003 and canonical Product/Design/current Architecture |
PASS for the dated review |
repository drift through origin/qa@cd26f23f4 |
PASS / SOURCE-ONLY; ca34ce649 changes booking/scale Runtime and tests but no Product/Design/commercial owner, so C1~C7 scope is unchanged; P2 current-state work must review the new Runtime behavior separately |
| required vendors plus two direct competitors reviewed from official sources | PASS |
| vendor claim vs CTC current/target/unknown separation | PASS |
| Runtime/DB/browser/provider/deployment verification | NOT_APPLICABLE |
| vendor security, financial, legal, implementation-quality diligence | NOT_RUN |
Vendor findings remain research. The user approved C1~C7, but no competitor feature, vendor, package name, price, SLA, topology or downstream Task was automatically approved.
Source:
docs/research/platform-foundation/2026-07-30/competitor-benchmark-gap-refresh.md— ctc repository · This page is an English translation of the source document. Identifiers, file paths and code symbols are unchanged. A user instruction quoted inside the text is kept in its original language.