Confirm the recipient can perform the requested action
A design team sends a 3D carton and asks a supplier to approve it in WebCenter. The supplier can see a screenshot but cannot find the promised 3D approval path. A file exists, yet the chosen sign-off workflow may not be available. Verify recipient readiness before treating missing controls as a defective carton design.
Esko's WebCenter 26.03 quick-start documentation places 3D-file upload, viewing and approval within the optional Advanced Approval module. That establishes a product capability and dependency, not proof that a specific organization has enabled it or that a particular recipient can approve the job.
Agree the approval scope and route
| Question | Evidence to obtain | Hold condition |
|---|---|---|
| Is the module available? | Confirmation from the actual WebCenter owner | Optional capability assumed from the product name |
| Can the recipient access the job? | Actual authorized recipient path | A screenshot is the only accessible object |
| What is being approved? | Named artwork and structural revision, with exclusions | “Looks good” interpreted as manufacturing release |
| What if 3D approval is unavailable? | Agreed alternative review route | Informal substitute silently counted as the intended approval |
Use an explicit fallback for a fictional carton
Suppose CARTON-R7 needs appearance review of panel placement and a folded shape. The supplier's actual environment has not been confirmed. The project owner should first establish whether the required module and recipient workflow exist. If not, agree an alternative such as controlled 2D artwork review plus a separately scoped structural review. Do not describe the fallback as a completed WebCenter 3D approval.
Record what the alternative can demonstrate. Flat artwork can show panel copy; a screenshot shows one representation; a physical sample can answer different assembly questions. None automatically supplies every other form of evidence. No file was uploaded or supplier review conducted for this example.
Keep visual acceptance distinct from production authority
The supplier-brief handoff guide identifies what a concept package must communicate. The sample approval guide records what a physical sample review covers. This decision concerns the availability of the named digital approval route, before either broader handoff is declared complete.
A browser-based 3D representation does not establish transit protection, food-contact suitability, die accuracy or print reproduction. Assign those questions to the real responsible parties and keep unresolved items open. A named approval module is a workflow tool, not a replacement for the agreed evidence.
Close with a reproducible review record
Retain the actual job, model and artwork revisions, recipient, available review route and scope of the resulting decision. If the receiving environment changes, recheck access rather than reusing an old successful screenshot as current evidence. CartVisual packaging concepts do not enable Esko modules or issue manufacturing approvals.