Four questions before the change
A successful local upgrade does not answer whether the external receiving route remains usable. Build the test around the actual partner, order type and endpoint.
| Observation or task | Action and evidence |
|---|---|
| What is changing? | Name the exact proposed sender release and retain the before-change setup reference. |
| What does the receiver support? | Obtain release/route confirmation from the receiving administrator or manufacturer. |
| Which configuration governs transfer? | Ask whether target-version settings or a manufacturer-provided DME apply; do not assume all transfers use them. |
| What proves readiness? | Agree a non-production test that reaches receiving import/review and the intended output checkpoint. |
What the official compatibility article covers
3Shape describes manufacturer-inbox compatibility mechanisms, a selectable manufacturer target version and manufacturer-specific DME settings. It also describes exceptions requiring manufacturer validation. These are scoped mechanisms, not a promise that every file export can be opened in any older release.
Source limitation requiring provider validation: the article is dated June 2024 but contains 2025 release examples and a current-plus-two-previous-version description. Do not translate that wording into a current 2026 range or copy its named manufacturer's version limit into a purchase decision.
Worked receiving-test example
Hypothetical lab A proposes sender release S-new while lab B retains receiver R-old. The provider identifies a supported order route and configuration for that pair. A permitted test is received, opened, checked against the brief and advanced to the agreed output checkpoint. Record each observation separately.
If the inbox receives the order but review cannot proceed, readiness is incomplete. Keep the failed checkpoint visible instead of reporting the upgrade compatible because transfer succeeded.
A bounded adoption decision
The responsible administrator manages backup, recovery and upgrade procedure under the provider's instructions; this guide is not an installer or rollback recipe. The workflow owner decides adoption using provider confirmation and the recorded receiving test.
Next step: send the worksheet's unresolved version/route question to the provider. If a live transfer already fails with the exact unsupported-version warning, use the separate diagnostic guide; do not downgrade or rewrite an order solely from this planning article.
Validation and limits
Louie validation pending — unverified locally. Louie and the receiving provider must confirm current sender/receiver release support, target-version settings or manufacturer DME applicability, any manufacturer validation delay and a representative receiving test. The article's 2025 examples and rolling window are not asserted as October 2026 support coverage.
Use internal references in the blank worksheet. Examples are hypothetical; applicable instructions and responsible approvals govern real work.
Source notes
Official sources checked October 6, 2026. Scope and dates below; installed applicability remains unverified. Worked examples and worksheets are original.
Prepared by Pristine Dental Design · October 6, 2026.