---
title: "Spatial Compiler for 3D product configurators: web-weight GLBs and LODs"
description: "Compile CAD and DCC product models into web-weight GLBs for 3D product configurators, with exact triangle budgets per LOD, packed UVs and baked ORM materials. Unchanged SKUs are 0-credit cache hits."
canonical: https://appliedmanifold.com/use-cases/ecommerce-configurators/
site: "Applied Manifold: The spatial compute cloud for 3D reality."
---

1.  [Home](https://appliedmanifold.com/)
2.  [Use cases](https://appliedmanifold.com/use-cases/)
3.  E-commerce configurators

USE CASE // E-COMMERCE 3D · AR

# Web-weight 3D for every SKU in the catalog.

Compile heavy CAD and DCC product models into web-weight GLBs with LODs and baked materials for your 3D product configurator. Each SKU is one API call, and your pipeline reruns it automatically whenever the catalog changes.

Get Free API Key [Read the docs →](https://appliedmanifold.com/docs/)

From $0.05 per asset, as low as $0.02 on Studio. Sandbox includes 500 free credits.

**PIPELINE // PRODUCT 3D PER SKU**

1.  IN sku\_4471\_armchair.glb CAD / DCC export
2.  [weld](https://appliedmanifold.com/docs/#op-weld) clean CAD seams
3.  [lod\_chain](https://appliedmanifold.com/docs/#op-lod-chain) 60k · 20k · 5k tris
4.  [uv\_pack](https://appliedmanifold.com/docs/#op-uv-pack) one atlas
5.  [orm\_bake](https://appliedmanifold.com/docs/#op-orm-bake) one packed texture
6.  OUT web .glb × 3 LODs \+ telemetry.json

Stages of one compile\_3d\_asset call (illustrative).

01 // PAIN → FIX

## Why product 3D is heavy to ship

A configurator loads at the speed of its heaviest model, and the catalog keeps changing.

1.  PAIN

    Product models arrive as CAD or DCC exports with millions of triangles, far too heavy for a mobile product page.

    FIX

    `decimate` to an exact `target_tris` per LOD. Telemetry reports triangles and VRAM so your pipeline enforces the page-weight budget before publishing.

2.  PAIN

    Every colorway, material and variant multiplies the files someone has to optimize by hand.

    FIX

    Each SKU is one API call from your catalog pipeline. Unchanged models are SHA-256 cache hits and cost 0 credits when the pipeline reruns.

3.  PAIN

    PBR materials ship as a pile of separate textures, adding requests and weight to every product view.

    FIX

    `uv_pack` lays out one clean atlas and `orm_bake` packs occlusion, roughness and metallic into a single texture.

02 // OPERATIONS

## Operations for product configurators

These operations cover everything between a CAD export and a model that loads quickly on a phone.

-   ### [lod\_chain](https://appliedmanifold.com/docs/#op-lod-chain) compile\_3d\_asset

    Decimates the same product to several triangle budgets, so the viewer can load the light one first.

-   ### [decimate](https://appliedmanifold.com/docs/#op-decimate) meshoptimizer

    Sets an exact `target_tris` per LOD, so the triangle budget behind your page weight is a number you choose.

-   ### [weld](https://appliedmanifold.com/docs/#op-weld) compile\_3d\_asset

    Repairs the open seams and non-manifold edges CAD tessellation leaves behind.

-   ### [uv\_pack](https://appliedmanifold.com/docs/#op-uv-pack) xatlas

    Lays out one non-overlapping atlas per product, ready for baked materials.

-   ### [orm\_bake](https://appliedmanifold.com/docs/#op-orm-bake) compile\_3d\_asset

    Packs occlusion, roughness and metallic into one texture, so each product view makes fewer requests.

-   ### [cache + dry\_run](https://appliedmanifold.com/docs/#controls) 0 credits

    Unchanged SKUs are free cache hits; dry runs estimate a full catalog rebuild before you start it.

03 // EXAMPLE ILLUSTRATIVE

## One SKU, three LODs

Your catalog pipeline sends a changed product over REST and checks every LOD against the page budget before it goes live.

terminal · REST · illustrative

```sh
curl -X POST https://api.spatialcompiler.dev/v1/compile \
  -H "Authorization: Bearer sk_test_spatial_sandbox" \
  -F "file=@sku_4471_armchair.glb" \
  -F 'options={"lods":[60000,20000,5000],"bake":"orm","format":"glb","dry_run":false}'
```

telemetry.json · illustrative

```json
{
  "status": "ok",
  "tris_in": 1840000,
  "lods": [
    { "target_tris": 60000, "tris_out": 60000 },
    { "target_tris": 20000, "tris_out": 20000 },
    { "target_tris": 5000, "tris_out": 5000 }
  ],
  "textures": ["orm (packed)"],
  "cache": "MISS"
}
```

Illustrative output. Not measured.

Numbers in the request are inputs and targets you choose.

04 // FAQ

## E-commerce 3D questions

[All questions →](https://appliedmanifold.com/faq/)

**README.CATALOG**

### Which format does it export for the web?

The output is .glb (glTF binary), which browser 3D viewers and configurators load directly.

### Can we enforce a page-weight budget per product?

Yes. Set a `target_tris` budget for each LOD. Your catalog pipeline then checks the returned telemetry (triangle counts, draw calls, VRAM footprint) before it publishes a model.

### What happens when only a few SKUs change?

Only the changed models cost credits. Unchanged models with unchanged options are SHA-256 cache hits at 0 credits. Before a full catalog rebuild, `dry_run: true` estimates its cost.

### What does it cost per SKU?

A SKU costs from $0.05 pay-as-you-go (a standard compile is 5 credits) and as little as about $0.02 on Studio. Sandbox includes 500 free credits.

## Put your catalog on a page-weight budget.

From $0.05 per asset, as low as $0.02 on Studio. Signup includes 500 free sandbox credits (~100 compiles), and cache hits and dry runs cost 0 credits.

Get Free API Key [Read the docs →](https://appliedmanifold.com/docs/) [Pricing →](https://appliedmanifold.com/pricing/)

[All use cases →](https://appliedmanifold.com/use-cases/)
