Standalone links & catalogs

Share your 3D product experience directly.

Maintain products and configurations in II3D without an online store. The initial release plans standalone URLs for all five capabilities and optional catalog templates for product manuals, supporting customer browsing, sales presentations and partner sharing. Standalone entries provide display and interaction without checkout.

  • In initial-release development
  • No storefront required
  • Display & interaction

CONNECTION MAP

  1. 01

    Products & configuration

    Models, materials, options and explanations

  2. 02

    One published version

    Frozen configuration and asset versions

  3. 03

    Standalone page or catalog

    Browsing, interaction and sharing

In initial-release development

Display and interaction without checkout

01 · CONTEXT

Start with your integration needs.

Identify the problems to solve around your existing pages, product information and workflows.

Scattered sharing entries

Sales teams repeatedly send images and videos, leaving customers without one entry for the product and configuration.

Product information is hard to browse

Products are spread across files, so customers repeatedly search for the right manual or instructions.

Repeated maintenance across channels

Websites, storefronts and sales presentations maintain separate content and can drift to different product versions.

02 · CAPABILITIES

Prepare the essentials for this connection.

Confirm standard publishing and additional business integration separately. Availability follows development, testing and project acceptance.

Standalone product URL

Provide a configurator, modular experience, manual, swatches or assembly guide to customers through one link.

Product-manual catalog

Choose an optional manual catalog template so customers can enter product explanations from one browsing entry.

Maintain products independently

Manage product information in II3D; a standalone link does not require a Shopify connection.

Share content across channels

Share configuration, published versions and runtime while each channel handles its own entry and business actions.

03 · USE CASES

Start with a concrete use case.

These examples show how products and workflows connect, helping you choose the right entry.

Sales presentations

Send a product link and explain appearance, materials, parts and dimensions.

Dealer product catalogs

Browse products in a manual catalog, then open an immersive explanation for each item.

Use and assembly instructions

Share an assembly-guide link for step-by-step installation, disassembly and use instructions.

04 · SETUP

Move from setup to integration in four steps.

Prepare source material, confirm content, validate the entry and deliver the agreed scope.

  1. 01

    Prepare product information

    Prepare products, models, materials, options or animations and select the capability.

  2. 02

    Configure and preview

    Configure selections, explanations or steps and review the customer experience.

  3. 03

    Choose the publishing entry

    Publish a product URL; optionally choose a catalog template for product manuals.

  4. 04

    Share and maintain versions

    Share the entry, manage updates through published versions and review customer access.

05 · FAQ

Common questions

Understand the preparation and usage boundaries before you begin.

Do I need a Shopify store first?

No. Products can be managed in II3D for standalone use. Standalone links and website embedding are both in the initial scope.

Can all five capabilities use standalone links?

The initial scope includes standalone display and interaction for all five capabilities. Availability follows publishing and validation. Catalog templates are an optional entry for product manuals.

Can customers place orders from a standalone link?

Standalone URLs have no checkout. Choose storefront integration for purchases; inquiries or other workflow handoffs can be assessed separately.

Will the content match the storefront experience?

The same configuration and published version share the runtime, with core display and interaction checked on equivalent devices. Page containers, purchases and platform-specific AR limits are handled separately.

Find the right connection for your platform and products.

Share your platform, product type, capabilities and page placement to discuss preparation and integration scope.