COMPATIBILITY

Compatibility is verified before release.

Every extension will publish an explicit OpenCart, PHP and dependency matrix after standalone validation. No inferred version ranges and no silent dependencies.

Abstract compatibility verification illustration

EXTENSION COMPATIBILITY

Current validation status.

Version cells remain intentionally unresolved until clean-install testing is complete.

ExtensionOpenCartPHPDependenciesStatus

Payment RecoveryPayment failure and recovery workflow tooling.Testing pendingTesting pendingDependency audit in progressIn validation

Shipment TrackingTracking-driven order workflow automation.Testing pendingTesting pendingCanada Post scope under validationIn validation

Store OperationsFuture operational utilities.Not definedNot definedNot definedPlanned

TESTING POLICY

Four gates before a compatibility claim.

Clean environment

Install on a clean OpenCart environment without the production store's theme or unrelated extensions.

Version matrix

Exercise the extension against explicitly selected OpenCart and PHP combinations.

Lifecycle checks

Test install, configuration, upgrade and uninstall behavior, including generated files and database changes.

Documentation match

Verify that published requirements and instructions match the tested build.

FAQ

Compatibility questions.

Why not publish likely versions now?

Because syntax compatibility is not the same as operational compatibility. Fencair will publish ranges after clean-install tests.

What if another extension is required?

Any required dependency will be listed explicitly. The goal is to remove private or store-specific dependencies before release.

What if my setup is not listed?

An unlisted combination should be treated as unverified, not assumed compatible.