NCM API

NCM API compatibility with REEID Translate

NCM API compatibility with REEID Translate is being evaluated from available plugin evidence. Create Nepal Can Move delivery orders from WooCommerce orders No specific visitor-facing translation surface is currently confirmed.

Visit NCM API ↗

AWAITING VERIFICATION

What the available evidence establishes for NCM API.

Official documentation did not establish a visitor-facing content item within the supported scope for this category.

AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.

PLUGIN PROFILE
NCM API is documented in the WooCommerce category with 6 concrete capabilities identified in the current evidence.

EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.

COMPATIBILITY REVIEW

How NCM API compatibility is evaluated

01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.

02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.

03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.

04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.

PLUGIN INTELLIGENCE

What the official plugin evidence shows

Plugin capabilities

  • Create Nepal Can Move delivery orders from WooCommerce orders
  • Sync NCM order details back into WordPress
  • Store NCM status updates for reference only
  • Manage NCM comments and tickets in WordPress
  • Register and test webhooks for delivery status updates
  • Provide a one-time migration for existing NCM API installs using legacy token and order-link meta keys

CONTENT BOUNDARY

NCM API capabilities and translation scope are documented separately.

The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.

Functional capability alone is not treated as evidence that a value should be translated.

LIMITATIONS & QA

Verification notes

  • No visitor-facing translation surface was established for this integration.

COMMON QUESTIONS

NCM API and REEID Translate FAQ.

What does NCM API do according to the available plugin evidence?

NCM API has 6 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.

Is a REEID translation surface currently confirmed for NCM API?

No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.

What would establish translation scope for NCM API?

The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.

RELATED GUIDES

Continue through the compatibility library.

INTEGRATION EVIDENCE

Evaluate NCM API in a multilingual WordPress workflow.

REEID documents NCM API functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.

Translation scope will be published when concrete visitor-facing content is established by evidence.

Shopping Cart
Scroll to Top